libcdio-devel
[Top][All Lists]
Advanced

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

Re: [Libcdio-devel] Ready for merging: libcdio branch trackno-higher-one


From: Thomas Schmitt
Subject: Re: [Libcdio-devel] Ready for merging: libcdio branch trackno-higher-one
Date: Fri, 28 Dec 2018 20:13:49 +0100

Hi,

Rocky Bernstein wrote:
> it would be great to
> create a test for this change. As with libcdio-paranoia I guess this would
> include a CD image of the right sort.

We could make a new .cue file with content

  FILE "cdda.bin"  BINARY
    TRACK 07 AUDIO
      FLAGS DCP
      INDEX 01 00:00:00
    TRACK 08 AUDIO
      FLAGS DCP
      INDEX 01 00:02:00

libcdio has files test/cdda.bin and test/data/cdda.bin.
libcdio-paranoia has test/data/cdda.bin.
All with identical content of 302 frames = 00:04:02.

But i did not test whether this .cue file content would cause the various
CD burner programs to write track 7 and 8 rather than 1 and 2.
(At least with cdrskin option "cuefile=" i am optimistic.)

How would a new .cue file be used for testing in libcdio ? I am quite
clueless in front of test/check_cue.sh.in and test/check_common_fn.in.


I tried above .cue content as file
  test/data/cdda_track_4_5.cue
and ran

  cd test && ../src/cd-info --no-device-info --cue-file data/cdda_track_4_5.cue

But this refused to work because of missing file cdda_track_4_5.bin until
i created a link

  ln -s ./cdda.bin ./test/data/cdda_track_4_5.bin

So does cd-info not read the FILE name from .cue ?

(The displaid track numbering is wrong: 1 and 2 instead of 4 and 5.
 Are Edd's changes for libcdio already merged in ?)


Have a nice day :)

Thomas
 



reply via email to

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