On 09/08/2011 04:31 AM, frankster wrote: > Can anyone think of anything simpler that would do the job? Although one > advantage of this is that it would > keep the driver simple, and all the complexity would be in core base > classes. >
Well, i can think of something more complicated, but maybe more universal. So the idea is that synth driver would register with core each kind of midi message it is going to send. During registration it specifies max rate or processing time for each message. Also it specifies the type - only last message of the kind shall be sent, or all queued messages of the kind shall be sent. Also maybe priority with respect to other messages. Then the drivers submit messages for sending to core in any order at any rate. The core maintain the queues for each registered kind of message. When the interface is available, the core selects among the queues next message, send it and blocks the sending for time specified at registration. -- Vladimir ------------------------------------------------------------------------------ Doing More with Less: The Next Generation Virtual Desktop What are the key obstacles that have prevented many mid-market businesses from deploying virtual desktops? How do next-generation virtual desktops provide companies an easier-to-deploy, easier-to-manage and more affordable virtual desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/ _______________________________________________ Jsynthlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel
