QUOTE(askoff @ Jul 25 2006, 06:11)

Those samples where about 30 seconds long and many of them had spots where the bitrate was under 128 kbps. The whole sample was tested and one could look out the audible difference anywhere in the sample. When you look at the scoreboard and the results which are close to 5, you have to think, how many of the all (more or less trained) listeners didn't hear any difference. Those results show's that it's very highly a likely that the sample is transparent to it's casual listener. You should take a look at those samples yourself to see how close to transparency they actually are.
I don't doubt that they are (when I get a working audio interface I'll listen, for sure; At the minute I have nothing but terrible internal laptop speakers, so I'd be lucky to ABX 64kbps!) I'm not questioning that those samples are transparent because I have no reason to suspect they might not be, and no way of checking. Since I hadn't read this test before, my first statement was not based on it whatsoever and thus doesn't attempt to comment on it at all.
QUOTE(Garf @ Jul 25 2006, 07:54)

What is the point of making the test simpler if a) the encoders are already performing so well most people can't hear differences b) they are all good enough that it's almost impossible to determine who's better.
Using easier samples would indeed lower the bitrate, but won't cause any problems for the encoders either. Think about what happens when the encoder mis-guesses the difficulty of an easy sample, and what happens when he mis-guesses the difficulty of a hard sample.
I don't say make the test simpler, I say test the lower bitrates of that setting; if it misguesses an easy sample and thinks that it's easier than it really is, surely that's just as likely to cause problems as if it misguesses a difficult sample and thinks it's easier than it really is?
QUOTE(Jebus)
Anyhow, you made a claim, we refuted it, and now you need to provide evidence to counter ours. Otherwise your claim that 128kbit/s isn't enough is unsubstantiated at best.
QUOTE(I)
Ok, so I was [...] incorrect
I've admitted I was wrong and if I didn't before, now I apologise for misleading the original poster; I'm almost certain that the last time I looked at such tests (it may have been some time ago...) they were nothing like so positive, and I was surprised when I saw that one; not keeping up with later tests may not be an excuse, but it's certainly a reason. By admitting being wrong, surely I'm taking back the statement I made? Since I have seen tests that go some way to contradict it, there's little point in my trying to continue. What I will do is continue questioning until I find out why samples with bitrates falling toward the lower end being tested.