"Render item as new take" question

so quick question... On a track I have an number of items of dialogue that are a bit noisy. I have used noise filtering plugins on each of the items individually to remove said noise. To apply the noise filtering to the item I hit "Render item as new take". This creates a new take of the same item, with the noise filtering applied, and thus no FX chain attached to the new item. Of course the original item remains as take 1 and the new rendered item is take 2. My question in this - Will REAPER still process the FX on take 1 (original item) when take 2 is selected? The plugin I use is Z-Noise which induces a PDC of 38400 (quite a lot!) so I hope that REAPER is no longer processing it when take 2 is selected, but I don't know how I can check if it is... That is all, thanks :)

I don't know the specific answer to your question but can you not render to a new track, with fx appled and mute the original or at least disable the effects? Kind Regards, Fleet

No, it shouldn't take CPU cycles but it might take some RAM (you can also set each FX offline to avoid this RAM usage).

That is what I generally thought. I should have noted though, my main concern is the PDC. REAPER tends to do some strange things with the PDC when video is involved. sometimes it doesn't all stay in sync. If take 2 is selected and the FX on take 1 isn't being processed, does it mean that the PDC for the FX on take 1 isn't being applied as well? Again, I hope it isn't.

Just solo the track you're rendering your items on. On playback, check the CPU hit before the render, then after the render. A significant increase would suggest take 1 is being rendered against the effect. My guess would be that only the selected take is being processed. Regards, DB

To answer the OP question, I would think that , as Reaper has per ITEM fx (and not per take fx), that FX are also applied to the second take. You could create a macro that renders as new take and then disable the fx on that item. Yves

This may be dependent on whether you have the preference "run fx on stop" ticked or not. Not only do I not get unused takes not taking up CPU but even the used ones stop processing audio once the file has passed and therefore no longer use CPU. One hint is that sometimes it's best to unloop the item and pull it's right side out so it still processes a few secs after. Helpful if the item fx is reverb.