[Jack-Devel] Is a M audio 1010lt too old to use with jack?

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

[Jack-Devel] Is a M audio 1010lt too old to use with jack?

vinnie
Hi, I am just starting out trying to get a linux based studio up and running. I am having a bit of troble getting my sound card to work. I have been trying to slove the problem myself, reading forums etc but I get the feeling I'm just going around in circles because I don't actually know what I am doing. I manage to change the error messages in jack but not actually solve them. This is the latest output from jack when I try to start it.

10:11:25.234 Statistics reset.

10:11:25.245 ALSA connection change.

10:11:25.329 D-BUS: Service is available (org.jackaudio.service aka jackdbus).

Cannot connect to server socket err = No such file or directory

Cannot connect to server request channel

jack server is not running or cannot be started

JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock

JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock

10:11:25.407 ALSA connection graph change.

10:12:01.086 D-BUS: JACK server is starting...

10:12:01.199 D-BUS: JACK server was started (org.jackaudio.service aka jackdbus).

Cannot connect to server socket err = No such file or directory

Cannot connect to server request channel

jack server is not running or cannot be started

JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock

JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock

Wed May 15 10:12:01 2019: Starting jack server...

Wed May 15 10:12:01 2019: JACK server starting in realtime mode with priority 10

Wed May 15 10:12:01 2019: self-connect-mode is "Don't restrict self connect requests"

Wed May 15 10:12:01 2019: ERROR: Cannot lock down 82280346 byte memory area (Cannot allocate memory)

Wed May 15 10:12:01 2019: Acquired audio card Audio0

Wed May 15 10:12:01 2019: creating alsa driver ... hw:PCH|hw:PCH|1024|2|48000|0|0|nomon|swmeter|-|32bit

Wed May 15 10:12:01 2019: configuring for 48000Hz, period = 1024 frames (21.3 ms), buffer = 2 periods

Wed May 15 10:12:01 2019: ALSA: final selected sample format for capture: 32bit integer little-endian

Wed May 15 10:12:01 2019: ALSA: use 2 periods for capture

Wed May 15 10:12:01 2019: ALSA: final selected sample format for playback: 32bit integer little-endian

Wed May 15 10:12:01 2019: ALSA: use 2 periods for playback

Wed May 15 10:12:01 2019: graph reorder: new port 'system:capture_1'

Wed May 15 10:12:01 2019: New client 'system' with PID 0

Wed May 15 10:12:01 2019: graph reorder: new port 'system:capture_2'

Wed May 15 10:12:01 2019: graph reorder: new port 'system:playback_1'

Wed May 15 10:12:01 2019: graph reorder: new port 'system:playback_2'

Wed May 15 10:12:01 2019: New client 'PulseAudio JACK Sink' with PID

1324

Wed May 15 10:12:01 2019: Connecting 'PulseAudio JACK Sink:front-left' to 'system:playback_1'

Wed May 15 10:12:01 2019: Connecting 'PulseAudio JACK Sink:front-right' to 'system:playback_2'

Wed May 15 10:12:01 2019: New client 'PulseAudio JACK Source' with PID 1324

Wed May 15 10:12:01 2019: Connecting 'system:capture_1' to 'PulseAudio JACK Source:front-left'

Wed May 15 10:12:01 2019: Connecting 'system:capture_2' to 'PulseAudio JACK Source:front-right'

Wed May 15 10:12:02 2019: Saving settings to "/home/vinnie/.config/jack/conf.xml" ...

10:12:03.253 JACK connection change.

10:12:03.254 Server configuration saved to "/home/vinnie/.jackdrc".

10:12:03.254 Statistics reset.

10:12:03.262 Client activated.

10:12:03.263 Patchbay deactivated.

10:12:03.356 JACK connection graph change.

Wed May 15 10:12:03 2019: New client 'qjackctl' with PID 2727


Anyway if anyone can point me into a direction of where to start reading so I can get some understanding of what I am doing/should be doing that would be much apperciated. 

Thanks



_______________________________________________
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: Is a M audio 1010lt too old to use with jack?

Tim-2
My Delta 1010L works fine.
It looks like Jack is running, below.

Maybe you're not getting any sound from the card?
For this card, try a good mixer, to adjust the hardware volumes.
There is envy24, and mudita24, both tailored for this card.
You can also try a general-purpose mixer like QasMixer.

Beyond that have a look at the documentation at the jack website.
It will tell you how to optimize the system by setting various
  limits and maybe get rid of the "ERROR: Cannot lock down" message.

One tip I can offer: Extensive tests on different modern multi-core
  PCs running either Linux or Windows showed that this card does not
  like all CPU cores enabled. Yours might have the same problem.
Symptoms are popping, crackling, and noise in the sound.
Unless someone has found a better fix, you'd likely want to turn
  off all but one core with commands like this, for a quad core CPU:

echo 0 | sudo tee /sys/devices/system/cpu/cpu1/online
echo 0 | sudo tee /sys/devices/system/cpu/cpu2/online
echo 0 | sudo tee /sys/devices/system/cpu/cpu3/online

Where cpu0 is left running.

(You can also do the same thing with most motherboard BIOS
  setup features.)

