Joseph Guisti

I've been using max primarily to remap the notes that a midi controller plays: I'm not sequencing or automating anything. There are no clocks or sequencers or anything. I simply want the first four pads of my midi controller to play notes from a scale I choose, things like that.

My current approach: I'm using 'split' to split off chunks of notes, then I'm using tables and colls to replace the note numbers in those splits with notes I choose from menus. The problem is that the operations affect the note number part of the midi message for each note I play, but the note numbers are totally off in their own world apart from the rest of the midi message associated with each note I play on my controller.

I've got a fix for the velocity, based on code I found here on the forum. But I'm at a loss for the rest. I'm wondering if there is a way I can keep all the velocity/channel/polypressure information for each note press somehow in a table so that it can be re-united with its note number siblings before hitting midiout.

**For extra fun, it would also be great if I could manipulate or scale that other midi message information, enabling me to, for instance, send different parts of the keyboard to different midi channels that I choose from a menu.

I've been using max primarily to remap the notes that a midi controller plays: I'm not sequencing or automating anything. There are no clocks or sequencers or anything. I simply want the first four pads of my midi controller to play notes from a scale I choose, things like that. 

My current approach: I'm using 'split' to split off chunks of notes, then I'm using tables and colls to replace the note numbers in those splits with notes I choose from menus. The problem is that the operations affect the note number part of the midi message for each note I play, but the note numbers are totally off in their own world apart from the rest of the midi message associated with each note I play on my controller. 

I've got a fix for the velocity, based on code I found here on the forum. But I'm at a loss for the rest. I'm wondering if there is a way I can keep all the velocity/channel/polypressure information for each note press somehow in a table so that it can be re-united with its note number siblings before hitting midiout. 

**For extra fun, it would also be great if I could manipulate or scale that other midi message information, enabling me to, for instance, send different parts of the keyboard to different midi channels that I choose from a menu. 

I've been using max primarily to remap the notes that a midi controller plays: I'm not sequencing or automating anything. There are no clock

how-do-i-make-custom-scales-for-my-keyboard-while-keeping-polypressure-and-velocity-information-attached-to-each-note

linnstrument theory cheater.zip

I would probably not use [split] but instead, I would transpose any notes in 1 to 12 with [%], and use a [coll] for 1 to 12, where if I would say if 1 is played, add 0, if 2 is play, add -1, if 3 is play, add 0, is 4 is play, add 1 etc... and I would use that to change the MIDI note without altering the velocity and channel using [unpack 0 0 0] [+]and [pack 0 0 0].

I would probably not use [split] but instead, I would transpose any notes in 1 to 12 with [%], and use a [coll] for 1 to 12, where if I would say if 1 is played, add 0, if 2 is play,  add -1, if 3 is play, add 0, is 4 is play,  add 1 etc... and I would use that to change the MIDI note without altering the velocity and channel using [unpack 0 0 0] [+]and [pack 0 0 0]. 

"and I would use that to change the MIDI note without altering the velocity and channel using [unpack 0 0 0] [+]and [pack 0 0 0]. "

I follow what you're saying, and using a modulo to play with midi notes is more common practice that what appears in my code, but I'm not convinced that is gonna solve my problem. Another way of stating my question: What about the [split] object changes the velocity or the channel any more (or less) than using a [%] and [coll] would?

From my initial experimenting, it seems that using a [%] doesn't solve the issue of hanging notes, glitchy polypressure data, and the rest of the things that happen when you do multiple operations on multiple notes without explicitly telling Max to keep track of each note and it's associated pressure/channel/velocity/etc. data.

If you look at the patch I include, I use a bit of code that I found to keep the velocity stuff intact. I found it because someone else was having the same problem I was, and I believe they were using the % method for note operations but they were still getting hanging midi notes.

I follow what you're saying, and using a modulo to play with midi notes is more common practice that what appears in my code, but I'm not convinced that is gonna solve my problem. Another way of stating my question: What about the [split] object changes the velocity or the channel any more (or less) than using a [%] and [coll] would? 

From my initial experimenting, it seems that using a [%] doesn't solve the issue of hanging notes, glitchy polypressure data, and the rest of the things that happen when you do multiple operations on multiple notes without explicitly telling Max to keep track of each note and it's associated pressure/channel/velocity/etc. data. 

If you look at the patch I include, I use a bit of code that I found to keep the velocity stuff intact. I found it because someone else was having the same problem I was, and I believe they were using the % method for note operations but they were still getting hanging midi notes. 

How do I make custom scales for my keyboard while keeping polypressure and velocity information attached to each note?