Re: Knob Wizard; Do You want it?
Posted: Wed Jan 09, 2019 3:10 pm
If You'd read the posts (on this forum) more recently than you would've seen there's a few wine users who tested Flowstone plugins. And the syntheway plugins seem to be working ok so, maybe. The poster had said there'd been some GPU glitches.
But, I was thinking if used in wine to be honest. Wine seems pretty popular; And it seems like if its installation experience is a bit more streamlined then that following might even double.
But, this is really neither here nor there. mac is "maybe" an option but bottom line is if image driven knobs are more stable "in Windows" or not. I see a great strength if a plugin can process music without even generating the images required in the code. If the code lies dormant and then creates the images only if opened it saves a great deal of CPU.
I think of it this way: On the plugin window opening it would create the image, that means for the entire session it would be loaded even if the window was closed. But the next time You load the same project the image would need to be reloaded again. It seemed surprising that by making a knob with only Ruby and primitives I was challenging My CPU (and GPU). So, it might be that this is a good, streamlined route.
My new Hydra is well beyond expectations and it doesn't ess due to a linear high and low pass implemented. I modded some MV high and low passes to achieve that. But it's a bit heavy GPU wise. Commercial quality sound is very easy with Hydra - I use it by itself now. Sometimes I pair it with Mini Boom switch. Maybe I'll add a few decibels in the volume though.
But, I was thinking if used in wine to be honest. Wine seems pretty popular; And it seems like if its installation experience is a bit more streamlined then that following might even double.
But, this is really neither here nor there. mac is "maybe" an option but bottom line is if image driven knobs are more stable "in Windows" or not. I see a great strength if a plugin can process music without even generating the images required in the code. If the code lies dormant and then creates the images only if opened it saves a great deal of CPU.
I think of it this way: On the plugin window opening it would create the image, that means for the entire session it would be loaded even if the window was closed. But the next time You load the same project the image would need to be reloaded again. It seemed surprising that by making a knob with only Ruby and primitives I was challenging My CPU (and GPU). So, it might be that this is a good, streamlined route.
My new Hydra is well beyond expectations and it doesn't ess due to a linear high and low pass implemented. I modded some MV high and low passes to achieve that. But it's a bit heavy GPU wise. Commercial quality sound is very easy with Hydra - I use it by itself now. Sometimes I pair it with Mini Boom switch. Maybe I'll add a few decibels in the volume though.