Skip to main content

Topic: AAC @ 128kbps listening test discussion (Read 63977 times) previous topic - next topic

0 Members and 1 Guest are viewing this topic.
  • rjamorim
  • [*][*][*][*][*]
AAC @ 128kbps listening test discussion
Reply #25
Quote
Nero is heavily tweaked and is based on the Coding Technoligies codec I believe.

Nero is 100% in-house development

Quote
That would take care of 3 of your 6 choices in my opinion.


FAAC must be definitely in, because of implications of open source/yadda yadda.

I actually think Faac is more essential in this test than Winamp

Quote
RealNetworks would be nice, to see a mostly untweaked Coding Technologies codec compared against Nero (heavily tweaked) one.


Real codec is absolutely unrelated to Nero, as I explained above. So, no, it won't work to compare them in these grounds.
Get up-to-date binaries of Lame, AAC, Vorbis and much more at RareWares:
http://www.rarewares.org

  • kwanbis
  • [*][*][*][*][*]
  • Developer (Donating)
AAC @ 128kbps listening test discussion
Reply #26
Quote
Quote
well ... you mean it to be an anchor ... but what happened to xing? ...

Blah!!!

Please consider all the bad comments on Xing done here and elsewhere over the years, and then come tell me I did a bad choice!

it sure it was a good choice, but it, turning not into the anchor, didn't harm the test ...

  • rjamorim
  • [*][*][*][*][*]
AAC @ 128kbps listening test discussion
Reply #27
Quote
it sure it was a good choice, but it, turning not into the anchor, didn't harm the test ...

It harm in the aspect that there's no perspective. Codecs dipped too low on scores. I wanted Xing to be like Blade was in the first 128kbps multiformat test. Always at the bottom, to avoid some otherwise reasonable codec being labeled very bad because others were better.
Get up-to-date binaries of Lame, AAC, Vorbis and much more at RareWares:
http://www.rarewares.org

  • guest0101
  • [*][*][*][*]
  • Banned
AAC @ 128kbps listening test discussion
Reply #28
I really like you original choices for the 5 AAC encoders (not including the anchor which appears to be open to much debate):

-Nero AAC encoder VBR profile Streaming :: Medium (@Ivan: Fast or HQ mode?)
-Apple iTunes 4.2 128kbps
-FAAC "whatever VBR setting comes close to 128kbps"
-Compaact! "same thing as above"
-Winamp AAC encoder 128kbps

Perhaps you will stick with them, as that selection should give you a smattering of the various AAC encoders. I trust your judgment on this rjamorim

  • westgroveg
  • [*][*][*][*][*]
AAC @ 128kbps listening test discussion
Reply #29
What about FhG AAC ?

I'm sure we can get permission / find a way to encode samples for test purposes

  • MGuti
  • [*]
AAC @ 128kbps listening test discussion
Reply #30
nero is very important
i would like to see real as compared to itunes
FAAC is a must (NCTU-AAC was based on FAAC i believe)
throw in winamp if you really want to
for the anchor use the itunes MP3 (we know it sucks and will act as a comparison between itunes AAC and MP3)

just my opinion, as long as nero, itunes, and faac are in there i'll be happy.

  • rjamorim
  • [*][*][*][*][*]
AAC @ 128kbps listening test discussion
Reply #31
Quote
What about FhG AAC ?

I'm sure we can get permission / find a way to encode samples for test purposes

Well, I agree that would be interesting, but I am not fond of testing codecs noone else has access to.

I mean, so what that it won, I can't use it anyway... :/
Get up-to-date binaries of Lame, AAC, Vorbis and much more at RareWares:
http://www.rarewares.org

  • Dologan
  • [*][*][*][*]
  • Members (Donating)
