[Jack-Devel] Jack_Capture not starting anymore after having Jackd running as systemd service
10 Dec
2018
10 Dec
'18
2:53 p.m.
Hey!
Using the jack audio toolkit with my pisound DAC on a Raspberry Pi 3 which was a hassle -
but I got it running with some hacks.
Now for convenience I added jackd and jack_connect (to route input to output) as a service
inside systemd - which works as expected. Before I could easily start jack_capture to
record the input. But now it’s not starting anymore unfortunately. I get this error:
jack_capture -c 5 -mb -tm -f flac
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
>> jack_client_open() failed, status = 0x11
I copied jack_capture also to /usr/locale/bin
My systemd service files:
jack-connect.service —> starts also jackd.service
[Unit]
Description=jack-connect
Wants=jackd.service
After=jackd.service
[Service]
Type=oneshot
ExecStartPre=/bin/sleep 1s
ExecStartPre=/usr/local/bin/jack_connect system:capture_2 system:playback_2
ExecStart=/usr/local/bin/jack_connect system:capture_1 system:playback_1
jackd.service
[Unit]
Description=jackd Unit
[Service]
ExecStart=/usr/local/bin/jackd -t 2000 -P 75 -d alsa -d hw:pisound -r 48000 -p 128 -n 2 -X
seq -s
ExecStop=/usr/bin/killall jackd
Can anyone help me with this?
Kind regards
Jan
10 Dec
10 Dec
3:07 p.m.
I don't know if this is the problem, but it looks like it.
The problem seems to be:
"jackd" needs to run by the same user as the clients.
(At least that's how it was in the old days, but maybe something
has changed since then).
E.g. If the process owner of jackd is root, you can't run jack_capture
as a normal user.
I'm also pretty sure you can run several jackd simultaneously
on the same machine as long as each jackd is run by a different user.
On Mon, Dec 10, 2018 at 10:53 PM jack(a)microfx.de <jack(a)microfx.de> wrote:
Hey!
Using the jack audio toolkit with my pisound DAC on a Raspberry Pi 3 which was a hassle -
but I got it running with some hacks.
Now for convenience I added jackd and jack_connect (to route input to output) as a
service inside systemd - which works as expected. Before I could easily start jack_capture
to record the input. But now it’s not starting anymore unfortunately. I get this error:
jack_capture -c 5 -mb -tm -f flac
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
>> jack_client_open() failed, status = 0x11
I copied jack_capture also to /usr/locale/bin
My systemd service files:
jack-connect.service —> starts also jackd.service
[Unit]
Description=jack-connect
Wants=jackd.service
After=jackd.service
[Service]
Type=oneshot
ExecStartPre=/bin/sleep 1s
ExecStartPre=/usr/local/bin/jack_connect system:capture_2 system:playback_2
ExecStart=/usr/local/bin/jack_connect system:capture_1 system:playback_1
jackd.service
[Unit]
Description=jackd Unit
[Service]
ExecStart=/usr/local/bin/jackd -t 2000 -P 75 -d alsa -d hw:pisound -r 48000 -p 128 -n 2
-X seq -s
ExecStop=/usr/bin/killall jackd
Can anyone help me with this?
Kind regards
Jan
_______________________________________________
Jack-Devel mailing list
Jack-Devel(a)lists.jackaudio.org
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org 
3:11 p.m.
On Mon, December 10, 2018 3:53 pm, jack(a)microfx.de wrote:
Now for convenience I added jackd and jack_connect (to
route input to
output) as a service inside systemd - which works as expected. Before I
could easily start jack_capture to record the input. But now itâs not
starting anymore unfortunately. I get this error:
jack_capture -c 5 -mb -tm -f flac
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
Probably as Kjetil wrote the user accounts are not the same.
In the [Service] section of the systemd file you can have User= and Group=
lines to set the user and group which the service should be run. Perhaps
if you make a user account and add that account in the systemd service
file and also log in as that user when you want to use jack_capture it
will still work as you would like.
--
Chris Caudle
3:18 p.m.
Ah, that seems to be the problem! Thanks for the quick reply!
My initial idea was to add this as well as a service but jack_capture needs user input -
is this possible with a service? Like an additional script that triggers the recording?
On 10. Dec 2018, at 23:11, Chris Caudle
<chris(a)chriscaudle.org> wrote:
On Mon, December 10, 2018 3:53 pm, jack(a)microfx.de wrote:
Now for convenience I added jackd and
jack_connect (to route input to
output) as a service inside systemd - which works as expected. Before I
could easily start jack_capture to record the input. But now itâs not
starting anymore unfortunately. I get this error:
jack_capture -c 5 -mb -tm -f flac
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
Probably as Kjetil wrote the user accounts are not the same.
In the [Service] section of the systemd file you can have User= and Group=
lines to set the user and group which the service should be run. Perhaps
if you make a user account and add that account in the systemd service
file and also log in as that user when you want to use jack_capture it
will still work as you would like.
--
Chris Caudle
_______________________________________________
Jack-Devel mailing list
Jack-Devel(a)lists.jackaudio.org
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
3:26 p.m.
On Mon, December 10, 2018 4:18 pm, jack(a)microfx.de wrote:
My initial idea was to add this as well as a service
but jack_capture
needs user input - is this possible with a service? Like an additional
script that triggers the recording?
If you need user input, will you be using jack_capture after logging in? A
service should just be for a program which runs constantly in the
background, jack_capture seems more of an interactive program, although
you could probably run in from something like a shell script.
Have you tried the suggested solution yet, add a new account that is used
both for running jackd as a service, and as your login account when you
want to run jack_capture?
--
Chris Caudle
3:35 p.m.
Yes! Adding User / Group to the .service fixed the problem of not starting! Thanks a lot!
My setup would best look like this:
The pisound has a button. I have it now configured and working that when I press a button
it runs a shell script which checks if my jackd service is running - if yes, stop else
start (so one button solution to start / stop) - I need this because I couldn’t figure out
how to use Volumio with jack2 and to switch between Spotify/Airplay with Volumio - so this
is a working workaround so far.
Now I’d like to start recording when doing a double-press on the button and stop it with
the same double-press (it’s a feature of the pisound).
On 10. Dec 2018, at 23:26, Chris Caudle <chris(a)chriscaudle.org> wrote:
On Mon, December 10, 2018 4:18 pm, jack(a)microfx.de wrote:
My initial idea was to add this as well as a
service but jack_capture
needs user input - is this possible with a service? Like an additional
script that triggers the recording?
If you need user input, will you be using jack_capture after logging in? A
service should just be for a program which runs constantly in the
background, jack_capture seems more of an interactive program, although
you could probably run in from something like a shell script.
Have you tried the suggested solution yet, add a new account that is used
both for running jackd as a service, and as your login account when you
want to run jack_capture?
--
Chris Caudle
3:27 p.m.
On Mon, Dec 10, 2018 at 11:18 PM jack(a)microfx.de <jack(a)microfx.de> wrote:
Ah, that seems to be the problem! Thanks for the quick reply!
My initial idea was to add this as well as a service but jack_capture needs user input -
is this possible with a service? Like an additional script that triggers the recording?
How about letting jack_capture listen to OSC?
jack_capture --help-osc
Then you can run jack_capture as root like this:
jack_capture --osc 7777 --filename-prefix
/recording/directory/jack_capture_recording_
And as a normal user you can run
oscsend localhost 7777 /jack_capture/tm/start
oscsend localhost 7777 /jack_capture/tm/stop
to start and stop recording.
Robin Gareus might help more on this, since he wrote that code.
I'm not entirely sure if this is the best way to use the OSC interface.
3:36 p.m.
On Mon, Dec 10, 2018 at 11:27 PM Kjetil Matheussen
<k.s.matheussen(a)gmail.com> wrote:
On Mon, Dec 10, 2018 at 11:18 PM jack(a)microfx.de <jack(a)microfx.de> wrote:
I just tried it, and this seems to work the way you want it. But you
need to run jack_capture with the "-tm" option to start it in time
machine mode.
You might also want to use the "--daemon" option for jack_capture,
which will stop it from printing stuff to stdout.
Ah, that seems to be the problem! Thanks for the quick reply!
My initial idea was to add this as well as a service but jack_capture needs user input -
is this possible with a service? Like an additional script that triggers the recording?
How about letting jack_capture listen to OSC?
jack_capture --help-osc
Then you can run jack_capture as root like this:
jack_capture --osc 7777 --filename-prefix
/recording/directory/jack_capture_recording_
And as a normal user you can run
oscsend localhost 7777 /jack_capture/tm/start
oscsend localhost 7777 /jack_capture/tm/stop
to start and stop recording.
Robin Gareus might help more on this, since he wrote that code.
I'm not entirely sure if this is the best way to use the OSC interface.
3:37 p.m.
that indeed looks like a solution! But I would need to know if jack_capture is recording
to stop it again because I want to use a button to trigger start/stop of the recording -
and I can’t think of a solution right away. Good input for the recording directory - I was
asking myself how to do that since I couldn’t find that in the help file.
On 10. Dec 2018, at 23:27, Kjetil Matheussen
<k.s.matheussen(a)gmail.com> wrote:
On Mon, Dec 10, 2018 at 11:18 PM jack(a)microfx.de <jack(a)microfx.de> wrote:
Ah, that seems to be the problem! Thanks for the quick reply!
My initial idea was to add this as well as a service but jack_capture needs user input -
is this possible with a service? Like an additional script that triggers the recording?
How about letting jack_capture listen to OSC?
jack_capture --help-osc
Then you can run jack_capture as root like this:
jack_capture --osc 7777 --filename-prefix
/recording/directory/jack_capture_recording_
And as a normal user you can run
oscsend localhost 7777 /jack_capture/tm/start
oscsend localhost 7777 /jack_capture/tm/stop
to start and stop recording.
Robin Gareus might help more on this, since he wrote that code.
I'm not entirely sure if this is the best way to use the OSC interface.
3:56 p.m.
On Mon, Dec 10, 2018 at 11:37 PM jack(a)microfx.de <jack(a)microfx.de> wrote:
that indeed looks like a solution! But I would need to know if jack_capture is recording
to stop it again because I want to use a button to trigger start/stop of the recording -
and I can’t think of a solution right away. Good input for the recording directory - I was
asking myself how to do that since I couldn’t find that in the help file.
A little bit hacky, but you can use the --hook* functions to make
jack_capture run arbitrary commands when starting and stopping:
"
[kjetil@localhost jack_capture]$ more hookstart.sh
#!/bin/sh
touch /tmp/jack_capture_is_recording
[kjetil@localhost jack_capture]$ more hookstop.sh
#!/bin/sh
rm -f /tmp/jack_capture_is_recording
"
And if you run jack_capture with the arguments
--hook-close ./hookstop.sh --hook-timing ./hookstart.sh
The file /tmp/jack_capture_is_recording will exist when recording.
4:14 p.m.
On Mon, Dec 10, 2018 at 11:56 PM Kjetil Matheussen
<k.s.matheussen(a)gmail.com> wrote:
The file /tmp/jack_capture_is_recording will exist when recording.
By the way, with the hooks you can also (from the outside),
know the filename of the currently recording file, and also how
long time it has been recording.
(The hooks are also made by Robin Gareus, so he might have some
additional input.)
4:52 p.m.
Alright! I added everything… but I have some routing problems right now so I cannot
install the osc package. Will try tomorrow.
I just tested the whole setup … and I get crackling when running jackd as mentioned above
with systemd …does it run with another priority maybe? When using my old scripts to start
jack2 everything is normal.
On 11. Dec 2018, at 00:14, Kjetil Matheussen
<k.s.matheussen(a)gmail.com> wrote:
On Mon, Dec 10, 2018 at 11:56 PM Kjetil Matheussen
<k.s.matheussen(a)gmail.com> wrote:
The file /tmp/jack_capture_is_recording will exist when recording.
By the way, with the hooks you can also (from the outside),
know the filename of the currently recording file, and also how
long time it has been recording.
(The hooks are also made by Robin Gareus, so he might have some
additional input.)
5:01 p.m.
On Tue, Dec 11, 2018 at 12:52 AM jack(a)microfx.de <jack(a)microfx.de> wrote:
Alright! I added everything… but I have some routing problems right now so I cannot
install the osc package. Will try tomorrow.
I just tested the whole setup … and I get crackling when running jackd as mentioned above
with systemd …does it run with another priority maybe? When using my old scripts to start
jack2 everything is normal.
You might not have the right privilege to run jackd as a normal user
with SCHED_FIFO or SCHED_RR priority (I.e realtime priority).
Try to run jackd manually in the shell as a normal user and see if it
shows a warning message about this.
If you do get a warning, there's probably some info at jackaudio.org
on how to enable realtime privileges for normal users, or you can
google it. I don't remember exactly how right now. :-)
5:07 p.m.
But I was running jack before as user pi with my scripts and with systemd also as user pi
… ah maybe different group? I just made the Group=pi as well… is there a special group
maybe?
On 11. Dec 2018, at 01:01, Kjetil Matheussen
<k.s.matheussen(a)gmail.com> wrote:
On Tue, Dec 11, 2018 at 12:52 AM jack(a)microfx.de <jack(a)microfx.de> wrote:
Alright! I added everything… but I have some routing problems right now so I cannot
install the osc package. Will try tomorrow.
I just tested the whole setup … and I get crackling when running jackd as mentioned above
with systemd …does it run with another priority maybe? When using my old scripts to start
jack2 everything is normal.
You might not have the right privilege to run jackd as a normal user
with SCHED_FIFO or SCHED_RR priority (I.e realtime priority).
Try to run jackd manually in the shell as a normal user and see if it
shows a warning message about this.
If you do get a warning, there's probably some info at jackaudio.org
on how to enable realtime privileges for normal users, or you can
google it. I don't remember exactly how right now. :-)
5:10 p.m.
On Tue, Dec 11, 2018 at 1:07 AM jack(a)microfx.de <jack(a)microfx.de> wrote:
But I was running jack before as user pi with my scripts and with systemd also as user pi
… ah maybe different group? I just made the Group=pi as well… is there a special group
maybe?
Yes, maybe you need to run in the "audio" group or something like that.
Check /etc/security/limits.conf. Mine looks like this:
@realtime - rtprio 99
@realtime - memlock unlimited
If it looks like this, you don't need to be a member of a special group.
5:12 p.m.
I just changed it to Group=audio …same
@audio - rtprio 99
@audio - memlock unlimited
On 11. Dec 2018, at 01:09, Kjetil Matheussen
<k.s.matheussen(a)gmail.com> wrote:
On Tue, Dec 11, 2018 at 1:07 AM jack(a)microfx.de <jack(a)microfx.de> wrote:
But I was running jack before as user pi with my scripts and with systemd also as user pi
… ah maybe different group? I just made the Group=pi as well… is there a special group
maybe?
Yes, maybe you need to run in the "audio" group or something like that.
Check /etc/security/limits.conf. Mine looks like this:
@realtime - rtprio 99
@realtime - memlock unlimited
If it looks like this, you don't need to be a member of a special group.
5:16 p.m.
it’s already set - I pasted the output of /etc/security/limits.conf
it’s as it should be
@audio - rtprio 99
@audio - memlock unlimited
On 11. Dec 2018, at 01:14, Kjetil Matheussen
<k.s.matheussen(a)gmail.com> wrote:
On Tue, Dec 11, 2018 at 1:12 AM jack(a)microfx.de <jack(a)microfx.de> wrote:
I just changed it to Group=audio …same
Maybe this helps:
* - rtprio 99
* - memlock unlimited
You might also have to reboot after changing this file, don't know.
5:17 p.m.
ah.. reboot … heh … that’s it. I just rebooted - but I forgot to systemctl daemon-reload -
thanks!
On 11. Dec 2018, at 01:14, Kjetil Matheussen
<k.s.matheussen(a)gmail.com> wrote:
On Tue, Dec 11, 2018 at 1:12 AM jack(a)microfx.de <jack(a)microfx.de> wrote:
I just changed it to Group=audio …same
Maybe this helps:
* - rtprio 99
* - memlock unlimited
You might also have to reboot after changing this file, don't know.
5:20 p.m.
Hmm… nope. Sorry for the spam. Still crackling after reboot + daemon-reload. This could
have been so easy.
On 11. Dec 2018, at 01:17, jack(a)microfx.de wrote:
ah.. reboot … heh … that’s it. I just rebooted - but I forgot to systemctl daemon-reload
- thanks!
On 11. Dec 2018, at 01:14, Kjetil Matheussen
<k.s.matheussen(a)gmail.com> wrote:
On Tue, Dec 11, 2018 at 1:12 AM jack(a)microfx.de <jack(a)microfx.de> wrote:
_______________________________________________
Jack-Devel mailing list
Jack-Devel(a)lists.jackaudio.org
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
I just changed it to Group=audio …same
Maybe this helps:
* - rtprio 99
* - memlock unlimited
You might also have to reboot after changing this file, don't know.
5:38 p.m.
Maybe you can do this in your service configuration:
ExecStart=/usr/local/bin/jackd -t 2000 -P 75 -d alsa -d hw:pisound -r
48000 -p 128 -n 2 -X seq -s > /tmp/jackd_output.txt
And then check /tmp/jackd_output.txt if there's anything wrong.
(by the way, doesn't services log to some file?)
On Tue, Dec 11, 2018 at 1:20 AM jack(a)microfx.de <jack(a)microfx.de> wrote:
Hmm… nope. Sorry for the spam. Still crackling after reboot + daemon-reload. This could
have been so easy.
On 11. Dec 2018, at 01:17, jack(a)microfx.de wrote:
ah.. reboot … heh … that’s it. I just rebooted - but I forgot to systemctl daemon-reload
- thanks!
On 11. Dec 2018, at 01:14, Kjetil Matheussen
<k.s.matheussen(a)gmail.com> wrote:
On Tue, Dec 11, 2018 at 1:12 AM jack(a)microfx.de <jack(a)microfx.de> wrote:
_______________________________________________
Jack-Devel mailing list
Jack-Devel(a)lists.jackaudio.org
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
I just changed it to Group=audio …same
Maybe this helps:
* - rtprio 99
* - memlock unlimited
You might also have to reboot after changing this file, don't know.
5:48 p.m.
somehow the file is not being created - but yes, I can see in journalctl those warnings:
Dec 11 01:47:07 MICROLABS-P1 jackd[11977]: Jack: JackAlsaDriver::Read warning fBufferSize
= 128 nframes = 256
Dec 11 01:47:10 MICROLABS-P1 jackd[11977]: Jack: JackSocketServerChannel::Execute :
fPollTable i = 1 fd = 11
Dec 11 01:47:14 MICROLABS-P1 jackd[11977]: Jack: JackAlsaDriver::Read warning fBufferSize
= 128 nframes = 256
Dec 11 01:47:20 MICROLABS-P1 jackd[11977]: Jack: JackSocketServerChannel::Execute :
fPollTable i = 1 fd = 11
On 11. Dec 2018, at 01:38, Kjetil Matheussen
<k.s.matheussen(a)gmail.com> wrote:
Maybe you can do this in your service configuration:
ExecStart=/usr/local/bin/jackd -t 2000 -P 75 -d alsa -d hw:pisound -r
48000 -p 128 -n 2 -X seq -s > /tmp/jackd_output.txt
And then check /tmp/jackd_output.txt if there's anything wrong.
(by the way, doesn't services log to some file?)
On Tue, Dec 11, 2018 at 1:20 AM jack(a)microfx.de <jack(a)microfx.de> wrote:
>
> Hmm… nope. Sorry for the spam. Still crackling after reboot + daemon-reload. This
could have been so easy.
>
>> On 11. Dec 2018, at 01:17, jack(a)microfx.de wrote:
>>
>> ah.. reboot … heh … that’s it. I just rebooted - but I forgot to systemctl
daemon-reload - thanks!
>>
>>> On 11. Dec 2018, at 01:14, Kjetil Matheussen <k.s.matheussen(a)gmail.com>
wrote:
>>>
>>> On Tue, Dec 11, 2018 at 1:12 AM jack(a)microfx.de <jack(a)microfx.de>
wrote:
>>>>
>>>> I just changed it to Group=audio …same
>>>>
>>>>
>>>
>>> Maybe this helps:
>>>
>>> * - rtprio 99
>>> * - memlock unlimited
>>>
>>> You might also have to reboot after changing this file, don't know.
>>
>> _______________________________________________
>> Jack-Devel mailing list
>> Jack-Devel(a)lists.jackaudio.org
>> http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
>
6:01 p.m.
I removed the User / Group part from the .service file and the crackling is gone. Reading
this now where it is explained:
https://github.com/jackaudio/jackaudio.github.com/wiki/Cgroups … Thank you so much for
your time and really helpful tips&tricks - learned a lot!
This is my first mailing list and I hope I am not too much of a bugger because not
following common rules I don’t know yet.
On 11. Dec 2018, at 01:48, jack(a)microfx.de wrote:
somehow the file is not being created - but yes, I can see in journalctl those warnings:
Dec 11 01:47:07 MICROLABS-P1 jackd[11977]: Jack: JackAlsaDriver::Read warning fBufferSize
= 128 nframes = 256
Dec 11 01:47:10 MICROLABS-P1 jackd[11977]: Jack: JackSocketServerChannel::Execute :
fPollTable i = 1 fd = 11
Dec 11 01:47:14 MICROLABS-P1 jackd[11977]: Jack: JackAlsaDriver::Read warning fBufferSize
= 128 nframes = 256
Dec 11 01:47:20 MICROLABS-P1 jackd[11977]: Jack: JackSocketServerChannel::Execute :
fPollTable i = 1 fd = 11
On 11. Dec 2018, at 01:38, Kjetil Matheussen
<k.s.matheussen(a)gmail.com> wrote:
Maybe you can do this in your service configuration:
ExecStart=/usr/local/bin/jackd -t 2000 -P 75 -d alsa -d hw:pisound -r
48000 -p 128 -n 2 -X seq -s > /tmp/jackd_output.txt
And then check /tmp/jackd_output.txt if there's anything wrong.
(by the way, doesn't services log to some file?)
On Tue, Dec 11, 2018 at 1:20 AM jack(a)microfx.de <jack(a)microfx.de> wrote:
>
> Hmm… nope. Sorry for the spam. Still crackling after reboot + daemon-reload. This
could have been so easy.
>
>> On 11. Dec 2018, at 01:17, jack(a)microfx.de wrote:
>>
>> ah.. reboot … heh … that’s it. I just rebooted - but I forgot to systemctl
daemon-reload - thanks!
>>
>>> On 11. Dec 2018, at 01:14, Kjetil Matheussen <k.s.matheussen(a)gmail.com>
wrote:
>>>
>>> On Tue, Dec 11, 2018 at 1:12 AM jack(a)microfx.de <jack(a)microfx.de>
wrote:
>>>>
>>>> I just changed it to Group=audio …same
>>>>
>>>>
>>>
>>> Maybe this helps:
>>>
>>> * - rtprio 99
>>> * - memlock unlimited
>>>
>>> You might also have to reboot after changing this file, don't know.
>>
>> _______________________________________________
>> Jack-Devel mailing list
>> Jack-Devel(a)lists.jackaudio.org
>> http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
>
_______________________________________________
Jack-Devel mailing list
Jack-Devel(a)lists.jackaudio.org
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
11 Dec
11 Dec
4:27 a.m.
It seems like I made a loop with little success but I couldn’t get rid of the crackling.
So I reverted everything so I get clean sound. But I am still stuck at launching
jack_capture - even as root.
sudo jack_capture --daemon -c 5 -mb -tm -f flac
Cannot read socket fd = 5 err = Success
CheckRes error
JackSocketClientChannel read fail
Cannot open jack_capture 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
Any further ideas what I could inspect / try?
On 11. Dec 2018, at 02:01, jack(a)microfx.de wrote:
I removed the User / Group part from the .service file and the crackling is gone. Reading
this now where it is explained:
https://github.com/jackaudio/jackaudio.github.com/wiki/Cgroups … Thank you so much for
your time and really helpful tips&tricks - learned a lot!
This is my first mailing list and I hope I am not too much of a bugger because not
following common rules I don’t know yet.
On 11. Dec 2018, at 01:48, jack(a)microfx.de wrote:
somehow the file is not being created - but yes, I can see in journalctl those warnings:
Dec 11 01:47:07 MICROLABS-P1 jackd[11977]: Jack: JackAlsaDriver::Read warning fBufferSize
= 128 nframes = 256
Dec 11 01:47:10 MICROLABS-P1 jackd[11977]: Jack: JackSocketServerChannel::Execute :
fPollTable i = 1 fd = 11
Dec 11 01:47:14 MICROLABS-P1 jackd[11977]: Jack: JackAlsaDriver::Read warning fBufferSize
= 128 nframes = 256
Dec 11 01:47:20 MICROLABS-P1 jackd[11977]: Jack: JackSocketServerChannel::Execute :
fPollTable i = 1 fd = 11
_______________________________________________
Jack-Devel mailing list
Jack-Devel(a)lists.jackaudio.org
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org On 11. Dec 2018, at 01:38, Kjetil Matheussen
<k.s.matheussen(a)gmail.com> wrote:
Maybe you can do this in your service configuration:
ExecStart=/usr/local/bin/jackd -t 2000 -P 75 -d alsa -d hw:pisound -r
48000 -p 128 -n 2 -X seq -s > /tmp/jackd_output.txt
And then check /tmp/jackd_output.txt if there's anything wrong.
(by the way, doesn't services log to some file?)
On Tue, Dec 11, 2018 at 1:20 AM jack(a)microfx.de <jack(a)microfx.de> wrote:
>
> Hmm… nope. Sorry for the spam. Still crackling after reboot + daemon-reload. This
could have been so easy.
>
>> On 11. Dec 2018, at 01:17, jack(a)microfx.de wrote:
>>
>> ah.. reboot … heh … that’s it. I just rebooted - but I forgot to systemctl
daemon-reload - thanks!
>>
>>> On 11. Dec 2018, at 01:14, Kjetil Matheussen <k.s.matheussen(a)gmail.com>
wrote:
>>>
>>> On Tue, Dec 11, 2018 at 1:12 AM jack(a)microfx.de <jack(a)microfx.de>
wrote:
>>>>
>>>> I just changed it to Group=audio …same
>>>>
>>>>
>>>
>>> Maybe this helps:
>>>
>>> * - rtprio 99
>>> * - memlock unlimited
>>>
>>> You might also have to reboot after changing this file, don't know.
>>
>> _______________________________________________
>> Jack-Devel mailing list
>> Jack-Devel(a)lists.jackaudio.org
>> http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
>
_______________________________________________
Jack-Devel mailing list
Jack-Devel(a)lists.jackaudio.org
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
6:48 a.m.
I made some changes and get different behaviour now! I read somewhere to user instead of
Group the SupplementaryGroups=audio. Now with user pi and that SupplementaryGroups
jack_capture starts when running it manually from /usr/local/bin
On 11. Dec 2018, at 12:27, jack(a)microfx.de wrote:
It seems like I made a loop with little success but I couldn’t get rid of the crackling.
So I reverted everything so I get clean sound. But I am still stuck at launching
jack_capture - even as root.
sudo jack_capture --daemon -c 5 -mb -tm -f flac
Cannot read socket fd = 5 err = Success
CheckRes error
JackSocketClientChannel read fail
Cannot open jack_capture 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
Any further ideas what I could inspect / try?
On 11. Dec 2018, at 02:01, jack(a)microfx.de wrote:
I removed the User / Group part from the .service file and the crackling is gone. Reading
this now where it is explained:
https://github.com/jackaudio/jackaudio.github.com/wiki/Cgroups … Thank you so much for
your time and really helpful tips&tricks - learned a lot!
This is my first mailing list and I hope I am not too much of a bugger because not
following common rules I don’t know yet.
_______________________________________________
Jack-Devel mailing list
Jack-Devel(a)lists.jackaudio.org
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org On 11. Dec 2018, at 01:48, jack(a)microfx.de wrote:
somehow the file is not being created - but yes, I can see in journalctl those warnings:
Dec 11 01:47:07 MICROLABS-P1 jackd[11977]: Jack: JackAlsaDriver::Read warning fBufferSize
= 128 nframes = 256
Dec 11 01:47:10 MICROLABS-P1 jackd[11977]: Jack: JackSocketServerChannel::Execute :
fPollTable i = 1 fd = 11
Dec 11 01:47:14 MICROLABS-P1 jackd[11977]: Jack: JackAlsaDriver::Read warning fBufferSize
= 128 nframes = 256
Dec 11 01:47:20 MICROLABS-P1 jackd[11977]: Jack: JackSocketServerChannel::Execute :
fPollTable i = 1 fd = 11
_______________________________________________
Jack-Devel mailing list
Jack-Devel(a)lists.jackaudio.org
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org On 11. Dec 2018, at 01:38, Kjetil Matheussen
<k.s.matheussen(a)gmail.com> wrote:
Maybe you can do this in your service configuration:
ExecStart=/usr/local/bin/jackd -t 2000 -P 75 -d alsa -d hw:pisound -r
48000 -p 128 -n 2 -X seq -s > /tmp/jackd_output.txt
And then check /tmp/jackd_output.txt if there's anything wrong.
(by the way, doesn't services log to some file?)
On Tue, Dec 11, 2018 at 1:20 AM jack(a)microfx.de <jack(a)microfx.de> wrote:
>
> Hmm… nope. Sorry for the spam. Still crackling after reboot + daemon-reload. This
could have been so easy.
>
>> On 11. Dec 2018, at 01:17, jack(a)microfx.de wrote:
>>
>> ah.. reboot … heh … that’s it. I just rebooted - but I forgot to systemctl
daemon-reload - thanks!
>>
>>> On 11. Dec 2018, at 01:14, Kjetil Matheussen <k.s.matheussen(a)gmail.com>
wrote:
>>>
>>> On Tue, Dec 11, 2018 at 1:12 AM jack(a)microfx.de <jack(a)microfx.de>
wrote:
>>>>
>>>> I just changed it to Group=audio …same
>>>>
>>>>
>>>
>>> Maybe this helps:
>>>
>>> * - rtprio 99
>>> * - memlock unlimited
>>>
>>> You might also have to reboot after changing this file, don't know.
>>
>> _______________________________________________
>> Jack-Devel mailing list
>> Jack-Devel(a)lists.jackaudio.org
>> http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
>
_______________________________________________
Jack-Devel mailing list
Jack-Devel(a)lists.jackaudio.org
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
7:15 a.m.
Okay folks. I made it. Thank you sooo much. I have now everything as service and can start
/ stop it with a shell script. Really good mailing list!
On 11. Dec 2018, at 12:27, jack(a)microfx.de wrote:
It seems like I made a loop with little success but I couldn’t get rid of the crackling.
So I reverted everything so I get clean sound. But I am still stuck at launching
jack_capture - even as root.
sudo jack_capture --daemon -c 5 -mb -tm -f flac
Cannot read socket fd = 5 err = Success
CheckRes error
JackSocketClientChannel read fail
Cannot open jack_capture 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
Any further ideas what I could inspect / try?
On 11. Dec 2018, at 02:01, jack(a)microfx.de wrote:
I removed the User / Group part from the .service file and the crackling is gone. Reading
this now where it is explained:
https://github.com/jackaudio/jackaudio.github.com/wiki/Cgroups … Thank you so much for
your time and really helpful tips&tricks - learned a lot!
This is my first mailing list and I hope I am not too much of a bugger because not
following common rules I don’t know yet.
_______________________________________________
Jack-Devel mailing list
Jack-Devel(a)lists.jackaudio.org
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org On 11. Dec 2018, at 01:48, jack(a)microfx.de wrote:
somehow the file is not being created - but yes, I can see in journalctl those warnings:
Dec 11 01:47:07 MICROLABS-P1 jackd[11977]: Jack: JackAlsaDriver::Read warning fBufferSize
= 128 nframes = 256
Dec 11 01:47:10 MICROLABS-P1 jackd[11977]: Jack: JackSocketServerChannel::Execute :
fPollTable i = 1 fd = 11
Dec 11 01:47:14 MICROLABS-P1 jackd[11977]: Jack: JackAlsaDriver::Read warning fBufferSize
= 128 nframes = 256
Dec 11 01:47:20 MICROLABS-P1 jackd[11977]: Jack: JackSocketServerChannel::Execute :
fPollTable i = 1 fd = 11
_______________________________________________
Jack-Devel mailing list
Jack-Devel(a)lists.jackaudio.org
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org On 11. Dec 2018, at 01:38, Kjetil Matheussen
<k.s.matheussen(a)gmail.com> wrote:
Maybe you can do this in your service configuration:
ExecStart=/usr/local/bin/jackd -t 2000 -P 75 -d alsa -d hw:pisound -r
48000 -p 128 -n 2 -X seq -s > /tmp/jackd_output.txt
And then check /tmp/jackd_output.txt if there's anything wrong.
(by the way, doesn't services log to some file?)
On Tue, Dec 11, 2018 at 1:20 AM jack(a)microfx.de <jack(a)microfx.de> wrote:
>
> Hmm… nope. Sorry for the spam. Still crackling after reboot + daemon-reload. This
could have been so easy.
>
>> On 11. Dec 2018, at 01:17, jack(a)microfx.de wrote:
>>
>> ah.. reboot … heh … that’s it. I just rebooted - but I forgot to systemctl
daemon-reload - thanks!
>>
>>> On 11. Dec 2018, at 01:14, Kjetil Matheussen <k.s.matheussen(a)gmail.com>
wrote:
>>>
>>> On Tue, Dec 11, 2018 at 1:12 AM jack(a)microfx.de <jack(a)microfx.de>
wrote:
>>>>
>>>> I just changed it to Group=audio …same
>>>>
>>>>
>>>
>>> Maybe this helps:
>>>
>>> * - rtprio 99
>>> * - memlock unlimited
>>>
>>> You might also have to reboot after changing this file, don't know.
>>
>> _______________________________________________
>> Jack-Devel mailing list
>> Jack-Devel(a)lists.jackaudio.org
>> http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
>
_______________________________________________
Jack-Devel mailing list
Jack-Devel(a)lists.jackaudio.org
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
10 Dec
10 Dec
5:12 p.m.
On Tue, Dec 11, 2018 at 1:09 AM Kjetil Matheussen
<k.s.matheussen(a)gmail.com> wrote:
@realtime - rtprio 99
@realtime - memlock unlimited
If it looks like this, you don't need to be a member of a special group.
Ouch, no, you need to be a member of the realtime group.
See here: http://jackaudio.org/faq/linux_rt_config.html
5:27 p.m.
ah, … the problem wasn’t osc not being installed. The error is: "osc not supported.
liblo was not installed when compiling jack_capture” guess I have to check how that is
working then.
On 10. Dec 2018, at 23:27, Kjetil Matheussen
<k.s.matheussen(a)gmail.com> wrote:
On Mon, Dec 10, 2018 at 11:18 PM jack(a)microfx.de <jack(a)microfx.de> wrote:
Ah, that seems to be the problem! Thanks for the quick reply!
My initial idea was to add this as well as a service but jack_capture needs user input -
is this possible with a service? Like an additional script that triggers the recording?
How about letting jack_capture listen to OSC?
jack_capture --help-osc
Then you can run jack_capture as root like this:
jack_capture --osc 7777 --filename-prefix
/recording/directory/jack_capture_recording_
And as a normal user you can run
oscsend localhost 7777 /jack_capture/tm/start
oscsend localhost 7777 /jack_capture/tm/stop
to start and stop recording.
Robin Gareus might help more on this, since he wrote that code.
I'm not entirely sure if this is the best way to use the OSC interface.
2342
days inactive
2343
days old
jackaudio@lists.linuxaudio.org
27 comments
3 participants
participants (3)
-
Chris Caudle -
jack＠microfx.de -
Kjetil Matheussen