Winamp 5.9.1 Released

[damien147]

Hello!

I unistalled the older version and did a clean install of this version.Everything is fine except wasapi output where I can't choose it.

I saw wasapi installed on plug ins-->output and I double-click,right-click or click configure and nothing happens.No wasapi tray icon either.Any ideas what to do to make wasapi work?

[DJ Egg]

Hello!

I unistalled the older version and did a clean install of this version.Everything is fine except wasapi output where I can't choose it.

I saw wasapi installed on plug ins-->output and I double-click,right-click or click configure and nothing happens.No wasapi tray icon either.Any ideas what to do to make wasapi work?

It's a very basic Wasapi Output plugin, and still unfinished.
No config, no tray icon.
The selected (highlighted) Output Plugin becomes the active one.
So if Wasapi Output is selected and you hear music, then that means it's working...

[damien147]

Oh!It's working then.Thank you very much.

[jvidal]

ok, tell me where to drop a few files and i'll do it.

or, you can send me an e-mail address in a private message and I can send them to you via wetransfer, for example.

[peter2008]

Hi! Thanks for the great job. But I still have same problem with https audio streaming URLs. I can't play them when I open Winamp. But if I stop, wait, and try it later, it works fine from that moment. It's always first minute just after opening Winamp and try it first. We discussed about it on previous release, but still happening and it's a pity, because I use it mostly for audio streaming URLs...

[mountainmaster]

Each time I install a new Winamp version it removes its file associations. Next time I play an audio file Windows goes back to that crappy Groove music player.

So I have to restore Winamp as my default music player, which is not as straightforward as it seems in Windows. These are the steps I have to follow (Windows 10).

1. Install new version of Winamp (duh)

2. Restore Winamp as the Windows default music player
- Open Settings - Apps - Default Apps - Music Player
- Choose Winamp from the list. If Winamp is not in the list of known players, associate an audio file type (wav, mp3 or whatever) to Winamp manually in File Explorer using the "open with" dialog.

3. Restore the file context menu (not to be confused with the folder context menu which works fine)
- Open Settings - Apps - Default Apps - Choose default apps by file type
- For each file type that should have the context menu pick Winamp from the list. Even though Winamp is already selected it must be selected again to make this work!

Having to go through all of this is very annoying. Is this the intended installer behavior? And is it possible to have an installer that preserves file associations?

[matan2001]

Hello again,
After having no luck trying to get Winamp back and running without a full uninstall, I removed the program and reinstalled it.
Even after the reinstall Winamp crashed after startup, so I decided to remove the leftover Winamp folder contents that stay after the uninstallation.

The folder's contents after an uninstall were as follows:
* A "vis_classic" folder and the requisite files in the Plugin folder
* 8 Language packs
* A cPro2__Aluminum skin
* 2 ClassicPro related files in the System Folder (ClassicPro.wbm, ClassicPro.w5s)

After reinstalling Winamp once more it finally booted up without crashing, so I wanted to test which of my previously installed plugins were causing the issue.
LyricsPlugin and Win7Shell both installed and worked perfectly, but installing ClassicPro made Winamp crash.

Even after an uninstall of ClassicPro, Winamp kept crashing, but deleting ClassicPro.wbm and ClassicPro.w5s in the System folder fixed the issue.

Is there something that can be done in later releases to fix the issue with the ClassicPro skins?
I have been using them for years now and it's a shame Winamp suddenly stopped working with them...

[DJ Egg]

Hello again,
After having no luck trying to get Winamp back and running without a full uninstall, I removed the program and reinstalled it.
Even after the reinstall Winamp crashed after startup, so I decided to remove the leftover Winamp folder contents that stay after the uninstallation.

The folder's contents after an uninstall were as follows:
* A "vis_classic" folder and the requisite files in the Plugin folder
* 8 Language packs
* A cPro2__Aluminum skin
* 2 ClassicPro related files in the System Folder (ClassicPro.wbm, ClassicPro.w5s)

After reinstalling Winamp once more it finally booted up without crashing, so I wanted to test which of my previously installed plugins were causing the issue.
LyricsPlugin and Win7Shell both installed and worked perfectly, but installing ClassicPro made Winamp crash.

Even after an uninstall of ClassicPro, Winamp kept crashing, but deleting ClassicPro.wbm and ClassicPro.w5s in the System folder fixed the issue.

Is there something that can be done in later releases to fix the issue with the ClassicPro skins?
I have been using them for years now and it's a shame Winamp suddenly stopped working with them...

