MIDI Expression 2.9.3 BETA is available

[Rob]

System Realtime messages should be easy to implement--im willing to add that.

Being able to send SysEx or an arbitrary number of messages is a pretty niche feature. There's no way I could implement it on the single input MIDI Expression (not enough device resources), but possibly for the Quattro and iO.

If I was going to implement something like sending SysEx, how long of a SysEx message woukd you recommend I support. Would 32 bytes be enough? Could I get away with 16 bytes?

[jlmh007]

It you’ll be really nice if you can implement the system real time messages. And would be super awesome if the IO had the option to send more than one message per press like the Disaster area midi baby 1 and 3, the DoReMidi mc-20, the AirStep, the hotone Ampero midi control. They all are nice devices but what I like from the MEx IO is the midi thru and the freedom to put the pedals or switches wherever I want.

About the Sysex length, I really don’t know how to check the length of a Sysex. Let me attach an screenshot with some Sysex I use to control my zoom Ms-50 pedal, I’ve used even longer Sysex to make program changes to my korg x50 synth using the MSolutions dualFS controller. I guess the longer the better haha!

Your product has great features and it’s super cool you are always improving it and making it better! Congrats and thanks for that !

[Audioproduction]

Hi, I support jlmh007 request to implement system realtime messages.

I have a use case where I need to filter midi start and stop commands but keep midi clock. I currently use another solution but it would be much simpler to filter messages directly with the Midi Expression transformer. The most flexible implmentation would allow to individually filter realtime messages:

F8 clock
FA start
FB continue
FC stop
FE active sensing

[Rob]

I have a use case where I need to filter midi start and stop commands but keep midi clock. I currently use another solution but it would be much simpler to filter messages directly with the Midi Expression transformer.

Sure. I don't even need to update the firmware to support that request.

UPDATE: After some more thought, it would be a bit of a waste to use a transformer for that purpose. I'll instead implement a separate filter section on the Routing Page, allowing users to specify up to 8 types of messages to filter for both the USB MIDI port and DIN MIDI OUT port.

[jlmh007]

Adding a filter means the IO will only pass only some messages and restrict the passing of others from incoming midi or it also means the IO will be able to send the system messages like stop by itself ?

[Rob]

I will also allow pedals to send real-time messages, but you bring up a good point. If the filter is on the DIN out, i would need to still allow pedals to pass realtime messages. I'll give it some more thought.

[Rob]

I'm heading on vacation for 6 weeks but I got some pics to share. Still a bit of UI work to do.

07-10-2024, 15-21-09.png (110.15 KiB) Viewed 2503 times

07-10-2024, 15-21-49.png (33.12 KiB) Viewed 2503 times

07-10-2024, 15-22-34.png (212.42 KiB) Viewed 2503 times

[Audioproduction]

Hi Rob,

This looks great ! Will it be possible to select mutiple messages for filtering (ie. active sensing + system realtime) ?

Have a great vacation.