Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: WinAMP 5 beta 1 is out! (Read 29315 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

WinAMP 5 beta 1 is out!

Reply #25 –
Quote
Dumb question: How exactly does one rip with WinAmp?
Why isn't "aac" selectable in the diskwriter output?

It shows up for me under Preferences - CD Ripping - Encoder tab - Encoding Format - AAC v1.00.  I haven't tried ripping/encoding with it, though.  All options in the drop down are selectable for me except LAME.

---
And an interesting point I just discovered...if you select Vorbis as the encoder, the "Quality Factor" it shows ranges from -0.10 to 1.00, so you'd scale up 10x to relate these to quality settings for normal Vorbis encoding.  For example, "quality factor" 0.50 shows a nominal bitrate of 160kbps, = to oggenc -q 5.

WinAMP 5 beta 1 is out!

Reply #26 –
Does someone know what kind of AAC encoder is bundled with Winamp 5? Is it a totally new one?
Wavpack Hybrid -c4hx6

WinAMP 5 beta 1 is out!

Reply #27 –
Quote
Interesting news for Peter Pawlowski and foobar2000 users: go into General Preferences -> Titles -> Advanced Title Formatting and check the format syntax. Looks very similar to foobar2000's, doesn't it?

Now press the Help button. Seen it anywhere before...?

Looks like someone's playing Catch-up over at Nullsoft...

WinAMP 5 beta 1 is out!

Reply #28 –
Arrggh!  Trading one bug for another.

Well, Winamp 5 beta apparently has no international character support.  I know this has always been an issue for W/A, but I had it working fine with Winamp 5 alpha.  No joy for the beta version.

So, it's a choice between no intl char support in the beta, and the old "not saving the title display formatting" in previous versions (2.91, 2.95 and 5 alpha).  In pre-5-beta versions of W/A, I set the title display in Vorbis decoder v1.35 to %artist% ~ %album% ~ %title%, and whenever I restart Winamp it reverts to %artist% ~ %title%.  I have to reset this value every stinking time.  Ugh.

Lesser of the two evils, I guess.  I'd rather reconfigure an option each time I start W/A than read garbaged characters all the time.  Maybe they can fix this before release, I hope.

WinAMP 5 beta 1 is out!

Reply #29 –
Quote
Does someone know what kind of AAC encoder is bundled with Winamp 5? Is it a totally new one?

I believe it's Dolby's implementation but I'm not sure about this. http://www.afterdawn.com/news/archive/3910.cfm
 

WinAMP 5 beta 1 is out!

Reply #30 –
I'm surprised by W5, and it's a positive surprise... all of my input plugins from Winamp 2 - mostly dozens of emulation-related ones (in_sid, in_tfmx, in_adlib, in_snes, etc.) seem to work perfectly with the 5 beta. So far I like this Winamp 5 as much as I hated Winamp 3...

At first, I intended to run W5 once, check it and delete it, so I keep it in a temp dir with old plugins copied into it... but I'm actually tempted to copy it over my current Winamp 2.95...  (and use only classic skins, of course )

WinAMP 5 beta 1 is out!

Reply #31 –
Latexxx > thank you. Isn't QuickTime based on a Dolby implementation (the same maybe), but of course tuned by Apple? Are other softwares & encoders based on Dolby encoder?
Wavpack Hybrid -c4hx6

WinAMP 5 beta 1 is out!

Reply #32 –
Quote
Latexxx > thank you. Isn't QuickTime based on a Dolby implementation (the same maybe), but of course tuned by Apple? Are other softwares & encoders based on Dolby encoder?

Yes. Quicktime is based on Dolby's aac encoder if I'm not completely wrong. The usage of Dolby's encoder in Winamp 5 is just a guess. There was some discussion about it when the alpha version of Winamp 5 hit the net.

WinAMP 5 beta 1 is out!

Reply #33 –
[flame removed by moderation]

WinAMP 5 beta 1 is out!

Reply #34 –
Quote
[flame removed by moderation]

right.
Nothing but a Heartache - Since I found my Baby ;)

WinAMP 5 beta 1 is out!

Reply #35 –
Quote
Dumb question: How exactly does one rip with WinAmp?
Why isn't "aac" selectable in the diskwriter output?

Apparently the latest alpha versions actually have a CD ripper built in. But you have to pay for support, unless you managed to get your hands on one of the leaked copies that was never supposed to come out

WinAMP 5 beta 1 is out!

Reply #36 –
... [span style='font-size:8pt;line-height:100%']please feel free to delete this (now) useless post.[/span] ...
Nothing but a Heartache - Since I found my Baby ;)

WinAMP 5 beta 1 is out!

Reply #37 –
Quote
I'm surprised by W5, and it's a positive surprise... all of my input plugins from Winamp 2 - mostly dozens of emulation-related ones (in_sid, in_tfmx, in_adlib, in_snes, etc.) seem to work perfectly with the 5 beta. So far I like this Winamp 5 as much as I hated Winamp 3...


Yeah, I guess this is great for software writers like myself who never updated their Winamp 2.x plugins to 3.x (my excuse being I personally found Wasabi horribly complex for the [should be] simple task of writing an input plugin, particularly because I never found a nice 'hello world' input plugin example).

