Rendering & export
Turning performances into files — loops, clips, and finished pieces.
Rendering in rip chopper is deliberately unexciting: the file you get is the performance you saw. All the drama went into making that sentence true.
What renders
- A capture selection — the usual path. Select a range in the capture editor and press Render; you get a video clip of that performance, picture composited exactly as the canvas showed it, audio mixed with your lane settings.
- A loop — the same, with the loop toggle on (it’s on by default): the render is built to repeat seamlessly, and lands on a pad as a loopable instrument.
- A single layer — one lane bounced by itself, either composited in the canvas frame (with transparency, for reuse in other tools) or at the layer’s original dimensions.
- A combined clip — two or more clips fused into one.
Where renders go
Onto pads, mostly. A render isn’t an export so much as a consolidation: the ten-pad jam becomes one clip, which is easier to play, layer, and re-chop. Files live in your project and can always be revealed in Finder for use anywhere else.
Loops that actually loop
Seamless looping is harder than it looks — codecs round audio durations, and a loop that’s 40 milliseconds long wraps audibly out of phase within a minute. rip chopper renders loop audio in a lossless sidecar with the exact duration the loop needs, so a rendered loop cycles cleanly for as long as you leave it running.
You’ll never think about this. That’s the point.
Fidelity promises
Worth restating from Core concepts: renders are driven by the same envelope math, the same layer ordering, and the same clock as live playback. A release tail you heard fades in the file. A clip that faded in over its attack fades in the render. The canvas layout you arranged is the layout you get.