Post All Winamp 5.666 Official Plugin Bug Reports In This Thread

[DJ Egg]

Report ALL Winamp 5.666 Plugin bugs in this thread ONLY.

ALL OTHER REPORTS WILL BE DELETED (YOU HAVE BEEN WARNED).

INCOMPLETE\LAME REPORTS (AKA: IMPOSSIBLE TO REPRODUCE) WILL BE IGNORED OR DELETED.


Here is a LIST of the Official Plugins and their Versions that shipped with 5.666

Input:
Nullsoft AVI Demuxer v0.75 [in_avi.dll]
Nullsoft CD Plug-in (MusicID 2.6) v4.02 [in_cdda.dll]
Nullsoft DirectShow Decoder v1.13 [in_dshow.dll]
Nullsoft FLAC Decoder v3.1 [in_flac.dll]
Nullsoft Flash Control Playback v1.15 [in_swf.dll]
Nullsoft Flash Video Decoder v1.45 (h) [in_flv.dll]
Nullsoft LineIn plugin v3.16 [in_linein.dll]
Nullsoft Matroska Demuxer v0.83 [in_mkv.dll]
Nullsoft MIDI Player v3.55 [in_midi.dll]
Nullsoft Module Decoder v2.94 [in_mod.dll]
Nullsoft MP4 Demuxer v2.65 [in_mp4.dll]
Nullsoft MPEG Audio Decoder v4.104 [in_mp3.dll] (patch available)
Nullsoft NSV Decoder v1.75 [in_nsv.dll]
Nullsoft Vorbis Decoder v1.76 [in_vorbis.dll]
Nullsoft Waveform Decoder v3.25 [in_wave.dll]
Nullsoft Windows Media Decoder v3.78 [in_wm.dll]

Output:
DirectSound Output v2.64 (d) [out_ds.dll]
Disk Writer v2.18 [out_disk.dll]
WaveOut Output v2.17 (d) [out_wave.dll]

Visualization:
Advanced Visualization Studio v2.82 [vis_avs.dll]
MilkDrop v2.25c [vis_milk2.dll]
Nullsoft Tiny Fullscreen v2.16 [vis_nsfs.dll]

DSP/FX:
Nullsoft Signal Processing Studio DSP v0.39b [dsp_sps.dll]

CD Ripping Encoders:
FLAC Encoder 2.43 (libFLAC 1.3.0) [enc_flac.dll]
MP3 Encoder v1.37 [enc_lame.dll] (with lame_enc.dll 3.99.5)
MPEG-4 AAC Encoder v1.08 [enc_fhgaac.dll]
Ogg Vorbis Encoder v1.54 (aoTuV b6.03)
SHOUTcast MPEG-2 ADTS-AAC Encoder v1.08 [enc_fhgaac.dll]
WAV Encoder v1.02a [enc_wav.dll]
WMA Encoder v1.23 [enc_wma.dll]

General Purpose:
Jump To File Extra v1.32 (Build 1215) [gen_jumpex.dll] (v1.33.1216 available)
Nullsoft Error Feedback v1.12 [gen_crasher.dll]
Nullsoft Global Hotkeys v1.97 [gen_hotkeys.dll]
Nullsoft Media Library v3.75 [gen_ml.dll]
Nullsoft Modern Skins Support v1.49 [gen_ff.dll]
Nullsoft Notification Area Control v2.45.1 [gen_tray.dll]

Media Library:
Nullsoft Auto-Tagger v2.08 [ml_autotag.dll]
Nullsoft Bookmarks v1.27 [ml_bookmarks.dll]
Nullsoft Database Import/Export v2.64 [ml_impex.dll]
Nullsoft Device Manager v1.34 [ml_devices.dll]
Nullsoft Downloads v1.31 [ml_downloads.dll]
Nullsoft Format Converter v2.76 [ml_transcode.dll]
Nullsoft History v2.03 [ml_history.dll]
Nullsoft Local Library v3.32 [ml_local.dll]
Nullsoft Now Playing v4.01 [ml_nowplaying.dll]
Nullsoft Online Services v2.01 [ml_online.dll]
Nullsoft Playlist Generator v1.81 [ml_plg.dll]
Nullsoft Playlists v1.71 [ml_playlists.dll]
Nullsoft Podcasts v1.52 [ml_wire.dll]
Nullsoft Portable Music Player Support v2.24 [ml_pmp.dll]
Nullsoft Replay Gain Analyzer v1.28 [ml_rg.dll]
Nullsoft Rip & Burn v1.99 [ml_disc.dll]

