Re: [Jsynthlib-devel] mysterious manufacturer ID!

2011-09-06 Thread frankster
Nice find - that guy is using a Keystation Pro 88 and I have this keyboard, so this pretty much proves the device ID is coming from the keyboard. thanks. On 06/09/2011 22:03, Narfman96 - Narfland Studio wrote: > Hi Guys Glad to see the project back up and active... I'm a long time > lurker a

Re: [Jsynthlib-devel] mysterious manufacturer ID!

2011-09-06 Thread Narfman96 - Narfland Studio
Hi Guys Glad to see the project back up and active... I'm a long time lurker and JSynthLib user. I'm not a programmer by any means but I help out when I can.   To support what you found the 00H 20H 08H sysex ID for a Keystation midi controller is mentioned on this Linux site:  http://www.sp

Re: [Jsynthlib-devel] mysterious manufacturer ID!

2011-09-05 Thread Vladimir Avdonin
On 09/04/2011 06:33 AM, frankster wrote: > Assuming that it is the Keystation Pro 88 that is responding, then of Did you try to autoscan when nothing but keystation is connected? -- Vladimir -- Special Offer -- Download

Re: [Jsynthlib-devel] mysterious manufacturer ID!

2011-09-05 Thread William Zwicky
On Sun, Sep 4, 2011 at 4:33 AM, frankster wrote: > 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-aud

[Jsynthlib-devel] mysterious manufacturer ID!

2011-09-05 Thread frankster
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