# Midiout and sysex issue

**URL:** <https://forum.juce.com/t/midiout-and-sysex-issue/15555>\
**Category:** General JUCE discussion\
**Created:** [September 17, 2015, 11:00pm UTC](https://forum.juce.com/t/midiout-and-sysex-issue/15555 "2015-09-17T23:00:25Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![AaronLeese](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/aaronleese/32/624_2.png) [@AaronLeese](https://forum.juce.com/u/AaronLeese)\
**Post date:** [September 17, 2015, 11:00pm UTC](https://forum.juce.com/t/midiout-and-sysex-issue/15555/1 "2015-09-17T23:00:25Z")

</div>

&nbsp;

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.

&nbsp;

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).

&nbsp;

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.

&nbsp;

&nbsp;

---

<div class="post-metadata">

**Author:** ![jules](https://avatars.discourse-cdn.com/v4/letter/j/41988e/32.png) [@jules](https://forum.juce.com/u/jules)\
**Post date:** [September 18, 2015, 8:38am UTC](https://forum.juce.com/t/midiout-and-sysex-issue/15555/2 "2015-09-18T08:38:59Z")

</div>

Which&nbsp;OS?

---

<div class="post-metadata">

**Author:** ![AaronLeese](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/aaronleese/32/624_2.png) [@AaronLeese](https://forum.juce.com/u/AaronLeese)\
**Post date:** [September 18, 2015, 4:00pm UTC](https://forum.juce.com/t/midiout-and-sysex-issue/15555/3 "2015-09-18T16:00:10Z")

</div>

&nbsp;

&nbsp;

Aha! both Win nd Mac .... but it's a my mistake.

&nbsp;

I just hadn't noticed that&nbsp; **MidiMessage::createSysExMessage** adds the starting/ending bytes (0xF0,&nbsp;0xF7&nbsp;) automatically.

The docs mention it too ... I was just moving too quickly.

&nbsp;

Also - you may want to take a look at the issues with the "secure" version of your site, which is broken:

https://www.juce.com/

&nbsp;

I only notice it because my browser remembers that being a valid address. Maybe get someone to put up a reroute&nbsp;in the apache config.

&nbsp;