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: Tue, 19 Jun 2012 15:52:12 -0700
To: "'Chris Wilson'" <cwilso@google.com>
Cc: <public-audio@w3.org>
Message-ID: <BC05C166CA1F47E582A4E555383FE1B8@TWTHINK>
Okay, I'll install Canary and then check it...
 
- TW


  _____  

From: Chris Wilson [mailto:cwilso@google.com] 
Sent: Tuesday, June 19, 2012 2:38 PM
To: Tom White (MMA)
Cc: public-audio@w3.org
Subject: Re: MIDI web synth (was Re: MIDI proposal implemented)


Nope, it just creates an Oscillator.  You need to run it in Chrome Canary
(or Dev Channel, I think) - Chrome Stable (the normal release) doesn't
support Oscillators yet.  Sorry, should have been more explicit.


On Tue, Jun 19, 2012 at 11:46 AM, Tom White (MMA) <lists@midi.org> wrote:



Chris,
 
Sorry for the long delay time... I'm just now checking this out but I can't
get it to output anything... is there supposed to be an output source
selector?
 
- TW


  _____  


From: Chris Wilson [mailto:cwilso@google.com] 

Sent: Wednesday, June 13, 2012 7:18 PM
To: Tom White (MMA)
Cc: public-audio@w3.org
Subject: Re: MIDI web synth (was Re: MIDI proposal implemented)


Actually, it was easier to just deploy a synth skeleton I've been working
on.   <http://midi-synth.appspot.com/> http://midi-synth.appspot.com/ has a
very fast attack time.  (no UI at all though.  :)


On Wed, Jun 13, 2012 at 12:49 PM, Tom White (MMA) <lists@midi.org> wrote:



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 
Received on Tuesday, 19 June 2012 22:52:39 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 19 June 2012 22:52:40 GMT