Tim.

On 5/14/19 6:20 PM, Vinnie Beaumont wrote:

> Hi, I am just starting out trying to get a linux based studio up and
> running. I am having a bit of troble getting my sound card to work. I
> have been trying to slove the problem myself, reading forums etc but I
> get the feeling I'm just going around in circles because I don't
> actually know what I am doing. I manage to change the error messages in
> jack but not actually solve them. This is the latest output from jack
> when I try to start it.
>
> 10:11:25.234 Statistics reset.
>
> 10:11:25.245 ALSA connection change.
>
> 10:11:25.329 D-BUS: Service is available (org.jackaudio.service aka
> jackdbus).
>
> Cannot connect to server socket err = No such file or directory
>
> Cannot connect to server request channel
>
> jack server is not running or cannot be started
>
> JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1,
> skipping unlock
>
> JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1,
> skipping unlock
>
> 10:11:25.407 ALSA connection graph change.
>
> 10:12:01.086 D-BUS: JACK server is starting...
>
> 10:12:01.199 D-BUS: JACK server was started (org.jackaudio.service aka
> jackdbus).
>
> Cannot connect to server socket err = No such file or directory
>
> Cannot connect to server request channel
>
> jack server is not running or cannot be started
>
> JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1,
> skipping unlock
>
> JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1,
> skipping unlock
>
> Wed May 15 10:12:01 2019: Starting jack server...
>
> Wed May 15 10:12:01 2019: JACK server starting in realtime mode with
> priority 10
>
> Wed May 15 10:12:01 2019: self-connect-mode is "Don't restrict self
> connect requests"
>
> Wed May 15 10:12:01 2019: ERROR: Cannot lock down 82280346 byte memory
> area (Cannot allocate memory)
>
> Wed May 15 10:12:01 2019: Acquired audio card Audio0
>
> Wed May 15 10:12:01 2019: creating alsa driver ...
> hw:PCH|hw:PCH|1024|2|48000|0|0|nomon|swmeter|-|32bit
>
> Wed May 15 10:12:01 2019: configuring for 48000Hz, period = 1024 frames
> (21.3 ms), buffer = 2 periods
>
> Wed May 15 10:12:01 2019: ALSA: final selected sample format for
> capture: 32bit integer little-endian
>
> Wed May 15 10:12:01 2019: ALSA: use 2 periods for capture
>
> Wed May 15 10:12:01 2019: ALSA: final selected sample format for
> playback: 32bit integer little-endian
>
> Wed May 15 10:12:01 2019: ALSA: use 2 periods for playback
>
> Wed May 15 10:12:01 2019: graph reorder: new port 'system:capture_1'
>
> Wed May 15 10:12:01 2019: New client 'system' with PID 0
>
> Wed May 15 10:12:01 2019: graph reorder: new port 'system:capture_2'
>
> Wed May 15 10:12:01 2019: graph reorder: new port 'system:playback_1'
>
> Wed May 15 10:12:01 2019: graph reorder: new port 'system:playback_2'
>
> Wed May 15 10:12:01 2019: New client 'PulseAudio JACK Sink' with PID
>
> 1324
>
> Wed May 15 10:12:01 2019: Connecting 'PulseAudio JACK Sink:front-left'
> to 'system:playback_1'
>
> Wed May 15 10:12:01 2019: Connecting 'PulseAudio JACK Sink:front-right'
> to 'system:playback_2'
>
> Wed May 15 10:12:01 2019: New client 'PulseAudio JACK Source' with PID 1324
>
> Wed May 15 10:12:01 2019: Connecting 'system:capture_1' to 'PulseAudio
> JACK Source:front-left'
>
> Wed May 15 10:12:01 2019: Connecting 'system:capture_2' to 'PulseAudio
> JACK Source:front-right'
>
> Wed May 15 10:12:02 2019: Saving settings to
> "/home/vinnie/.config/jack/conf.xml" ...
>
> 10:12:03.253 JACK connection change.
>
> 10:12:03.254 Server configuration saved to "/home/vinnie/.jackdrc".
>
> 10:12:03.254 Statistics reset.
>
> 10:12:03.262 Client activated.
>
> 10:12:03.263 Patchbay deactivated.
>
> 10:12:03.356 JACK connection graph change.
>
> Wed May 15 10:12:03 2019: New client 'qjackctl' with PID 2727
>
>
> Anyway if anyone can point me into a direction of where to start reading
> so I can get some understanding of what I am doing/should be doing that
> would be much apperciated.
>
> Thanks
>
>
>
> _______________________________________________
> Jack-Devel mailing list
> [hidden email]
> http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
>
_______________________________________________
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: Is a M audio 1010lt too old to use with jack?

John Rigg
On Tue, May 14, 2019 at 09:46:37PM -0400, Tim wrote:
> My Delta 1010L works fine.
> It looks like Jack is running, below.

Is it running with the right card? It only shows two channels.
You may need to turn off any onboard audio interface in the
BIOS if you haven't done so already.

The Arch Linux Wiki has good instructions on setting up audio
on Linux.

> One tip I can offer: Extensive tests on different modern multi-core
>  PCs running either Linux or Windows showed that this card does not
>  like all CPU cores enabled. Yours might have the same problem.
> Symptoms are popping, crackling, and noise in the sound.
> Unless someone has found a better fix, you'd likely want to turn
>  off all but one core with commands like this, for a quad core CPU:

YMMV here. I have six Delta 1010 (same ice1712 chip as 1010LT)
and haven't encountered this problem. I've used them on Linux for
~14 years with a variety of 2-core and 4-core systems. I'd try it
first without this measure and only resort to it if necessary.

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: Is a M audio 1010lt too old to use with jack?

vinnie
This post was updated on .
I have blacklisted my onboard sound card and now jack displays 12 capture and
playback clients as I expected to see from the 1010. but if I try to connect
them I get this kind of thing

Wed May 15 21:18:51 2019: Connecting 'system:capture_1' to
'system:playback_1'
21:18:53.683 XRUN callback (22 skipped).
21:18:54.378 JACK connection change.
Wed May 15 21:18:54 2019: Connecting 'system:capture_2' to
'system:playback_2'
21:18:56.268 XRUN callback (24 skipped).
21:18:58.440 XRUN callback (20 skipped).

(edit, lots of xrun callbacks)

21:19:50.720 XRUN callback (3 skipped).
21:19:54.082 XRUN callback (765).
21:19:54.110 ALSA connection graph change.
21:19:54.206 ALSA connection graph change.
21:19:54.731 XRUN callback (53 skipped).
Wed May 15 21:19:54 2019: ERROR: JackPosixProcessSync::LockedTimedWait error
usec = 5000000 err = Connection timed out
Wed May 15 21:19:54 2019: ERROR: Driver is not running
Wed May 15 21:19:54 2019: ERROR: Cannot create new client
21:19:56.739 XRUN callback (18 skipped).
21:19:58.749 XRUN callback (18 skipped).

I can get sound through the 1010 using envy24 patchbay. I have inputs 3,4
playing out outputs 1,2, so the card woks. I think I am just having troble
with jack?  



--
Sent from: http://jack-audio.10948.n7.nabble.com/Jackit-f3.html
_______________________________________________
Jack-Devel mailing list
Jack-Devel@lists.jackaudio.org
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
Reply | Threaded
Open this post in threaded view
|

Re: Is a M audio 1010lt too old to use with jack?

vinnie
Right well I have spent the day on iy and this is where I got to...

22:00:01.905 JACK is starting...
22:00:01.906 /usr/bin/jackd -dalsa -dhw:M1010LT -r48000 -p1024 -n2
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping
unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping
unlock
no message buffer overruns
no message buffer overruns
no message buffer overruns
jackdmp 1.9.12
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2016 Grame.
Copyright 2016-2017 Filipe Coelho.
jackdmp comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
JACK server starting in realtime mode with priority 10
self-connect-mode is "Don't restrict self connect requests"
audio_reservation_init
Acquire audio card Audio0
creating alsa driver ...
hw:M1010LT|hw:M1010LT|1024|2|48000|0|0|nomon|swmeter|-|32bit
configuring for 48000Hz, period = 1024 frames (21.3 ms), buffer = 2 periods
ALSA: final selected sample format for capture: 32bit integer little-endian
ALSA: use 2 periods for capture
ALSA: final selected sample format for playback: 32bit integer little-endian
ALSA: use 2 periods for playback
22:00:01.996 JACK was started with PID=3131.
22:00:09.065 Could not connect to JACK server as client. - Overall operation
failed. - Server communication error. Please check the messages window for
more info.
JackPosixProcessSync::LockedTimedWait error usec = 5000000 err = Connection
timed out
Driver is not running
Cannot create new client
Cannot read socket fd = 29 err = Success
CheckRes error
JackSocketClientChannel read fail
Cannot open qjackctl client
JackShmReadWritePtr1::~JackShmReadWritePtr1 - Init not done for -1, skipping
unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping
unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping
unlock
22:00:11.003 JACK is stopping...
Jack main caught signal 15

I have learnt a fair bit but mainly gone roung in circles, oh well maybe
tomorrow



--
Sent from: http://jack-audio.10948.n7.nabble.com/Jackit-f3.html
_______________________________________________
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: Is a M audio 1010lt too old to use with jack?

John Rigg
On Wed, May 15, 2019 at 03:03:42AM -0700, vinnie wrote:
> Right well I have spent the day on iy and this is where I got to...
>
.....
> 22:00:01.905 JACK is starting...
> 22:00:01.906 /usr/bin/jackd -dalsa -dhw:M1010LT -r48000 -p1024 -n2
....
> Cannot open qjackctl client

When troubleshooting it's better to avoid qjackctl and just use
the command line to start jackd, ie.:

 /usr/bin/jackd -dalsa -dhw:M1010LT -r48000 -p1024 -n2

From your OP it looks like you're running pulseaudio. If
so, try disabling it.

Another source of potential problems IME is dbus. I see
you're using jack2, which many distros compile with dbus
as a dependency. On my own (Debian) systems I recompile it
without dbus. An alternative would be to install jack1
instead, if it's available on your distro.

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