because I like using Linux/UNIX and the terminal, wanted to try doing something in Python, and learn a thing or two about CDs and disc images, I started writing my own Cue sheet to CU2 sheet conversion tool. I figure, one or the other here might find it useful, as some don't have a Windows machine in reach at all times or don't want to use Wine.
I released Cue2cu2 on GitHub as open source software. Feel free to try it out (at your own risk). I'm keen on your guys' feedback!
I quote the Readme file:
Matt and Yuri, are the mentioned inconsistencies maybe a bug? As I don't know what exactly the PSIO does internally, I have no idea if this is really how the timecodes in the CU2 sheet should look like.By default, Cue2cu2 uses the compatibility mode, and thus, aims to create a CU2 sheet that is identical to what the PSIO System Console would output. While the resulting CU2 sheets seem to work fine with the PSIO, they appear to be inconsistent. Each track's starting position is 2 seconds behind the position noted in the original cue sheet, and "trk end" is 6 seconds beyond the bin file's end. Disabling compatibility mode uses the timecodes from the original cue sheet as well as seemingly correct values for size, data1 and trk end. However, as of writing this, it is unconfirmed if/what is the reason behind the timings per PSIO System Console. Thus, the non-compatibility mode is to be treated as experimental and subject to change.
For comparison, here are (shortened) CU2 sheets for Destruction Derby 2:
Compatibility mode, identical to PSIO System Console output:
Code: Select all
ntracks 19 size 61:30:06 data1 00:02:00 track02 06:59:49 (...) track19 58:06:60 trk end 61:34:06
Code: Select all
ntracks 19 size 61:28:06 data1 00:00:00 track02 06:57:49 (...) track19 58:04:60 trk end 61:28:06
I haven't tested non-compatibility mode CU2 sheets on my PSIO yet, as I consider compatibility the highest priority for Cue2cu2 and the non-compatibility mode very experimental until I have feedback from Matt and Yuri.