Re: Sudden problem Jack refuses to start.

classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: Sudden problem Jack refuses to start.

John Rigg
On Tue, Aug 06, 2019 at 01:06:31AM -0400, [hidden email] wrote:
> It looks to me like it is and ALSA problem....

What happens if you do the following?
1. Disable Pulseaudio
2. Look in /proc/asound/ to see which hw device (hw:0, hw:1 etc)
   your 1818 is
3. Start jackd from command line with -dhw:0 (or whichever one
   is the 1818) instead of the "fancy" name

John
_______________________________________________
Jack-Devel mailing list
[hidden email]
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
Reply | Threaded
Open this post in threaded view
|

Re: Sudden problem Jack refuses to start.

liebrecht
On 2019-08-06 10:54, John Rigg wrote:

> On Tue, Aug 06, 2019 at 01:06:31AM -0400,
> [hidden email] wrote:
>> It looks to me like it is and ALSA problem....
>
> What happens if you do the following?
> 1. Disable Pulseaudio
> 2. Look in /proc/asound/ to see which hw device (hw:0, hw:1 etc)
>    your 1818 is
> 3. Start jackd from command line with -dhw:0 (or whichever one
>    is the 1818) instead of the "fancy" name
>
> John
> _______________________________________________
> Jack-Devel mailing list
> [hidden email]
> http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org


Thank you John,
I get the following, would you mind to help me interprate this as I do
not see how I can change the jack string with this info.


/proc/asound$ grep -r -i 1818 *
card1/midi0:AudioBox 1818 VSL
card1/stream0:PreSonus AudioBox 1818 VSL at usb-0000:00:12.2-1.1, high
speed : USB Audio
card1/usbmixer:Card: PreSonus AudioBox 1818 VSL at usb-0000:00:12.2-1.1,
high speed
card1/usbmixer:Card: PreSonus AudioBox 1818 VSL at usb-0000:00:12.2-1.1,
high speed
card1/usbmixer:    Control: name="AudioBox 1818 VSL Audio 2.0 Output
Playback", index=3
card1/usbmixer:    Control: name="AudioBox 1818 VSL Audio 2.0 Output
Playback", index=2
card1/usbmixer:    Control: name="AudioBox 1818 VSL Audio 2.0 Output
Playback", index=1
card1/usbmixer:    Control: name="AudioBox 1818 VSL Audio 2.0 Output
Playback", index=0
card1/usbmixer:    Control: name="AudioBox 1818 VSL Clock Selector Clock
Sour", index=0
card1/usbmixer:    Control: name="AudioBox 1818 VSL Internal Clock
Validity", index=0
card1/usbmixer:    Control: name="AudioBox 1818 VSL S/PDIF Clock
Validity", index=0
card1/usbmixer:    Control: name="AudioBox 1818 VSL ADAT Clock
Validity", index=0
cards: 1 [VSL            ]: USB-Audio - AudioBox 1818 VSL
cards:                      PreSonus AudioBox 1818 VSL at
usb-0000:00:12.2-1.1, high speed
oss/sndstat:PreSonus AudioBox 1818 VSL at usb-0000:00:12.2-1.1, high
speed
oss/sndstat:1: AudioBox 1818 VSL
seq/clients:Client  20 : "AudioBox 1818 VSL" [Kernel]
seq/clients:  Port   0 : "AudioBox 1818 VSL MIDI 1" (RWeX)
VSL/midi0:AudioBox 1818 VSL
VSL/stream0:PreSonus AudioBox 1818 VSL at usb-0000:00:12.2-1.1, high
speed : USB Audio
VSL/usbmixer:Card: PreSonus AudioBox 1818 VSL at usb-0000:00:12.2-1.1,
high speed
VSL/usbmixer:Card: PreSonus AudioBox 1818 VSL at usb-0000:00:12.2-1.1,
high speed
VSL/usbmixer:    Control: name="AudioBox 1818 VSL Audio 2.0 Output
Playback", index=3
VSL/usbmixer:    Control: name="AudioBox 1818 VSL Audio 2.0 Output
Playback", index=2
VSL/usbmixer:    Control: name="AudioBox 1818 VSL Audio 2.0 Output
Playback", index=1
VSL/usbmixer:    Control: name="AudioBox 1818 VSL Audio 2.0 Output
Playback", index=0
VSL/usbmixer:    Control: name="AudioBox 1818 VSL Clock Selector Clock
Sour", index=0
VSL/usbmixer:    Control: name="AudioBox 1818 VSL Internal Clock
Validity", index=0
VSL/usbmixer:    Control: name="AudioBox 1818 VSL S/PDIF Clock
Validity", index=0
VSL/usbmixer:    Control: name="AudioBox 1818 VSL ADAT Clock Validity",
index=0


