rinri
/
cuetools-jp
1
0
Fork 0
Code Issues 0 Pull Requests 0 Releases 0 Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
269 Commits
1 Branch
296 KiB
 
 
 
 
 
 
Branch: master
Branches Tags
${ item.name }
Create branch ${ searchTerm }
from 'master'
${ noResults }
cuetools-jp/doc/cuebreakpoints.1

100 lines
2.4 KiB
Raw Permalink Blame History 

  1. .TH "cuebreakpoints" "1"

  2. .SH NAME

  3. cuebreakpoints \- report track breakpoints from a CUE or TOC file

  4. .SH SYNOPSIS

  5. .B cuebreakpoints

  6. [ {

  7. .B \-i

  8. .I format

  9. |

  10. .BR \-\-input\-format =\fIformat\fP

  11. } {

  12. .B \-\-append\-gaps

  13. |

  14. .B \-\-prepend\-gaps

  15. |

  16. .B \-\-split\-gaps

  17. } ]

  18. [

  19. .I file

  20. \&... ]

  21. .br

  22. .B cuebreakpoints \-h | \-\-help

  23. .br

  24. .B cuebreakpoints \-V | \-\-version

  25. .SH DESCRIPTION

  26. .B cuebreakpoints

  27. reports the track breakpoints found in CUE and TOC files, which are

  28. typically created by compact disc ripping software.

  29. The breakpoints are in a format usable by

  30. .B shnsplit

  31. (part of the shntool package).

  32. .PP

  33. Three approaches to track pregaps are available: append (to previous track),

  34. prepend (to succeeding track), and split (from both preceding and

  35. succeeding tracks).

  36. The split approach can result in up to twice as many breakpoints being

  37. reported as there are tracks on the disc.

  38. .PP

  39. The first track's pregap cannot be appended to the previous track, so it is

  40. prefixed to the track in both append and prepend modes.

  41. If you want the track without it, use the

  42. .B \-\-split\-gaps

  43. option.

  44. .PP

  45. If no filenames are specified,

  46. .B cuebreakpoints

  47. reads from standard input, and an input format option

  48. .I must

  49. be specified.

  50. If one or more filenames is provided, but the input format option is not

  51. specified, the input format will be guessed based on each file's suffix

  52. (e.g.,

  53. .I .cue

  54. or

  55. .IR .toc ).

  56. This heuristic is case-insensitive.

  57. .SH OPTIONS

  58. .TP

  59. .BR \-h ", " \-\-help

  60. displays a usage message and exits.

  61. .TP

  62. .BR \-i " \fIformat\fP, " \-\-input\-format=\fIformat\fP

  63. sets the expected format of the input file(s) to

  64. .IR format ,

  65. which must be either

  66. .B cue

  67. or

  68. .BR toc .

  69. .TP

  70. .B \-\-append\-gaps

  71. appends pregaps to the end of the previous track.

  72. This is the default.

  73. .TP

  74. .B \-\-prepend\-gaps

  75. prefixes pregaps to the beginning of each subsequent track.

  76. .TP

  77. .B \-\-split\-gaps

  78. separates pregaps from both the preceding and succeeding tracks.

  79. .TP

  80. .B \-V, \-\-version

  81. displays version information and exits.

  82. .PP

  83. If more than one of

  84. .BR \-\-append\-gaps ,

  85. .BR \-\-prepend\-gaps ,

  86. and

  87. .B \-\-split\-gaps

  88. are specified, all except the last encountered are ignored.

  89. .SH "EXIT STATUS"

  90. .B cuebreakpoints

  91. exits with status zero if it successfully generates a report for each

  92. input file, and nonzero if there were problems.

  93. .SH AUTHOR

  94. Cuetools was written by Svend Sorensen.

  95. Branden Robinson contributed fixes and enhancements to the utilities and

  96. documentation.

  97. .SH "SEE ALSO"

  98. .BR cueconvert (1),

  99. .BR cueprint (1)