Subject: Re: [linux-audio-dev] laaga: withdrawal/amendment of automated mixing proposal
From: Benno Senoner (sbenno_AT_gardena.net)
Date: Sun Jun 17 2001 - 02:19:48 EEST
I may miss something buy my proposal would be to have the receiver (the
client) doint the mixing.
Eg if client1's input port has only 1 source feeding it then simply evaluate
that buffer directly.
If there is more than one source (many-to-one) then get the data from the
other sources and mix them together to an intermediary buffer which will be
the one used for processing.
The receiving client should block till all sources feeding its input ports
are ready. At this point mixing can occur (after completion the sources can
be informed that mixing is done).
Is this applicable to your model ?
Benno.
On Friday 15 June 2001 22:41, Paul Davis wrote:
> i have just realized a fundamental problem with the automated mixing
> proposal that i made a few weeks back.
>
> the mixing was to be done by the engine, but it has to be done
> immediately before executing the client whose inputs might be mixed.
>
> the problem is that for out-of-process clients, we don't want to
> switch back and forth between the clients and the engine, we want to
> switch from one to the next and then back the engine only when we have
> to. this means that we can't mix at the right time, which means that
> we can't mix at all.
>
(...)
>
> its either that or we drop automated mixing completely, which would be
> a shame, since it means no Many-to-One connections.
>
> or we do even more context switches, which doesn't seem too good of an
> idea.
>
> Your Comments Please.
>
> --p
This archive was generated by hypermail 2b28 : Sun Jun 17 2001 - 02:47:49 EEST