Portables:
Nullsoft Android Device Plug-in v1.71 [pmp_android.dll]
Nullsoft Creative NJB Plug-in v0.57 [pmp_njb.dll]
Nullsoft iPod Plug-in v0.89 [pmp_ipod.dll]
Nullsoft Microsoft PlaysForSure Plug-in v0.99.1 [pmp_p4s.dll]
Nullsoft USB Device Plug-in v1.61 [pmp_usb.dll]
Nullsoft Wi-Fi Device Plug-in v1.55 [pmp_wifi.dll]
Nullsoft ActiveSync Plug-in v0.20 [pmp_activesync.dll]

____________________________________________________________


Provide the following Information with every Report,
and with every CONFIRMATION of someone else's report:

Winamp 5.666 (5.6.6.3516) - clean install (with NO 3rd-party plugins)
Winamp Language Pack (if not using default English US)
Skin: eg. Bento, Winamp Modern, Winamp Classic (or all)
Windows OS, including Service Pack & Locale
System specs (mobo, cpu, ram)
Video Card, Video Card Drivers version
Sound Card, Sound Card Drivers version
DirectX version
Plugin (and version) affected by/causing the bug

A full, detailed, step-by-step method of reproduction

If applicable, also include Error Logs and/or FULL Error Messages.

The more information you provide US, the Faster we can or will help you.

To reproduce some bugs, we may also need a link to a zipped sample file
(eg. an .mp3, .aac, .wav, .mid file, etc, which exhibits the bug).
You can use zippyshare.com, wikisend.com, sendspace.com or mediafire.com for uploading, and then post the download link here. Note, if you have a Junior Member status, then submitted url's will only be visible to admins/mods.

If no-one responds, this does not mean that your report has been ignored. All posts are noted, even if no edit appears at the end of your post to say whether it has been reproduced or not.


Do NOT report ANY 3rd-party plugin bugs/issues here.
Report them to the author(s) instead and point them to the 5.55 SDK (more info)


Maintained by DJ Egg

[winamp_noob]

Hi.

There is a bug in Jump To File Extra v1.2.6 (Build 1165) [gen_jumpex.dll] plugin.

Here is how to re-produce it:

Install Lite version of Winamp 5.64 (latest version) without any additional plugins. (CLEAN install, also removed %APPDATA%\Winamp folder to ensure its not settings thing).

Set up Enqueue & Play as the default action for winamp so when you dbl click on the file it gets queued right after the currently playing file.

Also set up to scan tags in the background (Title->Read Metadata in the background when files are loaded or viewed ... ).

The bug is random and can occur randomly.

Sometimes it even occurs If after crash I try to play the same file by dbl clicking (so it should be just put into the queue).

I have crashdumps activated in the Windows 7 SP1, so here is a crashdump for Winamp:

http://www.mediafire.com/?p89u05t4h4r563b

Let me know if you need any more info.

Thanks.

Problem signature:
Problem Event Name: APPCRASH
Application Name: winamp.exe
Application Version: 5.6.4.3418
Application Timestamp: 51cb537f
Fault Module Name: gen_jumpex.dll
Fault Module Version: 1.2.6.1165
The time stamp module with the error: 51bb4aad
Exception Code: c0000005
Exception Offset: 0000332b
OS Version: 6.1.7601.2.1.0.256.1
Language Code: 1049
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

[DrO]

i've loaded the dump file but i'm struggling to get it to load the debug files i've got for that version of the gen_jumpex.dll so may need to give you a specific version to try out. will follow-up based on what i can sort out with the debug files or get you to try out a specific version.

