Wish: Midi CC# to choose between 5 modes

1anP

Inspired
If you checkout the same thread title on the AM4 discussion you will find forum member laxu posted the sysex code for all of the available 5 Modes.

1. Presets---------F0 00 01 74 14 ?? ?? ?? F7
2. Scenes---------F0 00 01 74 14 ?? ?? ?? F7
3. Effects---------F0 00 01 74 14 ?? ?? ?? F7
4. Tuner/Tap-----F0 00 01 74 14 ?? ?? ?? F7

I'm hoping Fractal may provide the #CC midi command for these Modes for the VP4 in a future firmware update, anyone from Fractal know if this may happen?
In the meantime has anyone had any luck capturing the sysex code for these Modes and can share? Perhaps Fractal can provide the sysex code for people like me wanting to implement this function using their midi controllers? 🤞
 
Last edited:
The first part of sysex message is the Manufacturer and Device ID. So the code 00 01 74 14 is the ID for Fractal and VP4 and thats all I know so far.
F0 is the message start, F7 is the message end and I just need the data I have shown above as ?? ?? ?? .

I have WireShark and MIDIOX (free apps) to try and capture the sysex code (Modes) going from the VP4 editor to the VP4 device but no luck. Its above my pay grade trying to use these capture apps to get what I need.

Its been done for the AM4 so I'm hoping someone has the data and is willing to share it on this forum. I have my AM4 and VP4 working together as one unit and would really appreciate being able to use Mode selection to make it even better.

BumbleBTop.JPG
 
Likely the same Sysex works for the VP4 and all you need to do is change the ID part of the message to the VP4 ID.

To sniff it out, you would need to use MIDI OX to log the traffic on the VP4 USB MIDI, then have VP4-Edit open to have it send some traffic through it. If you can see that stream in the MIDI OX, you should be able to find the device ID.

If VP4-Edit has the same mode button switches, you can just use those to see the relevant MIDI Sysex commands.

I agree Fractal should just make these MIDI CC switchable for ease of use.
 
You’ll also need to recompute the xor checksum for the new device id 0x14 instead of 0x15 for the am4.

Untested calculated xor:

F0 00 01 74 14 12 48 4B F7 Presets

F0 00 01 74 14 12 58 5B F7 Amp mode

F0 00 01 74 14 12 49 4A F7 Scenes

F0 00 01 74 14 12 4A 49 F7 Effects

F0 00 01 74 14 12 18 1B F7 Tuner/tap tempo
 
Last edited:
You’ll also need to recompute the xor checksum for the new device id 0x14 instead of 0x15 for the am4.

Untested calculated xor:

F0 00 01 74 14 12 48 4B F7 Presets

F0 00 01 74 14 12 58 5B F7 Amp mode

F0 00 01 74 14 12 49 4A F7 Scenes

F0 00 01 74 14 12 4A 49 F7 Effects

F0 00 01 74 14 12 18 1B F7 Tuner/tap tempo
Bingo!
Tested the sysex code on my VP4 and it works perfectly :cool:
I guess it can be added alongside the AM4 sysex code for Modes in the Fractal Wiki.
Just remember the Amp Mode is not needed for the VP4 of course.
Thank you so much for your calculated code! It now means I can have my MC6Pro controlling my AM4 and VP4 together in a much more unified way.
Gotta love the Fractal community!
 
Likely the same Sysex works for the VP4 and all you need to do is change the ID part of the message to the VP4 ID.

To sniff it out, you would need to use MIDI OX to log the traffic on the VP4 USB MIDI, then have VP4-Edit open to have it send some traffic through it. If you can see that stream in the MIDI OX, you should be able to find the device ID.

If VP4-Edit has the same mode button switches, you can just use those to see the relevant MIDI Sysex commands.

I agree Fractal should just make these MIDI CC switchable for ease of use.
I did try using the AM4 sysex code with the VP4 ID I captured by changing out the 15(AM4) with 14(VP4) but it didn't work. Nomoretubes realised the code had to be xor'd so we were on the right track, but one step short for getting it to run. So in the end your code capture of the modes for the AM4 and my finding the VP4 ID and nomoretubes calculation got us over the line!
 
Last edited:
I did try using the AM4 sysex code with the VP4 ID I captured by changing out the 15(AM4) with 14(VP4) but it didn't work. Nomoretubes realised the code had to be xor'd so we were on the right track, but one step short for getting it to run. So in the end your code capture of the modes for the AM4 and my finding the VP4 ID and nomoretubes calculation got us over the line!
credits to @yek for having the checksum algo both called out and an example command to make it plug and chug on the wiki!
 
Bingo!
Tested the sysex code on my VP4 and it works perfectly :cool:
I guess it can be added alongside the AM4 sysex code for Modes in the Fractal Wiki.
Just remember the Amp Mode is not needed for the VP4 of course.
Thank you so much for your calculated code! It now means I can have my MC6Pro controlling my AM4 and VP4 together in a much more unified way.
Gotta love the Fractal community!
Could you please attach an editor screen grab of the Morningstar editor command that works for you. I cannot get my MC6pro to get the VP4 to go to scene mode for example. If it is working for you then I either made a mistake or some settings are wrong in the VP4.
Thanks
 
SysexMessage1.jpg

SysexEditor1.jpg

The sysex code shown is for the VP4 Scene Mode as you requested and tested using my MC6Pro. I use the Create Sysex Preset feature of the MC6Pro editor which is found in the menus by clicking on the 3 ellipsis ... just above the word Buffer in the top screenshot.
Hope this helps and you can get on with programming your controller.
 
Thanks very much for the explanation. It was exactly as I had set it up.

At first it didn't work. Then I turned the MC6 and Vp4 off then on and it is now working.

So once again thanks for your help.
 
Last edited:
If it's doable via sysex, I honestly do not get it why fractal does not provide a simple way of cc mapping for these options for people that do not have controllers able to send sysex?
 
If it's doable via sysex, I honestly do not get it why fractal does not provide a simple way of cc mapping for these options for people that do not have controllers able to send sysex?
I totally agree with you and am hoping Fractal will actually do this in a future firmware update. I'm thinking maybe Fractal are preoccupied at the moment with their Icon plugin release and soon will return once again to hardware?
 
ICONS and each hardware group has its own team. Some resources are shared, but it's managed.
Thats good to know and thanks for the info!
Is the Fractal team looking at implementing midi CC# commands for Mode selection for the new AM4 and VP4 devices?
 
Thx for figuring this out - works great with both AM4 and VP4 using my Morningstar MC6 Pro.

Only thing I'm stuck with is that I would like to use midi channel #4 for VP4 and #5 for AM4.. would there be any chance that the '01' in Sysex position 3 could be the midi channel?

Cheers,
Joce

EDIT: just tested it and the answer is no.. but somehow I guess the Sysex messages must be sent on all channels by default because it works even I limit each devices to receive midi on their respective Ch4 and Ch5..
 
Last edited:
Back
Top Bottom