Tom Hall

#9 Velocity Sequencer Part I

#10 Velocity Sequencer Part II

Part 3 - Tying It Together: Integrating MIDI and the Sequencer

#11 Velocity Sequencer Part III

Episode 1: An Introduction to Programming in the Max Environment

Episode 2: Creating Some Basic Audio Effects

Episode 5: Creating a Velocity Sequencer MIDI Effect

Episode 6: Creating a Wobble Bass MIDI Instrument

Episode 8: Creating a Live API-based Step Sequencer


programming-in-max-for-live-creating-a-velocity-sequencer-midi-effect-episode-5

Hey, I've just completed this but mine looks like this:

Screen Shot 2017-08-23 at 15.43.44.png

why the big blue bar? I can only think I have done something wrong in the object inspector? 

i'ts probably something really simple. your help would be much appreciated!

Hey, I've just completed this but mine looks like this: 

why the big blue bar? I can only think I have done something wrong in the object inspector? 
i'ts probably something really simple. your help would be much appreciated!

I've just completed this patch, too, and I get the same result: there's a mistake somewhere which causes the multislider to revert back to a single slider (rather than 16).

It's the "pattr steps" object which is causing this problem. If you disconnect it from the input of the multislider, then the 16 bar multislider works as expected. Since the "pattr steps" object is designed to save the current/last saved state of the multisliders (which will be helpful), I'll try to figure how it can be repatched correctly.

It's the "pattr steps" object which is causing this problem.  If you disconnect it from the input of the multislider, then the 16 bar multislider works as expected.  Since the "pattr steps" object is designed to save the current/last saved state of the multisliders (which will be helpful), I'll try to figure how it can be repatched correctly.

Here's the "correct" way to patch the pattr steps object. I figured that it needed to receive the output of the multislider in order to capture the current values of the sliders. Then, of course, one of the outputs needed to be patched to an input of the multislider in order to send the captured/saved state of the multislider back to it so that it can be reset. Now, when I close and reopen the Live set, I can continue from where I left off the last time. Here's what the patcher looks like:

Screen Shot 2018-03-18 at 10.34.17 AM.png

Here's the "correct" way to patch the pattr steps object.  I figured that it needed to receive the output of the multislider in order to capture the current values of the sliders.  Then, of course, one of the outputs needed to be patched to an input of the multislider in order to send the captured/saved state of the multislider back to it so that it can be reset.  Now, when I close and reopen the Live set, I can continue from where I left off the last time.  Here's what the patcher looks like:


Programming in Max for Live: Creating a Velocity Sequencer MIDI Effect, Episode 5