Winamp 5.3
Winamp 5.3 Full
Winamp 5.3 Pro (asks for key during install)
Winamp 5.3 Standard (no media library or vis plugins)
Winamp 5.3 Lite

Full Changelog (108 lines) & More Info
http://forums.winamp.com/showthread.php?threadid=256207

Wow, Lame 3.97 release is included! It seems that you are very fast regarding QA tests...

More seriously, will Winamp include an mp3 encoder configuration box similar to this one day?:
http://lame.sourceforge.net/lame_ui_example.php
It seems way more easier to grasp for newcomers than the preset selection drop-down box.

On a sidenote: do you know of any stand-alone LAME front-end with that kind of interface? I'm looking for one.

BeSweet
LameDropXp
Omni Encoder

Wow, they must have discovered the meaning of all that Hex mystery iTunes puts in the metadata to pull this one off.

From the changelog

* New: Replaygain support for MP3, AAC, Vorbis, M4A and WMA

Awesome! Someone finally listened!!!

Edit: Here's a screenshot

i thought that b3 became final release

for those who do not know: lame b3 was tested in the winamp beta builds. Maybe only the string was updated.

Good point

seeing as the understanding was that 3.97final is just a recompiled 3.97b3 it was felt more sensible to ship a version not marked as 'beta' (i remember the talks about 3.97b2 when that became the recommended HA version to use and we had a nice talk over n00bs confusion of a beta being the recommended version against an earlier full release ). also i believe that the mp3 encoder just pulls the lame version from lame (putting 3.97b3 would then reflect that appropriately)

as for the changing over to the 'recommended' layout, i can't really comment on that though i know it has been mentioned but it's a matter of if it's decided on to be done or just getting the time to do it (as with anything heh)

-daz

I report a bug: Mp3 files wrapped in a wav file with Riff header seem not to be playable in Winamp 5.3. Even file info is not available.

Regards

Enrico

have a look at this which explains how to get support for such files again...

-daz

how do I control replaygain support for MP3/AAC?

I see no way to select track or album gain

There is a global control for all input plugins supporting it in preferces > general > playback

There is a small bug in FLAC decoder v1.1.2b included in Winamp Essentials: option 'show average bitrate while playing' gives oposite results.

Adding LAME 3.97 - good.

Not updating the presets for ages - not good.

Alt-presets has been outdated for a while, no? It uses the old vbr engine which is not recommended?

The -Vx presets should be added.

Otherwise a very nice release!

DrO, you should have pointed out that * means that it is fixed in latest internal builds and should be in the next release, 5.31. Also whenever I update Winamp my default vis. always goes back to AVS. But besides that it's good to see that Winamp will be adding native FLAC support, hopefully FLAC encoder too for ripping (just to spread the FLACness, we all know sonic engine is no EAC)

Does anyone know whether the Winamp team's planning to add APE tagging capabilities to in_mp3.dll sometime in the future? I'm used to tag my MP3 files with both ID3v1 for portable players and APEv2 for PC playback, mainly because of annoying compatibility issues I had with ID3v2.4 in the past. Using Winamp, I'm forced to rely on alternative MP3 input plugins as a workaround for this problem at the moment. Of course, I know I could simply convert the APE tags to ID3v2.3 using MP3tag or foobar2000, but meanwhile I clearly prefer the APE tagging format to ID3v2.

Edit: Typo.

The -Vx presets can be used by choosing Quality: Normal, Mode: VBR (new or old) and setting VBR Quality to the desired value.

Alt-presets use the same vbr engine btw.

I second that!

http://www.hydrogenaudio.org/forums/index....st&p=416561

http://www.hydrogenaudio.org/forums/index....mp;#entry418790

As far as I know there have been numerous fixes regarding ID3v2.4 in Winamp 5.3. They were mentioned in the beta build changelogs although they seem to have vanished in the definitive changelog.

Maybe a Winamp dev can enlighten us?

It's on my todo list, but I have no timeline as to when it's going to appear.

For those interested, the LGPL source for the replaygain analysis code is here: http://forums.winamp.com/showthread.php?s=...threadid=256408

Main change from the MP3Gain-sourced code is the ability to run multiple instances simultaneously (via a context pointer)

I'd suggest you to also apply the fix for denormals:
http://lame.cvs.sourceforge.net/lame/lame/...p;diff_format=l

I see, Thank you

Enrico

Thanks for that reply. The missing timeline doesn't matter, at least it's good to know that support for APE is planned to be added sometime in the future.

yep, that's a carryover from the reference plugin, it should say 'show instantaneous bitrate while playing'

Funny ways AOL has of making themselves look good... :)

If you'll notice, the code used to generate that graph seems to fill the bars -minimally- to the end of each item's text. MSN is the only one that reaches beyond. Just an odd bug, or poor design, and kind of offtopic too.

Updated in_mp3 now available

I see in the changelog that 5.3 supports 24bit decoding. Now, is 24bit able to improve playback quality (audibly?) of compressed audio such as mp3 when the decoder itself creates 24bit output? This could be the case, since mp3 "waveform" is created at output time. What would the improvement actually be, just SNR?

BTW, does anybody know how foobar handles this? I assume bitrate conversion happens after decoding there.

The native output of Winamp's mp3 decoder is 64bit float, so converting to 24 or 16 only happens at the end. If your soundcard's DAC is 24bit, why decimate to 16 only to have the driver add zeroes to go back up to 24? It makes more sense to go straight to 24. Also, applying ReplayGain and decimating to 16bit is problematic, as you effectively lose 1-2 bits of dynamic range, and that's starting to head into audibility territory.

Benski, on the topic of the mp3 decoder, does the in_mp3 plugin perform any dithering when it is set to output 16 bits? If not, is this planned for a future release?

@LMS

Dithering is always used if "Use Dither" is selected in the "Playback" options. It's a global setting that works for in_mp3.dll, in_vorbis.dll, in_wm.dll and in_mp4.dll. The additional in_flac.dll should be supported by it as well.

Edit: It's "setting", not "settings"

So, if I understand correctly, if one has an audio card, that only supports 16-bit output, one should not enable ReplayGain, as it will decrease output quality? Is it recommended then to use DirectSound output, which can output 24-bits even if the audio card doesn't support it. I know that there is a conversion done, so the actual output is still 16-bit, but is the loss you described not present with 24-bit output w/ DirectSound output?

There is now an update pack installer available which contains updated bugfix versions of in_mp3, ml_local, ml_playlists, and the missing filereader.w5s

Download Winamp 5.3 Update Pack | More Info

Note the very careful wording: "starting to head into".

In practise it will only apply to files with large negative gains, which usually don't exactly have a lot of dynamic range to start with.

When I use 24 bit, it is interressant to enable dither or not ?

Found possible bug: when playing internet radio stream, the "View file info" or alt+3 should display stream URL, codec etc., however it doesn't do anything.

J.M.

Not really. Dithering is important for 16 bit playback of 24 bit source material, but not the other way round.

Sorry if this been already answered, but I seem having problem with id3 tags - I have files with both id3v1 and id3v2, but Winamp will display id3v1?? shouldn't it display id3v2 if both id3 versions are present?
Also to the new mp3 file info box, I'm missing some information here (mainly stereo type)

Yes, ID3v2 takes precedence over ID3v1.
It sounds like you've installed some 3rd-party mp3 input plugin,
eg. one of: in_mad, in_!mpg123, or in_mp3pro, maybe?

The only known issues with the extra fields (Album Artist, Disc, Gain) in the newer in_mp3 Tag Editor are:
1) tabbing is not in the correct order, and
2) Disc isn't grayed-out when ID3v2 is unchecked,
both of which have already been fixed internally for 5.31

Updated in_mp3.dll available
http://stashbox.org/2168/in_mp3.dll

This fixes the following 5.3/5.3a-specific issues:
-Lame header ignored when ID3v2 tag is greater than 16kb
-An ID3v2.4 per-frame unsynchronization bug
-Crash when modifying ID3v2.4 tags with UTF-8 data
-And possibly some other minor fixes...

Looks like 5.31 is out.

http://download.nullsoft.com/winamp/client...amp531_full.exe

And the size just keeps on going up...

Already posted: Link

The file size growed because of the new flac encoder/decoder.

Ooh. Not *validated* yet. I see. :)


Using 5.12. From that to 5.31 it's +20% (~1MB). Must be something more than a FLAC codec. Maybe more Predixis bitmaps? :)

the predixis crap generally adds about 0.5Mb to the installer once it's been built

-daz

Unicode, support for 24 Bit, ReplayGain scanner, CD Text support, this all brings a few kb more.

But I agree, Predixis is huge and crap.

[Edit]Hey DrO, two times the word "crap" related to predixis, that's funny.

Quote from: http://flac.sourceforge.net/

Also see:
http://www.hydrogenaudio.org/forums/index....st&p=443961

Oh noes.. 1mb larger download. Tragedy!!!