Skip to main content

Topic: LAME 3.97 beta recommendation (Read 99882 times) previous topic - next topic

0 Members and 1 Guest are viewing this topic.
  • yulyo!
  • [*][*][*]
LAME 3.97 beta recommendation
Reply #50
I wanna ask you a dumb question.
  I have downloaded the latest recommanded Lame version.
  I am encoding to mp3 usind CDex or Razorlame. usually i use --alt-preset insane.
but now i read that the "--alt-preset" thing is dead.
  Updating to the latest recommanded Lame version should change me any settings in CDex for example? I have 3.97 in CDex right now but there are still --alt-preset. Mr. Questionman is reconizing the rezulted file as encoded with --alt-preset insane (?).
  So, in conclusion. The ultimate Lame must change something in the programs we use or is just an internal thing.
  Sorry for this stupid question
  • Last Edit: 05 October, 2005, 06:01:24 AM by yulyo!

  • stephanV
  • [*][*][*][*]
LAME 3.97 beta recommendation
Reply #51
Vietwoojagig:

What exactly do you want?

Because HA is recommending a Lame version labeled as beta, you want the Lame devs to remove the beta tag? Or do you want the HA recommendation be reverted to another (marked as stable) version. What, what?

Quote
Give me the reason, why you call it beta AND recommend it.

As Lyx already pointed out, the "you" you use here doesn't exist. HA and the LAME devs are not the same thing. If you only trust developers on what is the recommended version then why would you care about the HA one? But if we all must trust devs on their recommendations (or nomenclature) then there wouldn't need to be a HA recommendation at all, because it would only be redundant. The opinions of stability of this LAME version just differs between HA and Lame. If you have found any major flaws in this version, I'm sure people would be happy to hear about it.

Basically what you are saying is that HA shouldn't make any recommendations at all (or at least that those would be superfluous) and that many of the audio encoders and even software people are using for back-up shouldn't be used at all. But IMO it doesn't make sense to attach such high consequences on what is just a word with a very ambiguous meaning.
"We cannot win against obsession. They care, we don't. They win."

  • cabbagerat
  • [*][*][*][*][*]
LAME 3.97 beta recommendation
Reply #52
Quote
I am encoding to mp3 usind CDex or Razorlame. usually i use --alt-preset insane.
but now i read that the "--alt-preset" thing is dead.
Updating to the latest recommanded Lame version should change me any settings in CDex for example? I have 3.97 in CDex right now but there are still --alt-preset. Mr. Questionman is reconizing the rezulted file as encoded with --alt-preset insane (?).
So, in conclusion. The ultimate Lame must change something in the programs we use or is just an internal thing.
[a href="index.php?act=findpost&pid=331790"][{POST_SNAPBACK}][/a]
alt-presets aren't dead - they just aren't recommended any more because there is a more clear and more compact way of specifying the intended encode quality. The -V flags replace the functionality of the --alt-presets.

alt-presets still work (AFAIK), but map to -V numbers.
Simulate your radar: http://www.brooker.co.za/fers/

LAME 3.97 beta recommendation
Reply #53
Quote
Vietwoojagig:

What exactly do you want?

Because HA is recommending a Lame version labeled as beta, you want the Lame devs to remove the beta tag? Or do you want the HA recommendation be reverted to another (marked as stable) version. What, what?[a href="index.php?act=findpost&pid=331794"][{POST_SNAPBACK}][/a]
As I already said in my very first post: Wait until the beta-flag is removed and then recommend it. Why getting hectic so close to the final version?

  • ezra2323
  • [*][*][*][*][*]
LAME 3.97 beta recommendation
Reply #54
I was surprised to see -V 3 -vbr new recommended as a transparent setting. This is the 1st time I have ever seen an MP3 bit rate average that low (175 avg) recommended as transparent. Previously, APS which is now -V 2 was always the standard for minimum transparency.

Is there a testing thread that supports the -V 3 recommendation? If it is indeed transparent, and sinc eit is officially recommended as such I assume it is, this is great news! It's about a 10% reduction in file size from -V 2 (APS) !

