On Sat, Mar 22, 2003 at 08:38:39AM +, Steve Harris wrote:
On Sat, Mar 22, 2003 at 08:30:22 +, Simon Jenkins wrote:
Something has to make this ramp/curve(/whatever), because at its
source (eg UI widget or incoming midi message) the toggling of a
switch *is* an event. But the rise and
On Mon, Mar 24, 2003 at 03:08:12PM -0800, Tim Hockin wrote:
Interesting stuff worth talking about.
Is this a clean, natural division? I don't think so. Why does the
model treat the output of an envelope generator as being (in many
respects) more like a string than it is like an oscillator
Interesting stuff worth talking about.
Is this a clean, natural division? I don't think so. Why does the
model treat the output of an envelope generator as being (in many
respects) more like a string than it is like an oscillator output?
Why isn't it clear what an LFO's output type should be?
On Sat, Mar 22, 2003 at 08:30:22 +, Simon Jenkins wrote:
Something has to make this ramp/curve(/whatever), because at its
source (eg UI widget or incoming midi message) the toggling of a
switch *is* an event. But the rise and fall characteristics should
belong to the owner of the source,
quote who=Tim Hockin
i know that. In galan it is the same.
But why should this difference be so clearly stated in the API ?
Can you show me a nice API that makes the two feel similar?
Controls: multiple datatypes, receive events in time-order queues
Ports: are assigned buffers (possibly
On Thu, Mar 20, 2003 at 04:35:51PM -0800, Tim Hockin wrote:
struct XAP_module {
char *label;
char *name;
uint32_t flags;
/* how many instances of this module are allowed? */
int count_max;
/* per-module controls and I/O */
int n_controls;
why support the difference between ports and controls ?
This is done in the C galan and tony somehow managed to remove this
difference in the C++ galan.
Because throughout all the XAP discussions we have made it clear that
controls are event-driven and ports are audio-rate data (specifically
On Fri, Mar 21, 2003 at 02:49:53PM -0800, Tim Hockin wrote:
why support the difference between ports and controls ?
This is done in the C galan and tony somehow managed to remove this
difference in the C++ galan.
Because throughout all the XAP discussions we have made it clear that
i know that. In galan it is the same.
But why should this difference be so clearly stated in the API ?
Can you show me a nice API that makes the two feel similar?
Controls: multiple datatypes, receive events in time-order queues
Ports: are assigned buffers (possibly datatyped) of arrays of
Tim Hockin wrote:
LADSPA is much the same way - connect anything to anything. But several
people in the XAP discussion feel that normalized data (0 to 1.0 or
whatever) is bad. I am still of the position that I could be convinced to
support two basic control types: numerical (normalized) and
I fear we've all been very busy. I know I have. I have not had time to
devote to XAP, though I have certainly not lost interest.
So today I start looking at my evolving spec doc again. The biggest chunk
of undecidedness lies in the area of Channels. We never really resolved the
Bays/Channels
11 matches
Mail list logo