Also
VSL/usbmixer:    Control: name="AudioBox 1818 VSL Clock Selector Clock
Sour", index=0
Seemingly is at the core of why my spdif stopped working, but that is
another issue.
Alsa UG is basically dead, and dont resp-ond.
I have contacted them about the clock sour issue and not a single post
on the ug for months now.
I guess it is time to get rid of alsa. Hope something else comes along.
_______________________________________________
Jack-Devel mailing list
[hidden email]
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
Reply | Threaded
Open this post in threaded view
|

Re: Sudden problem Jack refuses to start.

Chris Caudle
On Tue, August 6, 2019 3:13 pm, [hidden email] wrote:
> I guess it is time to get rid of alsa. Hope something else comes along.

ALSA is the only audio driver architecture shipped with the linux kernel,
so currently you will need to change operating systems to get rid of ALSA.

I think what you need is not to get rid of ALSA, just to improve on ALSA
user tools for configuring audio interfaces with many options.

--
Chris Caudle


_______________________________________________
Jack-Devel mailing list
[hidden email]
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
Reply | Threaded
Open this post in threaded view
|

Re: Sudden problem Jack refuses to start.

Chris Caudle
In reply to this post by liebrecht
On Tue, August 6, 2019 3:13 pm, [hidden email] wrote:
> Alsa UG is basically dead, and dont resp-ond.

What are you calling the Alsa UG?  Are you referring to the alsa-users
mailing list?
Probably linux-audio-users would be more active, especially for studio
recording style interfaces.

--
Chris Caudle


_______________________________________________
Jack-Devel mailing list
[hidden email]
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
Reply | Threaded
Open this post in threaded view
|

Re: Sudden problem Jack refuses to start.

liebrecht
On 2019-08-06 16:25, Chris Caudle wrote:
> On Tue, August 6, 2019 3:13 pm, [hidden email] wrote:
>> Alsa UG is basically dead, and dont resp-ond.
>
> What are you calling the Alsa UG?  Are you referring to the alsa-users
> mailing list?

Yes alsa-users mailing list, it is dead as a doornail.
_______________________________________________
Jack-Devel mailing list
[hidden email]
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
Reply | Threaded
Open this post in threaded view
|

Re: Sudden problem Jack refuses to start.

John Rigg
In reply to this post by liebrecht
On Tue, Aug 06, 2019 at 04:13:05PM -0400, [hidden email] wrote:
> I get the following, would you mind to help me interprate this as I do  
> not see how I can change the jack string with this info.
>
> /proc/asound$ grep -r -i 1818 *
> card1/midi0:AudioBox 1818 VSL

The card number corresponds to the hw: number.
This is card 1, so use -hw:1, eg.:
jackd -dalsa -hw:1 -r44100 -p512 -n8

I notice you also have an M-Audio USB interface plugged in.
I wonder if the two USB audio devices are sometimes detected
in the wrong order. This could happen if one of them becomes
inactive and needs re-plugging, for example.

