Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #236341 > unrolled thread

cdrskin: burn cdda with cue sheet file

Back to article view | Back to linux.debian.user

Contents

  cdrskin: burn cdda with cue sheet file Michael Lange <klappnase@freenet.de> - 2021-06-23 11:20 +0200
    Re: cdrskin: burn cdda with cue sheet file Reco <recoverym4n@enotuniq.net> - 2021-06-23 11:30 +0200
      Re: cdrskin: burn cdda with cue sheet file "Thomas Schmitt" <scdbackup@gmx.net> - 2021-06-23 12:30 +0200
        Re: cdrskin: burn cdda with cue sheet file The Wanderer <wanderer@fastmail.fm> - 2021-06-23 12:50 +0200
          Re: cdrskin: burn cdda with cue sheet file The Wanderer <wanderer@fastmail.fm> - 2021-06-23 13:10 +0200
            Re: cdrskin: burn cdda with cue sheet file "Thomas Schmitt" <scdbackup@gmx.net> - 2021-06-23 13:40 +0200
          Re: cdrskin: burn cdda with cue sheet file "Thomas Schmitt" <scdbackup@gmx.net> - 2021-06-23 13:10 +0200
        Re: cdrskin: burn cdda with cue sheet file Michael Lange <klappnase@freenet.de> - 2021-06-23 18:20 +0200
          Re: cdrskin: burn cdda with cue sheet file "Thomas Schmitt" <scdbackup@gmx.net> - 2021-06-23 19:10 +0200
            Re: cdrskin: burn cdda with cue sheet file Michael Lange <klappnase@freenet.de> - 2021-06-23 19:30 +0200

#236341 — cdrskin: burn cdda with cue sheet file

Hi,

I am trying to burn a bunch of WAV files onto an audio CD with cdrskin
using a cue-file. The only reference about how to create these files I
could find is at
https://web.archive.org/web/20151223114027/http://digitalx.org/cue-sheet/
where under "Examples" example no. 3 shows how to create a cue file with
multiple source files. So for testing I tried a cue file with the
following contents:

PERFORMER "Unbekannter Interpret"
TITLE "Unbekanntes Album"
FILE "/home/klappnase/Musik/Japan/Barbara/Barbarous Virginity/01 Can! Can! Can!.wav" WAVE
  TRACK 01 AUDIO
    PERFORMER "Unbekannter Interpret"
    TITLE "01 Can! Can! Can!"
    INDEX 01 00:00:00
FILE "/home/klappnase/Musik/Japan/Barbara/Barbarous Virginity/02 Life in Heaven.wav" WAVE
  TRACK 02 AUDIO
    PERFORMER "Unbekannter Interpret"
    TITLE "02 Life in Heaven"
    INDEX 01 00:00:00
FILE "/home/klappnase/Musik/Japan/Barbara/Barbarous Virginity/03 Dest.wav" WAVE
  TRACK 03 AUDIO
    PERFORMER "Unbekannter Interpret"
    TITLE "03 Dest"
    INDEX 01 00:00:00

According to that digitalx.org page this looks "legal" to me, however
it does not work, instead I get the following eror:

cdrskin: FAILURE : In cue sheet file: Multiple occurrences of FILE

So my question is:
is there any reference how to set up a cue sheet for cdrskin that shows
how it should be done, or is this simply not possible using a cuefile?

Thanks in advance, and best regards

Michael

.-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.

Our missions are peaceful -- not for conquest.  When we do battle, it
is only because we have no choice.
		-- Kirk, "The Squire of Gothos", stardate 2124.5

[toc] | [next] | [standalone]

#236342

	Hi.

On Wed, Jun 23, 2021 at 11:09:29AM +0200, Michael Lange wrote:
> According to that digitalx.org page this looks "legal" to me, however
> it does not work, instead I get the following eror:
> 
> cdrskin: FAILURE : In cue sheet file: Multiple occurrences of FILE

cdrskin(1) says:

cuefile=path
Read a session description from a cue sheet file in CDRWIN format. Base
the tracks on a *single file* which is given in the sheet by command FILE.

> So my question is:
> is there any reference how to set up a cue sheet for cdrskin that shows
> how it should be done, or is this simply not possible using a cuefile?

Your best option is to merge your files into one big file and to produce
an appropriate .cue for that file.

Reco

[toc] | [prev] | [next] | [standalone]

#236344

Hi,

Michael Lange wrote:
> > https://web.archive.org/web/20151223114027/http://digitalx.org/cue-sheet/
> > cdrskin: FAILURE : In cue sheet file: Multiple occurrences of FILE

Reco wrote:
> cdrskin(1) says:
> a *single file* which is given in the sheet by command FILE.

Indeed. cdrskin expects a single FILE command in the CUE file.
That's how i have read the CDRWIN CUE descriptions years ago.

The above web page about cue-sheet says
  "FILE commands must appear before any other command except CATALOG.
   This rule contradicts the examples on this site: Note"

