It appears that PlugData's version strips both the status byte F0 as well as the terminator F7, whereas vanilla passes both (0.55-0 and 0.54-1). I don't think I'm confusing a vanilla object with an else object, am I? What else could I be overlooking? You can confirm it with this if you want sysex recording test.pd

PS: I tested as standalone as well as a VST3

There is a very old bug report about this: https://github.com/plugdata-team/plugdata/issues/1195
Maybe follow up there (and mention your OS and plugdata version, which you omitted here).

In the plugin version this is not really expected to work since a plugin host will very likely filter these kind of messages.
Especially with VST3 where the spec is very restrictive on what MIDI can do.

@dreamer Thanks. That looks to be a different issue, but if a no one else points out how my expectations are wrong then I'll file a report on github. Windows 10, plugdata 0.8.3, REAPER 7.16

I love how something from less than a year ago is "very old" Time is definitely speeding up as I age.

I originally though this was a VST3/JUCE bug, but it seems that that has been fixed in JUCE now: https://forum.juce.com/t/juce-vst3-sysex-midi-bug/58893/4

So I'll check why this isn't solved in plugdata yet...

@timothyschoen Well that was fast, thanks! One correction though: as a plug-in, plugdata passes the status byte. It doesn't when running stand-alone.

If there's no status byte, how do you know when the message is finished?

In SuperCollider, the backend packs up the bytes as an Int8Array (there's no user-facing byte-by-byte interface), which sidesteps that question. But if the sysex object is emitting a stream of bytes, it seems to be that a closing delimiter would be necessary.

hjh

@ddw_music I think you mean terminator, not status byte. I'm using [fudiformat] to generate the body of the sysex message, so I just omit the -u flag and scan for the colon and newline.

Edit: I just looked it up. The spec lists F7 as a status byte, so I guess sysex has two status bytes. Confusing.

@jameslo said:

Edit: I just looked it up. The spec lists F7 as a status byte, so I guess sysex has two status bytes. Confusing.

Yeah, this was the sense in which I meant status byte (any byte in MIDI whose most significant bit is set).

hjh