If you’re the type of person who likes to tinker, and do lots of sound design, you’re gonna like it here. You’re definitely going to miss the FL piano roll though.
10 місяців тому+3
Welcome to the family! We have a lot of fun here :)
Just amazing tips! Thank you! I really like the way you describe things. Clear and to the point, with all the right level of details. Brilliant work. Btw, I don't know if you know, but the way you write Taches with an accent pronounces differently and means "Task" (I speak french). The way you pronounce it, is with no accent and means "stain". 🙂
Really cool, ive done something similar, my idea was to make a generative live techno machine.. the biggest problem i always faced was how to introduce each new generation.. bc you dont know how its gonna sound live and also the change is abrupt... but this is really cool to generate ideas, save them and then just use them as loops i gues.. or do you use this in a live context? thanks!
My immediate thought is that you could use the cue feature in the mixer. You can set it so that activating solo on a track will keep the others playing, but only play the solod part through your headphones. This would let you quickly mute several drum parts at once for the audience, but would allow you to still hear them and change them in various ways. Then when you want a part to start again, you just toggle solo off.
10 місяців тому+3
The trick is to set up a headphone cue so that you can hear the generations before sending it to the house. You can have one of each of these bad boys on A and B and then use the cross fader to pick which one is playing (or both).
Thank you so much! It would be nice if Bitwig had a trigger modulator instead of the button. Because now if you only want to change a value for one sound, you can only do it when the main button is deactivated.
Hi, thanks for your video and the time you've spent sharing your knowledge and passion. Do you have any idea if there's a way to override the "ALL" button ? What I mean is, once i've generated a sound with the "ALL" button, then I can't randomize it's values via the other buttons anymore (they're already "on" inside the grid). Easy way to avoid that is to "always click twice the "ALL" button ; a way cooler solution would be a way to keep the randomized values generated by the "ALL" button at the same time as switching back the state of the buttons inside to grid to "off"... If you, or anyone reading this, have an intch about that, I'll be greatful.
This is exactly the problem I am currently having. I've tried a few different approaches, but haven't found a way around this yet. Otherwise, this is a fun way to generate some drum loops that I might not otherwise - the pitch, decay and filter randomization make it way more creative than e.g. XO or Atlas.
I figured out that if you duplicate the four randomizer modules in the grid and assign the new buttons to each of the individual parameters you can have both an all group and the individual buttons. Not too elegant, it but it works.
Many thanks. Regarding your glitch, I find that in the latest version of Bitwig the highlight rectangles don't show around selected groups of clips in the clip view; it looks like this might be related.
Hi Tâches, is this the same device as your Haus Drummer preset, or has it been updated?
10 місяців тому
This is an improved approach that allows for you to actually choose the rhythms. Haus Drummer generated the patterns too - which was a bit limiting at the end of the day. Also this uses normalized samples so the levels aren't jumping all over the place anymore.
@ Thanks! I figured this out after watching the entire video rather than than replying after 5 minutes! I tried to sign up (again!) for your mailing list but haven't received a download email. Could it be because I was already signed up, so it didn't trigger?
Not sure about this. This seems to ignore the whole mixing process. With each hit being normalised at 0db - how useful would the output of all of this be?
9 місяців тому
That’s why I mention later on to roughly “mix” the outputs with the level output of each sampler. I rarely deviate from multiples of -6 as level for every part in my mixes.
Good. Lord. The idea of min/maxing your stuff ahead of time via macros is such STUPIDLY clutch advice I now feel like a complete moron. Other than weird experiments, why allow adjustments, knobs, sliders etc to throw anything into a garbage sound range? I feel like this should be formalized, Like the Taches Rule of Knobs. I''m sorry, come again? ;P Milage may vary outside the current context with that name, but whatever. #sorryNotSorry
Thats nuts. Beautiful times we live in. I started in Bitwig 3 days ago, came from FL Studio, and my mind gets blown on an hourly bases since.
If you’re the type of person who likes to tinker, and do lots of sound design, you’re gonna like it here. You’re definitely going to miss the FL piano roll though.
Welcome to the family! We have a lot of fun here :)
Oh how we love to tinker haha
This is just brilliant Taches!
Thanks friend :)
Thanks that was really cool. I find your workflow really great without complicating things and also allowing max variation.
Glad you liked it! Happy creating Boris :)
Heeeey good to see you back with Bitwig stuff!
This is incredibly useful. I make wildly different music than you but this technique is applicable to many scenarios. Many thanks.
Glad it was helpful! Happy creating :)
Absolutely awesome video! Great job!
Just amazing tips! Thank you! I really like the way you describe things. Clear and to the point, with all the right level of details. Brilliant work.
Btw, I don't know if you know, but the way you write Taches with an accent pronounces differently and means "Task" (I speak french). The way you pronounce it, is with no accent and means "stain". 🙂
Ooh i didnt know about the normalise button! That's always been my issue with these "128's" 😎
Just one word, Sick!
Godsend channel !
Really cool, ive done something similar, my idea was to make a generative live techno machine.. the biggest problem i always faced was how to introduce each new generation.. bc you dont know how its gonna sound live and also the change is abrupt... but this is really cool to generate ideas, save them and then just use them as loops i gues.. or do you use this in a live context? thanks!
My immediate thought is that you could use the cue feature in the mixer. You can set it so that activating solo on a track will keep the others playing, but only play the solod part through your headphones. This would let you quickly mute several drum parts at once for the audience, but would allow you to still hear them and change them in various ways. Then when you want a part to start again, you just toggle solo off.
The trick is to set up a headphone cue so that you can hear the generations before sending it to the house. You can have one of each of these bad boys on A and B and then use the cross fader to pick which one is playing (or both).
Thank you so much! It would be nice if Bitwig had a trigger modulator instead of the button. Because now if you only want to change a value for one sound, you can only do it when the main button is deactivated.
Hi, thanks for your video and the time you've spent sharing your knowledge and passion. Do you have any idea if there's a way to override the "ALL" button ? What I mean is, once i've generated a sound with the "ALL" button, then I can't randomize it's values via the other buttons anymore (they're already "on" inside the grid). Easy way to avoid that is to "always click twice the "ALL" button ; a way cooler solution would be a way to keep the randomized values generated by the "ALL" button at the same time as switching back the state of the buttons inside to grid to "off"... If you, or anyone reading this, have an intch about that, I'll be greatful.
This is exactly the problem I am currently having. I've tried a few different approaches, but haven't found a way around this yet. Otherwise, this is a fun way to generate some drum loops that I might not otherwise - the pitch, decay and filter randomization make it way more creative than e.g. XO or Atlas.
I figured out that if you duplicate the four randomizer modules in the grid and assign the new buttons to each of the individual parameters you can have both an all group and the individual buttons. Not too elegant, it but it works.
Many thanks. Regarding your glitch, I find that in the latest version of Bitwig the highlight rectangles don't show around selected groups of clips in the clip view; it looks like this might be related.
Thanks! 👌
No problem :)
Hi Tâches, is this the same device as your Haus Drummer preset, or has it been updated?
This is an improved approach that allows for you to actually choose the rhythms. Haus Drummer generated the patterns too - which was a bit limiting at the end of the day. Also this uses normalized samples so the levels aren't jumping all over the place anymore.
@ Thanks! I figured this out after watching the entire video rather than than replying after 5 minutes!
I tried to sign up (again!) for your mailing list but haven't received a download email. Could it be because I was already signed up, so it didn't trigger?
@@carlcaulkett3050 Same! Have you got it yet? Thank you for these videos & free downloads Taches.
Wonderful!
Cheers! :)
Not sure about this. This seems to ignore the whole mixing process. With each hit being normalised at 0db - how useful would the output of all of this be?
That’s why I mention later on to roughly “mix” the outputs with the level output of each sampler. I rarely deviate from multiples of -6 as level for every part in my mixes.
love
why wouldn't you just download a drum machine plugin .... seems like to much faffing around .... or am i missing something ?
Good. Lord. The idea of min/maxing your stuff ahead of time via macros is such STUPIDLY clutch advice I now feel like a complete moron. Other than weird experiments, why allow adjustments, knobs, sliders etc to throw anything into a garbage sound range? I feel like this should be formalized, Like the Taches Rule of Knobs.
I''m sorry, come again? ;P Milage may vary outside the current context with that name, but whatever. #sorryNotSorry