[ardour-users] software monitoring
thomas.desbarats at gmail.com
Fri Jan 20 06:17:24 PST 2006
2006/1/20, Paul Davis <paul at linuxaudiosystems.com>:
> On Sat, 2006-01-21 at 00:12 +1030, Andrew Johnston wrote:
> > Now how does this all relate to the monitoring options present in
> > qjackctl?
> > Should they be left off les they confuse the issue further when trying
> > to monitor with ardour?
> > Or do they need to match the settings in ardour...ie software
> > jack..software ardour, hardware jack...hardware ardour?
> "h/w monitoring" as presented by Ardour and JACK as an option is
> controlled by JACK. if you have not enabled it or it is not available
> for your audio h/w, then it will do nothing. It is similar to the ASIO
> DirectMonitoring support, and allows JACK clients (e.g. Ardour) to ask
> JACK to enable h/w-based monitoring for a specific channel. It is very
> limited (you can only monitor the input of channel N on the output of
> channel N). Moreover, at this time only 3 types of audio interface (the
> hammerfall series, the hdsp series and any cards based on the
> ice1712/ice1724 chipsets) have support within JACK to enable this.
My Echo layla24 have it.
The echomixer and the layla act like a true hard mixer, i.e. I can direct
any imput on any output (there's a matrix mixer)
"h/w monitoring" used in reference to the capabilities of a particular
> audio interface has nothing to do with JACK or Ardour. It is something
> that you have to control with another program, typically one
> specifically aimed at that type of audio interface (e.g. envy24control,
> or hdspmixer).
> in ardour 2.0, we refer to this 2nd meaning of "h/w monitoring" as
> "external monitoring".
> ardour-users mailing list
> ardour-users at lists.ardour.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Ardour-Users