4 Oct
2002
4 Oct
'02
5:22 p.m.
On Fri, Oct 04, 2002 at 09:43:18 -0400, Paul Davis wrote:
the port reconnection code is evil. i think its
completely the wrong
approach. its just a kludge to avoid using a patch bay.
I disagree, its only a kludge because there is no clean way to implement
it with the current API.
The insert connection mode is a feature people want (without dicking about
with patchbays) and the reconnection code is a logical extension of that.
- Steve
4 Oct
4 Oct
8:30 p.m.
New subject: [linux-audio-dev] meterbridge 0.0.4
On Fri, Oct 04, 2002 at 09:43:18 -0400, Paul Davis
wrote:
my sense is that what people want to do is to "attach" the meter to a
cable, so to speak.
output port --------------------> input port
^
|
put meter here
and watch it
i don't see that this requires any messing with "reconnection" - just
connect the meter input port to the LHS output port.
the place where its tricky is with a port that has JackPortIsTerminal
marked:
wherever ---> input port |
and people want to meter the signal arriving at the terminal input
port.
i'll try to think more about how i believe this should be done. i
don't think that connecting/reconnecting is right.
--p
the port reconnection code is evil. i think its
completely the wrong
approach. its just a kludge to avoid using a patch bay.
I disagree, its only a kludge because there is no clean way to implement
it with the current API.
The insert connection mode is a feature people want (without dicking about
with patchbays) and the reconnection code is a logical extension of that.
5 Oct
5 Oct
6:43 a.m.
New subject: [linux-audio-dev] meterbridge 0.0.4
On Fri, Oct 04, 2002 at 06:33:28 -0400, Paul Davis wrote:
the place where its tricky is with a port that has
JackPortIsTerminal
marked:
wherever ---> input port |
I dont know why JackPortIsTerminal matters, the tricky part is when you
have several outputs:
foo ------.
\
bar --------> alsa_pcm:out_1
/
foo ------'
becomes
foo ------.
\
bar --------> meter --- alsa_pcm:out_1
/
foo ------'
i'll try to think more about how i believe this
should be done. i
don't think that connecting/reconnecting is right.
Given the current system I believe that it is. Though I am maybe
connection happy.
There are some equivalent systems where connections to inputs are alowed:
foo ------.
\
bar --------> alsa_pcm:out_1
/ \
foo ------' \
`--> meter
I wouldn't like to say if this is a good idea. Obviously it would help
here, but it may make the graph code more complicated and confuses the
semantics of connections.
- Steve
10:06 a.m.
New subject: [linux-audio-dev] meterbridge 0.0.4
the place where its tricky is with a port that has
JackPortIsTerminal
marked:
wherever ---> input port |
and people want to meter the signal arriving at the terminal input
port.
i'll try to think more about how i believe this should be done. i
don't think that connecting/reconnecting is right.
the obvious solution:
* client registering terminal input port registers an output port,
ties the output port to the terminal input port.
* meter using the output port.
problem: this violates the intended semantics of "terminal port".
--p
3:35 p.m.
New subject: [linux-audio-dev] meterbridge 0.0.4
On Sat, Oct 05, 2002 at 08:09:23 -0400, Paul Davis wrote:
the obvious solution:
* client registering terminal input port registers an output port,
ties the output port to the terminal input port.
* meter using the output port.
problem: this violates the intended semantics of "terminal port".
I dont think there should be anything special about terminal ports (as far
as the clients are concerned, obviously the graph sorted needs to use it
for grounding out the graph.
- Steve
8427
days inactive
8428
days old
linux-audio-dev@lists.linuxaudio.org
4 comments
2 participants
participants (2)
-
Paul Davis -
Steve Harris