LAME woes

[Michael Zacherl.]

I think I know what's going on: LAME doesn't support 24bit AIF ... 24bit WAV is ok.
well ... need sleep - further testing tomorrow.
m.

On May 26, 2010, at 02:44 , Michael Zacherl. wrote:

> I think I could narrow it down ... it's not entirely consistent though:
> Earier I suspected something like the byte order - at least the sound reminded me on that type of error.
> I did some test files and the one not working has 24 bit data.
> Well ... LAME can't handle 24bit files?
> iTunes does.
> Admittedly the built-in help didn't enlighten me.
> 
> (what's up with the different settings, I dunno)
> 
> Michael.
> 
> On May 25, 2010, at 21:30 , Tony Hardie-Bick wrote:
> 
>> Aaarggh,
>> 
>> I seriously would like to know what the issue is, but have no idea.
>> 
>> I have had zero problems with lame - apart from VBR load probs on small non-FP 
>> ARM players, years ago. It all works just great, all files play back perfectly, 
>> everywhere, and to an exceptionally high audio quality.
>> 
>> But I always run from a command line, on Linux, when creating mp3s.
>> 
>> Any further info much appreciated.
>> 
>> Tony (HB)
>> 
>> Michael Zacherl. wrote:
>>> Hi All,
>>> 
>>>  I installed iTunes-LAME on my MBP and it's not working properly:
>>> 
>>> http://code.google.com/p/blacktree-itunes-lame/downloads/list
>>> 
>>> The script itself works, its nicely integrated with iTunes 9.
>>> I also can run the encoder within the shell (Terminal).
>>> 
>>> In both cases the generated MP3 is faulty.
>>> It's shorter and very noisy ... as if white noise was superimposed.
>>> 
>>> I know the sound when data bytes were shuffled so I used the -x option but this didn't change anything.
>>> 
>>> Funnily enough it was intermittend first - the proposed default setting is -h -b 160 (-h is the same as -q 2).
>>> So I set it to -b 320 and it worked. 
>>> Then I started to experiment with the quality setting (-q) and regardless to what value I set it, it starts going mad.
>>> Meanwhile its not intermitted anymore ... even the plain -b 320 setting doesn't work - also within the shell (commandline).
>>> 
>>> I deleted the .plist file (prefs) and started over - to no avail.
>>> 
>>> Any clue what's going on?
>>> 
>>> thanks,  Michael. 


--
noise chasers: http://blauwurf.at