Hi all,
I'm putting together an inprocess client (as it was the lowest hanging fruit), but I'd like to output log messages, I note that outputting to stdout/stderr doesn't seem to work.
Is there any API into which I can hook my logging framework output ?
Regards
/Robert
On Wed, January 31, 2018 9:03 am, Robert Bielik wrote:
> Ok ð although this is jack2 built *without* dbus and running on a
> headless RPi3.
How does the rc.local start jackd under the user account? Maybe it could
start a screen session at that point, and when you ssh in you can connect
to the screen session. If you are not familiar with screen it is an
application that (among other features) will let you disconnect an ssh
session while the underlying terminal session continues to run (usually
breaking the ssh session will kill the terminal session associated with
that login). When you connect again with ssh you start screen with the -r
argument to restore connection to the already running screen session
rather than starting a new session.
--
Chris Caudle
On Wed, January 31, 2018 9:30 am, Robert Bielik wrote:
> As shown here (I wrote that msg in the forum):
"You have been notified about this topic, please login to view it."
I don't really feel like going through the effort of creating a new
account on some web site I've never heard of to fix your problem. If you
would like help on this mailing list then I recommend you send relevant
information to this mailing list.
> The files in /dev/shm aren't supposed to vanish during
> lifetime of jackd process, right ?
Not typically.
I found this in common/JackShmMem.cpp:
jack_log("JackShmMem::delete size = %ld index = %ld", size, info.index);
So it seems like at least some shared memory operations get logged.
Maybe try -v for verbose logging.
--
Chris Caudle
Hi all,
New to JACK wrt actual usage, I'm having a project which I want to setup as follows:
1. JACK in (hw:0,0) -> "JACK mixer"
(This one should be as low a latency as possible, preferably 48 frames @48 Khz, i.e. 1ms buffer size)
2. Any-app-using-ALSA -> ALSA JACK plugin -> JACK "mixer"
3. JACK "mixer" -> JACK DSP plugin -> JACK out (hw:0,0)
This will, in this particular case, run on a RPi3. Design goals are: One low latency route between input and output on a I2S sound card (1. above) and the rest of the applications using ALSA should share a higher latency route. The output of the JACK "mixer" should pass a JACK plugin before reaching hw:0,0.
Before I get my hands too dirty I'd just like to ask if this architecture is feasible to do ?
Regards
/Robert
Am Mittwoch, 31. Januar 2018 16:03 CET, Robert Bielik <Robert.Bielik(a)dirac.com> schrieb:
> > >> Socket is associated with the desktop session?
> > >
> > > Ah, seems like a very reasonable explanation. Although I'm not nearly
> > > linux-savvy enough to "fix" this, so I'd appreciate pointers ��
> >
> > I'm just regurgitating buzzwords connected to "dbus". Maybe they help
> > trigger the memory of someone who actually has a clue.
>
> Ok �� although this is jack2 built *without* dbus and running on a headless RPi3.
Yes, D-Bus is only one part of Linux session handling. Both systemd (most likely your init system) and PAM
will do some magic. To find out where your jack client expexts jackd's socket run:
$ strace -e connect,open jack_lsp -c > /dev/null
Cheers, RalfD
> Yes, I managed to get it working with that guide, however now I have
> intermittent problems when rebooting, I think it is due to the LD cache,
> sometimes .so files in /usr/local/lib are not found.
In these cases, when it doesn't work I get:
Could not open driver directory /usr/lib/arm-linux-gnueabihf/jack: No such file or directory
Could not find any drivers in driver directory!
Failed to create server object
So I do:
sudo ldconfig /usr/local/lib/
and voila, it works again. As you probably can tell, Linux is not my forte...
Regards
/R
Hi,
when looking at jack_evmon output, it tells numeric port ids when a new
port is registered, unregistered or connected.
I wondered if there is an API method to get the same number from a
jack_port_t or port name string.
Best regards
Thomas
On Mon, January 15, 2018 10:13 am, Benny Alexandar wrote:
> I want both PC and USB sound card ports to be accessed at the same time.
The design of jackd (really any sound server) requires it to be
synchronized to the sampling clock of the interface, and since your two
interfaces are not synchronized to each other then jackd cannot use both
at the same time without some intervention.
Using two at the same time requires choosing one card to the be the main
backend device, then loading a sample rate converter to make the sample
stream rate to and from the secondary card(s) match exactly that of the
main card.
The packages you want are zita-alsa2jack and zita-jack2alsa, in Fedora
both come together in a package named zita-ajbridge.
This is covered in the jack FAQ, which needs to be updated, the section
describing alsa_in and alsa_out bridges is the relevant section, but those
older implementations had some problems, the zita bridges are higher
quality replacements.
http://jackaudio.org/faq/multiple_devices.html
The zita tools are included in the audio aware distributions, if you are
using a distribution which does not package them for some reason you can
get them along with the other zita applications here:
https://kokkinizita.linuxaudio.org/linuxaudio/
The jackd v1 implementation includes the equivalent of the zita bridges
internally, they need to be enabled from the command line but not loaded
as an external component. The jackd v2 implementation (I think you said
you were using jackd 1.9.12, that is considered jackd v2) does not yet
include the zita bridges as part of the server, you will need to load them
externally.
--
Chris Caudle
On Sun, January 28, 2018 9:34 am, Benny Alexandar wrote:
> After starting jack server using qjackctl
What jack settings were used in qjackctl? Which driver was chosen, and
which interface?
> Then in qjackctl connected the graph as shown in the attached picture.
That graph works if j2a is controlling the sound card, if jack was started
with the ALSA driver and the USB device as the interface then jackd would
already be controlling the sound card.
When providing information it will save a lot of time if you actually copy
and past the command line you used as well as the resulting messages. For
example you stated that you started zita-a2j, did you start zita-j2a with
the same command line parameters as zita-a2j? What status messages were
printed at that time? What was in the messages window of qjackctl (that
is where the output from the jackd server is displayed)?
You have given about a fourth of the information needed to help you
determine what is happening on your system.
--
Chris Caudle
Hello,
Hello,
I tried to configure Jack control (Jack_v1.9.11_64_setup.exe) to bind Traktor to Ableton but the solution did not suit me, I uninstalled Jack Audio control and since then I can not launch the TRAKTOR 64-bit application .
I can still launch TRAKTOR in 32 but the uninstall has removed something that blocks the software.
Thank you for your help.
Vincent
Bonjour,
J'ai essayé de configurer Jack control (Jack_v1.9.11_64_setup.exe) pour lier Traktor vers Ableton mais la solution ne me convenant pas, j'ai désinstallé Jack Audio control et depuis je ne peux plus lancer l'appli TRAKTOR en 64 bits.
Je peux encore lancer TRAKTOR en 32 mais la désinstallation à enlevé qelque chose qui bloque le logiciel.
Merci de votre aide.
Vincent