Stuck notes - dropped midi events - solved.
Stuck notes - dropped midi events - solved.
- Subject: Stuck notes - dropped midi events - solved.
- From: Todd Blanchard <email@hidden>
- Date: Wed, 5 Sep 2007 11:06:04 -0700
On Sep 4, 2007, at 5:35 PM, William Stewart wrote:
The SetRenderCallback is a callback that is only for providing
audio input to an AU that has audio input. As the music device
doesn't have audio input it fails as you see.
Ah - OK, I didn't spot the render notify api and assumed they were
the same thing. Gotcha.
MusicDeviceMIDIEvent is an API call that is made to schedule MIDI
events to a synth or effect that supports MIDI. Some releases ago,
we had a threading problem with scheduling notes on or off from the
non-render thread, but this has been fixed for some time now, so
this won't be your problem.
Actually - that is precisely my problem as it turns out. There is at
least one commercially available virtual instrument out there that
does not like to have midi pushed at it outside of its render
thread. Queueing midi in the receive thread and sending it in the
render thread of the device has solved my problem and midi response
is now rock solid where before it was very glitchy. So, I don't
think I'd relax that requirement at all unless you are going to
provide queueing for the device behind the scenes for the virtual
instrument implementor somehow.
If you are interested in knowing which nifty instrument has the issue
- email me privately. I don't want to give them a bad rep. It is a
really great instrument.
-Todd Blanchard
_______________________________________________
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