web audio/midi

[tatch]

sequencers/synths
theremin
acid macine
Otomata - Generative Musical Sequencer - reminds me a little of ssj71's cellular automaton synth except the automaton is for sequencing i think
Circuli - Generative Ambient Sound Instrument
synth with midi - only works on chrome i think
molgav
juno 106
http://www.websynths.com/
http://nicroto.github.io/viktor/


drum machines
stepkit
html5drummachine - contains tr-808, tr-909, linndrum, machinedrum and acoustic drum kit sounds
typedrummer not very flexible but fun to play around with

daws
audiotool
audiosauna
hya chrome only

misc
http://webaudio.github.io/web-midi-api/
online metronome
http://createdigitalmusic.com/2014/05/p ... ode-music/
multitouch controller - works with chrome
guitar stompbox
browser-based livecoding

it'd be cool if web midi were to support jack-midi integration, then it would actually be pretty straightforward to use a webapp in your setup. of course it probably won't rival native applications but still interesting I think.

[bluebell]

With the following ~/.asoundrc I can feed the browser's output into JACK:

pcm.!default {
type plug
slave.pcm "jack"
hint {
show on
description "Playback/recording through JACK"
}
}
pcm.jack {
type jack
playback_ports {
0 "system:playback_1"
1 "system:playback_2"
}
capture_ports {
0 system:capture_1
1 system:capture_2
}
hint {
show on
description "Playback/recording through JACK"
}
}

[tatch]

http://createdigitalmusic.com/2015/04/n ... wser-midi/ chrome supports midi now. pretty cool i'm gonna give it a shot just for fun.

update:
latency isn't the greatest. multitouch with a touchscreen is supported in chrome-stable but not chromium or chrome-beta (touch support is still imperfect though, dropdown selections aren't properly responding to touch input). midi input only works with the chrome 43 beta and as falktx said is alsa-midi (instead of making a midi port you connect via the app. my k-board isn't showing up so I'm using the midi-through port). still cool though

that's still no native jack support.

I was referring to the fact that if we want jack-midi support via browser, it should probably be better to have audio working first (as native jack).

whenever web-midi is implemented in linux browsers, it will use ALSA-MIDI.

this is probably true, too bad. I'm not sure how we could approach implementing jack for web browsers but it seems like it would be nontrivial.

[tatch]

http://www.synthtopia.com/content/2015/ ... b-browser/

looks like chrome support for midi is stable now. i've added a couple of web synths that are mentioned in the comments