Can't get MIDI IN to work (chrome 38)

[lukephills]

Hi Chris,

I'm using Chrome 38 with the MIDI flag enabled but I can't get your synth (or drum machine) to connect with any of my MIDI controllers.

I've enabled the chrome flag and restarted. I've also installed the jazz-plugin even though I wasn't sure if I needed it. What steps need to be taken for this to work?

Thank you

[cwilso]

Hmm, strange. You shouldn't need the Jazz plugin, but it shouldn't harm anything either.

Can you open up the developer tools console and see if any warnings are firing?

[lukephills]

No there's nothing in the console apart from the key logs and there is no text in the MIDI_IN select box on the synth.

[cwilso]

Have you tried a more recent version? Could you install Chrome Canary alongside and check it?

[lukephills]

Yes just tried in Canary and its not working either.

Looking at line 51 of midi.js: var list=midiAccess.inputs();
My list.length = 0. I'm guessing thats not right?

I have an Akai MPD & a yamaha keyboard plugged in and MidiKeys open just to check.

[cwilso]

In Canary, you shouldn't get to that point. No, it shouldn't be 0, but
Canary shouldn't be dropping in to that clause, because it has the new
implementation of midiAccess - it should fail the test above

if ((typeof(midiAccess.inputs) == "function"))

and drop into the clause around line 70 instead.

What OS are you on?

On Fri, Nov 14, 2014 at 3:26 AM, Luke Phillips notifications@github.com
wrote:

Yes just tried in Canary and its not working either.

Looking at line 51 of midi.js: var list=midiAccess.inputs();'
Mylist.length = 0`. I'm guessing thats not right?

I have an Akai MPD & a yamaha keyboard plugged in and MidiKeys open just
to check.

—
Reply to this email directly or view it on GitHub
#11 (comment).

[cwilso]

Oh, guessing OSX from MIDIKeys. Hmm.

On Fri, Nov 14, 2014 at 8:07 AM, Chris Wilson cwilso@gmail.com wrote:

In Canary, you shouldn't get to that point. No, it shouldn't be 0, but
Canary shouldn't be dropping in to that clause, because it has the new
implementation of midiAccess - it should fail the test above

if ((typeof(midiAccess.inputs) == "function"))

and drop into the clause around line 70 instead.

What OS are you on?

On Fri, Nov 14, 2014 at 3:26 AM, Luke Phillips notifications@github.com
wrote:

Yes just tried in Canary and its not working either.

Looking at line 51 of midi.js: var list=midiAccess.inputs();'
Mylist.length = 0`. I'm guessing thats not right?

I have an Akai MPD & a yamaha keyboard plugged in and MidiKeys open just
to check.

—
Reply to this email directly or view it on GitHub
#11 (comment).

[lukephills]

Apologies yes Canary does go down that route but it doesn't make it into the for loop on line 89.

I'm on OSX v 10.9.4

[cwilso]

Weird. I'm guessing you've got an odd API in your build - I'll have to
look into it a bit more in a couple of days.

On Fri, Nov 14, 2014 at 9:01 AM, Luke Phillips notifications@github.com
wrote:

Apologies yes Canary does go down that route but it doesn't make it into
the for loop on line 89.

I'm on OSX v 10.9.4

—
Reply to this email directly or view it on GitHub
#11 (comment).

[lukephills]

I just tested on my work computer (OS 10.9.5 & Chrome 38) and the midi synth worked!

It must be something to do with my machine. Do you think it would it help if I reinstalled chrome or perhaps there's an app running in the background that may be conflicting with it.

[janbiasi]

You have to enable the requestMidiAccess method in your chrome flags; Try to open chrome://flags/ and search for "requestMidi.." and press enable 😸

[cwilso]

Should be fixed now.

[lukephills]

Hi @cwilso, it's still not working for me. It detected that a keyboard was connected; 'KEYBOARD' in the select box, but pressing the keys didn't do anything. Then I disconnected the keyboard and refreshed the page multiple times and it still has 'KEYBOARD' in the select box (when no midi controller is connected).

@janbiasi I don't have a requestMidiAccess option in chrome flags. There's only an 'Enable Web MIDI API' which is activated.

[cwilso]

@lukephills - I'm not sure what's going on. I'm not getting midi messages delivered in my current stable (42.0.2311.135) either; however, it works fine in Beta channel, and also in Canary. Try installing Canary and see if it works; Stable is going to 43 very soon.