Originally Posted by DJ Egg
View Post
Announcement
Collapse
No announcement yet.
Post All Winamp 5.666 Core Bug Reports In This Thread
Collapse
X
-
Originally Posted by DrO View Postthe whole of the JTFE shell handling needs to be re-written as it was known that some parts were broken with other changes which had to be made to get it supporting other required changes for the 5.66 release. as i own the source code, the plug-in can be updated irrespective of whatever may happen. so apologies to all that i've screwed this up for though i think you can try toggling some of the options to get it like before, but i cannot remember which at the moment.
Comment
-
-
Originally Posted by Zith ro max View PostI was able to restore the enqueue functionality by going to Preferences > Shell Options then enabling "Add "Enqueue & Play' to Winamp's associated file types", then check "Add files into the queue for delayed playback" then the radio button for inserting at the end of the queue. Then I unchecked the "Add Enqueue & Play" option and it works. If you re-enable it and disable the delayed playback option, it will again play immediately.
Comment
-
-
I can confirm that Zithromax's workaround/fix works. Thanks.
The only quirk being....
It's also adding the enqueued item to the JTFE Play Queue
Or if the song is already in the playlist (e.g. if a large playlist is loaded)
and you "Enqueue in Winamp" the same song from Explorer,
then the original playlist entry for that song also gets added to the JTFE Play Queue.
Maybe this isn't such a bad thing though, but it is a change of behaviour.
Before, it just added the enqueued item(s) to the end of the current playlist only.
It didn't also add them to the JTFE Play Queue
(which it shouldn't if the main EnqPlay option is unchecked in JTF options).
What it means is that the first enqueued item will play next, even if there's still a number of existing songs in the playlist before it.
Hopefully it can be fixed so we can get the expected behaviour back...
Comment
-
-
Hi!
I know it's kind of to late and maybe pointless too, but here is my bug report anyway.
Version 5.66, the latest one, it's unable to queue files trough context menu. When I do that - it starts playing immediately... I didn't succeeded to enqueue any files... did reinstall few times, but nothing helped.
It works perfectly in v.5.65
Comment
-
-
Hi Zypher76,
Known problem, has already been reported several times.
Until it is fixed, a couple work-a-rounds have been discussed (search forums). They both have side effects that may be undesirable for you.Winamp v5.9.2.10042 - Quinto Black CT v3.8 skin
Windows 11 Home 64-bit v22H2 desktop - Logitech Z906 5.1 speaker system
Comment
-
-
OS: MS Windows XP Professional (Svc Pack 3)
Locale: English (US)
CPU: AMD Sempron Processor LE-1250 @ 2.2 GHz
Memory: 3.0 GB RAM
Graphics: nVidia GeForce GTS 450
Sound: VIA High Definition Audio
DirectX 9.0c
Problem (This isn't so much a functional problem as an inconvenience):
In the "Winamp Classic" skin, the classic Oscilloscope visualization no longer correctly displays the "Lines" mode, even when it is selected in Winamp Preferences. Instead, it displays the "Dot" mode. I've confirmed that the "Dot" and "Solid" modes display properly, and the "Lines" mode appears to display properly in the Bento / Big Bento and Winamp Modern skins. I did not notice this issue in my previous version of Winamp, 5.65.
As a test, I did remove all my third-party plugins and there was no change in behavior.
EDIT - I just updated to version 5.666 and the issue still remains.
Comment
-
-
Originally Posted by mjponso View PostProblem (This isn't so much a functional problem as an inconvenience):
In the "Winamp Classic" skin, the classic Oscilloscope visualization no longer correctly displays the "Lines" mode, even when it is selected in Winamp Preferences. Instead, it displays the "Dot" mode. I've confirmed that the "Dot" and "Solid" modes display properly, and the "Lines" mode appears to display properly in the Bento / Big Bento and Winamp Modern skins. I did not notice this issue in my previous version of Winamp, 5.65.
As a test, I did remove all my third-party plugins and there was no change in behavior.
EDIT - I just updated to version 5.666 and the issue still remains.My Winamp Info Report | My Winamp Backup Log | My WACUP Info Report
Own Projects: | Winamp Tray Control Icon Pack v3.5.3 | Winamp Backup Tool v3.6.0 | >> Winamp Info Tool v6.1.0 << |
German Translations: | Offizielle Deutsche Winamp Sprachdatei v5.66 | Offizielle Deutsche Winamp Sprachdatei Plus Version 5.666
Useful Winamp Plug-ins: | SNESAmp | 64th Note | NotSo FatSo | Highly Experimental PSF Player | Yar Matey! Playlist Copier v1.12 |
Comment
-
-
Originally Posted by DJ Egg View PostD'oh! If only you'd reported it a few hours earlier.... :-)
Well spotted. Thanks!
Comment
-
-
5.666, the number of the beast!PENN STATE Radio or http://www.LION-Radio.org/
--
BUG #1 = Winamp skips short tracks
Wish #1 = Multiple Column Sorting
Wish #2 = Add TCMP/Compilation editing
Comment
-
-
There is still a a bug that still haven't been fixed wich annoys a little bit. The Media Library is somehow "freezed" in the ripping section and you have to click on something else to get it back. Look to the left side: http://img534.imageshack.us/img534/1108/zfu2.png
Comment
-
-
Originally Posted by tomraver View PostWinamp 5.66
Clean install, yes
3rd-party skins or plugins, no
Language Pack: French (fr)
Skin: Winamp Modern
OS: Windows 7 Professional (64-bit)
Locale: French
CPU: Intel I7 3930K
Memory: 8GB RAM
Graphics: Geforce GTX 480ti
Problem:
Over the taskbar icon I only see the first letter of the song playing with this version. Was fine in previous version
More Info:
I used to have 5.65 and no problem
What can i do?
Thanks you
Comment
-
-
Using the Winamp Classic skin. If I play an MP3/WAV/M4A file and use the mouse to drag the Seeking Bar to a new time point, when I release the mouse the display continues to show "Seek To: xx:xx" instead of reverting to the song title. Doesn't happen with WMA files. Doesn't happen when seeking with the keyboard. This behavior has been occurring with Winamp versions >= 5.65 (5.64 is fine).
Comment
-
Comment