[winamp_noob]

Thanks, DrO.

Waiting patiently for your results!

Big up.

[winamp_noob]

hey, DrO!

been awhile.. any results?

[Aminifu]

Hi winamp_noob,

Have you tried version 1.2.7 of gen_jumpex.dll in the latest stable and beta versions of Winamp?

[winamp_noob]

Originally Posted by Aminifu

Hi winamp_noob,

Have you tried version 1.2.7 of gen_jumpex.dll in the latest stable and beta versions of Winamp?

thanks, installed 5.65, will report back if it occurs again..

[DrO]

sorry I thought I'd replied to this, the build aminifu mentions will give me a more usable crash dump if the issue happens again (the prior build had it enabled but not in the way needed to make the crash dump usable).

[winamp_noob]

hi, just tried latest winamp 5.65.

crashlog is here: http://www.mediafire.com/?u6ozbclb9eo5gz6

[Morc]

Hi,

I have an annoying problem with Nullsoft Notification Area Control v2.44 [gen_tray.dll]. It's been going on at least since Winamp version 5.63, probably even further back. I have a few MP3 streams in my playlist and if I use the plugin back button to go from one stream to the previous Winamp hangs. If I use the back button on the application it works fine. If I try to go to a stream that refuses connection Winamp goes back to the stream that was played no problem. Next button works fine. The only non-standard plugins I have are SRS WOW! DSP (yes, very old, but still works well) and VQF input plugin version 0.91.

Oh, I read through both http://forums.winamp.com/showthread.php?threadid=161361 and http://forums.winamp.com/showthread.php?threadid=156839, but did not try a clean install.

[Pathfinder]

To replicate the crash, just play the MTM file. Crash reported as [in_mod.dll]

Winamp Modern skin, VISTA 32 bit AU
Video: NVIDIA Geforce 8600
Sound card: REALTEK ALC889c
Winamp modern skin

MTM file (KLF-FASC.MTM) together with crashreport uploaded to:
http://wikisend.com/download/363144/..._mtm_fault.zip
http://www.sendspace.com/file/ue2l11

Greets from Charles

[MrSinatra]

Originally Posted by Morc

Oh, I read through both http://forums.winamp.com/showthread.php?threadid=161361 and http://forums.winamp.com/showthread.php?threadid=156839, but did not try a clean install.

Morc, what ver are you currently using? try removing the plugins and/or running winamp in "safe mode" and see if the problem persists.

[Morc]

Originally Posted by MrSinatra

Morc, what ver are you currently using? try removing the plugins and/or running winamp in "safe mode" and see if the problem persists.

Hi MrSinatra, as I wrote I did this with 5.63. Now I'm on 5.65, I removed all except these plugins: gen_ff.dll, gen_tray.dll, in_dshow.dll, in_mp3.dll, out_ds.dll and read_file.dll and reproduced the problem. I tried safe mode as well, same thing. I'm using the Modern Skin skin.

[DrO]

Originally Posted by Morc

I have an annoying problem with Nullsoft Notification Area Control v2.44 [gen_tray.dll]. It's been going on at least since Winamp version 5.63, probably even further back. I have a few MP3 streams in my playlist and if I use the plugin back button to go from one stream to the previous Winamp hangs. If I use the back button on the application it works fine. If I try to go to a stream that refuses connection Winamp goes back to the stream that was played no problem. Next button works fine.

is purely a bug in gen_tray.dll due to it effectively double-pumping the play message which causes the lock-up (just shows how often people use it since it's been doing that since ~2007/8 when i last did it's main update).

check your pm please for a test build to try out in-conjunction with the current v5.65 release..

[Morc]

Originally Posted by DrO

is purely a bug in gen_tray.dll due to it effectively double-pumping the play message which causes the lock-up (just shows how often people use it since it's been doing that since ~2007/8 when i last did it's main update).

check your pm please for a test build to try out in-conjunction with the current v5.65 release..

