Re: [Jack-Devel] list current (ALSA) device

PrevNext  Index
DateSat, 25 May 2013 20:21:42 +0100
From Filipe Lopes <[hidden] at gmail dot com>
To[hidden] at lists dot jackaudio dot org
In-Reply-ToAdrian Knoth Re: [Jack-Devel] list current (ALSA) device
Follow-UpArnold Krille Re: [Jack-Devel] list current (ALSA) device
Follow-UpHarry van Haaren Re: [Jack-Devel] list current (ALSA) device
On Sat, May 25, 2013 at 7:52 PM, Adrian Knoth <[hidden]>wrote:

> On 05/25/2013 11:15 AM, Dan MacDonald wrote:
>
> > AFAIK there is no way to discover or display the device currently used
> > by J1 or J2.
>
> In case of ALSA, you can specify the nickname on the command line and
> know for sure:
>
>    jackd -d alsa -d hw:HDSPMxf1cd85
>
> Quite clear which device it uses. You get the nicknames from
> /proc/asound/cards.
>
> For firewire devices, the device ID or nickname is part of the portname.
>
> For dummy, there is no device, neither for net.
>
> IIRC, in case of jackdbus, you can query the backend parameters.
>
>
> After all, JACK is there to abstract from the hardware, some backends
> don't even have hardware.
>
>
> I don't think a JACK API extension would make sense.
>

You're missing the point here.

After JACK is started, the user is free to change settings - be it
~/.jackdrc, qjackctl, jackdbus, etc.
Once we do that, there's no way to know for sure what device and what
specific settings the currently running JACK is using.
PrevNext  Index

1369509709.29903_0.ltw:2,a <CAJ=bptacRCKGgZNKJXu_aw6vyn1vY110sBHwhV7r93Ug=MvpJA at mail dot gmail dot com>