- From: Olli Pettay <Olli.Pettay@helsinki.fi>
- Date: Fri, 22 Apr 2011 21:40:54 +0300
- To: Vilson Vieira <vilson@void.cc>
- CC: Chris Rogers <crogers@google.com>, public-audio@w3.org, Grant Galitz <grantgalitz@gmail.com>
On 04/22/2011 08:35 PM, Vilson Vieira wrote: > Hi Chris, > > 2011/4/22 Chris Rogers <crogers@google.com <mailto:crogers@google.com>> > > I think the point Tom is trying to make is that there are a bunch of > MIDI-sending hardware devices out there such as keyboards, DJ > controllers, fader boxes, etc. which can be connected to a computer. > So when we think of MIDI in those terms, the question becomes how > do we get the MIDI messages into a web application? I know Jussi > has experimented a bit here already. > > > Hans Huebner is working on a MIDI interface to devices based on node.js > and PortMidi [1]. I'm in touch with Hans. It is something similar with > osc-web [2]. On both cases we are using node.js as a kind of bridge > between MIDI/OSC and HTTP. So MIDI messages go over HTTP? Isn't latency pretty bad that way? I'd expect that we'll need some kind of midi streams which can be handled synchronously with audio and video streams in browsers. -Olli > > Cheers. > > [1] https://github.com/hanshuebner/midivent > > -- > Vilson Vieira > > vilson@void.cc > > ((( http://automata.cc ))) > > ((( http://musa.cc )))
Received on Friday, 22 April 2011 18:41:23 UTC