I mentioned this a while back more or less in passing, but I thought it might be useful to re-visit the matter of creating CD tracks.
There are a number of ways this might be implemented (of course Justin may not wish to implement any scheme) but here are some possibilities.
1. Going the whole hog - When rendering to wave, create a CD track cue at each point that a marker is in the project file, complete with marker label for CD text, by having the right stuff written in the cue-points chunk of the rendered wave file.
2. Going not quite so far - Provide for the generation of a separate "cue sheet" based on the markers in the project file. This can then be used in programs such as Nero and EAC which support cue sheets to put the CD tracks in the right places. Furthermore, "CueListTool" (natty freeware program from
http://www.stefanbion.de/cueltool/index_e.htm ) can take a cue sheet and insert its contents into a wave file as cue data, thus avoiding the need to build that function into Reaper.
3. Going somewhere in between - exactly the same as (2) above, but extend the info stored with markers beyond just the plain description. The Cue Sheet format provides for a number of fields and by having more than just the "name" field attached to each Reaper marker, these could also be used. A good summary of the format of cue sheets is at
http://en.wikipedia.org/wiki/Cue_sheet
4. Alternatively, in the render dialog, have a tickbox for "split file at markers" so that the rendered file would be broken up into filename_tk1, filename_tk2, filename_tk3 etc etc, which could then be dragged into Nero or whatever to compile the CD. However, that doesn't provide very well for CD text which personally I use a lot, and it's nice to end up with just one wave file with associated cue sheet to burn to CD rather than a stack of smaller waves.
================================================== ==
Creating a cue sheet from a Reaper project file could actually be a separate utility which someone other than Justin could put together - it's just text manipulation, and the location of markers is clearly set out in a small part of the project file text. However, it would be perhaps neatest if in the "Render" dialog there were to be a "creat cue sheet" tickbox which would create a ".cue" file matching the requested output filename for the render operation.
An extended approach to markers would provide for a marker window, listing the markers, their locations and their labels (and any other fields) and providing for jumping to any marker in the project when double-clicked in the marker window - also, editing of the marker data would also be handy in such a window. But perhaps that's one for version 2.0.
It's a personal workflow thing, but I'm about to start editing a concert recording lasting about 1h50mins and would love to try it in Reaper. However, there are lots of points in the concert needing separate CD tracks, and although I can mark them in Reaper as I locate them in the editing process, once the project is rendered I'd have to find them all again manually in the rendered wave file and use CueListTool to put in the CD track markers. Of course I could be guided by the list in the Reaper project file, but it's a bit of an inelegant and timeconsuming way of doing it.
Whatever (if any) method does get used, the importance of having CD tracks at frame boundaries (75 frames per sec for CD) should be borne in mind to avoid clicks at CD tracks. So CD tracks should be made to fall at the nearest frame boundary before the actual marker location.