AAC @ 128kbps listening test discussion
Reply #32
I support Roberto's initial codec choices fully, including l3enc as lower anchor. 
More than six codecs is absolutely insane and those that ask for it have probably never participated fully in one of Roberto's tests, or have an unhealthy amount of free time and patience.
None of the other choices IMO merits the place of any of the initially chosen contestants, since they are either 1) In beta or not-quite-final state 2) not really popular or relevant enough.

  • schnofler
  • [*][*][*]
  • Developer
AAC @ 128kbps listening test discussion
Reply #33
I also think Roberto's choice of codecs is nice as it is. The only other codec I'd be interested in, is the NCTU codec, for the same reason Bonzi stated in the second post of this thread (proving that listening tests are superior to ODG results). But none of the codecs of the original line-up seems debatable to me, with the possible exception of compaact (but I'd prefer testing a serious contender instead of just slapping some encoder which isn't really used anyway).
Lame as an anchor is a bad idea in my opinion. Not only because it might repeat the "Xing disaster", but because it would considerably increase the difficulty of the test and it's difficult enough as it is right now. With Lame there'd be six real codecs instead of five codecs and one ... well ... joke. And it will help general motivation if there's at least one codec everyone should be able to identify.

Now to an interesting question
Quote
-Should only LC be tested? Or maybe test other (better?) profiles when the encoder supports them, like FAAC and Compaact. I think an argument for this would be that it's like VBR vs. CBR - you shouldn't penalize some codecs because others lack that feature. A very good argument against this would be that LC is waaaay more supported now and probably in the future. Opinions?

I haven't really made up my mind about that one. The problem, of course, is that a comparison between an LC codec and one which uses additional tools will be completely useless to people who plan on using AAC on their portables. But it might also provide a very interesting outlook into the future. The latter, though, only holds if we can really expect considerable advantages from using the additional features. I'd really like to hear some comments from the developers on this. If the advantages are only slim, there's no point in using them, in my opinion. But if we can really expect a definite increase in quality, maybe it would be interesting to have FAAC use them, to see how it compares to the supposedly better, but then somewhat handicapped, commercial encoders.
But these are only some thoughts, I haven't really decided for myself yet whether that's a good idea.

  • Gabriel
  • [*][*][*][*][*]
  • Developer
AAC @ 128kbps listening test discussion
Reply #34
About the anchor:

I would very much like to see Lame in this test, as this would allow us (and me) to see how it performs against current AAC codecs.

However, it would make the test harder, and with less defined scale. Using something that we think will really be a low anchor is a better idea. This way the scale of notation will probably be more uniform.
Using l3enc 1.0 is, from an "historical" point of view very interesting.

So even if I would be interested to see Lame compared to AAC codecs, I think that it would be better for the purpose of this test (which is to compare AAC codecs) to use another anchor. I like the idea of l3enc 1.0.

  • bond
  • [*][*][*][*][*]
AAC @ 128kbps listening test discussion
Reply #35
doesnt faac maybe do well as "anchor" (maybe bringing the same or worse quality as lame)?
I know, that I know nothing (Socrates)

  • kl33per
  • [*][*][*][*][*]
AAC @ 128kbps listening test discussion
Reply #36
Obviously both the Apple and Nero codecs should be included, to see how they've each progressed since the last test.  Furthermore, I think compaact should definately been included, and as it seems to be undergoing fairly regular development as well as trying to establish an active user base here at HA, I think it's time we got an evaluation of it's quality.  I would also like to see how far FAAC has come being a free alternative.  Finaly, I'm probably most interested in the NCTU codec for the reasons Bonzi has stated.  As Winamp should be similar to iTunes (and apparantly Real as well) I think it should be dropped.  I think the anchor is also good choice and is deffinately a requirement.

On the issue of Lame.  Clearly in the last Multiformat test, LAME was behind by a fair margin.  Furthermore, this is specifically a AAC test and should not feature other formats.
  • Last Edit: 08 February, 2004, 07:57:55 AM by kl33per
www.sessions.com.au - Sessions Entertainment

  • dev0
  • [*][*][*][*][*]
  • Developer
AAC @ 128kbps listening test discussion
Reply #37
Quote
doesnt faac maybe do well as "anchor" (maybe bringing the same or worse quality as lame)?

FAAC has improved a lot recently and a lot of people will be suprised to hear how well it performs at 128kbps.
I've already found samples on which it performs better than LAME and I wouldn't be suprised, if their overall performace would turn out to be similiar. This is pure speculation though and not backed up by any tests (yet).
Gabriel's idea of including LAME seems very interesting to me, but LAME's performance is probably too good to serve as an anchor.

dev0
"To understand me, you'll have to swallow a world." Or maybe your words.

  • Gabriel
  • [*][*][*][*][*]
  • Developer
AAC @ 128kbps listening test discussion
Reply #38
Quote
Gabriel's idea of including LAME seems very interesting to me


Did you read my post? Perhaps I did not managed to properly expose my opinion?

  • ErikS
  • [*][*][*][*][*]
AAC @ 128kbps listening test discussion
Reply #39
1. Who uses Compaact? What's the reason behind including it in this test? (Not intending to sound demeaning in any way - just curious since I never seen it being used anywhere...)

2. Please replace the Rite of Spring sample! It drives me mad... 

  • rjamorim
  • [*][*][*][*][*]
AAC @ 128kbps listening test discussion
Reply #40
Quote
2. Please replace the Rite of Spring sample! It drives me mad... 

No problem. But please suggest another sample to replace it

Edit: Woot! 4444 posts
  • Last Edit: 08 February, 2004, 08:58:40 AM by rjamorim
Get up-to-date binaries of Lame, AAC, Vorbis and much more at RareWares:
http://www.rarewares.org

AAC @ 128kbps listening test discussion
Reply #41
Hi,

you all know I am biased. That said, I would really like to see compaact! in this test. Surely it has not so much users as Nero, but it is only 3 months old, and we are a very small company, not being able to make so much marketing. I personally think that compaact! has potential for being a popular encoder.

Regarding different profiles:
The main profile is not useless, it gives higher quality than the LC profile. However, the quality increase is not great (but of course greater than with the silly LTP profile).
I personally think every competing encoder should give its best, regarding settings and profiles in this test. But again, I'm biased...

Regards,
Alexander
zplane.development
http://www.zplane.de

AAC @ 128kbps listening test discussion
Reply #42
Well, I think the following codecs should be included:
  • Nero
  • iTunes
  • FAAD
  • Winamp
  • Real
I would either use l3enc or LAME for the 6th encoder.

  • Latexxx
  • [*][*][*][*][*]
AAC @ 128kbps listening test discussion
Reply #43
  • Nero
  • iTunes
  • Real
  • FAAC
  • Compaact
  • Anchor

  • knik
  • [*]
  • Developer
AAC @ 128kbps listening test discussion
Reply #44
Quote
I am personally very fond of the idea of using l3enc as anchor. It'll be a good insight on how perceptual audio coding developed since the first MP3 implementation. It'll be like "the oldest vs. the newest".

