After the user hits Ctrl-C on the client, jackd keeps playing some sound
it got from this client. Only jackd restart helps.
Why doesn't the server clear the buffer when client disconnects? What
part of code is responsible for cleaning up after a disconnected client?
Problem is observed on the FreeBSD 11.1 with jack-0.125.0
Yuri
Cheers everyone,
As part of my testing of, and indeed as (an intended) part of the
software I'm writing, I'm starting and stopping many jackd instances on
the box in question (a Pi).
Today, to my surprise, I seem to have hit upon some kind of limit, for
attempts to launch a server (via the command-line) fail with the message
"Too many servers already active". I haven't kept count, but I might
have successfully started and stopped a couple dozen instances of JACK
before that happened (only ever one at a time, though).
Now, the point is, there definitely *aren't* any jackd processes running
at the time I'm executing that command. So I'm wondering whether there's
perhaps some environment setting that JACK checks? Or something?
Note that a restart of the system fixes the issue. That wouldn't be an
acceptable long-term solution, however.
For what it's worth, I'm running JACK on a headless environment, and am
setting DISPLAY=:0 to work around the DBUS issues.
Ideas, suggestions, etc. much welcome.
M.
Hi guys,
First of all, sorry for my bad English.
So here's my question:
Im a DJ playing traktor (64 bit) and I want to use Ableton (64bit) effects.
In order to do so I need to route my traktor audio in Ableton.
I use a Native Instruments Audio 10 interface.
Is there a solution with Jackrouter for 64-bit?
And how to do so?
Greets,
--
Vintsent Bekaert
I need to combine two HDSPe MADI FX cards to one virtual device. I have a
working driver, which is alsa-compatible. I can select each single card in
any alsa-compatible application and all channels work flawless.
For combining the MADI FX cards to one virtual device, I created an
.asoundrc with 194 inputs for each card. When I start that virtual device
via
jackd -R -d alsa -C madifx_record_all -P madifx_playback_all
I get this error:
> creating alsa driver ...
>
madifx_playback_all|madifx_record_all|1024|2|48000|0|0|nomon|swmeter|-|32bit
> jackd: pcm_multi.c:1060: snd_pcm_multi_open: Assertion
`!slave_map[sidxs[i]][schannels[i]]' failed.
However, it works when I reduce the amount from 194 to 64 channels per
card. I tried to use 128 channels per card, but that fails the same way.
See my alsa-info attached, which also includes the .asoundrc content.
I also found this, which might be related:
https://ccrma.stanford.edu/mirrors/lalists/lad/2005/06/0202.html
To me, this looks like a bug. What do you think?
I am getting this error "Jack Error: zombified - calling shutdown
handler" with default timeout of 500ms. Increasing timeout to 4000ms
helps, but it isn't clear why 500ms isn't sufficient.
Jack thread only connects with the actual client code through the
process() callback. I timed process(), it never takes longer than 5ms.
Given that the system has very low CPU load, why does the process become
zombified? And why other apps, like Ardour, don't suffer from this?
Client: newly written Jack backend for qTox.
jack-0.125.0 on FreeBSD 11.
Yuri
jack_set_buffer_size limits frame size to the powers of 2.
The Opus codec (http://opus-codec.org/) doesn't like such frame sizes.
It defines frame sizes in milliseconds, and allows 5 ms, 10 ms, 20 ms,
25 ms, ... which in case of 48,000 sample rate are never a power of two.
It seems like Jack shouldn't be so strict in limiting frame rates to the
powers of 2.
How to solve this problem?
Yuri
On Thu, July 20, 2017 5:35 am, Yuri wrote:
> The fact that any DBus-linked program requires X indicates some
> problem. This should never happen.
It did not require X, just that the DISPLAY environment variable be set.
Explained later by Rowan.
--
Chris Caudle
I'm trying to run a script in my Odroid-U3 which launches Jack and Pd,
but Jack doesn't start.
This is my script, called 'launch_jack_pd.sh':
#!/bin/bash
jackd -dalsa -dhw:1 -i2 -o4 -p512 -r48000 &
pd -jack -inchannels 2 -outchannels 4 -nogui -open
I've tried launching it with cron (user's odroid cron, not root), by
appending the following line at the end:
@reboot sleep 30 ; sh /home/odroid/scripts/launch_jack_pd.sh
I've also tried launching it with rc.local, by placing the following
line before 'exit 0':
sudo -c '/home/odroid/scripts/launch_jack_pd.sh' - odroid &
None of them seem to work. Pd runs, but Jack doesn't. The script is
callable manually and works as expected. The Odroid runs lubunty 14.04.2
LTS, and Jack is jackdmp 1.9.10
Any tips?
The recommended download site http://jackaudio.org/downloads/ suffers
from these problems:
* It is http:// making it vulnerable to MITM attacks.
* It doesn't provide tarball fingerprints (md5 or sha256)
I recommend you discontinue it, and just use GitHub instead. A lot of
projects do this successfully. GitHub is already usable this way.
Yuri
