Thanks OnBeat, great tip.
Though; I think Nuendo’s RenderInPlace is designed like the “consolidate”-feature in ProTools, and Nuendo’s “bounce” is designed as PT’s “commit”?
Consolidate/RIP is some kind of exporting the clips like how they would sound through the output of the track they sit on, including all of its automation, and commit/bounce is rendering the clips with only the clip’s parameters like gain, envelope and fades, pitch, clip-effects (=offline processing), right?
When I use a noise-reduction plugin like “Cedar DNS One” in an insert in PT and then “Consolidate” a couple of clips from that track, PT returns these clips on a new track with the noise reduction applied , in just a couple of seconds…
…Why does this same procedure in Nuendo take insanely long (more than 20 minutes)?
And; why does Nuendo return 1 long clip instead of separate clips?
Is there something I’m not getting here, especially in my “expectation” (explained above) from the RIP-features?
I would love to have a workflow where I could actually USE the RIP-feature in order to share my clips with other people, just like you do, without using the bounce-workaround, which wouldn’t work for me since I’m using plugins with a learn-function, and I’m using plugins’ automation.
Thanks, Niek/ Amsterdam.