[SYSEX] No Sysex to Device MIDI Output

[sephult]

I seem to be having problems with Sysex and trying to debug.

I am doing a simple patch/performance change controller for external synthesizers.

I am in need for sending sysex data output as an example:
F0 42 30 19 4E 02 10 F7

So I am a little confused regarding the output of sysex data.
Originally I did this setup:

Sysex Editor, Set input Array to the above message, set output of sysex editor to MIDI Output(Sysex Input).
Where I found that in the devices the USINE Output didnt default connecting SYSEX to the Actual MIDI Device.
Further I could not find my data passing through the USINE to MIDI Sysex path.

I did try to do a bus and found I was able to trace the Sysex message to the MIDI Device Sysex....still though I have no triggering showing the message is being sent.

I have also tried doing a create message, looking into the Begin Sysex/End Sysex possibilities but could not figure out how to handle.

I believe I am approaching this right, any advice?

[bsork]

I suppose you're using Hollyhock?

I think SysEx functionality still isn't implemented in V6. You are not alone in wanting it, though!

[nay-seven]

yes, Midi sysex implementation is on our TODO list

[sephult]

Yep I am using HollyHock

Thank goodness I am just starting out piecing simple utilities together while learning...thought I was going crazy
I'd like to suggest a few things I think might make things simpler in my trials of doing this (which you probably already know).

Array Editor, ability to switch between decimal, binary, hex display for byte index input
Tab control for navigating Array/Sysex Byte Input
Auto populate hex $ symbol. Right now if you delete and put in say F0 instead of $F0, it will ignore and replace with $00

Thanks for the Reply, any master list location available for current implementations...and expected implementations? I am just slowly starting out this week but would love to do what I could to help debug as I learn.

[sephult]

Any more news on Sysex? I am trying to build a GUI controller that requires sysex and still cannot seem to get to work.

-S

[ceasless]

Hey sephult,

Not sure if it helps but you need to connect the sysex transport manually in your MIDI out device. By default sysex does not flow from the Usine output into the hardware output.

[sephult]

hmm I must be doing something wrong then...I did hook up all of the sysex but still not seeming to do anything sending to the output device. Do you have sysex working ceasless?

[sephult]

Quick test here
Sysex editor tied to midi output sysex.

Midi output shows response when sent, just never gets to the external world out of usine.
Ive checked my LoopMIDI and no Byte increase, as well as MIDI Ox has no reception.

I still think there is no sysex...that is a bummer. I have a ton of things I would love to do sysex for, implementing GUI controls.

-S

[sephult]

Well I think I might have stumbled onto making it work.

Seems if I do the following I could not get to work:
Sysex Editor, wire sysex to midi output, wire output device so sysex wire was there.
If I send, I could watch it go the whole way but not do anything at the end device.

I stumbled upon this, so if I wire the output and inject simultaneous the sysex editor and send it sets the wire array size properly and sysex started working.

This might be a bug where the device output cannot determine the size of the array or does not set it.

-S

[ceasless]

Yes sysex works fine for me, but I ran into this issue when writing the Push script.



This is the MIDI output device, the patch is accessible by double clicking on the device.

Here is what it looks like when the sysex is wired correctly:



I hope this helps solve your issue!

[sephult]

haha, thanks ceasless...no that wasn't my problem....Im trying to recreate several times.
I do wire it up...just seems that the output device will not get the array size right an not output.
I had to manually inject and set the size before it would start working.

-S

[ceasless]

Ah, okay.. glad to hear it is working now though!

[sephult]

Well I am having all sorts of oddities, started fresh and now I cannot get sysex editor to even output...lol
hmm something buggy here...partly me? maybe but something is buggy....

[nay-seven]

I'm testing sys ex out right now, sending the same message since more than 30mn now to stress the engine and don't see any problem (windows Usine send to Midi-ox monitor via copperlan)

here the patch used

[ceasless]

Sephult, what kind of device are you using as an output? I've heard that mani USB to midi cables have issues with sysex. I hope we can get you sorted, friend.

[sephult]

Thanks guys I appreciate the help.
I was multi-tasking so just finished up what I could so I can get some add-ons going.

I will put together a test-scenario and get some patches and more info up here for what I found.

-S

[sephult]

Well I do seem to be able to use LoopMIDI and I am now getting sysex to MIDI-OX.
I am trying to communicate with an Arturia Beatstep, where I reverse-engineered the sysex.

I am working on a companion, and standalone sequencer for the add-ons.
Seems at the moment I can get sysex to MIDI-Ox, but yes USB-MIDI to beatstep I cannot seem to get to respond.

I am able to get the Arturia MIDI control center to respond correctly, so I know it works.
I have noticed strange things with their driver, in Hollyhock if connected I have to a lot of times rescan and reselect the driver to get it to respond.

I will doublecheck my sysex and see what I can find, thanks guys

[sephult]

Okay so it seems to be the device output for the Arturia Beatstep.
I can put two device outputs, a LoopMIDI to MIDI-OX and I can see my sysex.

The Arturia Device output does not output the sysex. I have been able to get midi-sync to work however.
Again there has been strange driver issues, as if I start up HollyHock with the arturia unplugged.
I have to rescan uncheck and recheck to get it to work.

Thinking I might have a legitimate compatibility bug going on here.

-S