Mark Lanctot;128109 Wrote: > I'm not sure if it's this FLAC version, but I've been having some > problems with the encoder. > > On the last two albums I've ripped, FLAC stalls at a certain point > through encoding the WAV. The progress reading freezes. Something's > still going on because the processor load remains high. > > It could be a glitch in the WAV but even WAVs off a damaged CD have > encoded well before (although they didn't sound good). > > I'm reverting back to the released version to see if this clears up.
Interesting, I thought I had been using this encoder successfully since this thread was first started, but I see the "Mark of the past" had problems here. Today I tried encoding a file that choked this encoder. This time I can verify there are NO problems with the WAV file - earlier IIRC the problems went away when I re-ripped. This time it doesn't matter how often I re-rip. EAC indicates no errors and so does AccurateRip. I PMed Josh Coalson about this, because if this optimization is included in FLAC 1.1.3 the issue may pop up again. The encode crashes at 100% - the encoder freezes. The resultant FLAC seems to play OK in foobar, but searching within the file causes a 1/2 second pause. At the end of the file, foobar shows a stream error. FLAC -t shows an end of stream error at 98%. Everything works fine when the file is encoded with the original 1.1.2 though. Incidentally the experimental encoder has encoded about a thousand tracks without incident. -- Mark Lanctot ------------------------------------------------------------------------ Mark Lanctot's Profile: http://forums.slimdevices.com/member.php?userid=2071 View this thread: http://forums.slimdevices.com/showthread.php?t=22658 _______________________________________________ ripping mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/ripping
