Re: Stuck Notes and MIDIPacketList
Re: Stuck Notes and MIDIPacketList
- Subject: Re: Stuck Notes and MIDIPacketList
- From: Robert Grant <email@hidden>
- Date: Sat, 31 Jan 2004 16:08:27 -0500
Hi James,
Well the two I've managed to get stuck are Claw and Zebra. But as I
said - it's only after a good while when I eventually hit the right
combo (I imagine).
I've got Reason ReWired into my app - so I was using that to make sure
I was not dropping the note offs in my logic before the notes get
delivered to the synths.
Robert.
On Jan 31, 2004, at 4:02 PM, James Coker wrote:
Which AU synths? I still see stuck notes w/ NI plugins, but
very rarely w/ anything else. I think this happens w/ NI plugins
in my app (Numerology) because I currently send notes from a thread
that is not the AU render thread. This issue does not occur when
I run NI plugins standalone.
Note that the method that a standalone app (Reason) uses
to get MIDI notes is a bit different from what an AU receives.
Jim
On Jan 30, 2004, at 5:34 PM, Robert Grant wrote:
Here's an update. I think it may be an issue with particular synths.
Running a test with identical MIDI going to Reason synths and an AU
synth the AU synth got stuck but the Reason synths were fine. Another
test running 3 AU synths with the same MIDI data one AU synth didn't
get stuck while the others did.
It's hard to identify the condition that causes the stuck notes as I
now have to just whale (sp?) on the keyboard for quite a while before
a note sticks, but eventually one will. (I'm also moving the Mod
Wheel just to maximize the MIDI data flow).
The notes are being delivered on the Render thread. The mod wheel
changes are on another thread (if that's of interest).
Robert.
On Jan 29, 2004, at 6:54 PM, Doug Wyatt wrote:
On Jan 29, 2004, at 11:40, Robert Grant wrote:
The only thing I can think of now is that I'm taking too long in
the MIDIInputProc and the PacketList is being overwritten with a
new set of Packets (thus potentially losing a Note Off). Is this a
possibility?
No. The code that calls your input proc copies packetlists out of
the shared memory between the client and server, and into the stack.
I assume you're copying packetlists and not keeping copies of
pointers to them?
Doug
--
Doug Wyatt
Core Audio, Apple
_______________________________________________
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.
_______________________________________________
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.