How to send Midi msg from FM3 to AirStep ?

[Forza42]

Hello

I search on the forum and YT, I didn't find a way to send Midi msg to the AirStep from the FM3.
My idea is :
From the FM3, my 3 button change the Preset.

From the AirStep, I change Scenes.

So, when I change a Preset from the FM3, the Scene is not always the same, so the AirStep needs to know wich Scene is active to LightUp the corresponding Led.

For ex :
Preset 1 , with Scene 2. So the Airstep has the 2nd Led ON
from the FM3, I change to Preset 3, but the defaut scene is 1. At this point, the Led from the AirStep still the number 2, as it doenst have the information that the scene has changed from the FM3.


I tried some Midi setup, USB setup ... I m not able to send information to the Airstep from the FM3

thanks

 

[unix-guy]

You would need to send midi out the DIN ports.

It doesn't do midi over USB.

In any case, I don't think what you want to do is possible in any case unless the AirStep supports using midi to turn on the LED.

Otherwise, you'd create an infinite loop...

 

[mr_fender]

Yeah, syncing the footswitches usually requires poling the FM3 for status via Sysex messages. Not all MIDI controllers support that. The ones that do usually have a dedicated mode to sync with Fractal gear.

 

[lauke-lux]

Yeah, syncing the footswitches usually requires poling the FM3 for status via Sysex messages. Not all MIDI controllers support that. The ones that do usually have a dedicated mode to sync with Fractal gear.

AFAIK FM3 can send or receive only PC or CC messages through midi IN or OUT.

 

[mr_fender]

From the manual:


You can connect to the editor and perform updates via Fractal Bot using a 3rd party MIDI interface.

 

[Phosphenetre]

I'm also interested in this with the Airstep. I haven't purchased one yet, but I'm on the verge of doing so, if it can accomplish what I need.

It seems then like it's not possible to get the Airstep to 'stay in sync' with the status of the FM3 then, with respect to say the bypass state of blocks, or the currently active scene, like @Forza42 describes? @Rob13 also had a similar question a couple of years ago about getting the Airstep LEDs to sync with the bypass state of blocks.

It's unfortunately that there's nothing in the 'single, slim row of 4 - 5 switches' form factor that can accomplish things like these. The Airstep comes so close...

 

[Joshua_L]

Even though it’s been two years touring with a fm3 and an Airstep without problem I will be happy to have this too.

But honestly I don’t need it.

I use the Airstep for scenes, and the presets are changed via forscore on my iPad.
My scenes are always organized the same way so it’s not really a problem but it could be a bonus.

But from what I’ve tried, it’s not possible with the airstep.

 

[unix-guy]

It's unfortunately that there's nothing in the 'single, slim row of 4 - 5 switches' form factor that can accomplish things like these. The Airstep comes so close...

I'm pretty sure Voes covers that...

@voes?

 

[voes]

I'm also interested in this with the Airstep. I haven't purchased one yet, but I'm on the verge of doing so, if it can accomplish what I need.

It seems then like it's not possible to get the Airstep to 'stay in sync' with the status of the FM3 then, with respect to say the bypass state of blocks, or the currently active scene, like @Forza42 describes? @Rob13 also had a similar question a couple of years ago about getting the Airstep LEDs to sync with the bypass state of blocks.

It's unfortunately that there's nothing in the 'single, slim row of 4 - 5 switches' form factor that can accomplish things like these. The Airstep comes so close...

The MX is an excellent companion for the FM3/FM9/Axe-FX III.

The MX will sync completely with bidirectional Midi messages:

• Preset Name
• Scene Name
• Scene Select & Active Scene
• Block On/Off state
• Block Selected Channel
• Looper functions
• Tuner info
• Tempo (blink)

With the MF-Cable you only need one cable to connect MX and FM3/FM9/Axe-Fx III.



More info on https://voes.be/conn_fractal.html

 

[Phosphenetre]

View attachment 146015



The MX is an excellent companion for the FM3/FM9/Axe-FX III.

The MX will sync completely with bidirectional Midi messages:

• Preset Name
• Scene Name
• Scene Select & Active Scene
• Block On/Off state
• Block Selected Channel
• Looper functions
• Tuner info
• Tempo (blink)

With the MF-Cable you only need one cable to connect MX and FM3/FM9/Axe-Fx III.



More info on https://voes.be/conn_fractal.html

That looks really well thought-through and powerful! It's unfortunately a bit longer/wider than I'd be able to accommodate in my setup, but if things change over time and I have the space for the MX-5, it's going to be high on my list!

As far as I can tell though, the MX-5 would not be able to manage bi-directional sync, since it lacks the MIDI In jack?

 

[voes]

That looks really well thought-through and powerful! It's unfortunately a bit longer/wider than I'd be able to accommodate in my setup, but if things change over time and I have the space for the MX-5, it's going to be high on my list!

As far as I can tell though, the MX-5 would not be able to manage bi-directional sync, since it lacks the MIDI In jack?

Good observation. The MX-5 has only one MIDI connector to make the enclosure as small as possible.

But with the MF-Cable you can get Midi In/Out (bi-directional sync) and power from the FM3/FM9.



More info on https://voes.be/vfcable.html

 

[Phosphenetre]

Good observation. The MX-5 has only one MIDI connector to make the enclosure as small as possible.

But with the MF-Cable you can get Midi In/Out (bi-directional sync) and power from the FM3/FM9.



More info on https://voes.be/vfcable.html

Oh, so the MX-5's single MIDI connector manages to receive MIDI as well, when paired with the MF-Cable? That's very promising and some slick engineering, to pull all of that through the FASLINK port! I don't think I've seen any other manufacturers do anything to exploit the FASLINK. I'll see if I can rejig things around in my setup to make room for the MX-5. If not, maybe around the time I manage to make more space in a future setup.

 

[unix-guy]

Oh, so the MX-5's single MIDI connector manages to receive MIDI as well, when paired with the MF-Cable? That's very promising and some slick engineering, to pull all of that through the FASLINK port! I don't think I've seen any other manufacturers do anything to exploit the FASLINK. I'll see if I can rejig things around in my setup to make room for the MX-5. If not, maybe around the time I manage to make more space in a future setup.

I think only power is from the FASLink.

The midi still goes the the DIN jacks...

 

[voes]

I think only power is from the FASLink.

The midi still goes the the DIN jacks...

Oh, so the MX-5's single MIDI connector manages to receive MIDI as well, when paired with the MF-Cable? That's very promising and some slick engineering, to pull all of that through the FASLINK port! I don't think I've seen any other manufacturers do anything to exploit the FASLINK. I'll see if I can rejig things around in my setup to make room for the MX-5. If not, maybe around the time I manage to make more space in a future setup.

Only power is received from the FASlink. To sync Midi data, both Midi In and Out need to be connected.
Since the MX-5 has only Midi Out, you can use the MF-Cable to get power, Midi in and Midi Out.



More info on https://voes.be/vfcable.html

 

[Phosphenetre]

Only power is received from the FASlink. To sync Midi data, both Midi In and Out need to be connected.
Since the MX-5 has only Midi Out, you can use the MF-Cable to get power, Midi in and Midi Out.



More info on https://voes.be/vfcable.html

Ah yes, I misspoke earlier. What I meant to say was it's really cool that one cable sends all of that to the MX-5 through a single port on the MX-5 itself.