I've noticed this for some time, but it never mattered until just now (I have a device that is complaining).
So .... it seems like whenever you send a sysex message out, Juce will send an additional (empty) message.
I am referring to short sysex messages here, not ones that exceed the 256 limit and have to be sent in multiple packets.
I have a screenshot, but uploading images seems to have been disabled or having issues (it is under 1 mb, but I get an error message).
Anyway, after each sysex that is sent, I get a second (empty) sysex with just (f0 f7).
Any idea what is happening there? I've tried it both with the sendMessageNow and using a background thread.
Any other type of message (notes, controllers, etc) sends just fine ... it just seems to be a sysex issue.