New issue
Advanced search Search tips

Issue 895997 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Oct 17
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

WebMidi when a mididevice sends ActiveSense and Clock messages

Reported by stephen....@gmail.com, Oct 16

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.67 Safari/537.36

Steps to reproduce the problem:
1. connect a midi device to windows that sends ActiveSense and Clock messages.  (my problems is with a Yamaha CP33 midi'd to a MidiSport Uno midi=>usb interface
2. leave cp33 turned off.  other midi devices can be on.
3. open the attached index.html
3. the other midi devices behave fine and midi input shows in the section
4. turn on the Yamaha cp33 or similar device that sends ActiveSense and/or Clock messages

What is the expected behavior?
normal display of midi input in the html section

What went wrong?
I think WebMidi loses it's mind due to so many input messages.  My javascript ignores messages with command byte >= 0xF0, but junky midi messages still come in.

Did this work before? N/A 

Does this work in other browsers? Yes

Chrome version: 70.0.3538.67  Channel: stable
OS Version: 10.0
Flash Version: 

My Midisport Uno midi=>usb interface is not the greatest interface in the world.  But it works with my win32 api c++ midi program just fine.  I have to ignore the activesense and clock messages in the c++ program.  But that works just fine and I can use the yamaha cp33 / midisport uno just fine.  Please contact me if you have questions.  I'm very familiar with midi.  stephen.hazel@gmail.com  (my c++ app is at http://pianocheetah.com)
 
main.js
2.8 KB View Download
index.html
521 bytes View Download
main.css
285 bytes View Download
Labels: Needs-Triage-M70
Status: WontFix (was: Unconfirmed)
You just need to pass {sysex: true} as the first parameter to call requestMIDIAccess.
https://webaudio.github.io/web-midi-api/#dom-midioptions

> If this support is not requested (and allowed), the system will throw exceptions if the user tries to send system exclusive messages, and will silently mask out any system exclusive messages received on the port.

Also you need to host the page over https to get it permitted. This is a security requirement.

Sign in to add a comment