Random, probability?
Hi!
Another question: how to use random with probability?
1) I would like to control the slice order in LiveSlicer/Looper patch.
Instead of just randomising the order, I'd like to have a "probability" control for each slice - it would control the probability in % that the slice will retain it's original position.
In other words, a slider for each slice - when 0% then completely random, when at 100% then original position, or vice versa
Slice1 - 0% -> 100%
Slice2 - 0% -> 100%
Slice3 - 0% -> 100%
etc.
2) Another application could be for MIDI - the probability that the recorded MIDI notes keep their original pitch.
It could have a probability slider for each scale degree (or MIDI slice if found possible):
I - 0% -> 100%
ii - 0% -> 100%
iii - 0% -> 100%
etc.
This way it could be adjusted for an example that it never randomises the tonic, but always the sixth (if present, that is).
So, any of this possible?
And how?
Another question: how to use random with probability?
1) I would like to control the slice order in LiveSlicer/Looper patch.
Instead of just randomising the order, I'd like to have a "probability" control for each slice - it would control the probability in % that the slice will retain it's original position.
In other words, a slider for each slice - when 0% then completely random, when at 100% then original position, or vice versa
Slice1 - 0% -> 100%
Slice2 - 0% -> 100%
Slice3 - 0% -> 100%
etc.
2) Another application could be for MIDI - the probability that the recorded MIDI notes keep their original pitch.
It could have a probability slider for each scale degree (or MIDI slice if found possible):
I - 0% -> 100%
ii - 0% -> 100%
iii - 0% -> 100%
etc.
This way it could be adjusted for an example that it never randomises the tonic, but always the sixth (if present, that is).
So, any of this possible?
And how?
this kind of thing can be very hard to implement.
The Data/Random/Random Law Generator, will do the job
- set the length of the array module to the number of slices (3 in you example).
- set the max to the same value
the nth bar of the array will represent the probability that the slice nth will be played.
I hope it helps
The Data/Random/Random Law Generator, will do the job
- set the length of the array module to the number of slices (3 in you example).
- set the max to the same value
the nth bar of the array will represent the probability that the slice nth will be played.
I hope it helps
Olivier Sens
www.brainmodular.com
www.brainmodular.com
Thanks, just noticed your reply.
I'll try it out.
Maybe it'd be good to have a "threads with new posts" selection at the root level of the forum?
I think this would be the easiest way to see all new posts with a single click - just a thought.
I'll try it out.
Maybe it'd be good to have a "threads with new posts" selection at the root level of the forum?
I think this would be the easiest way to see all new posts with a single click - just a thought.
I fiddled with the RND Law Gen patch a little.senso wrote:this kind of thing can be very hard to implement.
The Data/Random/Random Law Generator, will do the job
- set the length of the array module to the number of slices (3 in you example).
- set the max to the same value
the nth bar of the array will represent the probability that the slice nth will be played.
I hope it helps
A few things that are a bit unclear at the moment:
1) Can I use the "RND Law" patch directly with the "Slice Num" patch of the "Live Looper/Slicer?
2) If so, where do I connect it?
3) Even though I had nr 1 (for an example) value to the max on the "RND Law" patch, it occasionally generated also other values. How to make it so, that when maxed, it'll generate only this value?
My questions are very basic, but that's what my patching level is...
yes it replaces the step module.
RNDlaw.out --->> Round module
RNDlaw.max = 32
also to be clear, in the random law sub-patch, set the array module size to 32.
you just need a trigger to generate a RNDlaw periodically (It can be a synchro 1/16 led).
Now, on RNDlaw panel each BAR represents the probability that the nth slice is played (from 0 to 31)
I know it's not so easy...but not my fault...this kind of math is hard!
RNDlaw.out --->> Round module
RNDlaw.max = 32
also to be clear, in the random law sub-patch, set the array module size to 32.
you just need a trigger to generate a RNDlaw periodically (It can be a synchro 1/16 led).
Now, on RNDlaw panel each BAR represents the probability that the nth slice is played (from 0 to 31)
I know it's not so easy...but not my fault...this kind of math is hard!
Olivier Sens
www.brainmodular.com
www.brainmodular.com
Little bit confused - a mix of inexperience and strange software behaviour.
Here's the patch I tried to construct:

But nothing seems to be happening with the play order.
If I connect the synchro 16th to the button of RND Law Generate, the playback just loops the first fraction of the file (about 1/32).
Also...
After a while I get this strange behaviour:

Notice the wire coming out of the Slice Num patch.
If I try to delete it, Usine says nothing selected, although it is.
Another problem related to the previous is that when I close Usine without saving, after restarting Usine, it seems that the buggy state has been saved after all.
Here's the patch I tried to construct:

But nothing seems to be happening with the play order.
If I connect the synchro 16th to the button of RND Law Generate, the playback just loops the first fraction of the file (about 1/32).
Also...
After a while I get this strange behaviour:

Notice the wire coming out of the Slice Num patch.
If I try to delete it, Usine says nothing selected, although it is.
Another problem related to the previous is that when I close Usine without saving, after restarting Usine, it seems that the buggy state has been saved after all.
I haven't looked into any details whatsoever here, but I can tell you that that "wire ending nowhere" is probably there because some original outlet within the sub-patch as been deleted; I guess it's a "pos" outlet(?).
Bjørn S
Sometimes, you have to close and re-open the patch to avoid the "nothing select" problem. Sometimes, it' seven better to close the patch, open another one, click on a wire for example, and then, re-open your patch. It works for me.
Another tip. Just move your "ON" button above the "num slice". Like this:
-in- num of steps
-in- generate
-in- ON
out - num slice
and not this:
-in- num of steps
-in- generate
out - num slice
-in- ON
-in- num of steps
-in- generate
-in- ON
out - num slice
and not this:
-in- num of steps
-in- generate
out - num slice
-in- ON
Thanks.
Seems indeed, that the reordering in a sub-patch creates these "connect to nowhere" wires in a higher level.
The not able to select thing happens only occasionally.
Sometimes when re-opening such a patch all the wires have been disconnected
Now, I have managed to get some randomisation out of this patch, but the playback is quite erratic - looping small segments fast, creating a noise, then again playing normally for a while.
Also, I couldn't enter 32 in the RND Script max value, when I start playback, it always reverts to 28,47222.
Well reading Senso's reply, maybe I shouldn't?
Seems indeed, that the reordering in a sub-patch creates these "connect to nowhere" wires in a higher level.
The not able to select thing happens only occasionally.
Sometimes when re-opening such a patch all the wires have been disconnected
Now, I have managed to get some randomisation out of this patch, but the playback is quite erratic - looping small segments fast, creating a noise, then again playing normally for a while.
Also, I couldn't enter 32 in the RND Script max value, when I start playback, it always reverts to 28,47222.
Well reading Senso's reply, maybe I shouldn't?
Who is online
Users browsing this forum: No registered users and 68 guests
