pechnatunk

I'd like to automate controller data in Max/MSP and send it to my korg rhythm synth (ER1mkii) at the Max end this seems quite easy.

But I can't seem to make sense of my korg's MIDI Implementation and it's data that appears in the max window.

my max window shows this with one data inc/dec being sent from the synth1 pitch knob.

I've worked out that 176(~191) is midi channel 1(~16), 12 is the CC value and 6 is the controller number, but i'm not sure about the others.

Using ~prepends and ~appends I've tried sending these numbers to the korg in various ways using single numbers/lists of 3 etc, but still to no avail.

I know this is not exactly a Max/MSP question but korg forums were no use.

I'd like to automate controller data in Max/MSP and send it to my korg rhythm synth (ER1mkii)  at the Max end this seems quite easy.

But I can't seem to make sense of my korg's MIDI Implementation and  it's data that appears in the max window.

nm | nl |   Parameter |          dd(MSB)   |      ds|
02 | 02 |   Syth Pitch  |         0~127      |     04 |

print:176
print:99
print:2
print:176
print:98
print:2
print:176
print:6
print:12

I've worked out that 176(~191) is midi channel 1(~16), 12 is the CC value and 6 is the controller number, but i'm not sure about the others.
Using ~prepends and ~appends I've tried sending these numbers to the korg in various ways using single numbers/lists of 3 etc, but still to no avail.

I know this is not exactly a Max/MSP question but korg forums were no use.
pls help
thanks
vic

maxmsp-is-fine-i-have-a-midi-problem

On 31 janv. 07, at 08:00, pechnatunk wrote:

A control change is composed of 3 bytes. The first by (here your 176) 

define it's a cc on a certain channel, the second is the controler 

number, the last one is just the controler value. So this is just the 

raw midi data. You don't need to generate that and send it to 

midiout, because ctlout does that for you.

> print:176
> print:99
> print:2
> print:176
> print:98
> print:2
> print:176
> print:6
> print:12

A control change is composed of 3 bytes. The first by (here your 176)  
define it's a cc on a certain channel, the second is the controler  
number, the last one is just the controler value. So this is just the  
raw midi data. You don't need to generate that and send it to  
midiout, because ctlout does that for you.

I now know whats going on with the NRPN's and CC's.

Well i know that 99, 98 and 6 are nrpn parameter numbers.

But it is still not as simple as you say - entering the controller value (n) controller number (2) and the channel (1) into a ctlout.

I also tried using 258 as the controller number. 

OK thanks, 
I now know whats going on with the NRPN's and CC's.

Well i know that 99, 98 and 6 are nrpn parameter numbers.
But it is still not as simple as you say  - entering the controller value (n) controller number (2) and the channel (1) into a ctlout.

I also tried using 258 as the controller number. 
(MSB x 128) + LSB 
(2 x 128) + 2

> ps. why is channel 1 represented as 176

And you should learn the Midi specification:

http://www.borg.com/~jglatt/tech/midispec.htm

http://www.midi.org/about-midi/specshome.shtml

pechnatunk wrote:
> ps. why is channel 1 represented as 176

-- 
Stefan Tiedje------------x-------
--_____-----------|--------------
--(_|_ ----|-----|-----()-------
-- _|_)----|-----()--------------
----------()--------www.ccmix.com


Max/MSP is fine - I have a MIDI problem.