QUOTE(marbo @ Jan 28 2007, 13:18)

The thing is, I had a working setting. But due to some crashes and a new installation .... The former setting worked as an on-the-fly encoding and the files are perfect. So I'm still after that string/setting! Is it possible that a string/setting working in Flac1.1.2 does not in 1.1.3?
I'm having the exact same problem--had it working perfectly for months, then did a new install of my operating system, and the now track time for all my on-the-fly FLAC files are messed up (maximum allowable, i.e. 3:22:54)
I still have my old install on another laptop drive, and I reinstalled that drive tonight, took screen shots of all my old settings, copied my old parameter string into a text file and then took all this information and tried to set up my new installation. Then I read all the tips and forum postings I could find via Google. Still no dice.
I'm going to put the old drive back in again and check what version of FLAC I was using, even though everything seems to be pointing to CDex not sending an accurate timing in the header to FLAC.exe. I'm still using CDex 1.51 by the way.
If anyone can diagnose my trouble, I'd be most grateful. Here's my string, the one that worked perfectly for me on my last install:
-8 -V -o %2 -T "artist=%a" -T "title=%t" -T "album=%b" -T "date=%y" -T "tracknumber=%tn" -T "genre=%g" -
I've got "On the Fly Encoding" and "Send WAV header to stdin" checked; I have ID 3 tag version set to "None", and I don't have "Don't delete ripped WAV file after conversion" checked.
Edit: I've installed 1.70 beta2, and that might be the answer to my problems. Anyone have opinions about this version vis-a-vis on the fly FLAC encoding?
Cheers,
N