Hi Richard, hi others,
at the moment I am porting over about 60 plugins from SoundFX (www.sonicpulse.de
- an AMIGA shareware I am still developing and which you can use with UAE!) to
ladspa. I have sucessfully got the ladspa-sdk working on the Amiga too (added a
small wrapper lib to fix system
[EMAIL PROTECTED] wrote:
>Anyway (IMHO), there should really be an API which combines audio and MIDI playback
>
mostly if you design an api with both midi and audio support, you would
want to isolate the audio part and the midi part as much as possible
because someone who develops a program tha
> Why is it important to keep the API simple, shouldn't it be functional in
first place and make the API usage simply?
Who says a simple API can't be functional?
> Anyway (IMHO), there should really be an API which combines audio and MIDI
playback, recording and timing of events and makes it pos
Why is it important to keep the API simple, shouldn't it be functional in first place
and make the API usage simply?
Anyway (IMHO), there should really be an API which combines audio and MIDI playback,
recording and timing of events and makes it possible to keep MIDI in sync with audio
(ALSA s
> > I don't want to support tempo (MIDI clock) scheduling in my MIDI API.
This
> > could be better handled in the application itself. Also, when slaved to
MIDI
> > clock
> > it is no longer possible to send messages ahead of time, and not
supporting
> > this
> > in the API makes that clear to the
