On Dec 8, 2010, at 8:32 AM, Roger Dannenberg wrote: > I'm not clear on exactly what you are observing, nor have I used a Korg > nano controller, but if you haven't found it, the "mm" program in > pm_tests is a "Midi Monitor" that will print details of the MIDI stream > to the console. This might help make the MIDI stream more fully visible > and easy to analyze. > > -Roger
Thanks Roger, That program shows pretty much the same info as my altered test program; as well as the same undesirable behavior. It makes channels visible, but I don't think that's all that important for my implementation. Unless a user wanted to use one program to output to the midi device to drive its controls (my Korg doesn't have that functionality) while simultaneously inputing that data to my plugin. I'm guessing different midi channels would need to be used to make that happen? The only time the channel changes is when I set that scene switch control on my device to #4, then the channel changes for each control but the controls ID's always stay the same (for each different type of control at least). Otherwise the channel output is always 0. I guess that makes sense though:) On Dec 8, 2010, at 8:03 PM, [email protected] wrote: > Kevin, > > I don't know that device, but controllers #1 and #7 and #11 are very commonly > used for Modulation wheel and Volume and Expression, so maybe Korg skipped > those in order to avoid conflicts. > > However, usually (at least for Mac and Windows) Korg has a device driver with > an editor so that you can remap the controllers to any number you want. > > - Rick Thanks Rick, Aha! A pattern. And I guess since HID devices are all pretty much the same (referring mostly to joysticks here) and midi devices can vary wildly, it makes sense that a cheap device like this Korg would be missing some control indexes. Is there any way in PortMidi to automatically detect what controls are present and which ones aren't so I can easily adjust for this? Thanks a lot guys, _______________________________________________ media_api mailing list [email protected] http://lists.create.ucsb.edu/mailman/listinfo/media_api