What is the difference between -V 2 and -V3? Is it primarily in limiting the high frequencies? (similar to the old APS with the Y switch)

  • sTisTi
  • [*][*][*][*]
LAME 3.97 beta recommendation
Reply #55
Quote
What is the difference between -V 2 and -V3? Is it primarily in limiting the high frequencies? (similar to the old APS with the Y switch)
[a href="index.php?act=findpost&pid=331812"][{POST_SNAPBACK}][/a]

The main bitrate savings come from the Y switch, but V3 also uses slightly more aggressive compression for lower frequencies, as can be seen from comparing -V2 -Y to -V3.
Proverb for Paranoids: "If they can get you asking the wrong questions, they don't have to worry about answers."
-T. Pynchon (Gravity's Rainbow)

  • rjamorim
  • [*][*][*][*][*]
LAME 3.97 beta recommendation
Reply #56
Quote
Vietwoojagig:

What exactly do you want?[a href="index.php?act=findpost&pid=331794"][{POST_SNAPBACK}][/a]


To stir controversy and create polemic.

There's no other reason to focus so much in four letters. Specially considering everything else here that is also beta AND recommended. Some people have too much free time on their hands, and need to find the most meaningless things to worry about.

Sigh...
Get up-to-date binaries of Lame, AAC, Vorbis and much more at RareWares:
http://www.rarewares.org

  • flipik
  • [*][*]
LAME 3.97 beta recommendation
Reply #57
Quote
Wait until the beta-flag is removed and then recommend it.


Stephan explained that very clearly. HA recommended it. HA is free to recommend anything. You are free to don't follow it. It's win-win situation, no need to worry or discuss anything.
If I recommend you to stick carrots up your ssa, I'm free to do it and you are free to don't follow my recommendation.
But never, never try to pursue me that I should not recommand it 'cause you think you've got smarter way how to use carrots..
Geeez 

LAME 3.97 beta recommendation
Reply #58
Quote
Stephan explained that very clearly. HA recommended it. HA is free to recommend anything. You are free to don't follow it. It's win-win situation, no need to worry or discuss anything.
If I recommend you to stick carrots up your ssa, I'm free to do it and you are free to don't follow my recommendation.
But never, never try to pursue me that I should not recommand it 'cause you think you've got smarter way how to use carrots..
Geeez 
[a href="index.php?act=findpost&pid=331834"][{POST_SNAPBACK}][/a]
The carrots-thing sound interesting.
I will try it!

  • jkauff
  • [*][*][*]
  • Members (Donating)
LAME 3.97 beta recommendation
Reply #59
Quote
OFF-TOPIC
Now, now, let's not get carried away.  "LAME Mars Edition pre-alpha-very-dangerous-dontuseme-toxic", all fine for me, but "Microsoft"? The words "microsoft" and "alpha" in the same sentence should be enough to send any sensible being running away, screaming. 
[a href="index.php?act=findpost&pid=331695"][{POST_SNAPBACK}][/a]

Microsoft doesn't use the term "alpha". They use "Version 1.0" instead.

  • askoff
  • [*][*][*][*]
LAME 3.97 beta recommendation
Reply #60
Let's change the beta to gamma and we can get over this 'huge' problem.

  • shafff
  • [*]
LAME 3.97 beta recommendation
Reply #61
Encspot says that 3.97 -V0 encoded file has 58% ss (joint stereo) blocks, when the same file, but 3.96 ape encoded has 73%
3.97 -V2 and -V1 gives only 7%-10% ss blocks on that file (Madonna - Secret).

Is it OK?

  • robert
  • [*][*][*][*][*]
  • Developer
LAME 3.97 beta recommendation
Reply #62
Quote
Just tried one sample, the good old "birds" and it degraded to 3.96 builds. Didn´t encode anything in awhile. Is there a thread for bringing in testing for 3.97b? Excuse me but i haven´t been around here for a while until i heard about this build. Cheers to all the ones still very active around here!
[a href="index.php?act=findpost&pid=331722"][{POST_SNAPBACK}][/a]

What settings do you use for the "birds" sample?

  • [JAZ]
  • [*][*][*][*][*]
LAME 3.97 beta recommendation
Reply #63
I believe that the developers of LAME are the only ones that can say why they call it beta, and so far have opted to not add fuel to the fire.

That said, It has to be understood that they don't see this as a bad practice. Apha versions were advised to not be used for real encodings, and have received much testing. This testing is the one that has allowed the versioning to become beta instead of alpha.

I have no clue if there are new features expected to be added before the stable version, nor if any of them is incomplete or misbehaving. In any case, it wouldn't be the first time that a LAME version has been labeled beta, and no final version of that branch has come.

So, in the end, if the developers don't tell us (the readers of this post) not to use the version and/or recommend it, it can be understood as in being "complete enough".

  • beto
  • [*][*][*][*][*]
  • Members (Donating)
LAME 3.97 beta recommendation
Reply #64
God, since Lame devs already have a 3.98alpha branch please make 3.97 stable and we can end this discussion!! What harm could it bring??
I personally believe that enough testing was made in 3.97, but I also believe that some best practices in software versioning should be observed as well.
Lame can always be patched afterwards if some strange-hidden-unknown problem(s) show up.
And differently from what most people here might think coherent software versioning does make a difference for the wider audience.

Bottom  line: make 3.97 final and end the discussion.


just my 2c 

  • rjamorim
  • [*][*][*][*][*]
LAME 3.97 beta recommendation
Reply #65
I just added LAME 3.97b compiles for several esoteric platforms to RareWares.

Hohoho
Get up-to-date binaries of Lame, AAC, Vorbis and much more at RareWares:
http://www.rarewares.org

  • Echizen
  • [*][*]
LAME 3.97 beta recommendation
Reply #66
There shouldn't be a problem to recommend a beta as long as it's the current best version. It was about time to replace the old version because there was a lot of effort from the developers. I'm glad the new vbr model seems stable and good.

I would like to see new listening tests from Roberto with different codecs and then compare it with old tests. Maybe with 3.90.3 and 3.97b1 both in, to see the difference one more time.

The only thing I don't like about the new recommend version/settings is the very unpredictable file size. I'm not satisfied to get an 80kbps MP3 with -V 5 while aiming for 128kbps. It's a strange feeling... Quality should matter, but size too. Let's say i would like to get the best quality around 192kbps. How good is the new ABR model in comparison to the old preset 192 of 3.90.3? If ABR is recommend for use up to 100kbps (see remark), is it included in the -V switches 8 and 9?
  • Last Edit: 05 October, 2005, 04:52:45 PM by Echizen

  • richard123
  • [*][*][*][*]
LAME 3.97 beta recommendation
Reply #67
Quote
The only thing I don't like about the new recommend version/settings is the very unpredictable file size. I'm not satisfied to get an 80kbps MP3 with -V 5 while aiming for 128kbps. It's a strange feeling... Quality should matter, but size too. Let's say i would like to get the best quality around 192kbps. How good is the new ABR model in comparison to the old preset 128 of 3.90.3?
[a href="index.php?act=findpost&pid=331962"][{POST_SNAPBACK}][/a]


Whenever I got files sizes much smaller than expected, I re-encode at a higher V level.  This is probably a silly thing to do.

  • Wombat
  • [*][*][*][*][*]
LAME 3.97 beta recommendation
Reply #68
Quote
Quote
Just tried one sample, the good old "birds" and it degraded to 3.96 builds. Didn´t encode anything in awhile. Is there a thread for bringing in testing for 3.97b? Excuse me but i haven´t been around here for a while until i heard about this build. Cheers to all the ones still very active around here!
[a href="index.php?act=findpost&pid=331722"][{POST_SNAPBACK}][/a]

What settings do you use for the "birds" sample?
[a href="index.php?act=findpost&pid=331924"][{POST_SNAPBACK}][/a]


I used -V2
Is troll-adiposity coming from feederism?
With 24bit music you can listen to silence much louder!

  • shrinkmail
  • [*][*]
LAME 3.97 beta recommendation
Reply #69
I am also intrigues by the big variations in file sizes and bit rates with the new -V settings. It's a paradigm shift from the old -alt preset regime.
Could an expert please comment on that, because this is throwing up unexpected issues for people who had gotten used to the results with the older versions. Quality is not an issue, as it's superiority has become an established fact.
P.S. I missed all the fun in the beta wrangles, so my 2c. All the google products except the plain vanilla search are beta. So, there...

  • jamesbaud
  • [*][*][*]
LAME 3.97 beta recommendation
Reply #70
Quote
I just added LAME 3.97b compiles for several esoteric platforms to RareWares.

Hohoho
[a href="index.php?act=findpost&pid=331956"][{POST_SNAPBACK}][/a]


Any chance of putting up new 3.97b versions of the special packages, i.e.
"lame_enc.dll modified to use INI File Setup"

thx.

jb

  • johnsonlam
  • [*][*][*]
LAME 3.97 beta recommendation
Reply #71
Quote
Any chance of putting up new 3.97b versions of the special packages, i.e.
"lame_enc.dll modified to use INI File Setup"


IMO, set the default configuration into 'INI' is benefit even for command line version, it means no need to create an extra ".BAT" file.

The advantage is everyone can change the 'INI' according to their needs, if they want other parameters occasionally, just override it by giving command line parameters.
  • Last Edit: 06 October, 2005, 03:21:25 AM by johnsonlam
Hong Kong - International Joke Center (after 1997-06-30)

  • Gabriel
  • [*][*][*][*][*]
  • Developer
LAME 3.97 beta recommendation
Reply #72
Quote
I am also intrigues by the big variations in file sizes and bit rates with the new -V settings. It's a paradigm shift from the old -alt preset regime.

Are you complaining that -V is a vbr setting, and thus produces variable bitrate?
Old vbr alt-presets were also variable in bitrate, there is no shift there (even less "paradigm shift"). If you do not want the result to be variable in bitrate, then why are you using vbr?

  • danbee
  • [*][*][*]
LAME 3.97 beta recommendation
Reply #73
Quote
The only thing I don't like about the new recommend version/settings is the very unpredictable file size. I'm not satisfied to get an 80kbps MP3 with -V 5 while aiming for 128kbps. It's a strange feeling... Quality should matter, but size too. Let's say i would like to get the best quality around 192kbps. How good is the new ABR model in comparison to the old preset 128 of 3.90.3?
[a href="index.php?act=findpost&pid=331962"][{POST_SNAPBACK}][/a]


Well, if the encoder only needed an average of 80kbps to attain the 'quality' that you specified, why should it use any more?  It would be a waste, right?

In the end, the ultimate test should be with your ears.
Dan

  • guruboolez
  • [*][*][*][*][*]
  • Members (Donating)
LAME 3.97 beta recommendation
Reply #74
Quote
Quote
May I suggest you to lower the minimal bitrate for -V0, which looks exagerated?
For classical music 230 kbps is a pretty high value (on average I obtained 221 kbps, with a minimal value corresponding to less than 180 kbps). 215...220 is more reasonable in my opinion.[a href=\"index.php?act=findpost&pid=331548\"][{POST_SNAPBACK}][/a]

It's hard to guess averages for LAME's VBR modes. I just encoded one of my favourite albums using -V2 --vbr-new and it ended up at 257kbps average.
[a href=\"index.php?act=findpost&pid=331557\"][{POST_SNAPBACK}][/a]
It's not exactly what I'm asking for. There's a problem with -V0 minimal bitrate, not the average one. For all other -V setting, the min. value on the current tables seems OK. But 230 kbps as minimal bitrate for -V0 seems to be wrong. The bitrate doesn't jump that high with musical stuff having few informations (or noise) in the highest SFB. Tested on my 150 reference full tracks (classical only): 80% of them have a bitrate inferior to 230 kbps. 31 tracks only get a higher bitrate.
That's why I'd change the bitrate range for -V0:
230...260 -> 210/220 [I let you choose]...260.