Four people in this very thread have asked for it. I’m not the only person asking for it (“unique to your situation”)
Please stop making false statements to that effect.
You’re falsely characterising me as the only person asking for this.
Other platforms.
I don’t want more cables, more devices, more OS’s, more updates.
I wanted one device that could handle midi with the advantage of filtering/conversion.
Midihub does this, and as stated by yourself, is perfectly capable of converting sysex.
I have accepted that in all likelihood I won’t be getting this functionality in Midihub.
Again.
I asked.
You answered.
You keep making incorrect summaries. I never said it is only you that wants this feature. SysEx, as a nonstandard interface between computers and instruments, by default means that it requires customization for the particular devices that one owns, according to their defined protocols, which are wildly different between different devices and manufacturers. Other users who are interested in this are likely interested because of totally different instruments and reasons. That’s what I meant by saying unique to your situation.
And again, you can solve this by running a script on your computer to which Midihub is connected, no need for any extra hardware.
Thanks for the reply.
I purchased the Midihub because it is a tightly integrated solution, the device, and the application that manages it.
I want to keep my solution as simple as possible, compact and fuss-free (script free?).
So, I don’t want to add more devices, scripts, applications, cables etc etc.
So the simple workflow of Daw>midihub>device is perfect.
As above sysex functionality was requested and re-requested by several people starting 4 years ago, that, alongside your statements that
but rather this is not a top priority
lead me to believe I’m not likely to see it soon. I don’t think that’s an unreasonable assumption to make.
However, I’m still trying to make music with a number of hardware devices, one of which only shows half it’s capabilities, because a) Waldorf abandoned it, and b) that functionality is hidden behind sysex.
USB midi is woeful, latency can be horrendous and unstable, so the midihub was perfect.
It kept it simple and neat as a solution.
Most DAWs are horrendous at sysex, hence why the midihub and its app were so appealing.
However, if that fork of development is not going to happen anytime soon, I’ll have to look for another, simple, elegant solution.
I’ll return on a regular basis to see if sysex appears.
Thanks for your help and advice.
Even though I’d love to have SysEx transformer functionality, I was suprised by the demanding tone from @Threlly above. I have tons of suggestions and ideas for many deivces, and always happy to share them, but I do realize that some of the features are more important than others. The mere fact that someone asked for a feature 4 years ago doesn’t make it more crucial.
Some companies lie that a feature will be added soon and nothing is changed in years (and won’t change). But what we have here is the honest answer that it may be done, but may be not – just don’t expect it.
Please, bump me when/if it’s implemented, but until then:
We are aware of this feature request, but there’s still things to do before we get there
So not a promise, but worthy of some expectation?, and as I have had to make clear several times I don’t think this is unreasonable.
I’ll try and not return to this, as I’ve already made my feelings very very clear, I hope you understand.
Being accused of being ‘demanding’ is a little unfair I feel.
I feel, others feel and the devs themselves have stated, the device is capable.
I wait with hope in my heart.
Hey @Giedrius, any chance you could share what the future development plans are for the Midihub - maybe a road map with expected deliveries. I saw you defending the the points that the device is not abandoned and I think a road map would be an effective way to reduce such claims.