Roman Thilenius

i need to rethink and rebuild my midi in and midi out 

abstractions. coming from OMS and currently using OS9 

Max 410 and OS 10.4.11 PPC Max 460 i have some basic 

questions about recognizing and creating channels and 

i am used to think in the following system:

channel 1 at port 1 is number 144, channel 2 is 145.

now is this still valid with max 5 and also with windows?

eventually i want to stop having an interface between my

midi formatting abstraction and the midiout abstractions

but only if that will really work on all systems.

i need to rethink and rebuild my midi in and midi out 
abstractions. coming from OMS and currently using OS9 
Max 410 and OS 10.4.11 PPC Max 460 i have some basic 
questions about recognizing and creating channels and 
ports on ymy midi data.

channel 1 at port 1 is number 144, channel 2 is 145.
160 is channel 12 of port 2 and so on.

eventually i want to stop having an interface between my
midi formatting abstraction and the midiout abstractions
but only if that will really work on all systems.

midi-advice

I'm not sure if this helps your situation but I've become a big fan of using port abbreviations with relevant objects in conjunction with max's options > midi setup dialog to interface with my studio devices (rather then having device assignments stored in patch menus).

Bradford Reed wrote on Tue, 19 May 2009 19:59

it is an idea to think about yet not in this context.

besides presets what i do is a "matrix" for realtime control 

so i want to be sure if this "144" logic still works everywhere. 

Bradford Reed wrote on Tue, 19 May 2009 19:59Hi Roman,

besides presets what i do is a "matrix" for realtime control 
(which port should this chord go?)

so i want to be sure if this "144" logic still works everywhere. 


midi advice