Redundant midi outputs

General
1

Hallo!

I have a question regarding redundant midi outputs with Ableset.

How do i make sure that sure the midi outputs keeps working after switching to computer B?

And how do i make sure I dont get double triggers?

Thx in advance

2

Hey @AdamSampler,

“MIDI outputs” can mean two different things in a redundant setup depending on your approach, and they’re solved in completely different ways. Here’s how each one works:

MIDI going out of Ableton Live

This is when you have MIDI tracks in your session sending notes/CCs to external gear (synths, lighting desk, a mioXM, etc.).

In this case both computers need to be connected to that destination, for example both USB ports of a mioXM/mioXL, or two separate inputs on your MIDI interface. Otherwise MIDI stops as soon as computer A goes down.

To avoid double triggers, use the +FOLLOWSCENE flag (short form +FS) on those MIDI tracks, for example:

Keys MIDI +FS

First, set the Connected Scene dropdown in AbleSet’s settings for each machine (in the “AbleNet on [Computer Name]” section) — computer A to Scene A, computer B to Scene B of your redundant audio interface. AbleSet then automatically mutes the flagged tracks on whichever computer is not currently selected on the interface. When the interface switches to B, B’s tracks unmute and A’s mute, so only one machine is ever sending MIDI.

MIDI going out of AbleSet itself

This is when AbleSet sends the MIDI — through MIDI mappings using /midi/send/note, /midi/send/cc, etc., through OSC tracks, or through scripting with sendMidiNote() / sendMidiCc().

Here, with AbleNet enabled, a command can be forwarded to all hosts, so every computer executes it. Two parameters handle this, and you can add them to any OSC command:

  • ableNet=false — stops AbleSet from forwarding that command to the other computers, so only the machine that received it executes it.
  • uuid=<string> — when the same command is sent to multiple AbleNet computers, only the first one with that UUID is executed and the rest are discarded.

Worth noting that this is a separate topic from MIDI control coming in. A controller physically connected to one computer only. That one is solved with the AbleNet toggle next to the MIDI input in the MIDI mapping page, or with MIDI forwarding from the AbleSet Connect app.

Which of the two cases are you dealing with? If it’s MIDI going out of Ableton Live, it’d also help to know which redundant audio interface you’re using.

Let me know and we’ll take it from there :slightly_smiling_face:

3

Hello!

Thank you so much. It was the first case with midi tracks doing program Changes :victory_hand:t2: