mirrors/pipewire
1
0
Fork 0
mirror of https://gitlab.freedesktop.org/pipewire/pipewire.git synced 2026-05-23 21:37:42 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions

seq: the training 0xf0 in continuations is optional

Browse source 
This is not strictly required because our control events have a size and
don't need the 0xf0 trailing byte to find the boundary.

It also makes it easier to just use the midifile events directly without
having to add the 0xf0.
This commit is contained in:
Wim Taymans 2026-05-21 17:51:51 +02:00
parent fdb08f3c60
commit 4e1257a6e6
2 changed files with 5 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

6
doc/dox/internals/midi.dox
View file

@ -83,15 +83,17 @@ start/end bytes combinations:
|-----------------------------------------------------------|
| Sublist Position | Head Status Octet | Tail Status Octet |
|-----------------------------------------------------------|
| first | 0xF0 | 0xF0 |
| first | 0xF0 | (0xF0) |
|-----------------------------------------------------------|
| middle | 0xF7 | 0xF0 |
| middle | 0xF7 | (0xF0) |
|-----------------------------------------------------------|
| last | 0xF7 | 0xF7 |
|-----------------------------------------------------------|
| cancel | 0xF7 | 0xF4 |
-----------------------------------------------------------
The trailing 0xf0 byte can be omitted at the end of continuation packets.
Nodes that require a complete SysEx message must be able to assemble the
complete message from the parts before processing the message.