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: Fri, 22 Jun 2012 12:29:38 -0700
To: <public-audio@w3.org>
Message-ID: <B0FA38B533204B4ABBB5134DA47FAF0F@TWTHINK>
Not sure why, but I can't get any sound out of this app using Canary
I'm running Windows 7 SP1, if that matters...
- TW


From: Tom White (MMA) [mailto:lists@midi.org] 
Sent: Tuesday, June 19, 2012 3:52 PM

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

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:

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
- TW


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

Sent: Wednesday, June 13, 2012 7:18 PM

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.
Received on Friday, 22 June 2012 19:29:59 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:49:59 UTC