When you render a track but choose to keep the original, it would be useful if the original was muted, and all filters disabled.
When you render a track, you are typically preserving CPU, but when you keep the original track you want to keep your options open just in case....
FR: Render track features
-
- KVRAF
- 2028 posts since 18 Mar, 2004 from New York, N.Y.
-
- KVRAF
- 1615 posts since 28 Mar, 2005
no need to disable the filters. If I'm not mistaken filters on muted tracks don't use any CPU.
-
- KVRAF
- 6490 posts since 14 Jun, 2004 from Rochester, NY
I agree. Okay he means to diable all filters to render simply the raw audio. I would use this a lot since I do mixing down, I could show the client A and B, one raw unmixed the other mixed so they can see why they should continue workign with me.
RonC
RonC
-
- KVRAF
- Topic Starter
- 2028 posts since 18 Mar, 2004 from New York, N.Y.
No, I really did mean to disable filters. On some plugins my CPU spikes until I disable it, even if the track is muted. Maybe this is only with troublesome plugins, I believe it has happened with Amplitube. Correct me if I'm wrong.
And I do mean to render it WITH the filters. This is the most basic use for rendering...to hear the effects without losing CPU...
And I do mean to render it WITH the filters. This is the most basic use for rendering...to hear the effects without losing CPU...