Another super neat way to do the probability modulation is to use the “curves” module as a mod-remap to put a transfer curve in between the random modulator and its destination. Set the time base of the curves module to frozen, so the rate is 0, then modulate the phase of that curves module with the random module up to 360 degrees - at this point, you can modulate the destination (mute) with the curves modulator, and the shape drawn in the curves modulator will determine what mute state you get at the output for each possible random input value. For instance, if you make the curves a 50% pulse, off in the first half and on in the second half, then all random values below 0.5 will get turned into a 0, and all random values above 0.5 will get turned into a 1, which will give us a 50% chance to mute. You can also quite nicely use this trick when you’re doing random modulation of a parameter like filter cutoff or reverb dry/wet, and just make a slightly tensioned ramp in the curves module, to bias the random value slightly in one direction.
One of the first things I did with Stepwise was put a bunch of them into a Note FX Layer, added Note FX to each Stepwise, then put a Humanize and Transpose Map after the Note FX Layer, and before a FM4. Came up with a really cool semi-generative bassline. Thanks for sharing :)
100% agree with your take at the end about how best to work with Bitwig, and the example of using the tank fx to spice up Reverb is exactly the one where I think Bitwig's design clicked for me
I’m sure you know this but if you’re using a drum machine you can also use choke targets to make sure the kick and snare have priority without going for the grid. I always enjoy how you problem solve though. I know that we can customize stepwise to do whatever we want but I don’t want to have 32 step modulators attached to control the offset, chance, velocity and pitch (via drum machine) Another thought is to just use stepwise to print some midi patterns and then go adjust it on the piano roll… or just use the drum mode on the piano roll… or just use audio 🧛🏼. I like stepwise. It’s more of something to encourage a different approach rather than become more efficient than my current workflow. Great video!
People are telling you get a hair cut. Good grief man who do they think they. It’s your hair style if you’re happy 😊. Thanks for the videos I’m thankful for your incredible content. I’d be happy no matter what your haircut is 😊
One thing I found useful was using the steps modulator then modulating the step length of a specific row for some pseudo generative patterns. Put the steps modulation on like a bar length then you can modulate like a kick for a bar of step length of 3 then next bar the pattern length is 5. Cool stuff
I messed around with steps and random modulators a lot too, but actually never thought about doing it the way you did. What I also want to do which you have not covered, is to only change snare and kick pattern every 2nd or 4th bar. I could only achieve this with multiple Stepwise modules in a chain, with the steps switching mute off on 1 and on on the other device. Hope that makes sense, but more so is I'm hoping you have a simpler solution. This is essential if you don't want the same repetitive drum pattern and create some variety, but with control of when and where the notes/drums hit.
@@PolarityMusic Well, using your idea, I found an alternative solution using Steps and ParSeq together, with the Mute split around 50/50. It's very rudimentary but it works. Don't understand why Bitwig didn't just make this a thing with Stepwise as they already have it implemented in the clip editor.
Another way to implement the step probability would be: modulate the mute with a Math modulator where one knob is controlled by the random and the other by Steps. That way you can visualize the combined effect. IDK if this helps or not...
you can keep one lane for extra notes to be played above the 8 different sounds and have 7 + 16 or 32 steps / Notes extra if needed with the step modulator
@@PolarityMusic tried many times already seems like its not working for me on windows 10... There may be a issue with windows 10 or my specific condition, I mean its also still in BETA so that makes sense
So I have to be proficient in math in order to play with probability per step? It doesn't sound like something that's meant for 'beginners' at all. If that's the case, it would make more sense for Stepwise to just be a wrapped grid patch like Polymer.
It would be so useful if the Steps modulator had a probability mode, so you didn't need to use two modulators per thing you want a different random seed for.
I do like to use two Steps at different speeds though, so you've got a 16th note probability sequence and then modulate that so probabilities increase near the end of a four bar loop for instance.
I think it’s a nothing addition, it just looks nice in screenshots and on the feature list. They want buyers to think it’s competitive with the additions in Cubase 14 (which also added modulation)
I would say in 2024 its time to stop abusing notes for drumpad triggers but rather introduce generic drumpad tags, pretty much like Select in a multisample works. But not with numerical ranges but labeled tags, you would assign to each pad and then send along with the note. Midi Controller drivers/scripts could provide a default mapping that assigns these tags to C1-D#2 or whatever range on demand, such them controllers continue to work seamlessly. Ideally all controllers would have this by default, unless the controller script provides a custom implementation. We can simulate this with channels currently. But it is yet another abusage plus it has a hard limit of 16, so it definitely doesnt cover the same range of use cases as the drum machine or the multisample.
If you trick Harmonize into working properly (see my Bitwig Harmonize Repair Manual video), you can use it to make Stepwise’s output follow the chords on the harmony track. th-cam.com/video/qjKo_IIjpsc/w-d-xo.html
It's def there because of the Drum theme they went with. That's pretty obvious, and I'm fine with that. That's what I wanted. Even the fact that it's 8 lanes is a dead giveaway. That's pretty standard stuff. Therefore it needs, at the very least, for the sake of consistency, simplicity, and complete control in an obvious manner: It doesn't even have to change much. Velocity per step. (drag note up/down, shift for fine tune) Repeat per step. (drag note to the right/left, shift for fine tune) Probability per step.(modifier key, and drag note in %, shift for fine tune) Up to 128 steps. (simple arrow for pages) It's got everything else you would need in a standard polyrhythmic drum sequencer. The mod possibilities are awesome, and that's one of the reasons I want a native midi drum step sequencer in Bitwig, but I don't want to have to count on mods, that kinda work, to do some of the most basic stuff found in even the crappiest midi drum sequencers. Honestly, It just seems like several lazy short comings, in an otherwise pretty good feature drum sequencer, for no good reason. I really don't get it. It's so weird it's absurd. I'm hoping a light goes off in someone's head over at BWS headquarters before the beta ends. Come on Bitwig, you can do it!🙃 I have not watched the whole vid yet, so apologies if you mentioned it, but if you add another SW in series you get 16 lanes.
Having a sequencer as a device seems to open up some cool creative possibilities, but at the same time it seems odd that they have this very cool and powerful thing already for working sequences within the clip editor, called operators, but you have to either give them up those function or reengineer them if you want to program with this device.
@@kmac. The operators are cool, but I don't use them because: Workflow. For me, staring at piano roll is the death of creativity. I hardly touch the thing. When it comes to electronic beat making specifically, I much prefer looking at a step sequencer. I've been using the things for a very long time and I just know numerically and visually what to do to get to where I'm going. I know I put probability in my asks, but honestly that's for the more rare occasions. I'm not really the biggest fan of probability and or random, (seems to be trendy these days) unless my aim is to sound, well, purposely random, which I do for effect in what is otherwise traditional songwriting.
Another super neat way to do the probability modulation is to use the “curves” module as a mod-remap to put a transfer curve in between the random modulator and its destination.
Set the time base of the curves module to frozen, so the rate is 0, then modulate the phase of that curves module with the random module up to 360 degrees - at this point, you can modulate the destination (mute) with the curves modulator, and the shape drawn in the curves modulator will determine what mute state you get at the output for each possible random input value.
For instance, if you make the curves a 50% pulse, off in the first half and on in the second half, then all random values below 0.5 will get turned into a 0, and all random values above 0.5 will get turned into a 1, which will give us a 50% chance to mute.
You can also quite nicely use this trick when you’re doing random modulation of a parameter like filter cutoff or reverb dry/wet, and just make a slightly tensioned ramp in the curves module, to bias the random value slightly in one direction.
One of the first things I did with Stepwise was put a bunch of them into a Note FX Layer, added Note FX to each Stepwise, then put a Humanize and Transpose Map after the Note FX Layer, and before a FM4.
Came up with a really cool semi-generative bassline.
Thanks for sharing :)
100% agree with your take at the end about how best to work with Bitwig, and the example of using the tank fx to spice up Reverb is exactly the one where I think Bitwig's design clicked for me
I’m sure you know this but if you’re using a drum machine you can also use choke targets to make sure the kick and snare have priority without going for the grid. I always enjoy how you problem solve though. I know that we can customize stepwise to do whatever we want but I don’t want to have 32 step modulators attached to control the offset, chance, velocity and pitch (via drum machine)
Another thought is to just use stepwise to print some midi patterns and then go adjust it on the piano roll… or just use the drum mode on the piano roll… or just use audio 🧛🏼.
I like stepwise. It’s more of something to encourage a different approach rather than become more efficient than my current workflow.
Great video!
People are telling you get a hair cut. Good grief man who do they think they. It’s your hair style if you’re happy 😊. Thanks for the videos I’m thankful for your incredible content. I’d be happy no matter what your haircut is 😊
That poly to mono thing is great for implementing linear drumming.
i am pretty sure this is just a beta version and will develop nicely in time, nice video bro, all the best
One thing I found useful was using the steps modulator then modulating the step length of a specific row for some pseudo generative patterns.
Put the steps modulation on like a bar length then you can modulate like a kick for a bar of step length of 3 then next bar the pattern length is 5. Cool stuff
Good idea 👍
That thumbnail is so creative 😅
Stepwise in tandem with Twisted Tools stuff goes crazy
Very inspiring thanks
1:28 there can never be too much cowbell 🔔
😂
channel fünf 😋 🙌
🤣
I messed around with steps and random modulators a lot too, but actually never thought about doing it the way you did. What I also want to do which you have not covered, is to only change snare and kick pattern every 2nd or 4th bar. I could only achieve this with multiple Stepwise modules in a chain, with the steps switching mute off on 1 and on on the other device. Hope that makes sense, but more so is I'm hoping you have a simpler solution. This is essential if you don't want the same repetitive drum pattern and create some variety, but with control of when and where the notes/drums hit.
Yes, this sounds like the best solution for this type of scenario just using multiple stepwise sequences. Good idea 👍
@@PolarityMusic Well, using your idea, I found an alternative solution using Steps and ParSeq together, with the Mute split around 50/50. It's very rudimentary but it works. Don't understand why Bitwig didn't just make this a thing with Stepwise as they already have it implemented in the clip editor.
Another way to implement the step probability would be: modulate the mute with a Math modulator where one knob is controlled by the random and the other by Steps. That way you can visualize the combined effect. IDK if this helps or not...
you can keep one lane for extra notes to be played above the 8 different sounds and have 7 + 16 or 32 steps / Notes extra if needed with the step modulator
"almost too funky for youtube" 😀
Have you seen the Plugin “Riffer”?
Tried to reproduce in the grid… not lucky so far
never too much cowbell!😆
is there anyways to capture stepwise as midi?
create new instrument track, use the "input" dropdown for the track, select the stepwise track. record.
@@PolarityMusic tried many times already seems like its not working for me on windows 10...
There may be a issue with windows 10 or my specific condition, I mean its also still in BETA so that makes sense
@@PolarityMusic Thank you for the feedback... i guess there is a bug on my side, its not working
this has nothing to do with windows. you can record midi of stepwise withing Bitwig.
@@PolarityMusic i tried and tried but it doesn't record on mine.... 🥲🥲🥲i mean its still in BETA... it does make sense its buggy
hehe step seq goes brrrr
So I have to be proficient in math in order to play with probability per step? It doesn't sound like something that's meant for 'beginners' at all. If that's the case, it would make more sense for Stepwise to just be a wrapped grid patch like Polymer.
It would be so useful if the Steps modulator had a probability mode, so you didn't need to use two modulators per thing you want a different random seed for.
I do like to use two Steps at different speeds though, so you've got a 16th note probability sequence and then modulate that so probabilities increase near the end of a four bar loop for instance.
Try using stepwise etc with Fors Tela. You’ll be happy.
looking into it, sounds dope
I think it’s a nothing addition, it just looks nice in screenshots and on the feature list. They want buyers to think it’s competitive with the additions in Cubase 14 (which also added modulation)
This is a minor update, it was never advertised as a huge update
wow
as a homeless producer bitwig 5.3 will come in handy with no way to lug hardware
I would say in 2024 its time to stop abusing notes for drumpad triggers but rather introduce generic drumpad tags, pretty much like Select in a multisample works. But not with numerical ranges but labeled tags, you would assign to each pad and then send along with the note. Midi Controller drivers/scripts could provide a default mapping that assigns these tags to C1-D#2 or whatever range on demand, such them controllers continue to work seamlessly. Ideally all controllers would have this by default, unless the controller script provides a custom implementation.
We can simulate this with channels currently. But it is yet another abusage plus it has a hard limit of 16, so it definitely doesnt cover the same range of use cases as the drum machine or the multisample.
Don't worry I still search "dia" for the key filter 😅
Haha! It’s just ingrained in my memory.
Too much cowbell??? Easiest unsub ever 😂
@@clrs6576 rushed to the comments to say the same thing 😂
🤣🤣🤣👏👏👏
If you trick Harmonize into working properly (see my Bitwig Harmonize Repair Manual video), you can use it to make Stepwise’s output follow the chords on the harmony track. th-cam.com/video/qjKo_IIjpsc/w-d-xo.html
It's def there because of the Drum theme they went with. That's pretty obvious, and I'm fine with that. That's what I wanted. Even the fact that it's 8 lanes is a dead giveaway. That's pretty standard stuff. Therefore it needs, at the very least, for the sake of consistency, simplicity, and complete control in an obvious manner:
It doesn't even have to change much.
Velocity per step. (drag note up/down, shift for fine tune)
Repeat per step. (drag note to the right/left, shift for fine tune)
Probability per step.(modifier key, and drag note in %, shift for fine tune)
Up to 128 steps. (simple arrow for pages)
It's got everything else you would need in a standard polyrhythmic drum sequencer.
The mod possibilities are awesome, and that's one of the reasons I want a native midi drum step sequencer in Bitwig, but I don't want to have to count on mods, that kinda work, to do some of the most basic stuff found in even the crappiest midi drum sequencers.
Honestly, It just seems like several lazy short comings, in an otherwise pretty good feature drum sequencer, for no good reason. I really don't get it. It's so weird it's absurd.
I'm hoping a light goes off in someone's head over at BWS headquarters before the beta ends. Come on Bitwig, you can do it!🙃
I have not watched the whole vid yet, so apologies if you mentioned it, but if you add another SW in series you get 16 lanes.
Having a sequencer as a device seems to open up some cool creative possibilities, but at the same time it seems odd that they have this very cool and powerful thing already for working sequences within the clip editor, called operators, but you have to either give them up those function or reengineer them if you want to program with this device.
@@kmac. The operators are cool, but I don't use them because: Workflow. For me, staring at piano roll is the death of creativity. I hardly touch the thing. When it comes to electronic beat making specifically, I much prefer looking at a step sequencer. I've been using the things for a very long time and I just know numerically and visually what to do to get to where I'm going. I know I put probability in my asks, but honestly that's for the more rare occasions. I'm not really the biggest fan of probability and or random, (seems to be trendy these days) unless my aim is to sound, well, purposely random, which I do for effect in what is otherwise traditional songwriting.
I think your hair is OK.
It's your moustache that needs rescuing 😜
nice try to sell us a new (non sense) payed update for bitwig :P
Actually more a guy showing us the best ways to get things out of the thing we bought.
Why are you watching it if you think it's nonsense?
Hm, no, that does not look like fun.
tell me!