The plural of "commands" might mean that more than one FILE command is
allowed, which the CUE file interpreter shall concatenate.
cdrskin does not do that. But the same effect can be achieved by following
Reco's proposal to concatenate the files before the cdrskin run.


> > is there any reference how to set up a cue sheet for cdrskin

Besides the man page text about option cuefile= with its list of supported
CUE file commands, there is
  https://sources.debian.org/src/libburn/1.5.2-1/doc/cdtext.txt/#L650

--------------------------------------------------------------------------

The intention of supporting CUE files in cdrskin was to handle the case of
a single input data file and multiple tracks.

The case of a 1:1 relation between input files and tracks is served by the
cdrecord-ish style of submitting multiple track sources and the non-cdrecord
option input_sheet_v07t=.
See the man page of cdrskin for input_sheet_v07t= and the example
  Write audio tracks and CD-TEXT to CD:

Further there is an example at
  https://sources.debian.org/src/libburn/1.5.2-1/doc/cdtext.txt/#L600


Have a nice day :)

Thomas

[toc] | [prev] | [next] | [standalone]

#236345

[Multipart message — attachments visible in raw view] — view raw

On 2021-06-23 at 06:26, Thomas Schmitt wrote:

> Hi,
> 
> Michael Lange wrote:
>> > https://web.archive.org/web/20151223114027/http://digitalx.org/cue-sheet/
>> > cdrskin: FAILURE : In cue sheet file: Multiple occurrences of FILE
> 
> Reco wrote:
>> cdrskin(1) says:
>> a *single file* which is given in the sheet by command FILE.
> 
> Indeed. cdrskin expects a single FILE command in the CUE file.
> That's how i have read the CDRWIN CUE descriptions years ago.

That strikes me as intuitively wrong, just based on terminology.

I have always intuitively understood the term "cue sheet" to be derived
in some way from the context of stage and/or screen acting, and to refer
to a list of items which are to be cued up and the order in and timing
with which they are to be so cued up. That necessarily implies not only
the possibility of having multiple items in the list, but indeed that it
probably would not usually make sense to bother with the sheet if there
were only going to be one item.

https://www.ascap.com/news-events/articles/2005/cuesheets seems to, at
least approximately, back up that conception.

I have never (that I recall) encountered cdrskin prior to reading this
thread, but if I had encountered a program that limited cue sheets to
having only one entry, I would have immediately considered that a
definitional bug - quite possibly on the design level.

If a "cue sheet" in an optical-media-creation context is indeed supposed
to be limited to only one item, then I severely question the choice of
that term (by whoever made that choice, all those years ago).

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man.         -- George Bernard Shaw

[toc] | [prev] | [next] | [standalone]

#236346

[Multipart message — attachments visible in raw view] — view raw

On 2021-06-23 at 07:02, Thomas Schmitt wrote:

> Hi,
> 
> The Wanderer wrote:
> 
>> I have always intuitively understood the term "cue sheet" to be
>> derived in some way from the context of stage and/or screen acting
> 
> I think it stems from the name of the data structure by which the
> layout of a SAO-Session is described to the drive by the SCSI command
> SEND CUE SHEET.

That would just push the question of where the name came from back and
up one level, then...

> It is supposed to be followed by a sequence of WRITE(10) commands 
> which deliver the payload data as a single unstructured stream.

...and that would, at least at a glance, seem to make it seem even
*more* like the term doesn't really fit the way it's being applied.

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man.         -- George Bernard Shaw

[toc] | [prev] | [next] | [standalone]

#236350

Hi,

i wrote:
> > [SEND CUE SHEET] is supposed to be followed by a sequence of WRITE(10)
> > commands which deliver the payload data as a single unstructured stream.

The Wanderer wrote:
> ...and that would, at least at a glance, seem to make it seem even
> *more* like the term doesn't really fit the way it's being applied.

According to MMC-6 of 2010 complaints about SCSI nomenclature should probably
be sent to

  INCITS Secretariat
  National Committee for Information Technology Standards
  Information Technology Institute
  1101 K Street NW, Suite 610
  Washington DC 20005

The term slipped through the X3T10 Technical Committee in 1997 when they
wrote MMC-1, the optical drive section of SCSI-3. Probably it stems from
an earlier manufacturer-specific set of CD burner commands.


Have a nice day :)

Thomas

[toc] | [prev] | [next] | [standalone]

#236347

Hi,

The Wanderer wrote:
> I have always intuitively understood the term "cue sheet" to be derived
> in some way from the context of stage and/or screen acting

I think it stems from the name of the data structure by which the layout
of a SAO-Session is described to the drive by the SCSI command SEND CUE
SHEET. It is supposed to be followed by a sequence of WRITE(10) commands
which deliver the payload data as a single unstructured stream.


Have a nice day :)

Thomas

[toc] | [prev] | [next] | [standalone]

#236378

Hi,

On Wed, 23 Jun 2021 12:26:46 +0200
"Thomas Schmitt" <scdbackup@gmx.net> wrote:

> Hi,
> 
> Michael Lange wrote:
> > > https://web.archive.org/web/20151223114027/http://digitalx.org/cue-sheet/
> > > cdrskin: FAILURE : In cue sheet file: Multiple occurrences of FILE
> 
> Reco wrote:
> > cdrskin(1) says:
> > a *single file* which is given in the sheet by command FILE.
> 
> Indeed. cdrskin expects a single FILE command in the CUE file.
> That's how i have read the CDRWIN CUE descriptions years ago.

> The above web page about cue-sheet says
>   "FILE commands must appear before any other command except CATALOG.
>    This rule contradicts the examples on this site: Note"

thanks for pointing this out, looks like I should have read more
carefully.

(...)
> 
> The case of a 1:1 relation between input files and tracks is served by
> the cdrecord-ish style of submitting multiple track sources and the
> non-cdrecord option input_sheet_v07t=.
> See the man page of cdrskin for input_sheet_v07t= and the example
>   Write audio tracks and CD-TEXT to CD:

Actually I had thought about that first, but wasn't able to find a way to
add pregaps to the audio tracks, should I wish to do so.
Now looking again I saw the sao_pregap command which might do exactly
that (I'm not 100 per cent sure about its usage, though). I tried a dummy
run with the following command:

cdrskin -v -dummy -eject dev=/dev/sr0 -sao speed=10 track1.wav \
	sao_pregap=75 track2wav sao_pregap=225 track3.wav track4.wav

Is my assumption correct that this will add a 1-second pregap before
track2 and a 3-second pregap before track3 and no pregap before track4?
Or did I get that wrong?

> 
> Further there is an example at
>   https://sources.debian.org/src/libburn/1.5.2-1/doc/cdtext.txt/#L600

Thanks, I'll look into that.

Best regards

Michael

.-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.

You!  What PLANET is this!
	-- McCoy, "The City on the Edge of Forever", stardate 3134.0

[toc] | [prev] | [next] | [standalone]

#236379

Hi,

Michael Lange wrote:
> cdrskin -v -dummy -eject dev=/dev/sr0 -sao speed=10 track1.wav \
>         sao_pregap=75 track2wav sao_pregap=225 track3.wav track4.wav
>
> Is my assumption correct that this will add a 1-second pregap before
> track2 and a 3-second pregap before track3 and no pregap before track4?

I hope so. :))
This stuff was implemented and tested in 2012. But there was few feedback
from users since then. Bit rot is always a risk in such situations. (Last
was in 2019 and caused libburn 1.5.0-1+deb10u1.)

You will have to invest a real medium (CD-RW would avoid plastic waste)
and then check with the actual CD players whether the options fulfilled
your expectations.

----------------------------------------------------------------------

If they do not what we expect, then please re-run cdrskin with
additional option -V and redirect standard error to a file. Like:

  cdrskin -V -v ... track4.wav 2>&1 | tee -i /tmp/cdrskin_scsi_log

If you only have CD-R, then use option -dummy. If you have a CD-RW it would
be better to see the SCSI command log of a real burn run.

Send file /tmp/cdrskin_scsi_log to my mail address directly. No need to clog
the list with a large file that mostly contains boring bytes.
The main objects of interest will be the MODE SELECT command with the
Mode Page 5 data and the SEND CUE SHEET command with the cue sheet data.


Have a nice day :)

Thomas

[toc] | [prev] | [next] | [standalone]

#236380

Hi,

On Wed, 23 Jun 2021 19:05:45 +0200
"Thomas Schmitt" <scdbackup@gmx.net> wrote:

> Hi,
> 
> Michael Lange wrote:
> > cdrskin -v -dummy -eject dev=/dev/sr0 -sao speed=10 track1.wav \
> >         sao_pregap=75 track2wav sao_pregap=225 track3.wav track4.wav
> >
> > Is my assumption correct that this will add a 1-second pregap before
> > track2 and a 3-second pregap before track3 and no pregap before
> > track4?
> 
> I hope so. :))
> This stuff was implemented and tested in 2012. But there was few
> feedback from users since then. Bit rot is always a risk in such
> situations. (Last was in 2019 and caused libburn 1.5.0-1+deb10u1.)
> 
> You will have to invest a real medium (CD-RW would avoid plastic waste)
> and then check with the actual CD players whether the options fulfilled
> your expectations.

thanks, according to my CD-player apparently you did a good job, the
pregaps seem to be just like they should :-)

Alas, I just encountered another problem, which does not belong
into this thread though (I am afraid I might finally have to buy me a new
drive :)

Thanks again, and best regards

Michael


.-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.

Sometimes a feeling is all we humans have to go on.
		-- Kirk, "A Taste of Armageddon", stardate 3193.9

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web