Re: Spurious MIDI note-on messages in AU
Re: Spurious MIDI note-on messages in AU
- Subject: Re: Spurious MIDI note-on messages in AU
- From: Stephen Blinkhorn <email@hidden>
- Date: Mon, 18 Aug 2008 22:36:20 -0600
On the off chance that anyone else has a similar problem I tracked my
bug down to a dodgy pointer in MySynthNote::Attack() which caused that
function to 'bum-out' early for want of a better expression. In
MonoTimbralInstrumentBase::RealTimeStartNote() below you can see that
IncNumActiveNotes() is called before AttackNote which is why I got
seemingly spurious note-on events.. I post just in case anyone else
makes this kind of mess :)
IncNumActiveNotes();
note->AttackNote(NULL, ..)
inGroup->mNoteList[kNoteState_Attacked].AddNote(note);
return noErr;
Stephen
On 6 Aug 2008, at 09:54, Stephen Blinkhorn wrote:
Hi all,
I know this a slightly long shot and a slightly desperate post :)
For some reason, after recent code changes of course, I'm getting
spurious MIDI note-on messages the first time my synth receives a
note. 6 to be precise. The problem is that these message are not
accompanied by a note-off so they just get stuck and are no longer
free notes. This is for a synth built upon the SinSynth structure
although a lot has changed. But I don't know why my changes have
affected this area. It seems that StartNote in AUInstrumentBase is
putting 6 extra note-on events in the SynthEventQueue which
PerformEvents picks up and then calls RealTimeStartNote.
Anyway, does this ring any bells for anyone.
Thanks,
Stephen.
_______________________________________________
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