• Date
    travisres
  • Date
  • Replies 6 replies
  • Subscribers 185 subscribers
  • Views 4584 views
  • Users 0 members are here

Bug: Midi Raw in Macro's and backup consoles

Hi Team,

We've been using Midi Raw notes on the current show to trigger some sound and video cues / scripts in Qlab. We've discovered a bug where if a cue  fired from the go button on the backup executes a macro which sends a MidiRaw note, it is not actually sent.  If you run the same q on the main console, it works as expected. The work around has been to put the Midi Raw straight into the Execute of the Cue and then either console's go button will fire it correctly.

We also have the problem that if the backup console tries to manually fire a macro [Macro] <xxx> [Enter] the macro will run, but the Midi note will not be sent. Firing the same macro from the main works as expected.

This is 2 Ions running 2.2.0. We aren't in a position to try 2.2.1 at the moment.

2 x 4 port gateways and a Show Control gateway are also on the network as well as an RVI or two.

  • The second issue is expected behavior, I think. You manually fire a macro, that's something that happens locally i.e. the backup console, but midi is not connected there. Regarding the first issue I agree, I wouldn't expect that either... Macros executed from a cue should happen on the master
  • in reply to ueliriegg

    Hi Ueli,

    Thanks for the reply. I guess I figured that even though its a backup desk, since we are using a Show control gateway, the MidiRaw command would be sent to whatever central sub routine handles Midi to then decide if its going out to a show control gateway, or to a local midi port, or how ever that decision is made.

    I guess I feel that if that is expected behavior, that is is not really correct for a multi console system. If I think of a standard Bway show, there may be multiple desks / programmers on the network; Conventional, Moving Light, Video etc... during the tech process. If Midi can only be sent by a specific programmer (the master), this seems counter productive to having multiple programmers who in theory can do their own thing when they need to, and link up with everyone else in other situations.

    Or thinking of a TV studio where often the mater and backup are RPU's in a rack somewhere, and there are roving consoles or RVI's in shading for actual show control.

    Or am I misunderstanding...

    Thanks,

  • in reply to travisres
    i was thinking about local midi. i hereby retract my earlier statement and let the good folks at ETC answer ;)

  • Hello!


    Would you mind shooting over the show file?

    Do you know the mode of the macro?

    Thank you,

  • in reply to saranow
    Hello Benjamin,

    Sasha asked me to look at your show file and there, is definitely a software bug here. Each of your macros that fire a midi raw instruction begin with "_clear_cmd"

    If you remove that, the macros will work from the backup as expected.
  • in reply to Nschu3728

    Hi Schulze,

    Thanks for this. Removing the _clear_cmd did indeed work for us.

    As you all look into the bug, I wanted to point out something I noticed before we made the change. While the backup console wouldn't fire the MidiRaw macros's either directly, or via a Cue execute, when the iPad connected to the backup ran the checkout cue list which had the macro's as cue executes, they worked correctly.

    I'm not sure why the iPad connected to the backup worked, but the actual go button on the backup didn't, but I thought I would point it out.

    Thanks again.

Related

www.etcconnect.com