SEARCH
NEW RPMS
DIRECTORIES
ABOUT
FAQ
VARIOUS
BLOG

BotDetect - Real-Time Bot Detection API
 
 

MAN page from OpenSuSE cdrdao-1.2.5-356.4.x86_64.rpm

CUE2TOC

Section: User Commands (1)
Index

 

NAME

cue2toc - convert CUE to TOC format

 

SYNOPSIS

cue2toc [-hnqv] [-otocfile][-wwavefile] [cuefile]

 

DESCRIPTION

Cue2tocconvertscuefilefrom CUE to TOC format and writes the result totocfile.If eithercuefile or tocfileis omitted or a single dash "-"cue2tocreads from standard input and writes to standard ouputrespectively.

CUE files are text files describing the layout of a CD-Rom andtypically carry the extension ".cue".

Cdrdao is a CD-burning application which has its own native TOCformat to describe the disc layout. Although cdrdao has directsupport for reading CUE files, it is currently limited to datatracks only. Socue2toc'smain usefulness lies in convertingCUE files containing audio tracks.

Output of CD-Text data can be disabled with the-noption.

CUE files often come with MP3 files but since cdrdao doesntsupport decoding them on the fly they probably must be decoded byother means prior to writing the CD (e.g. usinglame).For this reason you can specify a filename with the-woption to be used for all audio tracks instead of the onein the CUE file. Of course this is only really useful if allthe tracks are based on the same file. This seems to be the casequite often however.

Cue2tocnormally displays warning messages for unsupported commands andconstructs. The-qoption disables these warnings.

 

OPTIONS

-h
print a short help message

-n
no CD-Text; disable output of CD-Text information

-o tocfile
write result totocfileinstead of standard ouput

-q
quiet mode; do not print warnings

-v
print version number

-w wavefile
usewavefilefor all audio tracks

 

CUE FORMAT

What follows is a description of the CUE format expected bycue2toc.For information about the TOC format please consult thecdrdao(1)manual page.

CUE files consist of commands and their arguments which must beseparated from each other by any number of whitespace characters.Space, horizontal tabulator, newline and carriage return arerecognized as whitespace characters except inside strings surroundedby double quotes, where they are part of the string. Commands arenot case sensitive. CD-Text data can be at most 80 characters peritem.

Timecode values are accepted in the forms "X:X:X", "X:X" and"X" where each "X" must consist of at most two digits and may bezero padded to the left. They are interpreted as "M:S:F", "S:F" and"F" respectively where "M" means "minutes" and must be in the range0 <= M <= 99, "S" means "seconds" and must be in the range0 <= S <= 59, and "F" means "frames" and must be in the range0 <= F <= 74.

CUE files are logically divided into a global section andone to 99 track sections. Inside these sections the followingcommands are allowed:

 

Global Section

REManything_to_newline
CATALOGstring
CDTEXTFILEstring
TITLEstring
PERFORMERstring
SONGWRITERstring
FILEstringBINARY|MOTOROLA|AIFF|WAVE|MP3

REM
Optional.Introduces a comment. Anything from there on up to and including thenext newline character is ignored. Comments can appear anywhere inthe file but not between a command and its arguments.

CATALOG
Optional.The Media Catalog Number of the disc. Must be exactly 13 characters.

CDTEXTFILE
Optional.Specifies an external file containing CD-Text data. Ignored.

TITLE
Optional.The CD-Text title of the disc.

PERFORMER
Optional.The CD-Text performer of the disc.

SONGWRITER
Optional.The CD-Text songwriter of the disc.

FILE
Required.The name and type of the file to be used for all following tracks.Thestringcontains the name of the file followed by one ofBINARY, MOTOROLA, AIFF, WAVE or MP3.As far ascue2tocis concerned the type of the file is effectively ignored.NonethelessMOTOROLA, AIFF and MP3cause printing of a warning message since these file types cannot be used directly with cdrdao.

The first appearance of aTRACKcommand causes leaving of the global section and entering thetrack section.

 

Track Section

TRACKnumbermode
REManything_to_newline
FLAGS[DCP][4CH][PRE][SCMS]
ISRCstring
TITLEstring
PERFORMERstring
SONGWRITERstring
PREGAPtimecode
INDEXnumbertimecode
POSTGAPtimecode
FILEstringBINARY|MOTOROLA|AIFF|WAVE|MP3

TRACK
Required.Starts a new track definition. Thenumberis ignored. Themodemust be one ofAUDIO, MODE1/2048, MODE1/2352,MODE2/2336 or MODE2/2352.

FLAGS
Optional.Defines the flags for this track. Must be followed by oneor more of the following commands:DCP(digital copy permitted),4CH(four channel audio),PRE(pre-emphasis enabled) andSCMS(serial copy management system).SCMSis ignored because there is no corresponding option inthe TOC format.

