MIDI data with timestamps in the future?
MIDI data with timestamps in the future?
- Subject: MIDI data with timestamps in the future?
- From: Pete Yandell <email@hidden>
- Date: Tue, 23 Jul 2002 18:20:28 +1000
According to the documentation for MIDISend:
"Events with future timestamps are scheduled for future delivery"
Unfortunately this doesn't seem to be true in practice.
I've had a report from somebody using CoreMIDI to send data through a
virtual endpoint to my application (SimpleSynth) that packets injected
with future timestamps are played immediately by SimpleSynth.
Internally SimpleSynth simply passes incoming MIDI data to the built-in
synth audio unit.
My question is this: whose responsibility is it to actually delay the
packets? I would have thought it was up to CoreMIDI. If I have to do
it myself, my app gets a lot more complicated...I would have to add
parsing of MIDI data and some fairly complex scheduling code.
I'm currently trying to put together a complete test...I'll post again
when I have.
Pete Yandell
http://pete.yandell.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.