From: frankster <jsy...@te...> - 2011-09-05 09:03:33
|
So I've been playing with the auto scan functionality a little bit this weekend (I've made a standalone class which invokes MidiScan without a GUI which makes testing the device identification a little easier). In case anyone reading this is unfamiliar with the auto-scan, it basically sends out sysex Device Inquiry messages, which should elicit a response from compatible devices allowing the appropriate driver to be identified. I was testing the scanning for my Proteus 2000 so I was expecting to see one response to the Device Inquiry message, however I also received responses from an additional device! The Proteus 2000 is connected to the midi interface on my M-audio Keystation Pro 88 keyboard which in turn is connected via usb to my PC, so I would assume that the response is coming from this. However, the manufacturer ID that I would expect this to generate would be 00H 01H 05H according to the list at http://www.midi.org/techspecs/manid.php while the ID that I see is actually 00 20 08! f0 7e 7f 06 02 *00 20 08* 4d 14 35 01 20 31 30 31 f7 And on that manufacturer id list there is no entry for 00 20 08, although that list is incomplete and I would have to spend £50 to get them to post me the complete midi spec. Assuming that it is the Keystation Pro 88 that is responding, then of course I will have to implement librarian support for the "patches" on they keyboard although there's no mention of sysex in its manual. Anyway, the question that remains from all this is: does anybody have any idea what this manufacturer id is? cheers, Frankie |