CC to Sysex transformer

Hi @Giedrius

Happy New Year!

I know there have been other topics pertaining to Sysex, but a CC to Sysex transformer for Roland products would be amazing. I used to use a BomeBox for this however if the MidiHub provided a solution that would be great. Use case would be to connect a Novation LaunchControl XL and use it to control effect send levels of Roland JD-Xi.

I noticed in another post that MidiBoy was mentioned as a possible solution, if so how would this be implemented using a MidiBoy?

Cheers!

Happy New Year! :slight_smile:

The Midiboy can be programmed using Arduino IDE to perform many functions. As it has DIN-5 MIDI input & output ports, it’s suitable to be inserted in the middle of a chain to perform some processing on MIDI data passing through. For an example of such sketch, you may check out Midichords source code.

Some knowledge of programming is needed to create custom sketches. Modifying existing ones is a bit easier, but can be a bit trial & error.

Thanks @Giedrius!

Unfortunately as I program all day at work, the thought of more programming in my spare time doesn’t really appeal. I just thought if there was already a ā€œsketchā€ that would perform the action I require then I would consider investing in the MidiBoy.

Would really love it if MidiHub would support CC to SysEx transformation at some point in the future. May be worth checking out the approach Electra One have taken as regards sending SysEx values:

2 Likes

I’d also really appreciate a cc to sysex transformer pipe to unlock all of the functionality of the Roland JD-XI buried in the menus! The sysex checksum isn’t enforced (can be left as 0x00) which would make it simpler to implement.
E.g. To set rim drum (c#2) output level, send:
F0 41 10 00 00 00 0E 12 19 70 30 0E val 00 F7
Where val is mapped from a CC data value.

Me too.

I am following this Forum to evaluate the possibilities of this very exciting MIDI processor.

For me it is also very important to fire SysEx Strings modified with MIDI-Control Values.

I think it is a very amazing feature to activate parameters of old synth without expensive hardware controllers.

pretty please, this feature would be the gamechanger.

1 Like

Me too, this would be very welcome for my Waldorf Kyra.
In fact, ChatGPT tells me that the midihub will convert CC to sysex and even created a preset for me (haven’t tried it yet).

// Blokas Midihub Preset - Convert CC to SysEx for Waldorf Kyra

pipes:

  • name: MIDI Input
    type: midi_input
    port: A

  • name: CC Remap (optional)
    type: transform
    input_type: cc
    input_cc: 74 # CC 74 for filter cutoff
    output_type: sysex
    sysex_template: ā€œF0 3E 12 00 01 0F xx F7ā€ # Replace ā€˜xx’ with the dynamic value

  • name: MIDI Output
    type: midi_output
    port: B

Of course, ChatGPT hallucinated the whole thing :roll_eyes:

It might just be worth throwing into the mix for some future readers that, at the end of 2024, @Blokas announced pimidi for those who want to go in that direction.

One of the intro pimidipy patches performs CC → Sysex for the DX7 so we can see that it would handle that.

That’s interesting, however the midihub is my current device so I look forward to an update that covers this functionality.

Yep, I hear you
Just haven’t heard our friends in Vilnius mention the possibility of Sysex in a little while.

This is Giedrius about a year ago:




PS. I intend to use pimidi as an adjunct to Midihub, not a replacement for it.
Others will differ but I plan to have an rPi-pimidi USB host also performing tasks that I either can’t do with Midihub (eg. Sysex) or which are much simpler with Python

1 Like

Deathly quiet from the devs, over 1k views, but…nothing?

@Giedrius Hi, anything to add since then?

Threlly

No response @Giedrius ?
No response @Blokas ?
Jan 2021!

While there’s currently no SysEx transformation support in Midihub, we recommend using PimidiPy and Raspberry Pi to do the CC to SysEx transformations. See the docs and the DX7 example which implements CC to SysEx transforms to control Yamaha DX7 synth:

Ok, I have been informed of that solution before.
However, that’s what I purchased the Midihub for, not to have to have to buy more boxes, apps, OS’s etc, etc.
Midihub owners have been asking politely for 4 years.
If the Midihub is not capable of the functionality, please say so.

The Midihub hardware is capable of it, however, keep in mind that getting SysEx conversion feature into Midihub and the Editor done the right way is a significant amount of work effort, but it’s also a niche feature - the majority of users don’t have a use for SysEx other than passing it through Midihub between devices as is, and Midihub takes care of respecting the SysEx transactions when merging streams from multiple sources. As we are a small team, we must weigh our development efforts and make the right decisions in order to grow our business and capabilities, so we must first prioritize developing highest impact features and products, before we have the resources to work on SysEx conversions.

There are ways to script the desired SysEx conversions on computers or if you want it portable, you can do it on devices like Raspberry Pi.

1 Like

Thanks for the update, now that I understand that development as originally described for the Midihub will no longer take place/abandoned, it’s just a decision of what to replace it with.
Obviously I’ll try and find a device platform that will include the functionality I need and where development will continue.
I need something more robust than a RsbPi based system (hence the Midihub), but I’m sure my Midihub will find a welcome home somewhere.

Cheers.

Stop making false claims about Midihub. Its development is not stopped, and we never said SysEx conversion feature would get prioritized over all the other queued up features in the pipeline.

1 Like

To be specific in that case, am I correct to note that some level of sysex functionality was requested over four years ago? or did I get that wrong? (I just looked further up the thread)
Is the complete lack of development in that direction for four years significant?
Also, when I ask for some update, or indeed request that very functionality I am directed to another device platform.
Either something is going to happen with Midihub in this respect…or it isn’t

I’m looking for clarity, and you have stated that ā€œso we must first prioritize developing highest impact features and products, before we have the resources to work on SysEx conversions.ā€

You feel that it is not important, I feel differently and I suspect many others also do.
So I asked.
You replied.
Nothing is going to happen.
I need it, and I’m not going to get it via Midihub.
What am I missing here?

Best,
Threlly.

We are not saying it is not important, but rather this is not a top priority, based not on feelings, but on impact of the feature and the effort required to implement it properly. You are making false statements again.

You need some particular SysEx functionality, that is most likely unique to your situation and to the devices you own in your studio. This can already be achieved if you combine Midihub with another scriptable device such as a Raspberry Pi, which you ought to be able to find for a reasonable price, if you don’t go with the top model, as it would not be necessary for such use case. Or you can use your PC or laptop for this as well. We can help you with scripting it even, if you ask for help in our forums. This is quite an efficient solution in your case.