I noticed an issue testing out cdrdao and I haven't seen this in the cdrdao bug tracker. I'm hoping someone can check what I'm doing.
In the cdrdao man page there is an example TOC file, that will write the file "pregapdata.wav" as pregap region in track and "track.cdr" starting at 1:0:0 with a length of 1:0:0 as the main track data.
CD_DA
TRACK AUDIO
FILE "pregapdata.wav" 0
START
FILE "track.cdr" 1:0:0 1:0:0
[ignore rest of cmds...]
The bug I see, is that I have a TOC file setup the same way, yet when I scan the cdrdao written disc, using EAC, it reports a 0 pregap length for the track (in my case the track is not the 1st one which has a mandatory 0:2:0 pregap)
So playing around with this TOC, i thought maybe there was an issue with actually setting the START value inside of the track. So I changed my TOC to specifiy the length of the pregap track and the length of the pregap, now it looks like this:
CD_DA
TRACK AUDIO
FILE "pregapdata.wav" 0 1:0:0
START 1:0:0
FILE "track.wav" 0
So, I thought this would surely work, but instead cdrdao will give up before even starting:
ERROR: test.toc:4: START 01:00:00 behind or at track end.
Well, finally I figured there was only one piece of data missing, the length of "track.wav". So, after adding the length of "track.wav" cdrdao finally burns the track correctly and EAC confirms that there is a pregap of 1 minute The final TOC looks like this:
CD_DA
TRACK AUDIO
FILE "pregapdata.wav" 0 1:0:0
START
FILE "track.wav" 0 1:0:0
In the final case it was OK to remove the START length value. Also, I checked if the "pregapdata.wav" length was removed, then it goes back to the 2nd case failure. Any comments?