cuebreakpoints(1)

πŸ’– cuebreakpoints β€” the manual page, but make it make sense πŸ’–

okay bestie, welcome to cuebreakpoints(1), a lil utility from the General Commands Manual, and no cap it's about to be your new fave. πŸŽ€


✨ NAME ✨

cuebreakpoints β€” report track breakpoints from a CUE or TOC file πŸ¦‹


🌸 SYNOPSIS 🌸

cuebreakpoints [ { -i format | --input-format=format } { --append-gaps |
--prepend-gaps | --split-gaps } ] [ file ... ]
cuebreakpoints -h | --help
cuebreakpoints -V | --version

πŸ’… DESCRIPTION πŸ’…

so basically, cuebreakpoints reports the track breakpoints it finds in CUE and TOC files. those files are typically created by compact disc ripping software, so if you've ever ripped a CD you already know the vibe. ✨ and the breakpoints come out in a format that's usable by shnsplit (which is part of the shntool package) β€” so like, it feeds your splitter directly, we love a pipeline moment. πŸ”₯

there are three approaches to track pregaps and you will be picking one:

  • append β€” to the previous track
  • prepend β€” to the succeeding track
  • split β€” from both the preceding and succeeding tracks

heads up tho: the split approach can result in up to twice as many breakpoints being reported as there are tracks on the disc. it's giving "more is more" but for real, that's the deal. 😭

also, the first track's pregap cannot be appended to the previous track (there is no previous track, bestie, it's the first one πŸ’€). so it gets prefixed to the track in both append and prepend modes. if you want the track without it, use the --split-gaps option. that's the move. πŸ‘‘

one more thing: if no filenames are specified, cuebreakpoints reads from standard input, and an input format option must be specified. if one or more filenames is provided, but the input format option is not specified, the input format will be guessed based on each file's suffix (e.g., .cue or .toc). and this heuristic is case-insensitive, slay. 🌈


πŸŽ€ OPTIONS πŸŽ€

  • -h, --help β€” displays a usage message and exits. short and sweet, iconic behaviour. πŸ’–
  • -i format, --input-format=format β€” sets the expected format of the input file(s) to format, which must be either cue or toc. that's it, those are the only two, don't try anything else. 🫢
  • --append-gaps β€” appends pregaps to the end of the previous track. this is the default, so if you do nothing, this is what you get. ⭐
  • --prepend-gaps β€” prefixes pregaps to the beginning of each subsequent track. 🧚
  • --split-gaps β€” separates pregaps from both the preceding and succeeding tracks. the chaotic one. πŸ’…
  • -V, --version β€” displays version information and exits. πŸ¦‹
ok so if more than one of --append-gaps, --prepend-gaps, and --split-gaps are specified, all except the last encountered are ignored. last one wins, periodt. don't come crying to me when your first two flags ghosted you. 😭

πŸ“ EXIT STATUS πŸ“

cuebreakpoints exits with status zero if it successfully generates a report for each input file, and nonzero if there were problems. so like, zero = we ate, nonzero = something is up. πŸ”₯


πŸ‘‘ AUTHOR πŸ‘‘

Cuetools was written by Svend Sorensen. Branden Robinson contributed fixes and enhancements to the utilities and documentation. absolute legends, both of them. 🌟


🌈 SEE ALSO 🌈

go read those too bestie, iykyk. πŸ’œ


and that's the whole page fr fr β€” this was cuebreakpoints(1) from the General Commands Manual. mwah, take care of her. πŸŽ€πŸ’–βœ¨