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

What can we expect in the near future?

From: TJ <zoomclub@gmail.com>
Date: Mon, 25 Jun 2012 15:43:35 -0500
Message-Id: <6350F995-5A65-4E15-BC94-6FFB6414EBAE@gmail.com>
To: public-audio@w3.org
We are coming from Java, which was just barely okay for sound. There was the Java Sound API sequencer which was horrible and we ended up writing our own. All we needed was to create MIDI messages on the fly while iterating over a custom score structure not all the baggage of the Java sequencer. I see that some JS libraries like mudcube-midi-js are still using the nearly useless Java sequencer, to bad.

Having our own sequencer (the model itself) we are most interested in operations to create the full set of MIDI messages. How far along is the new standard on this aspect? We can roll our own library for this plus there are a few JS libraries for this type of thing in the wild but we prefer to use a standard package if possible.

To us, external MIDI device support for recording and playback is a completely separate option but what is available for IO here so far, that does not reply on Java?

Audio signal processing seems to be the focus, will the outcome be a streamlined MIDI to synth to mixer using effects toolkit? It seems this is the area that lacks the most, some good synth options that can load a full set of alternative timbres. What can we expect as far as synths and soundfonts go? Right now, it looks like each HTML5 or mobile app is doing its own basic sine wave type generator. Therefore, that old Java stuff is remaining relevant.

We are just catching up with the many excellent things going on in the HTML5 arena, hoping to learn more, cheers!
Received on Tuesday, 26 June 2012 11:59:56 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 26 June 2012 12:00:05 GMT