ISRC
Optional.The International Standard Recording Code for this track. Mustbe exactly 12 characters long.

TITLE
Optional.The CD-Text title of this track.

PERFORMER
Optional.The CD-Text performer of this track.

SONWRITER
Optional.The CD-Text songwriter of this track.

PREGAP
Optional.The length of the track pregap to be filled with zero data.Mutually exclusive withINDEX 0.

POSTGAP
Optional.The length of the track postgap to be filled with zero data.

INDEX
Optional.Thenumbermust be in the range 0 <=number<= 99. Index number 1 specifies the start of the track. Indexnumber 0 is the start of the track pregap filled with datafrom the file, i.e. the difference between index 0 and index 1is the length of the pregap. Index 0 is mutually exclusive withPREGAP.Index numbers greater than 1 specify subindexes for this trackand must be sequential.

FILE
Optional in track section. The syntax is the same as describedabove and if it appears inside a track specification it takeseffect on the nextTRACKcommand.

 

LIMITATIONS

The commandCDTEXTFILEand the flagSCMShave no equivalent in the TOC format and are ignored.

CUE files containing data tracks which specify a starting timegreater than zero cannot be converted bycue2tocbecause the TOC format does not provide a way to specify astarting time at all for data tracks. However if the CUE filedoes not contain any audio tracks you can try to use the CUE filedirectly with cdrdao.

 

EXAMPLE

Suppose we have the following CUE file "uwe.froehn.cue" describingan audio CD with CD-Text data:

REM Example CUE file with audio tracksCATALOG 1234567890123TITLE "Der Berg ruft"PERFORMER "Uwe Froehn"FILE "uwe.froehn.mp3" MP3TRACK 01 AUDIO  TITLE "Meine Mama ist die Beste"  PERFORMER "Uwe Froehn"  SONGWRITER "Hansi Klabuster"  REM two seconds pregap filled with audio data  INDEX 00 00:00:00  INDEX 01 00:02:00  REM subindexes  INDEX 02 00:35:17  INDEX 03 01:12:44TRACK 02 AUDIO  TITLE "Hoch oben im Tal"  SONGWRITER "Gabi Geil"  REM no pregap  INDEX 01 02:45:38TRACK 03 AUDIO  REM pregap with zero data  PREGAP 00:4:47  INDEX 01 07:58:74  REM postgap with zero data  POSTGAP 00:35:00

Since cdrdao cannot decode the MP3 file on the fly this step mustbe carried out by hand, e.g. using lame:

lame --decode uwe.froehn.mp3 uwe.froehn.wav

Although the filename appears only once in the example CUEfile it gets written for every track in the TOC file so youwould need to edit lots of occurences of the filename in theTOC file by hand. For this reason you can specify a stringwith the-woption to be used bycue2tocas the filename for all audio tracks. The command

cue2toc -w uwe.froehn.wav -o uwe.froehn.toc uwe.froehn.cue

should produce the file uwe.froehn.toc with the following content:

CATALOG "1234567890123"CD_DACD_TEXT {    LANGUAGE_MAP {        0 : EN    }    LANGUAGE 0 {        TITLE "Der Berg ruft"        PERFORMER "Uwe Froehn"    }}TRACK AUDIO    CD_TEXT {        LANGUAGE 0 {            TITLE "Meine Mama ist die Beste"            PERFORMER "Uwe Froehn"            SONGWRITER "Hansi Klabuster"        }    }    AUDIOFILE "uwe.froehn.wav" 00:00:00 02:45:38    START 00:02:00    INDEX 00:35:17    INDEX 01:12:44TRACK AUDIO    CD_TEXT {        LANGUAGE 0 {            TITLE "Hoch oben im Tal"            SONGWRITER "Gabi Geil"        }    }    AUDIOFILE "uwe.froehn.wav" 02:45:38 05:13:36TRACK AUDIO    PREGAP 00:04:47    AUDIOFILE "uwe.froehn.wav" 07:58:74    SILENCE 00:35:00

 

SEE ALSO

cdrdao(1),lame(1)

 

BUGS

Sincecue2toc'sdefinition of the CUE format is entirely based on a numberof different CUE files the author came across there is a veryhigh probability that it will not work correctly with all theother CUE files you might encounter. If this is the case foryou please send the problematic CUE file along with the versionnumber ofcue2tocto <dermatschAATTgmx.de>.

 

AUTHOR

Matthias Czapla <dermatschAATTgmx.de>


 

Index

NAME
SYNOPSIS
DESCRIPTION
OPTIONS
CUE FORMAT
Global Section
Track Section
LIMITATIONS
EXAMPLE
SEE ALSO
BUGS
AUTHOR

This document was created byman2html,using the manual pages.
 
ICM Bot detect detector