I read with interest a conversation in the help section about the possiblility of ‘Freezing’ tracks to an instrument to save CPU.
This is a great idea and would probably be quite easy to implement. After freezing a range to an instrument you could then choose to keep/mute/delete the pattern data or whatever. Very handy for those with slow CPUs or very heavy sequences.
I hope that Renoise gets a direct-from-disk feature at some point. Rendering large ranges to a disk-streamed file would be great.
I envisage a new screen within renoise much like the sample editor but instead multitrack… with basic editing tools etc.
When the user selects a range of pattern data to render to disk it appears in the multitrack view along a timeline that follows the pattern time.
The basic editing tools could be used to move that data around the timeline … cut/copy/paste sections and also to mix together (or bounce) sections down into a new track.
Looking a little deeper into this idea and some new thoughts :
A non-destructive approach would be cool. Where the original freeze/render becomes the parent file and all edits to this file are stored and undo-able.
Also the parent file could contain all the pattern data that was selected for the render. This would mean that the user could go into the multitrack view and actually edit the pattern data and re-render if he/she wanted to make some changes (but had long ago deleted the pattern data from the main view).
Of course if VSTi or samples had been moved/deleted since the render was done the pattern would not play back as before. This is a reasonable limitation I think … but :
To get around this the parent file could contain references to any samples or VSTi that had been used in it’s creation … it could get them into a temporary bank whos structure would be dictated by the state of the main instrument bank when the ‘freeze’ or ‘render’ was made.