This proposal is to add additional numeric value “seed” to any randomization in Bitwig. Any device/component which has random option should have this newly added property, which controls the random sequence. Any fixed value of “seed” means that random generated sequence will repeat from play to play on the timeline. By default, randomization would behave same way as it does currently - it does not repeat.
The sequence should not depend on the sample rate, neither on how many times it has been generated before on the timeline. The same seed number would produce always the same results.
As an example, this is how the feature could look like in the Random Dice module:
What problem(s) would this feature resolve?
Currently, any randomization in Bitwig does not repeat from play to play. If we play any given time position twice - it plays different. While it is good for improvisation, it’s not good from an engineering point of view. We cannot introduce changes to composition while keeping the rest fixed.
It’s very common, that we need to render a composition in different bitrates, or we need to fix few things while doing mastering and we don’t want to receive a new composition each time, we just want to have same one each time.
How does this feature fit in Bitwig as a product?
Bitwig puts a lot of emphasis on introducing randomness in the creative process. Thanks to randomization good surprises and great results can be achieved, and when you find them you don’t want to lose them.
There is already a seed setting available for clips and this would be a logical extension.
Is there already an alternative way to achieve this on Bitwig?
For some scenarios it’s possible to use a combination of LFOs + sample & hold instead of pure randomization.
Could it be implemented using Bitwig components or APIs, without Bitwig team’s support?
No.
Could it be provided by a VST or something else reasonably integrated with Bitwig?
Some VSTs (e.g. from MeldaProduction) have randomization which is always preserved.
Are there other products that offer this feature?
We don’t know.