SysEx data in a MIDI file is filtered?

In this way, I can easily decide whether to record 16 or 32 channels. It makes everything simpler.

So you use 2 global Layers each for a group of 16?
Nothing wrong with that, but you might as well create 2 ports and set one to if not used?

I have:

  • a layer that sets the mixer audio interface to record only 16 channels
  • a layer that sets the mixer audio interface to record only 32 channels

In this way, all the songs have 2 active tracks:

  • One towards the 16-channel layer
  • One towards the 32-channel layer

When I want to change the mixer setup, I just need to mute one or the other layer.

1 Like

Ah, ok, got it. Cool, thanks!

1 Like

That is totally cool :sunglasses: :sunglasses:

1 Like

Hi, I have installed the latest version 2.1.6 but it still doesn’t work.

We’re terribly sorry, you are correct. Next version fixes it, promised!

1 Like

Now it works, thanks!

However, I noticed that within the Controller Map it works even if the SySex block is checked.

Also, the MIDI fader shows no signs of activity when the sysex information is sent.

Right, we did one too good. Fixed with the next version (presumably, today).

You are sending sysex from a track via a layer…which fader do you expect to change and why?

1 Like

The level MIDI fade does not show activity when the sysex information passes through. It would be useful to understand if the information is being transmitted. Right now, I have to connect the Behringer X32R to see if the sysex command is actually working. Having visible sysex activity allows you to verify that everything is functioning without connecting the Behringer.

…in the Behringer mixer/soft? We have no idea what a receiving device does when we send SysEx, so we cannot show anything. But maybe still missing something?

Let me give you an example: When the MIDI track sends MIDI commands, the fader shows activity regardless of whether a MIDI device is connected or not. In this case, even without a connected device, you can tell that the project is working. The same would be useful for sysex commands, having the ability to see that everything is working even without necessarily having the receiving device connected. It would be enough to see an LED blink when sysex commands pass through, if you don’t want to use the MIDI fader.

An activity display for MIDI out…ok, got it. We could add a global one which engages if any MIDI is beeing sent (except Midi Clock).

1 Like