Re: Scheduling Midi data using 'MidiReceived'
Re: Scheduling Midi data using 'MidiReceived'
- Subject: Re: Scheduling Midi data using 'MidiReceived'
- From: Doug Wyatt <email@hidden>
- Date: Mon, 17 May 2004 16:14:41 -0700
Yes, that's the way the current implementation works -- there is no
schedule-ahead for sources. Unfortunately you'll have to do your own
scheduling.
I have a bug to address this ...
Best,
Doug
On May 15, 2004, at 12:10, Mark Gilbert wrote:
Folks.
I am scheduling time sensitive data with CoreMidi. I prepare my data,
then schedule it with 'MidiSend' with a defined timestamp for the time
at which I want it actually sent.
This works fine with MidiSend, going to real Midi ports, or IAC buses.
However, when I try to do the same thing with a Virtual midi source
(created by my app), using 'MidiReceived', the timestamp is ignored,
and the packet gets sent immediately, instead of waiting for the
timestamp.
I treat my 'virtual source' in exactly the same way as a real output
endpoint. Is this a bug, or do I need to do things differently with
MidiReceived. The port is working perfectly in all aspects apart
from this forward scheduling issue.
Any ideas ?
Cheers
Mark Gilbert.
--
email@hidden
Tel: +44 208 340 5677
fax: +44 870 055 7790
http://www.gallery.co.uk
http://www.mtools.info
http://www.metaflow.info
http://www.virtualvtr.com
http://www.libraryloader.com
New Product !!!
http://www.pictureready.com
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.