Skip to main content
Topic: Winamp 5.3 Released (Read 48221 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Winamp 5.3 Released

Reply #1
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.


Winamp 5.3 Released

Reply #3
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

Winamp 5.3 Released

Reply #4
Quote
* iTunes-compatible gapless playback (MP3/M4A) and encoding (M4A)

Wow, they must have discovered the meaning of all that Hex mystery iTunes puts in the metadata to pull this one off.
Every night with my star friends / We eat caviar and drink champagne
Sniffing in the VIP area / We talk about Frank Sinatra
Do you know Frank Sinatra? / He's dead

Winamp 5.3 Released

Reply #5
From the changelog

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

Awesome! Someone finally listened!!!

Edit: Here's a screenshot

Winamp 5.3 Released

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

i thought that b3 became final release

Winamp 5.3 Released

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


Winamp 5.3 Released

Reply #9
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

Winamp 5.3 Released

Reply #10
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

Winamp 5.3 Released

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

-daz

Winamp 5.3 Released

Reply #12
how do I control replaygain support for MP3/AAC?

I see no way to select track or album gain

Winamp 5.3 Released

Reply #13
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

Winamp 5.3 Released

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

Winamp 5.3 Released

Reply #15
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!
myspace.com/borgei - last.fm/user/borgei

Winamp 5.3 Released

Reply #16
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)
[span style=\'font-size:8pt;line-height:100%\']"We will restore chaos"-Bush on Iraq[/span]

Winamp 5.3 Released

Reply #17
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.

Winamp 5.3 Released

Reply #18
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!

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.

Winamp 5.3 Released

Reply #19
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.

I second that!

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

http://www.hydrogenaudio.org/forums/index....mp;#entry418790
WavPack 5.1.0 -b384hx6cmv / qaac 2.64 -V 100

Winamp 5.3 Released

Reply #20
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.

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?
Every night with my star friends / We eat caviar and drink champagne
Sniffing in the VIP area / We talk about Frank Sinatra
Do you know Frank Sinatra? / He's dead

Winamp 5.3 Released

Reply #21
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.


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


Winamp 5.3 Released

Reply #23
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


 
SimplePortal 1.0.0 RC1 © 2008-2019