libcdio-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Libcdio-devel] CD-Text patches


From: Thomas Schmitt
Subject: Re: [Libcdio-devel] CD-Text patches
Date: Sun, 25 Dec 2011 20:29:13 +0100

Hi,

a few weeks ago i concluded that my LG burner drives would not write
CD-TEXT. Different from drives by Samsung, LITE-ON, Optiarc.

This conclusion was wrong. CD-TEXT is not significant in this case.
The reason for the refusal is rather in the short tracks which are
defined in file test/data/cdtext.cue and in a yet unexplained peculiarity
of wodim with the command
  wodim -v dev=/dev/... -dao -text cuefile=cdtext.cue

MMC prescribes:
 "Each track has a minimum length of 4 seconds, not including the pause
  length preceding the track."
The LG drives are entitled by MMC to refuse on the CUE SHEET that
wodim sends them:
  0 : 01 00 00 41 00 00 00 00
  8 : 01 01 00 00 00 00 00 00
 16 : 01 01 01 00 00 00 02 00
 24 : 01 02 00 00 00 00 04 00
 32 : 01 02 01 00 00 00 06 00
 40 : 01 03 00 00 00 00 08 00
 48 : 01 03 01 00 00 00 0A 00
 56 : 01 AA 01 01 00 00 0E 06
All three tracks preceded by a pre-gap of 2 seconds which wodim takes
from the payload data. So only 2 seconds remain for the payload part.

If i double the size of test/data/cdtext.bin and also double the
addresses of the INDEX lines in test/data/cdtext.cue then my LG
drives accept the CUE SHEET of wodim and write CD-TEXT to the medium.


So i would propose to do this size doubling in libcdio test/data too.
E.g.
  cat cdtext.bin cdtext.bin >cdtext_x2.bin
  mv cdtext_x2.bin cdtext.bin
and in cdtext.cue:
  CDTEXTFILE "cdtext.cdt"
  FILE "cdtext.bin" BINARY
    TRACK 01 AUDIO
      INDEX 01 00:00:00
    TRACK 02 AUDIO
      INDEX 01 00:08:00
    TRACK 03 AUDIO
      INDEX 01 00:16:00


I believe wodim's CUE SHEET generator is buggy. It is seems to cut off
the first two seconds of each track, as if they were claimed by INDEX 00.

The one of cdrskin resp. libburn does not cause the LG drives to refuse.
My .cue file reader is now able to perform the libcdio test. I was
quite puzzled when a try on LG succeeded that was intended to fail.

  cdrskin -v dev=/dev/... -dao -text cuefile=cdtext.cue
produces this CUE SHEET with acceptable track lengths:
  0 : 01 00 00 41 00 00 00 00
  8 : 01 01 01 00 00 00 00 00
 16 : 01 01 01 00 00 00 02 00
 24 : 01 02 01 00 00 00 06 00
 32 : 01 03 01 00 00 00 0A 00
 40 : 01 AA 01 01 00 00 0E 06


Have a nice day :)

Thomas




reply via email to

[Prev in Thread] Current Thread [Next in Thread]