I’m still riding the hype train of Rack 2 Electric Boogaloo, but after reading through a thread discussing computers running slowly in Rack and how Rack actually runs, it made me wonder what it’s gonna be like when the plugin version of Rack is available.
Here’s a comment explaining the differences between how DAWs run compared to what Rack is doing:
I’m wondering what it will be like to work with Rack as a plugin, just because I know how careful I have to be with it in standalone to avoid pops and clicks (running lowest frame rate and other CPU saving options). In my DAW, I know when running Exhale (plugin by Output) that puppy can eat up ~20-25% just by itself, when it’s in a complicated project with lots of other tracks and plugins: it’s a lot. Will Rack be a plugin that I can only really have 1 or 2 instances in a project? I’m probably gonna be bouncing audio pretty often and disabling the actual plugin, as well as bussing all my effects, but I really like the interaction aspect of Rack, like potentially having different automation from tracks control CV in my patch and vice versa. Or sampling audio from live tracks and then playing with it inside of a patch during playback. Also will Rack be available to select as both a VST instrument and as an effect? That way you can have one patch be a sound source and have another be a really weird modular effect to put on your effects bus.
Sorry this post is long, just excited about all the different applications a plugin version could bring, but I’m worried about how my computer will react.