Feature request: Web MIDI ⇆ JACK
Reported by
karim.ra...@gmail.com,
Nov 26 2016
|
||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.100 Safari/537.36 Steps to reproduce the problem: 1. Open QJackCtl and start JACK 2. Open Ardour, goto Edit > Preferences > MIDI > Sync > Turn on "Send MIDI Clock" 3. Press Play in Ardour 4. Goto QJackCtl > Patchbay > Add Output Socket > Type:MIDI > Client:ardour > Plug:MIDI Clock out > Add plug > OK 5. Open a Web application that uses WebMIDI, e.g. http://solsticesequence.com/ 6. Refresh the MIDI inputs: the JACK output socket does not show up in the list What is the expected behavior? JACK input and output sockets should appear in the Web MIDI devices. What went wrong? The feature request is to connect to JACK input and output sockets and treat them as available MIDI devices. Currently, the workaround is to use a tool such as `a2jmidid` http://home.gna.org/a2jmidid/ to connect JACK sockets to ALSA MIDI ports, which are then picked up by Chromium as MIDI devices. Did this work before? N/A Does this work in other browsers? N/A Chrome version: 54.0.2840.100 Channel: stable OS Version: Ubuntu 16.04.1 Flash Version:
,
Nov 28 2016
,
Nov 28 2016
It would be quite a lot of work to add JACK MIDI to Chrome. Having to use a2jmidid is an unsatisfying solution, but as long as Linux audio consists of two worlds (JACK vs non-JACK), these kinds of bridges are necessary. How well does a2jmidid work with Chrome? If there are any issues (latency or other problems) we can look at those, but otherwise I would recommend just sticking with it. |
||
►
Sign in to add a comment |
||
Comment 1 by toyoshim@chromium.org
, Nov 28 2016Labels: -Pri-2 Pri-3
Status: Untriaged (was: Unconfirmed)