W3C home > Mailing lists > Public > public-audio@w3.org > April to June 2012

RE: MIDI web synth (was Re: MIDI proposal implemented)

From: Tom White \(MMA\) <lists@midi.org>
Date: Wed, 13 Jun 2012 12:49:31 -0700
To: <public-audio@w3.org>
Message-ID: <EF1E330644D74FA5870C3E80A8A75CA6@TWTHINK>
If the "loopback app" uses the same data path (up to the output) as the MIDI
web synth app, then yes (but "select input" is not needed because the input
should be the same)... 
 
The idea is to *only* change the output device, while keeping *all* of the
other code unchanged.
 
Thanks,
 
- TW


  _____  

From: Chris Wilson [mailto:cwilso@google.com] 
Sent: Wednesday, June 13, 2012 11:40 AM

Tom, do you just want a loopback app (select input, select output)?  I can
try to toss one together and post it.


On Wed, Jun 13, 2012 at 10:02 AM, Tom White (MMA) <lists@midi.org> wrote:



I agree it is better, but there is still enough delay to make live playing
difficult... but perhaps that is the response time of the synth itself, I
don't know... if I could use the same interface to select an external synth
then I could isolate the software synth and determine the delay from the
API...
 
- TW


  _____  

From: Tom White (MMA) [mailto:lists@midi.org] 
Sent: Monday, June 11, 2012 4:01 PM
To: public-audio@w3.org
Subject: RE: MIDI web synth (was Re: MIDI proposal implemented)


I'll check it out sometime this week, and let you know if it performs
noticeably better for me...
 
- TW



Incidentally, I converted this demo over to use the Jazz MIDI plugin
(instead of the Java-based MIDIBridge), and latency seems better to me
(startup time is unnoticeable now).  Unfortunately, I don't think I'll be
able to build a Web MIDI API shim on top of Jazz, because it only seems to
support short messages (i.e. no system exclusive, and possibly no system
real-time either).  But for note and continuous controller support, it's
much more responsive.




On Wed, Jun 6, 2012 at 11:34 AM, Tom White (MMA) <lists@midi.org> wrote:



Chris, 
 
FWIW, I tested this on my Thinkpad T420s (and Chrome 19.0.1084.52 m) and
there was obvious latency (compared to using the onscreen keys). 
 
(I didn't want Vilson's note to give you the sense that everything works
perfectly in the world <g>).
 
Tom White
www.midi.org
 
 



  _____  

From: Vilson Vieira [mailto:vilson@void.cc] 
Sent: Wednesday, June 06, 2012 9:10 AM

Chris, awesome, tested with a Novation Launchpad in Mac and it worked
perfectly. I didn't perceived latency.

Cheers.



On May 31, 2012, at 12:04 PM, Chris Wilson wrote:

> I found a few spare moments to graft MIDIBridge on to Aike's Web Audio
synth.  Try it out at http://midiwasynth.appspot.com/, check out the code at
https://github.com/cwilso/webaudiosynth.  Note that MIDIBridge can take a
few seconds to grab the MIDI device, so I put a popup dialog in to let you
know it's ready to go.
Received on Wednesday, 13 June 2012 19:49:56 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 13 June 2012 19:50:05 GMT