On 22/11/2011 20:10, Frankie Fisher wrote: > I actually did a little bit of work tidying a few drivers up last month > because a number of them claimed ownership of pretty much any device id > that they were passed. Oh!
> Anyone know how other software like this such as sounddiver etc deal > with detecting synths that don't support the standard midi enquiry? I seem to remember speaking to someone at Sound Quest about this; I'll try to dig up the answer if I've still got it in my email somewhere. > > I agree that a mechanism that gives a driver an opportunity to define or > carry out a custom enquiry could be useful for cases like this. Perhaps > an overridable function in the driver's base class which accepts a > device id and channel, and generates the appropriate message, and after > the standard sysex detection procedure has been run, it can do the same > for any driver that has overridden this function. Yes, exactly the sort of thing I was thinking of. Perhaps I should raise a feature request for it? John > frankie > > On 22/11/2011 15:11, John McCabe wrote: >> Hi >> >> Has anyone considered looking at the MidiScan stuff to deal more >> 'elegantly' with synths that don't respond to an device inquiry as per >> the MIDI standard? >> >> I noticed there is special code in there for the Waldorf Microwave 2, >> the Yamaha SY85 driver mentions that it doesn't respond and (my own >> 'project' at the moment) the Kawai K1 also doesn't respond to a standard >> MIDI device inquiry. >> >> I don't know about the SY85, but the K1 does have its own Machine ID >> request which seems a similar sort of thing so it may be relatively >> simple to refactor the code so that it sends a device inquiry then, if >> it doesn't get a response, loops round the installed device drivers >> checking for any that might have their own ID request etc.... >> >> John >> >> >> ------------------------------------------------------------------------------ >> All the data continuously generated in your IT infrastructure >> contains a definitive record of customers, application performance, >> security threats, fraudulent activity, and more. Splunk takes this >> data and makes sense of it. IT sense. And common sense. >> http://p.sf.net/sfu/splunk-novd2d >> _______________________________________________ >> Jsynthlib-devel mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure > contains a definitive record of customers, application performance, > security threats, fraudulent activity, and more. Splunk takes this > data and makes sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-novd2d > _______________________________________________ > Jsynthlib-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel > ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ Jsynthlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel
