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.

Parents Reply Children
  • 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