I ran into this problem, too and FINALLY solved it. FLAC would also randomly skip some tracks while ripping a CD, even though it claimed they were fine. If you told it to leave the WAV, it would have WAVs of everything but only FLACs of some.It's all in the command line. As you know, the FLAC arguments are:
%s --tag=artist="%1" --tag=album="%2" --tag=tracknumber="%3" --tag=title="%4" --tag=date="%6" --tag=genre="%7" --tag=comment="%8"
This are much more wordy than most other encoders, hence people not getting this problem more often. If you throw out all the tag stuff and just use %s, you'll find that every track rips (if you are having the same problem I was).
After much experimenting, I found that AG must have a very short buffer for the command line. Shorter than what windows accepts, at least. I got around it by creating my own batch file and using that instead.
My batch file looks like this:
code:
@echo off
c:
cd\flacs
c:\bin\flac.exe %1 --tag=artist=%2 --tag=album=%3 --tag=tracknumber=%4 --tag=title=%5 --tag=date=%6 --tag=genre=%7 -o %8
if exist %8 del %1
Then go into AG and set the encoder to user defined and point it at the batch file. Set the arguments to this:
code:
%s "%1" "%2" "%3" "%4" "%6" "%7" "%1 - %2 - %3 - %4.flac"
Now as you can probably see, these are imperfect solutions. I will eventually go back and make it a bit nicer. First, I had to harcode the output directory in the batch file. Second, I had to harcode the output filename as "%1 - %2 - %3 - %4.flac". This kind of sucks since these variables can still contain unsuable filename characters like slashes and colons. So that's why I have it only delete the wav file in the batch file if the flac file was successfully created. That makes it easy for me to go and hand fix the few that fail.
I also ditched the comment field because I never use it.
So though it is an imperfect solution, I hope it can help you out. I think I'll email in a request that that buffer be lengthened so this isn't necessary.