yes i use this a lot. It’s so simple and useful

Is there a way you could trigger others vsts from this ?

yea sure. Just feed the pitch and gate into a note out and load a vst after the grid

🙏

you can make the "phase" last longer with a "scaler" module after the "phase in" module or you simply change the phase length in the "inspector" of the grid: 1bar -> 2bar

you could utilize 2 quantizers. one with the more important notes for you and the second with less interesting notes and then switch between them with a select module + chance module. but the quantizer itself doesnt have the feature.

to have the signal value 0 at note a2 in the quantiser instead of c3. A minor and major share the same keys but the starting key is different. When I dial the attenuate to 0 I end up on the root of the scale

@@PolarityMusic Thank you. That makes perfect sense.

yes supermassive and a delay :)

@@PolarityMusic Thx.. and thx for the share.. always cool to see how you utilize these tools!

I did, almost by accident. I've been trying to understand what it does in Hold mode and how Phase input affects the output by looking at oscilloscope and retriggering S/H manually. then I finally realized that it's always a transition between 2 random values, so I thought 'what if the rest are hiding beyond phase range?', tested it and that was the eureka moment.

@@x-iso Fantastic ! A lot of thanks for that !!! For my part, I had noticed that this random LFO is called "S/H LFO" and I knew of course the "Hold" mode, but I didn't perceive the real aspect of this "sample & hold" because it it's not about sampling and holding a single value but a whole randomized function. It's really very powerful to use randomized values and to be able to go back at any time on one of them (example of changing pattern in the video) There's nothing to say ... Bitwig is so precise and powerfull.

have you tried typing in 0.001? It usually accepts higher and lower values than the module shows in the display

Yup, just type the exact value you want, visible value will be showed rounded, but real value won't be if it's not too precise

Oh yes, you guys are absolutely right! Pretty simple and straight forward, I had no idea you could do this! Thank you.

disable "free run when stopped" in the inspector of the grid

@@PolarityMusic amazing. Thanks a lot !! I have to learn grid basics

Sure. Use it inside of a note grid and instead of going into an oscillator you go to a note out. Done ✅

@@PolarityMusic thanks :)

And how can i trigger it with transport play space bar? I mean, its play all time regardles i hit play

Makes sense. We’re still figuring out how it works and I’m still don’t know why there are no hints in the manual that the phase input accepts greater than 1 integers :D

@@PolarityMusic Could be a programming oversight. Try turning the "Constant" and "Pattern" knobs up really really high and see if bitwig crashes with a segmentation fault :) if it does, then this is likely to be fixed in the future.

EDIT: Scratch my initial answer - "No, from my experience it seems to sample whole new set of random values, like it chooses a random seed for new pattern. and the set actually contains 32768 values in each - and + directions. important thing is that it actually retains the seed in the patch for given voice, so you can safely save the patch and use it later, and all the patterns will remain the same until you retrigger S/H LFO module. " I've re-done my testing and you're right, it actually does shift whole set one sample (value) in same direction, at least when it's in Hold mode. I even experimented with polyphonic patch, and if you settle with some number of voices and at least don't remove them and only add later, all the voices in polyphony also 'remember' their S/H LFO states until retriggered. This is also unique, as I don't remember any modules 'remember' anything beyond settings and parameter values. be it Array or Recorder, or even Delay, they all clear internal buffer when patch is initialising (so when you load it from preset for example, or re-activate the voices). Probably this all comes down to what digital noise actually is. Everything random in digital world is kinda fake random derived from formula, so what this module does in first place, it's just changes seed value for formula when you hit 're-trig', and the formula itself is designed to output a sequence of limited size. I haven't tested if in regular non-Hold mode it actually repeats those 32768x2 values if you don't retrig it. it's kind of a huge chunk to visually compare, but I'll try analyzing recording of 4 times worth of that sequence to see if it repeats when you cut it in half and align in parallel.

@@x-iso take a look at 7:05, doesn't it look like the generated sequence just shifts to the left, after the trigger? That doesn't look like a seed change to me. I could be reading it wrong, of course!

@@nosy-cat yes, somehow it slipped me and it does just shift the whole sequence one value at a time.