- From: Chris Wilson <cwilso@google.com>
- Date: Thu, 9 Feb 2012 20:46:15 -0800
- To: James Ingram <j.ingram@netcologne.de>
- Cc: public-audio@w3.org
- Message-ID: <CAJK2wqW=T4FWeHx61_aB+kLaRD=FPh-iMdKie=t8T4H8Ga5fcQ@mail.gmail.com>
Given the large number of potential descriptions of chords (particularly complex chords), that seems like a pretty advanced scenario - particularly with the time component you mention. I'd expect that to be analyzed in a Javascript library. On Thu, Feb 9, 2012 at 2:28 PM, James Ingram <j.ingram@netcologne.de> wrote: > I'm wondering if, for convenience, Chords could become part of the MIDI > API. > ChordOns would simply be a list of NoteOns which are conceptually > synchronous (received or sent within a very short time span). Similarly > with ChordOffs. > > My experimental AssistantPerformer [1] software uses a span of 12ms to > collect input NoteOns and NoteOffs into such packages. These are much > easier to program with than single notes. > As I remember, I arrived at 12ms by trial and error, so this obviously > needs discussing. Has anyone got a better idea of where the threshold > should be? Maybe it should also be exposed in the API? > > all the best, > James > > p.s. I'd like to add that I am currently working on a cleaner and leaner > version of my software, which I'm hoping to publish as open source software > soon. The patch editor has gone, but the notation and performance software > have been enhanced. > > [1] http://james-ingram-act-two.**de/moritz/** > moritzAssistantPerformer.html<http://james-ingram-act-two.de/moritz/moritzAssistantPerformer.html> > > > >
Received on Friday, 10 February 2012 04:46:44 UTC