Subject: Re: [ecasound] Proposition: Ecasound Blocking Audio Interface
From: smoerk (smoerk_AT_gmx.de)
Date: Sun Mar 02 2003 - 19:41:23 EET
why not use jack for this?
myprog1 | ecasound -i stdin -o jack:1 ---> --->
myprog2 | ecasound -i stdin -o jack:2 ---> jackd ---> ecasound -i jack:1,2,3
myprog3 | ecasound -i stdin -o jack:3 ---> --->
janne halttunen wrote:
> Hi all,
>
> Ecasound Blocking Audio Interface (EBAI)
> ----------------------------------------
>
> prologue
> --------
>
> I have for long have had the need some how to route audio to ecasound from my own little programs.
>
> First approaches have been something like:
>
> $ myprogram | ecasound -i stdin
>
> but to use ecasound's wonderful multitracking capabilities, a more complex approach must be assumed. Yet it's simple: FIFOs.
>
> So:
>
> $ mkfifo track1.raw
> $ mkfifo track2.raw
>
> And when I have my program writing to those FIFOs, I can start ecasound on them:
>
> $ ecasound -a 1 -i track1.raw -a 2 -i track2.raw
>
> This works, but it is a pain to write the same things always all over again. Hence, I propose standardization.
This archive was generated by hypermail 2b28 : Sun Mar 02 2003 - 19:31:40 EET