Winamp 5.9.1 Released

[jvidal]

@DJ Egg, maybe you should edit the first post, then. it says that unicode chars issues have been fixed, which -in your own words- is not the case.

Oh, and BTW, the issue with unicode chars lies on the FILENAMES with special/unicode chars, not in the ID3 tags. This is pretty obvious when clicking "Edit playlist entry", you can clearly see special characters as "?" or a "?" inside a rombus..., so that's why they are not displayed on playlists and are skipped by winamp (in short, it can't find a file with such filename)

just in case...

[ariszlo]

Oh, and BTW, the issue with unicode chars lies on the FILENAMES with special/unicode chars, not in the ID3 tags. This is pretty obvious when clicking "Edit playlist entry", you can clearly see special characters as "?" or a "?" inside a rombus...

That shows that your your filesystem uses LEGACY encoding, not Unicode. If it used Unicode then there would be two or more such special characters for each accented letter.

[Mikey7]

That shows that your your filesystem uses LEGACY encoding, not Unicode. If it used Unicode then there would be two or more such special characters for each accented letter.

Finally, a reasonable sounding "fix" to this issue. We've been reading about it here ever since 5.9.0 Final was released, regardless that no one else (to the best of my knowledge) including me have run into this. I have plenty of song titles (in Portuguese, for example) that have always rendered properly. This puts a real strain on the development team in trying to chase down an issue experienced only by a few and trying to confirm that it is caused by Winamp and not the user. Same for those who keep reporting 5.9 constantly crashing. My gut feel in those cases is that either the user's hardware or their Windows installation is causing the issue, not Winamp. That leaves the issues with .m3u playlists which again, I have not experienced. There are so many additional feature requests, like an updated browser to open up more podcast capabilities that it would be nice if the development team were freed up to pursue.

[jvidal]

That shows that your your filesystem uses LEGACY encoding, not Unicode. If it used Unicode then there would be two or more such special characters for each accented letter.

IF that were the case, I'd have problems with all applications that have to deal with unicode characters, but ONLY winamp has such issues. I have several other media players (Aimp, Foobar, QMMP, QMplay2) AND NONE OF THEM have any trouble whatsoever dealing with special filenames. they all deal with them perfectly.

[ariszlo]

I have several other media players (Aimp, Foobar, QMMP, QMplay2) AND NONE OF THEM have any trouble whatsoever dealing with special filenames.

OK. What is the filesystem of the device where you store your music? FAT32 or NTFS? If FAT32 then the filenames are encoded in legacy character sets and then what Winamp does not support is not Unicode but legacy character sets.

[jvidal]

are your seriously asking me If I use FAT32? what year is this? 2000???
of course it's NTFS, it's a 2TB drive, running win10 x64

[ariszlo]

what year is this? 2000???

Do you perhaps save your playlists as m3u rather than m3u8?

[jvidal]

nope I've re-created my playlists several times.

[Legendarion]

nope I've re-created my playlists several times.

WinAmp have 3 different filetypes of playlists:

M3U Playlist

PLS Playlist

M3U8 (Unicode) Playlist


https://i.postimg.cc/Hn5rFk2d/Filetype.jpg


Which of them did you choose? Or saved it on?


Your issue seems to have some similarities the one I used to have in many years.

---> http://forums.winamp.com/showthread.php?t=458611

[bhiter010]

I so LLLove winamp and have been using it since the beginnig))
thanks team))!!

[MrSinatra]

are your seriously asking me If I use FAT32? what year is this? 2000???
of course it's NTFS, it's a 2TB drive, running win10 x64

its a fair question. many external drives are still purposely FAT32.

stop being exasperated, it doesn't help. we all just want to hunt down the cause, and since it is happening to you, we are going to send you down various rabbit holes until we find a clue to the right one.

[jvidal]

WinAmp have 3 different filetypes of playlists:

M3U Playlist

PLS Playlist

M3U8 (Unicode) Playlist


https://i.postimg.cc/Hn5rFk2d/Filetype.jpg


Which of them did you choose? Or saved it on?



Your issue seems to have some similarities the one I used to have in many years.

---> http://forums.winamp.com/showthread.php?t=458611

winamp creates m3u8 lists by default. If I look into my default playlist, winamp.m3u8, I see that accented letters are displayed just as empty boxes.
If I look into winamp.m3u, then I I see accented letters replaced by "?"

[jvidal]

I found out something a little weird, If I open one my ML playlists with Notepad++, Special characters are displayed incorrectly, even though the program recognizes the encoding as "UTF-8 with BOM". If I change the encoding to ANSI, then the characters are displayed correctly (it should be the other way around).
I even wanted to post some of them here, but when I pasted them into a reply, they were displayed correctly (while they were not in the text editor)

But, as I've pointed before, the only media player having trouble with special characters is Winamp, all others work just fine.

[ariszlo]

with Notepad++

Notepad++ breaks Unicode, and recent versions of Winamp no longer support legacy character sets. It is 2022, you know. Use a decent text editor that does not break Unicode. There are some, just to name a few: EmEditor, EditPad Lite or even Microsoft's Notepad.

[Pawel]

Notepad++ breaks Unicode, and recent versions of Winamp no longer support legacy character sets.

What do you mean?
Notepad++ not break unicode!
You just have to know how to properly convert ANSI-UNICODE (and vice versa).
Menu->Encoding->Convert to ANSI
or
Menu->Encoding->Convert to UTF-8 with BOM