|
Post by MorEQsThanAnswers on May 15, 2019 17:17:55 GMT -6
Pro Tools lets you bypass and "make inactive." Can you deactivate individual plugins in Logic, or can you only turn off the whole track?
Thanks!
|
|
|
Post by wiz on May 15, 2019 17:24:24 GMT -6
Pro Tools lets you bypass and "make inactive." Can you deactivate individual plugins in Logic, or can you only turn off the whole track? Thanks! Hi I think by DSP you mean CPU .... I bypass plugins in logic, CPU usage drops. Cheers Wiz
|
|
|
Post by MorEQsThanAnswers on May 15, 2019 17:51:12 GMT -6
Pro Tools lets you bypass and "make inactive." Can you deactivate individual plugins in Logic, or can you only turn off the whole track? Thanks! Hi I think by DSP you mean CPU .... I bypass plugins in logic, CPU usage drops. Cheers Wiz Thanks man. Edited to minimize trolling hahah
|
|
|
Post by jampa on May 15, 2019 20:08:46 GMT -6
Wiz makes a good point. What happens when you monitor the CPU meter?
|
|
|
Post by georgetoledo on May 15, 2019 20:17:32 GMT -6
Generally, but I think that if you disable a virtual instrument that preloads samples, there is a decent chance they can still be in memory. If you disable/enable most audio unit VIs that load samples, it won’t trigger the plugin to reload the samples...which in those cases tends to indicate they aren’t being released my memory by disabling.
And if you disable a plugin it will still be able to generate the GUI if you open the panel up, receive values from the GUI, etc. It’s just not doing the processing cycle part of things.
So the answer is a little fine grained.
|
|
|
Post by the other mark williams on May 15, 2019 22:43:27 GMT -6
Generally, but I think that if you disable a virtual instrument that preloads samples, there is a decent chance they can still be in memory. If you disable/enable most audio unit VIs that load samples, it won’t trigger the plugin to reload the samples...which in those cases tends to indicate they aren’t being released my memory by disabling. And if you disable a plugin it will still be able to generate the GUI if you open the panel up, receive values from the GUI, etc. It’s just not doing the processing cycle part of things. So the answer is a little fine grained. This is just for me personally: I cannot realistically imagine a scenario where I would want a sample-based VI to "release" the samples from RAM when I simply hit the "bypass" button on a plugin. If that were the case, it would have to reload all the samples again when I hit "bypass" again to un-bypass the plugin. If I were still working in a 32-bit system and required large sample libraries, I could possibly see the point, but not in a modern DAW context. But again, that's just me.
|
|
|
Post by georgetoledo on May 15, 2019 23:20:17 GMT -6
Yeah, same. I think it makes sense that this seems to be the default behavior.
|
|
|
Post by M57 on May 16, 2019 4:22:27 GMT -6
Aren't we talking about two things here? CPU and RAM? Isn't the answer to the OP's question that when you disable the plugin the CPU doesn't go there?
|
|
|
Post by georgetoledo on May 16, 2019 8:28:13 GMT -6
Sure, but people disable plugins for more performance and I was mentioning a couple places in where it could still impact performance in edge cases.
And for one of the points - if you have a plugin disabled but have the window for it open it is still taking up some cycles. That takes up some CPU, but probably not much.
The times that this can be an issue is when someone has written a GUI that is falling back on CPU to render because the graphics commands aren’t supported by the GPU. Rare edge case type scenario.
|
|
|
Post by MorEQsThanAnswers on May 17, 2019 0:46:51 GMT -6
Aren't we talking about two things here? CPU and RAM? Isn't the answer to the OP's question that when you disable the plugin the CPU doesn't go there? The question came up when I was making a template for Hip-hop recording sessions. These clients typically expect rough mixes to listen to on the way home (or upload to Landr under my nose ). I was trying to figure out if having a ton of "bypassed" plug-ins waiting for me in the session could come with consequences during recording (using Logic).
|
|
|
Post by M57 on May 17, 2019 4:46:33 GMT -6
Aren't we talking about two things here? CPU and RAM? Isn't the answer to the OP's question that when you disable the plugin the CPU doesn't go there? The question came up when I was making a template for Hip-hop recording sessions. These clients typically expect rough mixes to listen to on the way home (or upload to Landr under my nose ). I was trying to figure out if having a ton of "bypassed" plug-ins waiting for me in the session could come with consequences during recording. I may be doing things backwards, but as a song-writer I like to mix as I go, which means that toward the end I'm laying down tracks into a nearly finished mix so I deal with this issue all the time. I do turn off plugs, but that's not always the convenient solution. For instance, sometimes I have plugs loaded that I'm not sure I want to use (maybe I still want to A/B some things), and that can become a type of recall issue down the line. I don't know what DAW you use, but when the going gets tough, I freeze tracks, which is probably the best way to do things. No recall necessary, cuts down significantly on CPU, and let's you hear things as they will be.
|
|
|
Post by MorEQsThanAnswers on May 17, 2019 14:36:58 GMT -6
I may be doing things backwards, but as a song-writer I like to mix as I go, which means that toward the end I'm laying down tracks into a nearly finished mix so I deal with this issue all the time. I do turn off plugs, but that's not always the convenient solution. For instance, sometimes I have plugs loaded that I'm not sure I want to use (maybe I still want to A/B some things), and that can become a type of recall issue down the line. I don't know what DAW you use, but when the going gets tough, I freeze tracks, which is probably the best way to do things. No recall necessary, cuts down significantly on CPU, and let's you hear things as they will be. Well in this case, I think it's a little different because none of my plugins are on at all during recording. This is so I can "1, 2, 3, GO!" after the last vocal is tracked. The idea that you bypass the plugins to reduce latency certainly helps, but doesn't answer the question as to if Logic and Pro Tools are taxing CPU differently when a plugin is "bypassed" versus when it is "inactive." Since you can't even render a GUI with an "inactive" plugin in PT, I imagine this is similar to not having anything instantiated in the first place, whereas a bypassed plug-in might still be drawing CPU. Maybe building the template and recording in PT makes the most sense (for the sake of "inactivating")?
|
|
|
Post by the other mark williams on May 17, 2019 19:42:41 GMT -6
I may be doing things backwards, but as a song-writer I like to mix as I go, which means that toward the end I'm laying down tracks into a nearly finished mix so I deal with this issue all the time. I do turn off plugs, but that's not always the convenient solution. For instance, sometimes I have plugs loaded that I'm not sure I want to use (maybe I still want to A/B some things), and that can become a type of recall issue down the line. I don't know what DAW you use, but when the going gets tough, I freeze tracks, which is probably the best way to do things. No recall necessary, cuts down significantly on CPU, and let's you hear things as they will be. Well in this case, I think it's a little different because none of my plugins are on at all during recording. This is so I can "1, 2, 3, GO!" after the last vocal is tracked. The idea that you bypass the plugins to reduce latency certainly helps, but doesn't answer the question as to if Logic and Pro Tools are taxing CPU differently when a plugin is "bypassed" versus when it is "inactive." Since you can't even render a GUI with an "inactive" plugin in PT, I imagine this is similar to not having anything instantiated in the first place, whereas a bypassed plug-in might still be drawing CPU. Maybe building the template and recording in PT makes the most sense (for the sake of "inactivating")? This may be one of those areas where Pro Tools just behaves differently than native DAWs. In Logic (or Cubase or DP or Reaper or Studio One, as far as I know...), there is no difference between "inactive" and "bypassed." There's just "bypassed." Does Pro Tools still use "voices"? Is that where the "inactive" thing is coming from? At least in Logic, there is no significant amount of CPU hit once you bypass a plugin (or a VI). Are you running out of CPU when using Logic? How are you monitoring when you use Logic? Through an interface's DSP mixer? Or directly through Logic? If you're monitoring through Logic, there is a setting in the transport where you can click a button to make it bypass all plugins that have a latency higher than whatever value you set. You can click that button when tracking, and then click it again when you're done. I prefer to monitor through my interface's DSP mixer, however, for the lowest latency possible.
|
|
|
Post by M57 on May 18, 2019 6:07:10 GMT -6
If you're monitoring through Logic, there is a setting in the transport where you can click a button to make it bypass all plugins that have a latency higher than whatever value you set. You can click that button when tracking, and then click it again when you're done. Where is this button? EDIT: Found it. For some reason, even when engaged, I'm not sure it works unless you go into Preferences/Audio/General and check Low Latency Mode (which was unchecked when I first looked).
|
|
|
Post by the other mark williams on May 18, 2019 9:45:11 GMT -6
If you're monitoring through Logic, there is a setting in the transport where you can click a button to make it bypass all plugins that have a latency higher than whatever value you set. You can click that button when tracking, and then click it again when you're done. Where is this button? EDIT: Found it. For some reason, even when engaged, I'm not sure it works unless you go into Preferences/Audio/General and check Low Latency Mode (which was unchecked when I first looked). yes, you have to check “Low Latency Mode” in the prefs. But again, there’s no particular need to do this if you monitor through your interface’s DSP mixer.
|
|
|
Post by Bob Olhsson on May 20, 2019 12:15:18 GMT -6
Pro Tools is designed for maximum compatibility between different facilities for collaboration. That requirement limits some features in native.
|
|