Does Otto's iTunesEncode work with beta 10's converter function? It's not working for me, although it works fine with version 8.3. I'm trying to convert a flac file to m4a using the parameters -i %s -o %d and iTunes 4.8.

Any ideas? Did I miss something in search?

I just tried and it worked for me - although I had to resort to "Convert to same directory" as I curiously wasn't getting a dialogue using "Convert to...".

I am on iTunes 6 though.

When you say it doesn't work, in what way? Does the WAVE file get created?

I changed the bit rate from 24 to 16 and it worked.

I get the convert to dialog box, btw.

At 24 bits, the temp wav file was created, but itunes didn't do anything when launched and I'd get a foobar error message: Error flushing file (Object Not Found) : file://C:\dir\filename.m4a

Ah, yes. I suppose I should have confirmed my setup.

I'm glad it is now working anyway.

I've no idea about my dialogue box, I may just need a reboot or something... I've never had the problem before.

By the way, how's the encoding speed in iTunes 6.0 compared to 4.8?

I'm sorry - I've only used it for testing.

Interesting. I suppose iTunes can't handle 24 bit WAV files. Or, at least, iTunes 4.8 can't. Might be worth trying with a newer version of iTunes.

FWIW, iTunesEncode doesn't even so much as open the input file, it just passes the filename along to iTunes.

I would have thought iTunes would display an error message if fed a file it couldn't handle.

I've been hesitant to install newer versions, out of concern for foo_pod compatibility and because I thought the QT encoder in 6.0 was much slower than the older encoders.

Thanks for the program. It makes encoding much easier.

If iTunesEncode gets an error from the call to iTunes, then it will spit out an "Error of some kind occured at such and such point" and return an error code to the shell. So if the calling program is checking error codes, it will know something fouled up. This assumes the calling program checks the error code, though. EAC can check those, but doesn't necessarily have to (I think it's a setting somewhere).

In any case, it will probably make iTunesEncode spit out an error message, but the message won't be particularly informative.

Works great (bless your heart, Otto42) in beta 10 and .83 for me. With latest iTunes (v.6.013) too AND TAGS WORK - - Yeehah I'm a happy camper now.

See my post under topic: Itunesencode, Tagging & Itunes - Help!
Good luck.