Re: [LAD] A3 clicks

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Fons Adriaensen <fons@...>
Cc: Linux Audio Developers <linux-audio-dev@...>
Date: Tuesday, June 18, 2013 - 4:17 pm

--001a11c2e79eac60aa04df700a0b
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Jun 18, 2013 at 12:12 PM, Fons Adriaensen wrote:

> On Tue, Jun 18, 2013 at 08:24:29AM -0400, Paul Davis wrote:

add it to the list of several hundred other items that all make A3 unusable
for this or that.

>

processors can be implemented that have no (builtiin) output, and the meter
is one of them.

the custom point could just stay

you're mistaken, unfortunately. the custom metering point has always been
"special", and does not exist when metering is set to pre/input/post.

--001a11c2e79eac60aa04df700a0b
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Tue, Jun 18, 2013 at 12:12 PM, Fons Adriaensen <fons@linuxaud=
io.org
> wrote:
On Tue, Jun 18, 2013 at 08=
:24:29AM -0400, Paul Davis wrote:

> inevitable, since you are changing the order of processors in the chan=
nel

thers

This makes A3 unusable for live work. For the simple reason that nobo=
dy expects
such a thing to happen, not any more than e.g. using a PFL should cause cli=
cks.
I will refrain from mentioning the not-so-kind adjectives that would be use=
d
to describe a HW mixer doing such a thing.<=
div>add it to the list of several hundred other items that all make A3 unus=
able for this or that. =A0

> i considered a design in which every possible metering point had a &qu=
ot;tap"

option, hence the

Why shouldn't that work for the custom point ? After all it *is* =
a 'tap'
and not a processor. And even if it is implemented as a processor (with an<=
br>
audio output that downstream depends on), =
processors can be implemented that have no (builtiin) output, and the meter=
is one of them.
the custom point could just stay
in place once created, along with any other metering point, active or not.<=
br>
As a bonus you can at least see were it is, even if not active. ISTR things=

were like that in earlier releases, but I could be mistaken.you're mistaken, unfortunately. the custom meteri=
ng point has always been "special", and does not exist when meter=
ing is set to pre/input/post.
=A0

--001a11c2e79eac60aa04df700a0b--

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[LAD] A3 clicks, Fons Adriaensen, (Tue Jun 18, 10:52 am)
Re: [LAD] A3 clicks, Esben Stien, (Wed Jun 19, 1:25 pm)
Re: [LAD] A3 clicks, Paul Davis, (Wed Jun 19, 1:45 pm)
Re: [LAD] A3 clicks, Paul Davis, (Tue Jun 18, 12:24 pm)
Re: [LAD] A3 clicks, Fons Adriaensen, (Tue Jun 18, 4:12 pm)
Re: [LAD] A3 clicks, Paul Davis, (Tue Jun 18, 4:17 pm)
Re: [LAD] A3 clicks, Nick Copeland, (Tue Jun 18, 4:28 pm)
Re: [LAD] A3 clicks, Fons Adriaensen, (Tue Jun 18, 11:00 pm)
Re: [LAD] A3 clicks, Paul Davis, (Tue Jun 18, 11:40 pm)
Re: [LAD] A3 clicks, John Rigg, (Tue Jun 18, 5:09 pm)
Re: [LAD] A3 clicks, David, (Tue Jun 18, 10:38 pm)
Re: [LAD] A3 clicks, Arnold Krille, (Tue Jun 18, 11:39 pm)
Re: [LAD] A3 clicks, Paul Davis, (Tue Jun 18, 11:41 pm)