Post All Winamp 5.666 Core Bug Reports In This Thread

[Airbag]

-Winamp 5.666 (5.6.6.3516) - clean install (and re-install as well), no extra plugins, addons
-English lang pack
-Asus P5K, intel Core 2 E6750, 4x1Gb Corsair XMS2
-Windows Vista Enterprise x64 SP1, locale:HU
-Asus EN8800GTS, Nvidia detonator 34.89
-Integrated HD audio, driver: 6.1.7601
-DX11

- When I start winamp and start scanning local media (only one folder with lots of mp3) (smart+ or default) it always crashes about after 3-4 mins.
- When I start to play a single album it crashes few mins later.
- When I do nothing just start winamp it always collapses in few mins.
I tried to change media scanning options, change output settings... but my favorite player always crashes.

Please fix this annoying thing. Thx.

[MrSinatra]

I read post 261, and I suspect you can whitelist or blacklist given usb drives, or perhaps drive letters anyway, via winamp ini files.

but can u explain a bit more? winamp shouldn't be scanning something automatically just b/c you connect it, and have you checked your "watch folders" settings?

[Waldschrat]

Hi,

any chance to disable scanning of connected USB sticks - see item #261

Regards
Waldschrat

[Aminifu]

Hi Sasha79,

Try the older Alt + Tab method to switch between running apps, instead of the Win + Tab method.

[Sasha79]

I have complaint about something that is not a bug,more annoying behavior and is not characteristic for other softwares:

I often keep opened 4 programes:Winamp v5.666.Lite(Classic Skin)administrator account,
shared settings,
Windows Media Player v11,Windows Explorer And Notepad,maximized,and they are all positioned in
Taskbar as Taskbar Buttons.I listen intermittently Winamp,than Windows Media Player,etc.
But,when I want Winamp to appear I exess Taskbar Button by pressing
Windows Button + Tab,select Winamp Task and than press ENTER to make it appear in a first row,
but it starts to minimize,instead of appearing maximized like other tasks.
It minimizes to Taskbar and then I must to reselect it again by Win Button + Tab and than ENTER to maximize it,so I late to mix up 2 songs correctly on time,the song fades out.

[DrO]

you would have been better off replacing in_mp3.dll in your install from the one posted 2 up from your post than going back to build 3507.

[osanjose]

Build 3516 does not deal well with tags

Finally I unistalled winamp 5.6.6 (build 3516), as far as I know the final release, and re-installed the previous 5.6.6 (build 3507) I still had the installation file, then everything returned to "normal". I can play any mp3 file. With the newest release I cannot play mp3 files generated by Lame encoder using Nero Suite 12 withe tags Nero creates for the file (I'm converting into mp3 files all my cd collection since the 1980's), however with build 3516 I can play all my music library files without crashes

On the other hand if I open those files using mp3Tag pro and then save them as mp3 again something changes in the files and build 3516 can then deal with those files and play them again.

Weirdo weirdo!!. What tag is the problem?... who knows!.

I can upload one of those files if someone wants to do further research. In the meantime my workaround is to use buld 3507

Thanks

Oscar

[Jim America]

That worked, thanks

[Aminifu]

Replace in_mp3.dll with the version from 5.666 build 3512.

[Jim America]

Winamp Crashes with certain MP3 ID3v2 Tags

Winamp 5.666 (build 3516)
Clean install, no 3rd-party skins or plugins
Language Pack: English
Skin: Bug occurs with all of Bento, Winamp Modern and Classic skins

OS: Windows 7 Home Premium (64-bit) AND Windows 8.1 (64-bit)
Locale: English US
CPU: Intel i5-2450M @ 2.50GHz
Memory: 8GB RAM
Graphics: Intel HD Graphics
Sound: Realtek HD Audio
DirectX 11

Problem:
Playing certain MP3 files causes Winamp to crash, disabling "Read ID3v2 Tags" in in_mp3.dll fixes the issue, as does removing the ID3v2 Tag from the offending file in a 3rd party program. The problem doesn't happen with 5.65

Method of Reproduction:
Open MP3 file with disagreeable id3 tag, immediately winamp crashes with "Winamp has stopped working / Close Program" dialogue box

Example of MP3 file that causes crash attached

[MrSinatra]

winamp doesn't recognize multiple fields within a frame, so maybe something odd with that, or the char set, etc... best thing to do is post some example files that demonstrate the issue, and then post exactly what you did to "fix" them.

edit: and an info tool report.

[osanjose]

After further research it seems related with another tags. Files have been created with Nero mp3 encoder (I guess Lame) and using mp3tagfpor it seems nothing is wrong., but I just set to blank "Comments" tags and now everything seems to work again. However this tag was blank before dong that operation, so maybe it has weird hidden characters that produces winamp to crash, or maybe it is some other tag.

Any clue?

[osanjose]

Winmp Crash with mp3 files with tagged images

Hi:

Latest winamp version is constantly crashing with some mp3 (320 kbps) files that includes a image in its tags. It seems other mp3 without images work well, but unluckily some other with images also goes well. The error is the following (sorry it is in Castilian Spanish but main information is useful)

Nombre de la aplicación con errores: winamp.exe, versión: 5.6.6.3516, marca de tiempo: 0x52aa753e
Nombre del módulo con errores: MSVCR90.dll, versión: 9.0.30729.6161, marca de tiempo: 0x4dace5b9
Código de excepción: 0xc0000417
Desplazamiento de errores: 0x00066812
Id. del proceso con errores: 0x4d8
Hora de inicio de la aplicación con errores: 0x01cf0d224c4afcec
Ruta de acceso de la aplicación con errores: C:\Program Files (x86)\Winamp\winamp.exe
Ruta de acceso del módulo con errores: C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCR90.dll
Id. del informe: 931136fc-7915-11e3-ade2-002185c68a24

This is a 64bit PC with Windows 7 SP1

Any idea, or clue to fix this?

Thanks

Oscar

[Victhor]

They who?

[MrSinatra]

they will probably tell you winamp is working as expected, and then the debate will be if winamp should recognize 00 or 0 as being different from null or no entry and / or should it be displayed?