Re: Diagnosing JACK

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



This has been very interesting but I am left with egg on my face.

Obtaining and plugging in a different device (Alesis iO2) fixed the
sound. This was a hardware problem.

sorry
Worik


On 09/10/15 19:05, worik 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@xxxxxxxxx 021-1680650, (03) 4821804
                          Aotearoa (New Zealand)
                             I voted for love

_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@xxxxxxxxxxxxxxxxxxxx
http://lists.linuxaudio.org/listinfo/linux-audio-user



[Index of Archives]     [Linux Sound]     [ALSA Users]     [Pulse Audio]     [ALSA Devel]     [Sox Users]     [Linux Media]     [Kernel]     [Photo Sharing]     [Gimp]     [Yosemite News]     [Linux Media]

  Powered by Linux