Subject: Re: [linux-audio-dev] discussion about development overlap
From: David Benson (daveb_AT_idealab.com)
Date: Fri Sep 29 2000 - 01:09:45 EEST
> Ok, I'll go back to my old example: using ecasound as an fx box for
> soundtracker. Is this kind of functionality already possible with GDAM?
No, not already possible, though fairly easy within the
architecture.
That's only because we don't define *any* policy of
what to do with midi events.
You'd have to write a client that handles MIDI devices and
maps them onto the server protocol. basically you'd
call gdam_midi_device_trap () appropriately
then in those callback, issue `GdamRequests' to do what you want.
It's still pretty low-latency when directed through a unix-domain socket.
Alternately, but much less flexibly,
a server plugin that directly reads midi events.
(midi events are usually handled client-side).
This stategy is probably better for embedding an
existing application in GDAM.
Perhaps I'll try to right a semi-generic XML-configured client of
the first form; that should be fairly easy and fun.
- Dave
> > It depends upon GTK+ as a backbone for the plugins.
>
> Hmm, does this affect only the plugins, or all apps that want to access
> the soundserver functionality?
>
> --
> . http://www.eca.cx ... [ audio software for linux ] /\ .
> . http://www.eca.cx/aivastus ... [ aivastus net radio ] /\ .
> . http://www.eca.cx/sculpscape [ my armchair-tunes mp3/ra/wav ]
>
>
This archive was generated by hypermail 2b28 : Fri Sep 29 2000 - 01:43:40 EEST