WARNING: THIS SITE IS A MIRROR OF GITHUB.COM / IT CANNOT LOGIN OR REGISTER ACCOUNTS / THE CONTENTS ARE PROVIDED AS-IS / THIS SITE ASSUMES NO RESPONSIBILITY FOR ANY DISPLAYED CONTENT OR LINKS / IF YOU FOUND SOMETHING MAY NOT GOOD FOR EVERYONE, CONTACT ADMIN AT ilovescratch@foxmail.com
Skip to content

SYSEX data is malformed #766

@okyeron

Description

@okyeron

Best I can tell, the SYSEX data being sent over USB (to the web interface?) is missing a Manufacturer's ID Byte. Thus when viewing the incoming data in MIDI Monitor or similar tools, the sysex data will show a strange manufacturer

Usually, the first data byte (after the 0xF0) will be a defined Manufacturer's ID. The MMA has assigned particular values of the ID byte to various manufacturers, so that a device can determine whether a SysEx message is intended for it. For example, a Roland device expects an ID byte of 0x41.

And then, Bytes 3 and 4 are usually the [Device ID] and Model ID

16n, 8mu and similar devices will do F0 7D 00 00 at the start of the SYSEX message - using 0x7D as a "dev" manufacturer and then 00 for device and model IDs

I'd hack on this to add it to the _core code, but it will also take some adjusting on the web-interface side.

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions