Page 1 of 1

MIDI note sent on update

Posted: Sun Nov 29, 2009 1:02 pm
by amoyer
So we are in the middle of our seasonal favourite (nightmare) of Nutcracker and this year we some how ended up without a sound operator so I decided I would send MIDI notes to the sound computer to fire the cues. I took one of the playbacks on the Light Palette Live and created a cue that just sent a MIDI note on as a macro every time the cue is fired. The cue worked fine and I thought we were all set until before the first rehearsal when we were checking levels in the cues and every time we recorded or updated a cue in the main cue list it sent also fired that macro. Seeing this as a potential problem for the rehearsal, as the LD was still going to be adjusting levels, I moved the macro to a look bump button.

Any idea why it would be firing the macro on a different cue list?

Re: MIDI note sent on update

Posted: Sun Nov 29, 2009 5:02 pm
by RobertBell
Is it sending a NOTE or MSC? If the cue list has MIDI checked in Properties, it will send a MSC GO (with number) on each GO.

Only if you are asserting a cue on the other list - should it send the GO. Maybe there is a palette in that list and we assert all cue lists using palettes you update. Or... maybe we assert all cue lists on ANY update. That might be dumb.

Re: MIDI note sent on update

Posted: Sun Nov 29, 2009 5:50 pm
by amoyer
RobertBell wrote:Is it sending a NOTE or MSC? If the cue list has MIDI checked in Properties, it will send a MSC GO (with number) on each GO.
Definitely sending a NOTE. HC.MidiNoteOn(1,1) to be specific.

Asserting all cue lists on ANY update might be the problem here. I don't think it should do that.

Re: MIDI note sent on update

Posted: Sun Nov 29, 2009 8:44 pm
by RobertBell
Or - only do macro on GO (into) cue vs. Asserts. I think it should do it on GOTOs, but maybe not asserts.

Re: MIDI note sent on update

Posted: Mon Nov 30, 2009 11:37 am
by BrianEvans
Go's and Goto's only for macros.
Having macros trigger on an update is deffintely a pain.

Re: MIDI note sent on update

Posted: Mon Nov 30, 2009 1:17 pm
by GaryDouglas
Rather than prevent the macro on reassert globally ( Since this can be useful under other circumstances) , I think it would be better for the script on the cue to check to see if the current cue number being asserted is different than the last cue number run.

This can be done by declaring a global 'current cue number' variable for each cue list and then checking that before sending the midi note. When you send the midi note, also set the variable to the last cue number that did it.