Hallo, Ryan Supak hat gesagt: // Ryan Supak wrote:

I'm trying to use PD as a MIDI routing tool -- I was using MIDIOX but I want to go a little more in-depth. Right now I'm still trying to learn the basics.

I'm currently playing with the ~notein

Careful With That Tilde~, Eugene. ;) It has a special meaning in Pd conventions (the philosphical ones, not the real ones), that is denoting signal objects and then belongs to the end of the object name.

and ~ctlin objects, and apparently the ~notein is aware of note number, velocity, and midi input number -- and the ~ctlin is aware of ctrl number, ctrl value, and midi input number.

1. what's the best way to determine the midi channel of incoming

data (and ultimately to output the data stream as a certain midi channel)?

Well, look at the midi channel outlet of [notein] or [ctlin], it sends the midi channel number.

2. I used pd -midiindev x,y to tell pd which midi inputs I wanted.

MIDI input 1 is showing up as "1", according to ~notein and ~ctlin, but MIDI input 2 is showing up as "17" or "20" (depending on the parameter used).

Yes, that's normal: The first device in Pd sends midi channels 1-16, the second sends 17-32 and so on for each device you can add.

To me it seems, that you are using the term "midi input" in a not really consistent way. IMO it's better to not talk of "input" but of:

• Midi device: the thing with plug and cable
• Midi channel: one distinct channel to send midi data like e.g. notes or controller data. Generally midi devices have 16 of these. Also be aware that some operations are "Omni", that is, they get sent to all (16) channels ("bend").
• Controller numbers (CC): These don't really compare with above, better think of them as the equivalent to the notes in [notein].

3. Is it possible to send Program Change messages with PD?

[pgmin] and [pgmout] are for Program Change messages.

Ciao

Frank Barknecht _ ______footils.org__