ArrayArrayArrayArrayArray
BrainModularBrainModular Users Forum2014-01-05T11:54:12+02:00https://www.brainmodular.com/forums/app.php/feed/topic/42392014-01-05T11:54:12+02:002014-01-05T11:54:12+02:00https://www.brainmodular.com/forums/viewtopic.php?t=4239&p=28712#p28712Statistics: Posted by beammy — 05 Jan 2014, 10:54
]]>
2014-01-02T01:10:42+02:002014-01-02T01:10:42+02:00https://www.brainmodular.com/forums/viewtopic.php?t=4239&p=28692#p28692There is no rule!
Statistics: Posted by hesspet — 02 Jan 2014, 00:10
]]>2014-01-02T00:58:43+02:002014-01-02T00:58:43+02:00https://www.brainmodular.com/forums/viewtopic.php?t=4239&p=28691#p28691 For me, I put the vst in a subpatch and use a patch on/off module instead of bypass. I think some vsts still use cpu when bypassed (not sure....)
-e
Statistics: Posted by woodslanding — 01 Jan 2014, 23:58
]]>2014-01-01T23:25:18+02:002014-01-01T23:25:18+02:00https://www.brainmodular.com/forums/viewtopic.php?t=4239&p=28690#p28690 Route the signal around your VST.
The patch of a VST created by Usine
and here's one possible solution:
There are many other ways to do so. (eg. put a fader in front of the vst and set the fader only 0 & 100%)
This solution is fast. Disadvantage: the vst is not stopped and sucks CPU performance during the bypass time.
Statistics: Posted by hesspet — 01 Jan 2014, 22:25
]]>2014-01-01T07:19:51+02:002014-01-01T07:19:51+02:00https://www.brainmodular.com/forums/viewtopic.php?t=4239&p=28682#p28682 One problem that I'm encountering, though, is that when you switch a VST plugin between "bypassed" and "not bypassed", say by patching a switch into its "bypass" input, there's about a quarter-second delay before a change to this takes effect. Is there any way around this?
I really do need to deactivate the VST itself, to save CPU usage - simply routing the audio past the VST wouldn't be a workable solution.
]]>BrainModularBrainModular Users Forum2014-01-05T11:54:12+02:00https://www.brainmodular.com/forums/app.php/feed/topic/42392014-01-05T11:54:12+02:002014-01-05T11:54:12+02:00https://www.brainmodular.com/forums/viewtopic.php?t=4239&p=28712#p28712Statistics: Posted by beammy — 05 Jan 2014, 10:54
]]>2014-01-02T01:10:42+02:002014-01-02T01:10:42+02:00https://www.brainmodular.com/forums/viewtopic.php?t=4239&p=28692#p28692There is no rule!
Statistics: Posted by hesspet — 02 Jan 2014, 00:10
]]>2014-01-02T00:58:43+02:002014-01-02T00:58:43+02:00https://www.brainmodular.com/forums/viewtopic.php?t=4239&p=28691#p28691 For me, I put the vst in a subpatch and use a patch on/off module instead of bypass. I think some vsts still use cpu when bypassed (not sure....)
-e
Statistics: Posted by woodslanding — 01 Jan 2014, 23:58
]]>2014-01-01T23:25:18+02:002014-01-01T23:25:18+02:00https://www.brainmodular.com/forums/viewtopic.php?t=4239&p=28690#p28690 Route the signal around your VST.
The patch of a VST created by Usine
and here's one possible solution:
There are many other ways to do so. (eg. put a fader in front of the vst and set the fader only 0 & 100%)
This solution is fast. Disadvantage: the vst is not stopped and sucks CPU performance during the bypass time.
Statistics: Posted by hesspet — 01 Jan 2014, 22:25
]]>2014-01-01T07:19:51+02:002014-01-01T07:19:51+02:00https://www.brainmodular.com/forums/viewtopic.php?t=4239&p=28682#p28682 One problem that I'm encountering, though, is that when you switch a VST plugin between "bypassed" and "not bypassed", say by patching a switch into its "bypass" input, there's about a quarter-second delay before a change to this takes effect. Is there any way around this?
I really do need to deactivate the VST itself, to save CPU usage - simply routing the audio past the VST wouldn't be a workable solution.