Thanks, works fine. I don't know why people don't use it, but again it may be used very much, just not to switch between streams, and there it worked fine.

[DrO]

Originally Posted by Pathfinder

To replicate the crash, just play the MTM file. Crash reported as [in_mod.dll]

Winamp Modern skin, VISTA 32 bit AU
Video: NVIDIA Geforce 8600
Sound card: REALTEK ALC889c
Winamp modern skin

MTM file (KLF-FASC.MTM) together with crashreport uploaded to:
http://wikisend.com/download/363144/..._mtm_fault.zip
http://www.sendspace.com/file/ue2l11

Greets from Charles

Replicated but there's little chance of a fix for it as in_mod is just buggy and needs a complete re-write which is not possible currently. alas there's not much that can be done even to patch the issue due to the nature of the failures.

have attached the file to this post for the future possibility it can be fixed.

[kzuse]

Okay I also am VERY OFTEN using the gen_tray and I am also annoyed every time that when I use the BACK button, the song "double-starts" which sounds like the first note "stuttering", depending on how much "silence" is at the start of the song.

I think I also reported this bug years and years ago, but it somehow went lost, and it is not so extremly annoying because I mainly use gen_tray to go the NEXT song (on Shuffle...) where this does not happen.

But nice to see that fixed in the next version!!

Especially if it also can cause, under some circumstances like yours, a real crash.

Thanks!