It may be simpler for troubleshooting purposes to leave the
M-Audio device unplugged (which may change the card number
of the 1818 so you'll need to check it again).

John
_______________________________________________
Jack-Devel mailing list
[hidden email]
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
Reply | Threaded
Open this post in threaded view
|

Re: Sudden problem Jack refuses to start.

John Rigg
In reply to this post by liebrecht
On Tue, Aug 06, 2019 at 04:13:05PM -0400, [hidden email] wrote:
> Alsa UG is basically dead, and dont resp-ond.
> I have contacted them about the clock sour issue and not a single post  
> on the ug for months now.
> I guess it is time to get rid of alsa. Hope something else comes along.

ALSA is the linux kernel audio subsystem and it isn't going
away in the foreseeable future.

Most ordinary users of ALSA probably use linux-audio-users
list nowadays. The alsa-devel list is still very active.
Note that JACK doesn't have an active jack-users list
either, but the project is very much alive.

John
_______________________________________________
Jack-Devel mailing list
[hidden email]
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
Reply | Threaded
Open this post in threaded view
|

Re: Sudden problem Jack refuses to start.

liebrecht
In reply to this post by John Rigg
On 2019-08-06 10:54, John Rigg wrote:

> On Tue, Aug 06, 2019 at 01:06:31AM -0400,
> [hidden email] wrote:
>> It looks to me like it is and ALSA problem....
>
> What happens if you do the following?
> 1. Disable Pulseaudio
> 2. Look in /proc/asound/ to see which hw device (hw:0, hw:1 etc)
>    your 1818 is
> 3. Start jackd from command line with -dhw:0 (or whichever one
>    is the 1818) instead of the "fancy" name
>
> John
> _______________________________________________
> Jack-Devel mailing list
> [hidden email]
> http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org

So here is the string I currently use;
/usr/bin/jackd --sync -P80 -ndefault -dalsa -dhw:VSL -r44100 -p512 -n8

I dont understand how it should be changed according to info below.



/proc/asound$ grep -r -i 1818 *
card1/midi0:AudioBox 1818 VSL
card1/stream0:PreSonus AudioBox 1818 VSL at usb-0000:00:12.2-1.1, high
speed : USB Audio
card1/usbmixer:Card: PreSonus AudioBox 1818 VSL at usb-0000:00:12.2-1.1,
high speed
card1/usbmixer:Card: PreSonus AudioBox 1818 VSL at usb-0000:00:12.2-1.1,
high speed
card1/usbmixer:    Control: name="AudioBox 1818 VSL Audio 2.0 Output
Playback", index=3
card1/usbmixer:    Control: name="AudioBox 1818 VSL Audio 2.0 Output
Playback", index=2
card1/usbmixer:    Control: name="AudioBox 1818 VSL Audio 2.0 Output
Playback", index=1
card1/usbmixer:    Control: name="AudioBox 1818 VSL Audio 2.0 Output
Playback", index=0
card1/usbmixer:    Control: name="AudioBox 1818 VSL Clock Selector Clock
Sour", index=0
card1/usbmixer:    Control: name="AudioBox 1818 VSL Internal Clock
Validity", index=0
card1/usbmixer:    Control: name="AudioBox 1818 VSL S/PDIF Clock
Validity", index=0
card1/usbmixer:    Control: name="AudioBox 1818 VSL ADAT Clock
Validity", index=0
cards: 1 [VSL            ]: USB-Audio - AudioBox 1818 VSL
cards:                      PreSonus AudioBox 1818 VSL at
usb-0000:00:12.2-1.1, high speed
oss/sndstat:PreSonus AudioBox 1818 VSL at usb-0000:00:12.2-1.1, high
speed
oss/sndstat:1: AudioBox 1818 VSL
seq/clients:Client  20 : "AudioBox 1818 VSL" [Kernel]
seq/clients:  Port   0 : "AudioBox 1818 VSL MIDI 1" (RWeX)
VSL/midi0:AudioBox 1818 VSL
VSL/stream0:PreSonus AudioBox 1818 VSL at usb-0000:00:12.2-1.1, high
speed : USB Audio
VSL/usbmixer:Card: PreSonus AudioBox 1818 VSL at usb-0000:00:12.2-1.1,
high speed
VSL/usbmixer:Card: PreSonus AudioBox 1818 VSL at usb-0000:00:12.2-1.1,
high speed
VSL/usbmixer:    Control: name="AudioBox 1818 VSL Audio 2.0 Output
Playback", index=3
VSL/usbmixer:    Control: name="AudioBox 1818 VSL Audio 2.0 Output
Playback", index=2
VSL/usbmixer:    Control: name="AudioBox 1818 VSL Audio 2.0 Output
Playback", index=1
VSL/usbmixer:    Control: name="AudioBox 1818 VSL Audio 2.0 Output
Playback", index=0
VSL/usbmixer:    Control: name="AudioBox 1818 VSL Clock Selector Clock
Sour", index=0
VSL/usbmixer:    Control: name="AudioBox 1818 VSL Internal Clock
Validity", index=0
VSL/usbmixer:    Control: name="AudioBox 1818 VSL S/PDIF Clock
Validity", index=0
VSL/usbmixer:    Control: name="AudioBox 1818 VSL ADAT Clock Validity",
index=0


_______________________________________________
Jack-Devel mailing list
[hidden email]
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
Reply | Threaded
Open this post in threaded view
|

Re: Sudden problem Jack refuses to start.

liebrecht
In reply to this post by John Rigg
On 2019-08-07 08:08, John Rigg wrote:

> On Tue, Aug 06, 2019 at 04:13:05PM -0400,
> [hidden email] wrote:
>> I get the following, would you mind to help me interprate this as I do
>> not see how I can change the jack string with this info.
>>
>> /proc/asound$ grep -r -i 1818 *
>> card1/midi0:AudioBox 1818 VSL
>
> The card number corresponds to the hw: number.
> This is card 1, so use -hw:1, eg.:
> jackd -dalsa -hw:1 -r44100 -p512 -n8
>
> I notice you also have an M-Audio USB interface plugged in.
> I wonder if the two USB audio devices are sometimes detected
> in the wrong order. This could happen if one of them becomes
> inactive and needs re-plugging, for example.
>
> It may be simpler for troubleshooting purposes to leave the
> M-Audio device unplugged (which may change the card number
> of the 1818 so you'll need to check it again).
>
> John

John ignore my latest email.
I didnt notice that you answered already.
This answers the question.
Thank you very much.

_______________________________________________
Jack-Devel mailing list
[hidden email]
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org