shaar

i'm building a sample-player patch that i'd like to control with my ohm64 controller.

i'm new to working with incoming midi data in max, and was hoping someone could give me a few tips on how to do the following:

the main 64-button grid will be used to select samples for playback. just one at a time for now. i'd like the button corresponding to the currently playing sample to remain lit up until i select another one. so i'll need to send a note on message to the ohm64 when i push a button, so that it lights up, and then when i select another button the previously pressed one should go out again. and the new one on, of course.

at the moment i'm trying to figure out how to automatically switch off the previously pressed button when i press a new one. does anyone have a tip for that maybe?

my ohm64 input-patch so far is pasted below. at the moment it's only four faders controlling playback volume, the matrix for choosing a sample, and a primitive playback speed control.

another questions, also about the data coming out of the notein object: what would be the best way to filter/distribute note on messages from the other buttons on the controller? these are controllers 65 to 81.

is there an object that allows me to specify ranges to pass through? for example "if the number is between 1 and 64, send out this outlet", "if the number is 65, send here" etc?

my impression is that route doesn't allow me to specify a certain range to pass through?

i'm building a sample-player patch that i'd like to control with my ohm64 controller. 

i'm new to working with incoming midi data in max, and was hoping someone could give me a few tips on how to do the following: 

the main 64-button grid will be used to select samples for playback. just one at a time for now. i'd like the button corresponding to the currently playing sample to remain lit up until i select another one. so i'll need to send a note on message to the ohm64 when i push a button, so that it lights up, and then when i select another button the previously pressed one should go out again. and the new one on, of course. 

at the moment i'm trying to figure out how to automatically switch off the previously pressed button when i press a new one. does anyone have a tip for that maybe? 

my ohm64 input-patch so far is pasted below. at the moment it's only four faders controlling playback volume, the matrix  for choosing a sample, and a primitive playback speed control. 

another questions, also about the data coming out of the notein object: what would be the best way to filter/distribute note on messages from the other buttons on the controller? these are controllers 65 to 81. 

is there an object that allows me to specify ranges to pass through? for example "if the number is between 1 and 64, send out this outlet", "if the number is 65, send here" etc?
my impression is that route doesn't allow me to specify a certain range to pass through?

midi-into-max-with-livid-ohm64-controller

split lets you divide a stream of numbers into ranges.

I'm not in front of my block right now, but there are many ways to achieve the only one button on at a time thing.

In general, building in deep, stateful, control of a complex patcher using something like the block/Ohm is a chunk of work.

I'm not in front of my block right now, but there are many ways to achieve the only one button on at a time thing. 

In general, building in deep, stateful, control of a complex patcher using something like the block/Ohm is a chunk of work.


i can't get the buttons to light up and then switch off again when another one is selected with your patch yet, but i'll try tweaking it. i haven't used any of those objects you just introduced me to yet.

yeah, i realize this is gonna be a fair amount of work, but i think it will be worth it ;)

i've never had a comprensive midi controller like this, so after a few years of mousing around this is exciting to me.

chris,
many thanks for those suggestions!

i can't get the buttons to light up and then switch off again when another one is selected with your patch yet, but i'll try tweaking it. i haven't used any of those objects you just introduced me to yet. 

i've never had a comprensive midi controller like this, so after a few years of mousing around this is exciting to me.


I didn't actually try that patch, but I will next time I'm in the studio.

i'll go over the patch part by part to make sure i understand what's going on

i'd be interested in seeing other examples of what ohm/block users are doing with their controllers within max. once i'm done with the midi control elements of my sampler patch i can share that if anyone's interested.

I have fairly deep block support in my Gyre step sequencer-ish thingie.


if i may ask for another tip, would you have any hints on how to map the buttons below the faders to "startloop" and "stop" messages to send to groove~ objects maybe?

i'm trying to turn these buttons into simple transport start/stop toggles, where the button stays lit as long as the groove~ is playing, and then turns off when i push it again.

making one button on a midi controller switch between two functions (in this case "stop" or "startloop") depending on the current status of the patch is something i'm trying to wrap my head around at the moment.

if i may ask for another tip, would you have any hints on how to map the buttons below the faders to "startloop" and "stop" messages to send to groove~ objects maybe? 

i'm trying to turn these buttons into simple transport start/stop toggles, where the button stays lit as long as the groove~ is playing, and then turns off when i push it again. 

making one button on a midi controller switch between two functions (in this case "stop" or "startloop") depending on the current status of the patch is something i'm trying to wrap my head around at the moment. 

This sort of support should probably be done in a series of abstractions, but maybe this will give you some ideas.

@shaar: I've been using an Ohm64 for a little while now, mainly for quick controller assignments but I did build a little drum machine that works specifically with the device recently. The patch is a mess but once my computer's back out of a box (new home) I'll put it up. It makes use of some of the things you've talked about here (although I haven't read the whole thread) such as toggled button lights and blinking lights for sequencing steps.

Ace controllers aren't they? I wish I'd waited for the new design of the Ohm though, mine doesn't look as cool in comparison!

@ chris muir, many thanks for the patch! will go over it tomorrow morning when my mind is fresh(er) and report back.

@ dickmedd, please do. would be interested in seeing how others use it.

i also am very impressed with the machine so far. first time i'm using a comprehensive midi controller that combines buttons, dials and faders and it's been really inspiring to play with the past few days.

@ dickmedd, please do. would be interested in seeing how others use it. 

i also am very impressed with the machine so far. first time i'm using a comprehensive midi controller that combines buttons, dials and faders and it's been really inspiring to play with the past few days.


Please Shaar, Can you attach the patch of the sampler controlled via Ohm64 complete?.

MIDI into Max with Livid Ohm64 controller