Thanks all for your contributions. I propose to set up somewhere a wiki page
so that all interested parties can append a specification document with
suggestions, reactions and so on.. ??
It sounds a good idea to set the boundaries between several levels of
librairies and raw some specifications
Hello Robert,
Le 18 mai 2010 à 11:54, Robert Mann a écrit :
f6 - Command PlayMidiChord(parameters : dito PlayMidiNote with pitch =
array of notes)
or chord name? (robert M)
Chord name is possibly a good thing, but it is better to have possibilities to
contruct chords with a list of
I think the below should be added to Set1 - BASIC AUDIO trim functions
*f16 - load, save and play audio from a variable*
Imagine an array with sounds!
Echo/Reverb, IMHO, is hard to do well and be efficient at the same time.
Most likely would be cheesy anyway, and this should be saved for
Hi all,
I am very interested in your requests, myself repeatedly
mentioned the lack of Runrev about Audio.
We have engineers that could create audio externals. It's the sort of thing
though we don't have immediate need for internally though. We could do
something using a platform like
Hello Lynn,
The basic Midi function could be (by example, :
1. Command PlayMidiNote
(midiChannel,instrument,pitch,duration,velocity,pano,vibrato,reverb) with
parameters :
midiChannel = Midi channel number
instrument = number of Midi instrument (General Midi § General Midi
Drum
1. Multiple audio streams, multichannel possibilities
2. Edit window primitives (waveform drawing, edit points)
3. Good level metering hooks
4. RTAS Plugins
5. SMPTE Library
6. Support for OGG and Flac
Building this stuff from scratch would be nuts - unless you're a great audio
code scientist -
Hi all,
Lynn Fredricks-2 wrote:
We have engineers that could create audio externals. It's the sort of
thing
though we don't have immediate need for internally though. We could do
something using a platform like kickstarter to do it. The question would
be,
what features and how much?