So does this mean Winamp 3 is officially dead as a failed experiment or what? And why the version 5 - was there ever a version 4? Are they trying to take the best of both worlds in taking Winamp 2.x plugins and Winamp 3.x skins into Winamp 5? Seems to make some degree of sense.

WinAMP 5 beta 1 is out!

Reply #38 –
Quote
Quote
I'm surprised by W5, and it's a positive surprise... all of my input plugins from Winamp 2 - mostly dozens of emulation-related ones (in_sid, in_tfmx, in_adlib, in_snes, etc.) seem to work perfectly with the 5 beta. So far I like this Winamp 5 as much as I hated Winamp 3...


Yeah, I guess this is great for software writers like myself who never updated their Winamp 2.x plugins to 3.x (my excuse being I personally found Wasabi horribly complex for the [should be] simple task of writing an input plugin, particularly because I never found a nice 'hello world' input plugin example).

So does this mean Winamp 3 is officially dead as a failed experiment or what? And why the version 5 - was there ever a version 4? Are they trying to take the best of both worlds in taking Winamp 2.x plugins and Winamp 3.x skins into Winamp 5? Seems to make some degree of sense.

How can it be "good" that they keep their ancient buggy input plugin API at cost of player features (unicode support) ? How many input plugins have you written to comment about this ? IMO even Winamp3 input API was much better, even though it had its faults. It's "good" only for programmers like you who keep their format closed and want to get some software support with minimum effort.
Microsoft Windows: We can't script here, this is bat country.

WinAMP 5 beta 1 is out!

Reply #39 –
Quote
Yes. Quicktime is based on Dolby's aac encoder if I'm not completely wrong. The usage of Dolby's encoder in Winamp 5 is just a guess. There was some discussion about it when the alpha version of Winamp 5 hit the net.

QuickTime is based on the Dolby Consumer AAC encoder, but it has been much tweaked inside Apple.

AOL has licensed the "Dolby AAC" low bitrate AAC enhancement technology for their AOL Radio. That technology is only available for the Dolby Professional encoder, it seems. Winamp doesn't seem to feature this technology, so it's either using the consumer encoder, or the professional encoder with Dolby AAC stripped.

I believe that, no matter what, Winamp will output different quality than QuickTime, since I doubt there has been any in-house tweaking.

There has been rumour that the Shoutcast Broadcaster will use Dolby AAC. So, one may guess that the Winamp AAC decoder can handle this enhancement extension.

WinAMP 5 beta 1 is out!

Reply #40 –
hmm, at the fwinamp forums the mods tell that winamp has licenced mpeg2 AAC and NOT mpeg4 AAC. are there any differencies in the standard?

@scortlibran: try this:
go to "options-preferences- skins - classic skin
check /uncheck "use skinned fonts for main window title display (no intternational title support)"

does this fix your problem?

WinAMP 5 beta 1 is out!

Reply #41 –
Quote
hmm, at the fwinamp forums the mods tell that winamp has licenced mpeg2 AAC and NOT mpeg4 AAC. are there any differencies in the standard?

Ignore the Winamp mods. They are so clueless and full of sh*t, it hurts.

And no, if you consider AAC LC (That's what Winamp uses), there's no difference.

WinAMP 5 beta 1 is out!

Reply #42 –
Quote
@scortlibran: try this:
go to "options-preferences- skins - classic skin
check /uncheck "use skinned fonts for main window title display (no intternational title support)"

does this fix your problem?

I tried toggling that, but it had no effect for me.  However, I just solved my problem by another means...

I unchecked the "Use advanced title formatting when possible" option under Prefs -> Titles, and intl chars are now displayed properly (except in the Library, which there will never be any help for, I'm afraid).

Since this overrides Advanced Title Formatting and defaults to the input plug-in title formatting, I had to then confirm whether this setting was being saved, as it never was in 5 alpha or previous 2.9n versions.  But it seems to be saving my (new) string format just fine: [%artist% ~ ][%album% ~ ]$if2(%title%,%filename%).

So all's good again.  Thanks for your suggestion, though!


Edit:  Not really important for the topic, but interesting nonetheless...

Quote
Winamp: The credits.

Code:
Justin Frankel
Christophe Thibault
Francis Gastellu
Brennan Underwood
Peter Pawlowski (who is sadly AWOL)

  So I wonder if they've sent out search parties? 

WinAMP 5 beta 1 is out!

Reply #43 –
Quote
How can it be "good" that they keep their ancient buggy input plugin API at cost of player features (unicode support) ? How many input plugins have you written to comment about this ? IMO even Winamp3 input API was much better, even though it had its faults. It's "good" only for programmers like you who keep their format closed and want to get some software support with minimum effort.


Well, if you look at the context of what I said, I was only saying that its 'good' for programmers like me, who have created a working plugin for 2.x and for whom rewriting the plugin for Winamp 3.x simply translates to a lot of time, in particular due to the lack of simple examples being provided. Regardless of whether a format is closed or open, the work still has to be done by someone.

WinAMP 5 beta 1 is out!

Reply #45 –
Thanks guruboolez, just what i was looking for.