bypassing an actor means that it will stop consuming cpu/gpu/ram resources?
Eryck last edited by
I think so, well let see if veterans here will confirm, but I guess it does stop the calcul.
You have similar bypassing functions in Protools or Max/msp, very practical to organize the work in case of heavy
You can do an experience by puting 2 or 3 demanding actors like the gaussian blur in a patch
, run a cpu inspector , then bypass the actors and see what happends ;-)
dbini last edited by
yes. i think its true with all actors. that's one reason why they have a bypass selector - i try to make my patches more efficient by automating the bypass on actors that aren't being used, eg: when crossfading between 2 processed video streams, if the fader is at 0 or 100, a comparator turns on the bypass for the processing on the stream that is no longer visible.
Another VERY useful actor for saving resources is the "User Actor On/Off" it basically allows you to create Kill switches for you user actors.
It will stop everything within the actor from working.. only when it receives an ON will the actor begin to use resources again.
Great to use if switching between sub routines in a patch.. turn off the routines not being used.
Yup it defiantly helps.Look at using the comparator actor so if a value is equal or less than, or equal to but more than vale it sends a trigger 'X' this can be linked to a toggle; this bypassing actors.
ey guys, thanks for the commentsI have been going forward a little bit more to find out that bypass just stops showing the results while it continues making the calculations. at least this is what I feel watching the results, and hearing my fan! I hope someone can confirm this info.anyway, I found in my way the user actor on/off, that definitely stop all calculations. so this was my solution.thanks!
I'm pretty sure it should stop the actors calculations, maybe some freeframes don't work that way but most should.
In any case, if you build your patch modular with sub user actors, its easier to stop effect chains easily with the actor on/off.
That would be my recommended method.
It sounds like you are able to move ahead, which is great.
I think the actors that can't dont even have a bypass switch.I am totally having a stab in the dark with that statement though - its always just been my understanding, might be wrong. I cant even remember which ones don't have bypass....
mark last edited by
Dear All,The bypass input is found on video actors only. It essentially skips the entire processing phase, and passes the first video input to the video output. If you feel that's not the case, then please tell me which specific actors you feel are continuing to process the image and I'll check. But I'm 99.9% sure this is the case for all of the actors with a bypass input. (There's a function in each video actor that processes the image; turning bypass 'on' prevents this function from ever being called.)I guess the way to test this is to literally remove the actor from the chain. If you do this, and your CPU usage/fan usage goes down noticeably, then perhaps I'm wrong about a particular actor. Let me know if that's the case.Please note that there are many other factors that can contribute to high CPU usage, including playing multiple movies, or a movie with a very high resolution, and other factors. It may or may not be the actors.Best Wishes,Mark
thanks mark!leo bettinelli here.I will be monitoring this and come back with an answer if I detect an actor which may be doing calculations even in bypass mode