Arturia Forums
Software Instruments => Pigments => Pigments - Feature Requests => Topic started by: craftycurate on January 09, 2019, 04:23:36 am
-
Would be great if each Analog OSC could be powered on and off individually, esp if making patches intended for high polyphony, to save on CPU.
-
I think it would be sufficient to internally switch off an OSC, if the volume is set to zero. This safes CPU and doesn‘t require a GUI change, so implementation is done faster.
-
If a volume of zero turns the oscillator off and you modulated the volume from zero, wouldn't that turn the oscillator on and off. Imagine doing that at audio rate!
Much better to have on/off buttons
-
If a volume of zero turns the oscillator off and you modulated the volume from zero, wouldn't that turn the oscillator on and off. Imagine doing that at audio rate!
Much better to have on/off buttons
Why would you modulate the volume of a switched off OSC?
Ok, a switch is the better alternative, but the volume approach is faster implemented, because no GUI change is needed. So that could be a first approach, until the switch is implemented.
-
Maybe you mis understand. In your "zero-volume = off" idea, every time you modulated an OSC that saw on and it went to zero you would switch the osc off! lol
I can't image that would be good to switch on and off all the time.
-
Maybe you mis understand. In your "zero-volume = off" idea, every time you modulated an OSC that saw on and it went to zero you would switch the osc off! lol
I can't image that would be good to switch on and off all the time.
Yes ... now I got it ;D
Yeah, we would be forced to avoid unwanted zero values in modulation, which would be a pain, because currently no exact value input / correction by keyboard is possible.
Conclusion: Both, exact parameter input and an on/off switch, are must haves for a future version.
-
It may be good to divide each OSC like a effect by tab.
-
Nice idea, personally think it would be better how it is.
-
If a volume of zero turns the oscillator off and you modulated the volume from zero, wouldn't that turn the oscillator on and off. Imagine doing that at audio rate!
Much better to have on/off buttons
Agreed - having on off buttons is a much better solution and more consistent with how things work elsewhere in the GUI e.g. the Master on\off for each main OSC, effect On\Off etc.
Simply deactivating the OSC when its volume is 0 is not really a solution - as others have posted, you don't want to be switching an oscillator on and off at audio rate.
-
Hi All
I asked for this request in testing but the dev team tell me if the osc volume is on 0 there is no more cpu used than if it was switched off.
regards
-
I asked for this request in testing but the dev team tell me if the osc volume is on 0 there is no more cpu used than if it was switched off.
So my zero volume workaround idea above to save on CPU is already implemented as it seems.
-
He said it uses "no more cpu", doesn't say it switches it off
-
He said it uses "no more cpu", doesn't say it switches it off
He said: „if the osc volume is on 0 there is no more cpu used than if it was switched off.“
For ME that clearly means, from a CPU perspectice zero volume or switch off would make no difference.