I would vote to use FAAC1.17 as an anchor since it's much worse than latest FAAC and it could be interesting to compare both versions.
If you don't like FAAC1.17 then I would vote for LAME to be an anchor
(even if it turns out not to be the worst it's still very interesting comparison)

Quote
I wouldn't like to replace Waiting. I love that sample for it's wacky behaviour, so I want to force you guys to listen to it over and over again until your ears pop out of your skull :B

Yes, Waiting is definitely not to be removed.

Quote
-Should only LC be tested? Or maybe test other (better?) profiles when the encoder supports them, like FAAC and Compaact. I think an argument for this would be that it's like VBR vs. CBR - you shouldn't penalize some codecs because others lack that feature. A very good argument against this would be that LC is waaaay more supported now and probably in the future. Opinions?

Those other profiles in FAAC are likely to be broken so it shouldn't be used.

  • MGuti
  • [*]
AAC @ 128kbps listening test discussion
Reply #45
since this will be a 128 test HE for nero won't help. im not sure what the main profile for AAC really is (and no idea what the difference is for LC). i think that all codecs should use LC simply because it is the setting that can be used on portables.  i don't know about anyone else, but the only time i would encode to 128 is if i had limited space on a portable. otherwise i would aim for a transparancy setting.

i think an early version of FAAC is a good idea. i would like to see how the open source encoder has progressed. besides won't lame be against AAC and the other codecs in the next multiformat test? there is no point in using it as an anchor since is might end up like Xing. pick a truely poor encoder.

Nero
itunes (real and winamp are assumed to be similar)
FAAC
compaact
NCTU-AAC (real or winamp could replace, but since NCTU doesn't use short blocks - or something to that effect - i would like to see how it performs)
FAAC 1.17 - anchor

oh, and will there be an vorbis test before the multiformat test to compare the various tunes?
  • Last Edit: 08 February, 2004, 10:41:47 AM by MGuti

  • dev0
  • [*][*][*][*][*]
  • Developer
AAC @ 128kbps listening test discussion
Reply #46
I'm completely opposed to including NCTU, until they have sorted out their licensing issues.
rjamorim's original selection seems to be the most sensible to me and l3enc would probably do fine as an anchor.

dev0
"To understand me, you'll have to swallow a world." Or maybe your words.

  • magic75
  • [*][*][*][*][*]
AAC @ 128kbps listening test discussion
Reply #47
Quote
Quote
Quote
well ... you mean it to be an anchor ... but what happened to xing? ...

Blah!!!

Please consider all the bad comments on Xing done here and elsewhere over the years, and then come tell me I did a bad choice!

it sure it was a good choice, but it, turning not into the anchor, didn't harm the test ... 

Well, I don't think you can compare it like that. Xing was chosen because pretty much everybody thought it would fail miserably. You can't say the same thing about Lame in this test. Using Lame here is to much risk messing up the point of the test: Which is the best AAC encoder?

In the MP3 case I think we were lucky to have iTunes serving as a "light" anchor.

And I guess we will see Lame against the AAC winner in the next multi-format test?

  • rjamorim
  • [*][*][*][*][*]
AAC @ 128kbps listening test discussion
Reply #48
Quote
I'm completely opposed to including NCTU, until they have sorted out their licensing issues.

According to them, they already sorted it out (I.E, started developing an encoder from scratch and gave up developing from Faac)

But still, due to their quite immoral past behaviour, I'm not very inclined to take them seriously and test their encoder.

About Faac 1.17: It has already been tested in the first AAC@128kbps test, so you can use that test to compare how it fared against others. I don't see much point testing an old version again.

But, in MP3's case, I would really like to know how it sounded when it was premiered

Quote
And I guess we will see Lame against the AAC winner in the next multi-format test?


Of course. I hoped to test another encoder since Lame was already tested in the former multiformat test. But since it won the MP3 test... heh

Actually, I think that's another good reason not to test Lame here. It has been tested in the 128kbps extension test, the 64kbps test, the MP3 test, will be tested in the next multiformat test... :B
Get up-to-date binaries of Lame, AAC, Vorbis and much more at RareWares:
http://www.rarewares.org

  • Tomb
  • [*][*][*]
  • Members (Donating)
AAC @ 128kbps listening test discussion
Reply #49
This may seem a stupid question but does the Quick Time Professional AAC Codec differ from the I-Tunes one or are they one and the same? I thought I read somewhere that there were slight differences but I cannot remember where I read this!

Depending on the answer I would like to see:
  • Nero
  • Quick Time
  • FAAC
  • Compaact
  • Winamp
  • Anchor
  • Last Edit: 08 February, 2004, 11:29:49 AM by Tomb