A bug in 5.9.2 I have found is related to certain fonts (in my case UnifontEX, my improvement of GNU Unifont, as well as the official GNU Unifont's last TrueType version, which has to be obtained from Unifont's official archive repo) being usable in the TrueType Font selection (it just never shows in the menu) except for when selecting the Playlist Menu font. I'm using a clean install of 5.9.2 on Windows 11 and Winamp Modern skin with the Uranium color scheme. I have an RTX 3070 GPU with a modern Intel Core i7. I'm on English (US) for language pack, and use an American English Windows 11. My locale is set to Japanese so that many of the Japanese MIDI files I play do not experience Mojibake. On that note, apparently, if I ever play a WAV or MP3 or other such audio in Winamp, playing a MIDI file via the default MIDI player plugin that outputs to an external MIDI device (in my case OmniMIDI with my JummBox SoundFont, namely V11) will actually play the WAV on top of it, and silencing that WAV can ONLY be done using the bundled DSP plugin with the "Simple Volume Control". So, in actuality, there are TWO bugs going on here. I'm using the latest versions of my drivers.
Step 1 for font bug:
Download the last TrueType version of GNU Unifont (15.0.06), or UnifontEX.
Step 2: Install it.
Step 3: Go into the "Playlist Preferences" and select "Use Font" You will observe that the fonts show up.
Step 4: Go into the "Modern Skins" preferences and then "Font Rendering"
Step 5: Try to change the "Fallback Font" or the "TrueType Replacement for Winamp Charset bitmap fonts" with the dropdowns. You will observe that the fonts that showed up earlier do not show up.
Step 6: Try to use the Skin Font Mapper. In the array of fonts usable, those fonts are also not visible.
MIDI Bug:
Step 1: Install OmniMIDI or any other Windows MIDI synth, or if you have a hardware MIDI synth, use it.
Step 2: Go to the MIDI Player input plugin configuration and select OmniMapper (selecting OmniMIDI will result in an endless error loop of it saying the device is in use)
Step 3: Play some regular audio files.
Step 4: Play some MIDI files. You will hear the audio files mixed over the MIDI files.
Announcement
Collapse
No announcement yet.
Post All Winamp 5.9.2 Bug Reports In This Thread
Collapse
This is a sticky topic.
X
X
-
Originally Posted by GrantZ View PostHaving the same crashing as probably many others in this thread. Winamp never even has time to generate a crash report, only Windows registers the crash. Basically the same report as Gunti posted except for Windows 11 (10.0.22621 Build 22621):
Trying now after uninstalling modules: NFT Library, HotMix Radio (or whatever it was called, sry) & Fanzone.
So far so good, but situation might change since the crashes have been fairly random at times. Will try to remember reporting back if it helped or not.
Leave a comment:
-
-
-
Having the same crashing as probably many others in this thread. Winamp never even has time to generate a crash report, only Windows registers the crash. Basically the same report as Gunti posted except for Windows 11 (10.0.22621 Build 22621):
Faulting application name: winamp.exe, version: 5.9.2.10042, time stamp: 0x64490348
Faulting module name: ntdll.dll, version: 10.0.22621.2134, time stamp: 0xcfd48485
Exception code: 0xc0000374
Fault offset: 0x000eca4f
Faulting application path: C:\Program Files (x86)\Winamp\winamp.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
So far so good, but situation might change since the crashes have been fairly random at times. Will try to remember reporting back if it helped or not.
Leave a comment:
-
-
Originally Posted by Xcile92 View Postalso no features to utilize dolby dts for headphones...
those things cost a small fortune and Winamp is a free player so do the math.
Leave a comment:
-
-
I had in the playlist 1100 tracks... and I tried to remove them (CTRL+A - del) and Winamp would close (if I deleted only a few... no problems) Same thing would happen to new playlist (CTRL-N)
Tried a lot of things until I noticed I had Shuffle and Reapeat All activated. When I de-activated those, deleting all the tracks worked fine.
Latest winamp v5.9.2. build 10042, no language pack, no 3rd party plugins
Laptop HP Gaming 15.6'' Victus 15-fa0025nq, FHD IPS, Procesor Intel® Core™ i5-12500H (18M Cache, up to 4.50 GHz), 8GB DDR4, 512GB SSD, GeForce GTX 1650 4GB
Windows 11 Pro 22H2 OS Build 22621.2215
Latest drivesrs for VideoCard/Audio
Leave a comment:
-
-
i've had to downgrade to windows 10 because winamp is extremely unstable on windows 11's latest build. everytime i'd go to do anything it just crashes no matter what i do. also there is a bug in volume control and its not in sync with windows sound control mixer. i have to have winamp at volume one to use the windows sound mixer and it isnt a smooth experience. and there is no multi CPU threading support such as a x64 release. and still no direct cloud support for OneDrive and Google Drive for multimedia playback. also im not sure if the app can utilize cpu's correctly in a specific core or thread if is busy. probbaly why it crashes. also direct 3d audio support could be buggy i have noticed playback issues if active to utilized my cpu.
Leave a comment:
-
-
Version 5.9.2 has many issues and I don't think they will be fixed. I went back to version 5.9.0
Leave a comment:
-
-
Originally Posted by -Px- View PostThat is heap corruption error code, check your addons and try to remove then one by one to find the offending one.
If you have ASIO output plugin, this is the first candidate.
So.. I've done one thing. Uninstall Winamp. Removed all folders associated with the app.
Installed the "last stable version" (at least the one that I've used 5.9.0 build 9999)
Not Installed the Winamp agent.
Running without any problem.
I will be using winamp heavily next days/week if this solves the issue I will install the recent version with the same settings and let you guys know what happen.
Thanks
Leave a comment:
-
-
Originally Posted by Gunti View PostWinamp is crashing all the time...
Win10 Home 22H2
Faulting application name: winamp.exe, version: 5.9.2.10042, time stamp: 0x64490348
Faulting module name: ntdll.dll, version: 10.0.19041.3324, time stamp: 0x7f9ebe8b
Exception code: 0xc0000374
Fault offset: 0x000e6d83
Faulting process ID: 0x4fd0
Faulting application start time: 0x01d9cb72a58b4d51
Faulting application path: C:\Program Files (x86)\Winamp\winamp.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report ID: 950abd81-696e-472a-900f-e8c8a8f329df
Faulting package full name:
Faulting package-relative application ID:
If you have ASIO output plugin, this is the first candidate.
Leave a comment:
-
-
Winamp is crashing all the time...
Win10 Home 22H2
Faulting application name: winamp.exe, version: 5.9.2.10042, time stamp: 0x64490348
Faulting module name: ntdll.dll, version: 10.0.19041.3324, time stamp: 0x7f9ebe8b
Exception code: 0xc0000374
Fault offset: 0x000e6d83
Faulting process ID: 0x4fd0
Faulting application start time: 0x01d9cb72a58b4d51
Faulting application path: C:\Program Files (x86)\Winamp\winamp.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report ID: 950abd81-696e-472a-900f-e8c8a8f329df
Faulting package full name:
Faulting package-relative application ID:
Leave a comment:
-
-
There is a slight annoying bug that makes Winamp to close unexpectedly. If I press the Load-button to get the saved playlist-file X amount of times, it suddenly closes. And it's not necessary only that button, but also on New and Save.
Leave a comment:
-
-
Originally Posted by tnblank77 View PostBeen on Winamp 5.6.66 forever; recently got tired of being notified by updates so tried 5.92 today. It crashes a second or two after I play anything (no prompts to report the crash or anything; just like closes).
Would like to provide more information/crash logs but not sure how to.
Returned to 5.6.66 again and everything is fine.
Leave a comment:
-
-
Been on Winamp 5.6.66 forever; recently got tired of being notified by updates so tried 5.92 today. It crashes a second or two after I play anything (no prompts to report the crash or anything; just like closes).
Would like to provide more information/crash logs but not sure how to.
Returned to 5.6.66 again and everything is fine.
Leave a comment:
-
Leave a comment: