Forums > MaxMSP

[Patch] Kick/Snare/Noise drum machine with bar quantization

April 29, 2008 | 4:01 pm

Just messing around with the transport object. You can control the velocity and timing of Kick/Snare/Noise (shaker) and if you ever change their timing it will update at the start of the next bar, much like Ableton’s global 1 Bar quantization. I wasn’t sure if this was possible using the quantize message to the metro (I tried), so my way just detects the start of a new bar and only sends the updated metro timing then. Any suggestions?


April 29, 2008 | 5:15 pm

On Apr 29, 2008, at 9:01 AM, marcos wrote:
> Just messing around with the transport object. You can control the
> velocity and timing of Kick/Snare/Noise (shaker) and if you ever
> change their timing it will update at the start of the next bar,
> much like Ableton’s global 1 Bar quantization. I wasn’t sure if this
> was possible using the quantize message to the metro, so my way just
> detects the start of a new bar and only sends the updated metro
> timing then. Any suggestions?

I used a similar technique in the NewThump patcher I posted a link to
a couple days ago.
It’s currently the top link here – http://www.xfade.com/max/examples

-C

Chris Muir
cbm@well.com

http://www.xfade.com


April 29, 2008 | 5:32 pm

I saw that, but a question/comment:

On yours when just using the kick to test, if I set it at 32n and then change it to 1n, it won’t wait till the bar is over to change, it will just change as soon as the current 32nd tick is over. At least that’s what I observed. I wasn’t really sure if your interval/quantize was doing anything. Unless you want no quantization, most people like to fire things off at the next 1 bar, or maybe 2 bars.

Am I missing something?


April 29, 2008 | 6:25 pm

On Apr 29, 2008, at 10:32 AM, marcos wrote:
> On yours when just using the kick to test, if I set it at 32n and
> then change it to 1n, it won’t wait till the bar is over to change,
> it will just change as soon as the current 32nd tick is over. At
> least that’s what I observed.

NewThump works in a quantized manner here. Perhaps you didn’t notice
that the way I’m changing the time value is itself quantized (via the
bpatcher TimeValQuantized_bp.maxpat) using a metro set to one measure.

-C

Chris Muir
cbm@well.com

http://www.xfade.com


April 30, 2008 | 7:18 am

Thanks for sharing, great :)


April 30, 2008 | 9:57 am

All the samples play at once, i want to make beat, please help :)


April 30, 2008 | 3:29 pm

Quote: petterdass wrote on Wed, 30 April 2008 05:57
—————————————————-
> All the samples play at once, i want to make beat, please help :)
—————————————————-

Change the umenu below the Kick, Snare, Noise. By default they are all the same. Not alot of choices to make beats here, just an example patch. Take a look at my 32 step sequencer thread if you want more control over the beats.


Viewing 7 posts - 1 through 7 (of 7 total)