[LAU] Diagnosing JACK

[Paul Davis]

The most common cause of this sort of thing is that JACK is using the
wrong device, and is using the wrong device because the device
discovery order in the kernel changed for some reason.

You should see the JACK FAQ on how to name devices so that the name
always refers to the same hardware.

There are no "logs" for JACK. You should use this command, while jack
is running, and email back its output:

   cd /tmp && wget http://jackaudio.org/downloads/adevices.sh && bash
./adevices.sh


On Fri, Oct 9, 2015 at 2:05 AM, worik <root at worik.org> wrote:
> Friends
>
> I am having trouble with JACK and I have no idea how to start diagnosing
> my problems.
>
> I am starting it with qjackctl. as I have been doing for ages using a
> M-AUDIO USB interface.
>
> I get no sound through it at all today, neither input nor output.  I
> have been using this setup for over a year with no problems.  Befire
> that I had constant problems that just went away.
>
> Now they are back.
>
> I am at my wits end, I can not find any logs where JACK is putting its
> output, which would be a start.
>
> I have had "pulseaudio" apear in the connections window, I was not
> seeing that when the system was working.
>
> Where do I start?  For a start where does JACK put its logs?
>
> I have the correct device selected in the setup tab
>
> Worik
>
> --
> Why is the legal status of chardonnay different to that of cannabis?
>                   root at worik.org 021-1680650, (03) 4821804
>                           Aotearoa (New Zealand)
>                              I voted for love
>
> _______________________________________________
> Linux-audio-user mailing list
> Linux-audio-user at lists.linuxaudio.org
> http://lists.linuxaudio.org/listinfo/linux-audio-user