Bypassing / Offlining JS FX with @gfx
|
08-15-2012 09:47 AM
|
|
Human being with feelings
|
|
Bypassing / Offlining JS FX with @gfx
... @gfx still runs
|
|
Issue Details
|
Project
Deprecated REAPER issue tracker
Category Arcana
Status Not a Reaper Bug
Priority 5 - Medium
Affected Version 4.25
Closed Version (none)
Yes votes
1
No votes
0
Assigned Users
(none)
Tags
JS FX
|
|
04-08-2013 08:09 PM
|
|
Administrator
|
|
|
I think it's important to make a distinction between bypassed (plug-in loaded but not processing audio) and offlined (plug-in not even loaded, only its configuration state in RAM). As far as the @gfx section still running and using CPU, you should also note that it only runs and uses CPU if the plug-in GUI is open, and if the @gfx section would like to still present UI it can, and if it detects that the audio side hasn't run recently, it could also bypass itself as needed. So basically, everything here is pretty much as it should be.
|
All times are GMT -7. The time now is 11:27 PM.