Does it still crash if you only remove the ClassicPro.wbm file?

Note this ref in the 5.9.1 changelog:

* Removed: [wbm] Lazy-loading wbm system files (no longer required)

[jvidal]

Oh, and BTW, just a small FYI, I installed Winamp 5.91 on one of my laptop copmputers (running win10 x86) and I see the exact same problem with UNICODE chars...

[matan2001]

Does it still crash if you only remove the ClassicPro.wbm file?

Note this ref in the 5.9.1 changelog:

* Removed: [wbm] Lazy-loading wbm system files (no longer required)

With ClassicPro installed I removed the ClassicPro.wbm file - Winamp started successfully and I was even able to switch to the ClassicPro Bento skin. When trying to adjust things in the skin there were parts of the UI that blacked out, and after quitting the program and opening it back up with the ClassicPro skin, Winamp crashed once again.

I was able to open it back up and it worked but evidently the skin makes Winamp unstable -performing actions like pausing a song creates the same black spots in the upper toolbar, and trying to move the window makes Winamp crash completely.

[ancho85]

winamp opens and after a couple of second it crashes

Winamp 5.9.1 opens and after a couple of second it crashes. The reporter.exe also tries to send the error logs by opening an email client I don't have installed, it hangs for about 10 seconds and then nothing. I just installed this version over 5.9.0 which was working fine.

[DJ Egg]

Winamp 5.9.1 opens and after a couple of second it crashes. The reporter.exe also tries to send the error logs by opening an email client I don't have installed, it hangs for about 10 seconds and then nothing. I just installed this version over 5.9.0 which was working fine.

Like with matan2001's case above, is there also a ClassicPro.wbm file in your Winamp\System folder?

If yes, delete it.

Other than Winamp\System\ClassicPro.w5s, the only other non-default plugins present are:

Winamp\Plugins
- in_wav.dll
- in_wv.dll

[ancho85]

Like with matan2001's case above, is there also a ClassicPro.wbm file in your Winamp\System folder?

If yes, delete it.

Other than Winamp\System\ClassicPro.w5s, the only other non-default plugins present are:

Winamp\Plugins
- in_wav.dll
- in_wv.dll

Thank you DJ Egg, removing both ClassicPro.w5s and ClassicPro.wbm fixes the issue!

[matan2001]

Like with matan2001's case above, is there also a ClassicPro.wbm file in your Winamp\System folder?

If yes, delete it.

Other than Winamp\System\ClassicPro.w5s, the only other non-default plugins present are:

Winamp\Plugins
- in_wav.dll
- in_wv.dll

Hi there once again, I am sorry for incessantly posting on here but I can't seem to quite have Winamp 5.9.1 play nicely with ClassicPro.
First of all, removing ClassicPro.w5s did seem to make things move in the right direction as it helped Winamp to at least launch [sometimes] without crashing, but interacting with the UI elements (as I stated previously): doing things like switching tabs\to the visualisation, using the upper toolbar - makes Winamp crash, sometimes with the Error Reporter coming up and sometimes without.

In certain times, Winamp will crash within launch and sometimes it will crash whilst playing a song and interacting with the UI in some way.

Recently while trying once more, it launched a "Winamp Script Failure" error message within launch, but actually managed to play the selected song completely.

Trying to play another track didn't work, and trying to close it prompted a Windows crash window. After choosing "Close Winamp" Windows relaunched the program, and after a few seconds of the selected song Winamp crashed again...

[Ivan75]

2. Restore Winamp as the Windows default music player
- Open Settings - Apps - Default Apps - Music Player
- Choose Winamp from the list. If Winamp is not in the list of known players, associate an audio file type (wav, mp3 or whatever) to Winamp manually in File Explorer using the "open with" dialog.

3. Restore the file context menu (not to be confused with the folder context menu which works fine)
- Open Settings - Apps - Default Apps - Choose default apps by file type
- For each file type that should have the context menu pick Winamp from the list. Even though Winamp is already selected it must be selected again to make this work!

Having to go through all of this is very annoying. Is this the intended installer behavior? And is it possible to have an installer that preserves file associations?

I've been having this same problem for years now. Now it doesn't work at all. Opening the file context menu by right-clicking the file (mp3, FLAC or wav in my case), setting it in the file properties to be opened by another program then reverting it back to Winamp used to help. Now nothing seems to work, no ''enqueue in Winamp'', ''play with Winamp'' ...nothing, only ''Open''.

What should we do to fix this and prevent it from happening in the future?