Re: [linux-audio-dev] LAAGA proposal, part ??

New Message Reply About this list Date view Thread view Subject view Author view Other groups

Subject: Re: [linux-audio-dev] LAAGA proposal, part ??
From: Paul Davis (pbd_AT_Op.Net)
Date: Wed Jun 06 2001 - 23:04:36 EEST


>> enum PortFlags {
>> PortIsInput = 0x1,
>> PortIsOutput = 0x2,
>> PortIsMulti = 0x4, /* supports multiple connections */
>
>This is multiple input connections, presumably. Does it meant that you
>will receive each input as a seperate buffer, or mixed? What will happen
>is this is not set?

As described previously, multi-input mixing is handled transparently
by the engine. no client/plugin ever deals with this.

>> PortIsPhysical = 0x8 /* refers to a physical connection */
>
>Is this so you can know is there is any point asking for hardware
>monitoring? I can't think of any other uses.

No, its so that applications that want to produce a UI that includes
list of real physical i/o stuff can do so.

h/w monitoring is not part of the client API. what you saw was more or
less the full extent of it.

>Also, I'm not clear on the mechanics of non-float audio. The source plugin
>will have to conjour the output buffer space from somewhere.

yep. as described in the comment for audioengine_port_register(), if
the port type is not a builtin, then a buffer must be provided as the
4th argument. i should also have documented that PortIsMulti is
illegal for such ports (to ensure 1:1 connections at all times, for
reasons documented in previous discussions).

--p


New Message Reply About this list Date view Thread view Subject view Author view Other groups

This archive was generated by hypermail 2b28 : Thu Jun 07 2001 - 00:29:30 EEST