(uhm... because I do not want to use Cloud in the near future, I wouldn't update to 5.7 so it would be so great if that could be included in another 5.6x Build OR maybe the new gen_tray could be downloaded separately manually?)

Thanks anyway and best regards,
kzuse

[DrO]

Originally Posted by kzuse

(uhm... because I do not want to use Cloud in the near future, I wouldn't update to 5.7 so it would be so great if that could be included in another 5.6x Build OR maybe the new gen_tray could be downloaded separately manually?)

are you really being serious? for somone that has been around these forums for so long i'd have expected you to know that like everything else you can un-check the Cloud components when installing the beta builds as explained at http://forums.winamp.com/showpost.ph...47&postcount=8

[kzuse]

Okay... I didn't read this, but you're right, I should have supposed that.

But actually, the point I wanted to express was another: In general, I'm not productively using Betas normally (except for one machine for testing purposes), so I will stick to 5.65 for now. That's why I asked if it would be backported to a new 5.6x "final" build.

If and when 5.7 is ready, I will install it without Cloud support (but one is never sure what an installer does NOT install when unchecked... ;-) )

--kzuse

[DrO]

rightio, i won't need to send you the test build of the plug-in as you seem to want to prefer to wait for another 5.6x build with it included and as i've gotten the confirmation the issue is fixed there's no reason to send out extra copies of it anyway.

and if you want to have a dig at what the installer does or doesn't do, just openly state it than trying to be coy. as it's known what it does and doesn't do and it's even been explained on these forums (when it should not) and is what has to be done as part of keeping Winamp free.

and this irritable post has been brought to you by the incessant annoyance caused by tooth ache.

[ujay]

Latest 5.7 build seems to work fine without the cloud, just by logging out. No need to install/uninstall the component all the time. Not been able to login for weeks now, so not been rigorously tested. If this turns out to have no side effects it's just what's needed to address the speed issues.

UJ

[kzuse]

O my god, I didn't want to annoy anyone as tooth ache and also didn't want to be irritating.

And the comment about the installer was in no way intended as an offence, just a thought about installers in general. Sorry if that could be gotten wrong...

Again, o my god......... ^^

I'll just wait for the next final, be it 5.6x or 5.7, install it, and be happy about the fix, which for me is not as crucial as I have experienced no crashes yet due to the double firing back button. It's all fine!

[mnemo]

Alright...

Winamp 5.65 - freshly installed
No Language Packs
Skin: Winamp Classic
Windows 7 64-Bit SP1, DE_DE
Intel i5-2600K 3.30 GHz, 4 GB RAM, Asus P8Z68-V S1155 Z68
GeForce GTX 560 Ti, Driver 320.49
Realtek HD, Driver 6.0.1.6251
DirectX 11?

There seems to be a problem with the metadata decoding in the Winamp MPEG Audio Decoder Plugin V4.100 (included with Winamp 5.65).

When listening to a specific stream the current title won't update for some tracks. The title also won't update when I stop/start the stream, Winamp just displays the stream name. Tests with XMplay and Foobar2000 show that they don't have this problem. When the title in Winamp is NOT displaying, starting the stream in either of these players will immediately show the title there, so everything is pointing at a bug in Winamp.

One of the track names this happens with is "Katy Perry - Roar" (yeah, yeah). Always when this plays, the title won't update in Winamp, it's very strange. A friend of mine working at the radio station has monitored the metadata in the stream and says that they have no problem on their end...

Stream URL is: http://httpmedia.radiobremen.de/bremenvier.m3u
Currently resolving to: http://gffstream.ic.llnwd.net/stream/gffstream_mp3_w49a

Stream info from Winamp:
Server: Limecast 2.0.1
Content-Type: audio/mpeg

Edit: The stream is playable outside of Germany.

If there is any debug mode or so that I can enable to provide more information, I'd be happy to help.

Thomas

[sonicwmat]

Winamp 5.65
English
Skin: Winamp Classic
Windows XP SP3
Intel i3-530@2.93ghz, 4 GB RAM, Gigabyte H57M
M-Audio 192
DirectX 9

Everytime I close WinAMP and restart, I have to go back into Input>Plugins>Waveform Decoder (v3.23) and reassociate wav to get WinAmp to play wav files...

[ravermeister]

have you tried to start winamp as Administrator and do the config change?
if you use Win7/Vista and Installed Winamp under C:\Program Files or C:\Program Files(x86)
it could be a permission problem --> UAC

[sonicwmat]

Originally Posted by ravermeister

have you tried to start winamp as Administrator and do the config change?
if you use Win7/Vista and Installed Winamp under C:\Program Files or C:\Program Files(x86)
it could be a permission problem --> UAC

I tried running as Administrator and no luck...have to consistently go back to Waveform and reassociate wav files as a type WinAmp can play....

[DrO]

you need to provide an info report.

[sonicwmat]

Originally Posted by DrO

you need to provide an info report.

Thanks...can you point me to the instructions for the info report?

[DrO]

is in the forum stickies for what needs to be provided when posting issues (is best I can provide as is a nightmare trying to find the links on a phone).

[Borkar]

Notifications (Modern Skin) do not refresh properly any more in Winamp 5.65 and 5.64. This has been reproduced on Win 7 x64 (no clean installation) and Win 8 x64 (clean installation) independently. The bug shows as follows:

The notifications in the bottom right corner used to show the current status (such as title name, "playback paused", "end of playback") on every key hit such as "play", "pause", "stop" (or mouse click on the corresponding buttons, respectively). Particularly, when playing a song, pressing "pause" displayed "playback paused". and when resuming with "play", it displayed the title of the song. This used to work perfectly and very reliably!

Since Winamp 5.64, those notifications became very unreliable and capricious! Pressing "pause" always shows "playback paused", but resuming the song with "play" does most of the time NOT display the song title again. Rarely it works, usually it doesn't. The same holds for stopping a song ("stop") and resuming the song again ("play").

In a nutshell, if the track is stopped or paused, pressing "play" does (in most of the cases) not show the song title in the notifications!

I consider this as a bug as it used to work perfectly in earlier versions of Winamp.

-Winamp 5.65, 5.64 - clean install
-Winamp Language Pack: none
-System specs: Lenovo Thinkpad T520, Intel i7 2nd gen., 8GB RAM
-Windows OS: Win 7 x64 SP1 (all updates as of today), Win 8 x64 (all updates as of today except update to Win 8.1)
-Intel HD graphics 3000 & nVidia NVS 4200M hybrid graphics (Win 7); VMware Workstation 10.0 graphics driver (Win 8)
-Conexant Cx20590 (Win 7); VMware Workstation 10.0 sound driver (Win 8)
-DirectX 11 (Win 7); DirectX 11 (Win 8)
-Detailed step-by-step method of reproduction: install Winamp 5.65, switch to Modern Skin, enable notifications and play around with "play", "pause", "stop", "forward", etc. hotkeys and you will see that the notifications are not always refreshed properly on every key stroke.
-NO 3rd-party plugins installed

[DrO]

it most likely relates to the fixes made to prevent it from randomly failing after a few shows (as was often being reported and seems to have stopped being reported since that release). i've not tried to replicate it but that seems like the most likely reason if it started with v5.64.

[Aminifu]

I have a different experience than Borkar. Most of the time the notifications work correctly. If I play with them long enough (rapid changes or waiting until each notification fades), I can get the play notification to not show after a pause or stop. If I keep cycling through pause & play or stop & play long enough or switch to the next or previous song, then the notifications all start working correctly again.

I have increased the time the notifications stay on the screen and the fade out time, don't know if that is the reason for my results. I don't remember the default times. Tell me what they are and I'll switch back and see if it makes a difference.

[Borkar]

The default times are fade in 1s, hold time 2s, fade out 5s. Personally, I prefer fade in 0.1s, hold time 2s, fade out 0.5s.

I am glad that you were able to reproduce it at least "somehow"!

[Aminifu]

Originally Posted by Borkar

The default times are fade in 1s, hold time 2s, fade out 5s. Personally, I prefer fade in 0.1s, hold time 2s, fade out 0.5s.

Thank you for the info. I get no difference with the default timing. I need to keep cycling thru several times before I get the play notification to fail. It happens sooner if I let the notifications fade completely. Again, several more cycles or switching to another song gets it working again.

I'm not able to select 100 milliseconds. My configuration shows 250, 500, and 750 for options below 1 second. This may be because I normally use a cPro skin and I did not disable that plug-in when I switched to the Winamp Modern skin.

Anyway, frequent or infrequent failures of the play notification to appear shows there is something not working right.

Obviously, it is much less of a problem for me and I probably would not have noticed, without you mentioning it. I normally use 2, 5, and 7.5 seconds. Even-though I have the notifications displaying at the top center of my screen, when I'm multitasking it takes me a little longer to glance at them during consecutive playback.

[debasishm89]

Hi,

Identified few crashes with latest free version of WinAMP Standard in below plugins. Few of them could lead to security issues i believe.

libmp4v2.dll
in_midi.dll

Reproduction Steps:

1. Get WinAMP standard from here :-> http://www.winamp.com/media-player/all
2. Get all POCs from here from below link.

<link removed>


Try to play them with the standard version. Let me know, if you have any trouble reproducing this issues.

Thank you!

[DrO]

there will be confirmed fixes for the libmp4v2.dll issues in the next release.

with the in_midi.dll issue, due to the age of the plug-in, a fix that prevents it crashing has been applied but what it's now broken we do not know as other than a complete re-write of the plug-in, it's likely we've broken something as part of trying to prevent the crash.

[debasishm89]

@DrO.

Thank you for your quick response. So, when you are planning to release patches for these (Mp4 & midi ) issues??

Thank you!

[DrO]

soon.

[debasishm89]

@DrO

Thank you. As I've already told, few of the reported issues are pretty serious, and has high security risk. I was planning to publish advisory for those. I will do that after you release patch for these issues.

Thank you!
Debasish Mandal

[Aminifu]

Originally Posted by DrO

the build number is what the beta builds were doing and we wanted to have the build shown on the about dialog but due to string sharing, that's how it all ends up being and tbh, it's cosmetic or can be altered via a plug-in (if it's that much of an issue) but you should be playing things anyway.

There's no pleasing everyone. I like that the complete version info is displayed without me having to open the about dialog (even-though it is rare that I have an empty playlist editor). I've always depended on the build number to be sure what version I'm using (when using beta and stable code), but that's just me.

It's also nice to see the place-holder llama image. I rarely see it nowadays with my configuration and file collection.