Issue metadata
Sign in to add a comment
|
onmidimessage not received for certain messages
Reported by
jon.knig...@gmail.com,
Nov 20 2017
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36 Steps to reproduce the problem: This is going to be difficult for you to reproduce - it occurs when connected to a Marshall Amps CODE series digital amp, and only occurs on Mac OSX. What is the expected behavior? All Midi messages should be received by the browser. What went wrong? Using Midi Monitor, we could see that an incoming midi message had been received by the Mac, but it did not trigger the onmidimessage event in javascript. Did this work before? Yes Don't know exactly, v61.0.3163.100 seemed to work consistently. Does this work in other browsers? Yes Chrome version: 62.0.3202.94 Channel: stable OS Version: 10.12.6 Flash Version: This is an issue with a firmware update process that we do through the browser, for Marshall CODE-series guitar amps. It is complicated by the fact that the device does a warm-reset in order to go into the mode required to update the firmware, and it then identifies itself as a different MIDI device. The process works fine on Chrome for Windows (even as a VM running on a Mac), and Android (v62.0.3202.84). On the Mac, it also works fine if we start the hardware in the firmware update mode, rather than it connecting and disconnecting as different MIDI devices. We used Midi Monitor (https://www.snoize.com/MIDIMonitor/), and could see the message appearing on the input port, but the onmidimessage event never fired: 11:49:49.199 From CODE Bootloader SysEx Unknown Manufacturer 12 bytes F0 00 21 15 30 10 00 21 01 00 76 F7 Other messages seemed to trigger onmidimessage successfully up until this point. We tried changing the chrome://flags/#enable-midi-manager-dynamic-instantiation flag to Disabled, but that didn't seem have any effect on the issue.
,
Nov 20 2017
,
Nov 21 2017
The issue needs to be tested with a Marshall Amps CODE series digital amp connected to mac OS. A Midi Monitor is also needed to test the issue. All the above mentioned hardware seems to be unavailable with TE-Hyd and MTV team. Hence, adding label TE-Hardware-Dependency and requesting some one from Blink>WebMIDI team to please have a look into the issue. Thanks...!!
,
Nov 21 2017
For info, what locations are the Blink>WebMIDI team members in? We'll check with Marshall to see if there's a possibility of getting an amp on loan for someone.
,
Nov 22 2017
Hi, I'm the owner of Web MIDI feature, but all members are based in Tokyo office, Japan. At this point, I have no idea what happens here. Let me discuss how we could find the problem together.
,
Nov 22 2017
Marshall are keen to get a CODE 25 amp to you to try and resolve this issue with messages with Chrome on Mac OS X. Could you please email me at jon.knight@transpose.net with contact details and a delivery address, and they will arrange for one to be shipped to you.
,
Nov 24 2017
Thank you for providing information and a device. There is a similar report, http://crbug.com/781220 The reporter said behavior changes based on chrome://flags/#enable-midi-manager-dynamic-instant, but I have no idea how it can affect the issue. Anyway, I will investigate reasons once I have the device.
,
Nov 24 2017
,
Dec 6 2017
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by jon.knig...@gmail.com
, Nov 20 2017