#121 read-toc produces incorrect index numbers

reproducible
open
nobody
5
2004-01-19
2004-01-19
Anonymous
No

when producing a toc file from a disc that has indexes
above 1, the resulting file numbers the indexes
incorrectly, even though the output messages generated
by cdrdao numbers them correctly.
for example, the following snippet of output was sent
to the screen during read-toc...

Analyzing track 08 (AUDIO): start 24:49:32, length
09:29:23...
Found index 2 at: 00:57:08
Found index 3 at: 02:32:30
Found index 4 at: 04:20:25
Found index 5 at: 06:40:33
Found 95 Q sub-channels with CRC errors.
Found ISRC code.
Control nibbles of track match CD-TOC settings.

and the resulting .toc file contains this...

// Track 8
TRACK AUDIO
NO COPY
NO PRE_EMPHASIS
TWO_CHANNEL_AUDIO
ISRC "GBAYE9801901"
FILE "data.wav" 24:49:32 09:29:23
INDEX 00:57:08
INDEX 02:32:30
INDEX 04:20:25
INDEX 06:40:33

Obviously these index numbers don't work. This is just
one example, there are others as well.
I'll attach the entire .toc file in case it helps.

Discussion

  • Nobody/Anonymous

    generated .toc file

     
  • Nobody/Anonymous

    Logged In: NO

    then of course it's entirely possible that I've not had
    enough caffiene today. my brain parsed
    INDEX 02:32:30
    as "index 2 is at some time offset" instead of "the next
    index, without being speficically numbered, starts just over
    2 minutes into the track".
    ugh.

    The only real bug here is that toc2cue can't do anything
    sensible with this. The .toc itself seems fine afterall.

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks