Next step is auto-sync the freezed pattern-sample to pattern length, than auto-apply slicing and run dblue’s ‘slices to pattern’ script ( New Tool (2.7 & 2.8): Slices To Pattern ) to have the freezed sample cut-up in the pattern again.
This will be incorporated into the next version, which should be arriving ‘soon’.
However, as the sample will be launched from the first pattern, if this pattern plays again later in the song sequence the sample will restart at that point.
This is not the required behaviour, so the tool will do a quick check to identify if the pattern in sequencer slot 1 is re-used later and if so will abort and instruct the user how to work around it (duplicate first pattern and make it unique).
There doesn’t appear to be any script access to track headroom value so the value is hard coded to Renoises default setting. There isn’t anything I can really do about this, sorry!
The volume and panning would then then ‘stack up’ (accumulate). i.e. If a track is panned hard right at -18db, then this will be observed in the rendering (the render will only have audio in the right channel and at -18db).
Setting the frozen track to 0db, center panning will result in the same output as the original track.
Good idea! I’ll look into adding this also.
As a general note, thanks for all the positive feedback
Either the linear mode isn’t working or the pattern mode, but it renders pattern by pattern in all cases.
Multi-track selection mode wouldn’t be a wrong thing either, in case some instrument plugins are routed to other tracks than the track that contains the notes for it.
And a minor correction:
-- We can only load 120 'notes' worth of patterns
if #renoise.song().patterns > 119 then
renoise.app():show_error("Sorry, track freezing currently only supports up to 120 patterns.")
You can load 256 samples if you would use the layering as well.
Are you copying Send devices over to the new track?
People need to be aware that if they were using a Signal Follower on the original track this will affect things assuming it was controlling a parameter on another track. Only way around this would be, in the even of their being a Signal Follower (with destination outside of original track, although this could be achieved through a Hydra) is to then copy the original track including DSP chain. Then delete all DSPs after the Signal Follower (except any Hydras just in case) then add a Gainer with -inf at the end to silence output.
Second point is probably far too much to worry about with this tool and best people consider the fact they may be using the track for more than it’s own audio themselves!