Public 128 kbit/s Extension Test
 

Harri Mellin in uk.rec.audio:

In article ,
ff123 wrote:

That's why a blind testing utility is used:

http://ff123.net/abchr/abchr.html

for Windoze only and windows users


Maybe writing the gui in java would have been a good idea, with native
codecs.

--
Jim H
3.1415...4999999 and so on... Richard Feynman

Public 128 kbit/s Extension Test
 

"Jim H" wrote in message

Harri Mellin in uk.rec.audio:

In article ,
ff123 wrote:

That's why a blind testing utility is used:

http://ff123.net/abchr/abchr.html

for Windoze only and windows users


Maybe writing the gui in java would have been a good idea, with native
codecs.

For programs of this (modest) level of complexity, Java is way too slow on
most contemporary machines.

Public 128 kbit/s Extension Test
 

Arny Krueger in uk.rec.audio:

"Jim H" wrote in message

Harri Mellin in uk.rec.audio:

In article ,
ff123 wrote:

That's why a blind testing utility is used:

http://ff123.net/abchr/abchr.html

for Windoze only and windows users


Maybe writing the gui in java would have been a good idea, with
native codecs.

For programs of this (modest) level of complexity, Java is way too
slow on most contemporary machines.




I disagree. But java is, in general written very badly, swing particuarly
so.

There were a lot of big performance gains in the 1.2 reference virtual
machine and API implementation, for example reflection was sped up nearly
20x. With a JIT compiler the efficiency of java is very close to that of
the native platform.

All that is needed here is a very simple program. I don't want to be drawn
into a long OT discusion of programing languages but I'm certain java would
be acceptably fast on a recent VM.

--
Jim H
3.1415...4999999 and so on... Richard Feynman