Re: CoreMidi MIDIFlushOutput
Re: CoreMidi MIDIFlushOutput
- Subject: Re: CoreMidi MIDIFlushOutput
- From: Doug Wyatt <email@hidden>
- Date: Mon, 11 Jun 2012 08:50:38 -0700
Hi,
The network driver uses a protocol with timestamps. It has already transmitted the data to the far end.
Doug
On May 18, 2012, at 9:20 , Frank Kugler wrote:
> Hello,
>
> I try to develop a little MIDI-APP on iOS.
> In this App, I send MIDI-Clock signals and I do this with a MIDITimestamp. To let CoreMidi do the hard work of timing and delivering at the right time I send the MIDI-Clock a little bit earlier. How much earlier depends on the latency of the midi connection. Lets say the greatest value is 300 ms.
> So a couple of messages are always allready send to CoreAudio and for some reason I want to cancel all outstanding MIDI-Messages by calling
> MIDIFlushOutput(NULL);
> this should cancel all pending schedules on all destinations.
>
> If I use an external MIDI-Device for the iOS-Device it works. But it does not work for the MIDI Netwok connections.
> So I wondering if I forgot something, or didn't find the hint in the documentation that this is not possible. Or is it a bug ?
>
> Thanks and Regards,
> fk
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Coreaudio-api mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden