Hi there,
before I go and open a ticket in Jack 2's Github issue tracker,
requesting a new release, I thought I'd ask whether this is already in
the making and ready in the short term?
IMHO the metadata support should be made available to Jack 2 users as
soon as possible, so developers can rely on it being available with a
broader user base.
Also, the latest release is now almost 1 1/2 years old.
Cheers, Chris
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
Hi,
I'm writing an MacOSX app that is able to capture audio from speaker and save the audio file to disk in wav or whatever format for further replay.
I googled a lot and found out that Jack might help me to do this kind of thing.
Is there any tutorials for this? Should I download JackOSX? I have cloned jack2 source code and successfully build example-clients/capture_client.c .
Could you give me some guide?
Thank you very much
I am using a Python API
(https://github.com/spatialaudio/jackclient-python) to instantiate JACK
clients in independent Python processes. With reasonable audio block
lengths (256 to 4096) it works very well to do pretty demanding
real-time signal processing tasks (just FYI and to understand the context).
The API allows me to detect occurring xruns with a reported signal
delay, coming from the JACK library. Sometimes xruns occur and the
reported delay is 0ms, while the audio stream clearly experiences a
dropout. I've also seen higher delays reported, but right now I cannot
tell under what conditions.
I just wonder how the delay times are gathered, how reliable or
conclusive they are in general and what an xrun "without delay" might mean?!
Hello, having trouble with the latency API.
I start Jack with this (the 6 periods are just for testing):
jackd -P30 -dalsa -r44100 -p512 -n6 -Xseq -D -Chw:M1010LT,0 -Phw:M1010LT,0
One Jack audio input port, one Jack audio output port,
one Jack midi input port, and one Jack midi output port
have been registered and connected to audio hardware ports
and midi hardware port respectively. All is functioning.
The ports were created with these calls:
jack_port_register(_client, name1, JACK_DEFAULT_AUDIO_TYPE,
JackPortIsInput, 0);
jack_port_register(_client, name2, JACK_DEFAULT_AUDIO_TYPE,
JackPortIsOutput, 0);
jack_port_register(_client, name3, JACK_DEFAULT_MIDI_TYPE,
JackPortIsInput, 0);
jack_port_register(_client, name4, JACK_DEFAULT_MIDI_TYPE,
JackPortIsOutput, 0);
So far so good. But when I ask for the latency of the
ports, the Jack midi ports are always reporting zero:
Jack audio client capture port:
Capture range: min 512 max 512
Playback range: min 0 max 3072
Jack audio client playback port:
Capture range: min 0 max 512
Playback range: min 3072 max 3072
Jack midi client capture port:
Capture range: min 0 max 0
Playback range: min 0 max 3072
Jack midi client playback port:
Capture range: min 0 max 512
Playback range: min 0 max 0
What could be wrong here?
Thanks.
Tim.
Hey!
I have a hard time setting up a tmux session started with systemd on
raspbian (patchbox OS, realtime kernel) to behaves like as if I started
my script manually.
This is my Jack Capture service:
[Unit]
Description=Jack Capture autostart daemon
Wants=jack.service
After=multi-user.target
[Service]
Type=forking
EnvironmentFile=/etc/environment
User=patch
Group=realtime
ExecStart=/home/patch/jack-capture-tmux.sh
[Install]
WantedBy=jack.service
and this my script to start tmux with jack capture:
#!/bin/bash
. /etc/environment
/usr/bin/jack_wait -w
tmux new-session -d -s jackd
tmux new-window -t jackd -n Jack Capture -d
sleep 1
tmux send-keys -t jackd:0 'cd ~/' C-m
tmux send-keys -t jackd:0 'clear' C-m
tmux send-keys -t jackd:0 'jack_capture -c 2 -mb -tm -f wav
--filename-prefix ABC-TEST- --hook-close ./hookstop.sh --hook-timing
./hookstart.sh' C-m
everything a bloated from all my tries to make this work...
Now it starts properly but if I look into that tmux session I get
warnings/errors:
jack_capture -c 2 -mb -tm -f wav --filename-prefix ABC-TEST-
--hook-close ./hookstop.sh --hook-timing ./hookstart.sh
Cannot lock down 82287136 byte memory area (Cannot allocate memory)
>>> Warning. Could not set higher priority for a SCHED_OTHER process
>>> using setpriority().
Cannot use real-time scheduling (RR/70)(1: Operation not permitted)
JackClient::AcquireSelfRealTime error
>>> Waiting to start recording of "ABC-TEST-10.wav"
>>> Press <Ctrl-C> to stop recording and quit.
I had this solved when starting the script manually by adding * - nice
-20 into /etc/security/limits.conf - but this obviously is not working
when starting the script within systemd (although same user).
Any ideas?
Cheers
Jan
Hi list,
(Sorry this question has already been discussed but the search function in the archive of the list does not work)
Is anyone working on the problem of getting Jack up and running on MacOS again? I installed Jack with brew but I get these “could not handle external client request” errors which seems to be old problems from looking at search results and GitHub discussions - problems introduced when MacOS audio architecture was changed a while back. Is there any progress on these matters? Is someone working on it? I need Jack as it is a dependency to another library I would like to use but I realize that I might have to abandon MacOS as a platform in the process.
Kindest regards,
Stefan
Hi,
I've been reading the code of Ableon's LinkHut's jack backend.
https://github.com/Ableton/link/blob/master/examples/linkaudio/AudioPlatfor…https://github.com/Ableton/link/blob/master/examples/linkaudio/AudioPlatfor…
And I was quite surprised because I did not find any latency compensation there.
So for real-time beat time synchronization this is quite important right?
BTW, if any jack expert finds the time and motivation to fix the jack
back-end of Link's example that would be awesome and a great example.
Then I've read the documentation:
http://jackaudio.org/api/group__LatencyFunctions.html
And I am totally confused.
Why a latency range? What is the use case for it?
How is the application supposed to work with multiple inputs and
outputs having each a different latency range?
What's the point of a latency range? If you're concerned about the
shortest path and the longest path, why wouldn't you be concerned
about any path in between?
How to know at which time on a given a clock (CLOCK_REALTIME or
CLOCK_MONOTONIC) a sample in the current process block will be played
on the sound card's output?
I've tried with qjackctl to set the periods/buffer to 12 with 2048
samples per buffer at 44100 Hz which is about half a second of
latency. Do you manage to get the correct latency reported with those
settings? See https://imgur.com/w45wsp8
Jack allows feedback routing, how do you deal with latency with such a graph?
I've been testing with Jack 1.9.12-8 on Archlinux and QJackCtl 0.5.6-1
Many thanks for your answer and your time,
Alexandre Bique
Folks,
I've been lurking here since the early 2000's, since the stuttering
beginning of jack (jaaa was it called then ?), and I'm amazed of the
ugly arrogance we recieve these days. "I have not contributed any kind
of idea or code, by still I know better". This pisses me off and get me
depressed. Jack, for one, is a piece of software I'm amazed about. I've
learned more reading this list than in any other so-called software
course.
Please show humility where it is due, ask questions and offer inisight
anytime, but keep your selfish, narrow minded view for yourself until
you can provide any educated opinion.
Thanks for reading. To all the jack devs, you have my thankful respect.
-- D.
