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

As Filipe says, I'm sorry but the suggestions don't really solve the issue
and please don't pretend the ps/grep combo isn't a kludge. JACK should be
targeting musicians and sound engineers, not sysadmins and devs (although I
realise most on this list are sysadmins and devs and wouldn't be too upset
about having to to a bit of cli magic now and again) but even then they are
likely to forget or not know about such a command for what seems like
pretty fundamental info about JACK's status.

I mainly use cadence to control J2 these days but I'd also like I simple
way to see the current device from jack_control, ideally.


On Sat, May 25, 2013 at 8:30 PM, Filipe Lopes <[hidden]> wrote:

> On Sat, May 25, 2013 at 9:18 PM, Harry van Haaren <[hidden]>wrote:
>
>> On Sat, May 25, 2013 at 8:21 PM, Filipe Lopes <[hidden]> wrote:
>>
>>> 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.
>>>
>>
>> ps -eLo cmd | grep "jackd"   will give you the exact jackd startup
>> arguments.
>>
>> @OP: just create setup presets, and QJackCtl renames its window to
>> JACK[<presetName>]
>> Easy solution. I look at my task bar / QJackCtl window, and see
>> JACK[alsa] now, as opposed to JACK[rme] when on the outboard card. Does
>> this solve your use case?
>>
>
> I don't think so, that works for jackd but not jackdbus.
> It will also not work if JACK was started outside QJackCtl
>
>
> 
> Jack-Devel mailing list
> [hidden]
> http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
>
>

1369514862.416_0.ltw:2,a <CANOoOjuXLcvBebTrW8GO726GPTr-mwzDV=75Oz59ZT=7zq+p8A at mail dot gmail dot com>