JackAudio March 2019

jackaudio@lists.linuxaudio.org

33 participants
15 discussions

Re: [Jack-Devel] Uninstalled Pulseaudio Jack/jackd2 Jack Reinstalled still wont start.

by liebrecht＠grossmann-venter.com

On 2019-03-26 09:44, Jörn Nettingsmeier wrote: > On 3/26/19 5:28 AM, liebrecht(a)grossmann-venter.com wrote: >> After jack is installed, I try to start it through mixbus which is >> about the only application I found that can actually start jack. I >> used mixbus for about 6 months with jack on another distro. qjacktcl >> does nothing but parse irrelevance and promisses so I dont use it >> anymore. > > That remark is bullshit and shows that you really need to change the > way you're thinking about problem solving. > Sorry I disagree, qjcakctl has given me nothing but trouble and still does. It goes much better without it. All it arguably does is to formulate a jack string....which the user should do on command line anyway, and then output mystery log errors which are substandard to reading the logs yourself. I have never found any constructive use for it other than "feelgood". Mixbus worked great once I removed qjackctl on my previous system. qjackctl was single most annoying interference problem. > Simplify the problem. > First, look at aplay -L to see if hw:VSL,0 is alive and well. As I reported already in another post it is recognised. > Now, start jack on the command line, starting with the paramters > mixbux helpfully suggests: > > jackd -t 200 -p 2048 -R -T -d alsa -n 2 -r 48000 -p 128 -d hw:VSL,0 > > It should fail in the same way you described above. If not, there is > something fishy in the way mixbus starts jackd. > As already reported, mixbus starts jack and jack runs IFF I dont start jack with qjackctl. Once qjackctl started jack, mixbus wont work. Mixbus starts jack with a string they disclose in the terminal output and it works. According to patchage as I reported in a previous post, mixxbus is connected to jack, but I get no signals from jack for the 1818vsl inputs in mixbus. > -n2 p128 looks like a pretty aggressive timing for a multichannel > interface. Try -n3 for a start, and -p1024, then gradually lower the > latency, but only if you really need it. I know I am just trying my documented default settings that worked perfectly before.

6 years

Re: [Jack-Devel] Jack Problems

by Chris Caudle

On Fri, March 22, 2019 5:30 pm, liebrecht(a)grossmann-venter.com wrote: > Who are the experts that will be using Jack. If you search through the linux audio users mail list archives you will find plenty of posts with help for new users of jack. But as you say: > [doesn't] deserve any criticism other than usability for newcombers That is a valid complaint. The problem is somewhat difficult to solve, partly because the problem being solved is complicated, partly because on most linux distributions the default audio configuration is set for playing back audio, not producing audio. > By large 95% of users complain about jack. Do you know why those users are using jack? Ardour has supported using ALSA directly for quite a while, I believe Qtractor and LMMS do as well. Do those users need the ability to route between applications which jack provides? > If I can find some of these experts it will go a long way to figure out > how to actually use it in reality. But I found none on the 10s of > usergroups related to audio that I subscribe to. 10's of usergroups? Did you start with linux-audio-users? That is the primary location for audio on linux information. > about jack. I myself have been using Linux since 97 and did a lot of > unix and assembler programming before 97. I am actually a little surprised to find you have been using linux for so long, there was a lot of basic information missing in your original email which I would expect an experienced user to provide out of habit. For example, your first email did not specify - which operating system you were using (jackd runs on 3). - later you indicated linux; which distribution? Which version? - which version of jackd and pulseaudio? You provided partial information from qjackctl: qjackctl reports the following. Cannot connect to server socket err = No such file or directory ... But did not provide the full output of the "Messages" window of qjackctl. For example, when qjackctl attempts to start jackd you should see the full command line which is used: 19:22:09.341 JACK is starting... 19:22:09.341 /usr/bin/jackd -P70 -t2000 -dalsa -dhw:Lambda -r48000 -p1024 -n3 -zt -I376 -O376 The output of jackd follows from there. "Cannot connect to server" type messages are common as jackd initially starts. You can also copy that command line and start jackd from a terminal so that you can see the startup messages being printed in real time. > I am hesitant to use jack as it almost never work consistently, > pulseaudio at least works. That is probably part of the problem. The way that pulseaudio ensures it works is starting early and locking exclusive access of the primary ALSA device. Recent versions give up control gracefully, for many years now on Fedora I have had no problems at all starting jackd with either qjackctl or from the command line, the version of pulseaudio shipped by fedora gives up control of the audio device when jackd requests, and when I stop jackd then pulseaudio takes control again. Knowing which distribution you use may make it easier for someone to help. Ubuntu typically breaks audio production software frequently, but there are optional repositories to help with that. > it is difficult for me to > understand jack as it has no consistent specification I am not sure I understand this complaint. Do you have an example of something in the man page or help output you find inconsistent? The different backends available and the way that there are arguments to the main jack server and separate arguments for the backend driver can be confusing. Is that what you are referring to? > what is the exact mechanism by which pulse > interfere with jack The pulseaudio server will open an ALSA device for exclusive access, but jackd also needs to open the ALSA device for exclusive access. Obviously only one server at a time can have exclusive access to a particular driver. Most modern versions of pulseaudio that I am familiar with using on Fedora Linux do not have that problem, but as you gave no indication of which linux distribution, which pulseaudio version, or which jackd version you are using it is difficult to say more than "works for me." jack-audio-connection-kit-1.9.12-6.fc29.x86_64 pulseaudio-12.2-1.fc29.x86_64 qjackctl-0.5.5-2.fc29.x86_64 > As I understand it jack should be an either/or/add > switch for audio streams I do not understand exactly what you are trying to convey. I think of jackd more like a patch bay for routing audio within the OS. Is that just a different way of saying the same thing you wrote there? > I found that jack seemingly does not really do direct hardware access Of course not, it has been a principle of general purpose operating systems for well over five decades that user space programs do not directly access hardware, the operating system kernel mediates access to the hardware. > which further complicates things On the contrary it simplifies things. It would be wasteful and error prone if the jack project had to duplicate the work done in the linux kernel audio drivers. It also gives a clear boundary to check basic audio functionality using ALSA utilities (such as aplay and arecord) separately from the routing and patch bay functionality of jackd. > If it in principle rely on alsa then those interfaces needs to be > very well documented how it communicates with > alsa, what the exceptions and conditions are etc. ALSA has an API, jackd also has an API, but I don't get the impression that is what you mean. The method that jackd uses to communicate with ALSA devices is the same as every audio software which supports ALSA, including pulseaudio, audacity, Ardour, etc. I am not really sure what you mean there, perhaps copying the actual output from jackd when it has an error will allow someone to help you by pointing out the messages which indicate why jackd could not start. > if there was e.g. just a hard patchbay application that would replace jack I would > use it in an instant. It would not be elegant but would clearly route > signals by hand. That is basically what jackd is. Having multiple audio interfaces complicates the situation, having multiple sound servers (e.g. jack and pulseaudio) complicates the situation. If you have a machine with only one audio interface and no other audio servers running just start jackd and it will work. Once your machine setup gets more complicated than that then any sound server will require you to make some configuration choices. One thing which may in the future prove useful to you is the Red Hat pipewire project. The aim of that project is to make a single server which combines the features of pulseaudio and jackd, and also provides similar features for video, running as the default media server for Fedora. That final working solution is still some time in the future, but sounds like it should be what you are looking for in terms of default working setup with only minimal configuration required. > That is maybe what is needed until jack becomes user friendly I am reminded of a quip about Unix operating systems: "Unix is user friendly, it is just very picky about who it makes friends with." > Isnt there at least some for of user debug frontend for jack that can > point to the errors Start jackd from the command line, copy and paste the output messages to an email so that someone can have hope of helping you. So far you have a lot of complaints but not much information. Regarding the question you asked of Holger: > How is that going to influence my abilty to use audio interfaces as now > alsa wont be able to access the usb ports directly when I follow the > link advice you included in your message. If I understand it right No, you misunderstood what the instructions were doing. They were essentially making sure pulseaudio did not start automatically, setting up jackd as the main audio server, launching pulse with the jack interface module as the audio interface instead of ALSA, and also secondarily setting up an ALSA pseudo-device which exposed a jack port as an ALSA device for software which attempts to use ALSA directly. I find that almost all current software versions support pulse, so the ALSA setup is not needed. Note that in my opinion if you need those instructions, your chosen linux distribution has not done a good job configuring the audio software provided in the distribution repositories. I don't want to be too repetitive, but in Fedora none of that is necessary, just start jackd and it works. You will probably need to load the jack modules in pulseaudio, but that may work by default now. I am not sure, I have had a modified pulse configuration file in my user directory for so long I am not positive of some of the current default behavior. -- Chris Caudle

6 years

[Jack-Devel] [ANN] The QStuff* Pre-LAC2019 Release Frenzy

by Rui Nuno Capela

Hello there! The Qstuff* pre-LAC2019 [17] release frenzy is now starting up... enjoy! Included in this batch: * QjackCtl 0.5.6 * Qsynth 0.5.5 * Qsampler 0.5.4 * QXGEdit 0.5.3 * QmidiNet 0.5.3 All the boring details follow suit... ** QjackCtl - JACK Audio Connection Kit Qt GUI Interface [1] ** QjackCtl 0.5.6 (pre-lac2019) is released! QjackCtl is a(n ageing yet modern, not so 'simple' anymore) Qt [6] application to control the JACK [7] sound server, for the Linux Audio [11] infrastructure. Website: http://qjackctl.sourceforge.net https://qjackctl.sourceforge.io Project page: http://sourceforge.net/projects/qjackctl Downloads: http://sourceforge.net/projects/qjackctl/files - source tarball: http://download.sf.net/qjackctl/qjackctl-0.5.6.tar.gz - source package: http://download.sf.net/qjackctl/qjackctl-0.5.6-35.rncbc.suse.src.rpm - binary package: http://download.sf.net/qjackctl/qjackctl-0.5.6-35.rncbc.suse.x86_64.rpm - AppImage [16] package: http://download.sf.net/qjackctl/qjackctl-0.5.6-7.x86_64.AppImage Git repos: https://git.code.sf.net/p/qjackctl/code https://github.com/rncbc/qjackctl.git https://gitlab.com/rncbc/qjackctl.git https://bitbucket.com/rncbc/qjackctl.git Change-log: - Refactored all singleton/unique application instance setup logic away from X11/Xcb hackery. - At last, JACK freewheel mode is now being detected as to postpone any active patchbay scans as much as possible. - Removed old pre-FFADO 'freebob' driver support. - HiDPI display screen support (Qt >= 5.6). - Graph port temporary highlighting while hovering, if and only if connecting ports of same type and complementary modes. - Bumped copyright headers into the New Year (2019). ** Qsynth - A fluidsynth Qt GUI Interface [2] ** Qsynth 0.5.5 (pre-lac2019) is released! Qsynth is a FluidSynth [9] GUI front-end application written in C++ around the Qt framework [6] using Qt Designer. Website: http://qsynth.sourceforge.net https://qsynth.sourceforge.io Project page: http://sourceforge.net/projects/qsynth Downloads: http://sourceforge.net/projects/qsynth/files - source tarball: http://download.sf.net/qsynth/qsynth-0.5.5.tar.gz - source package: http://download.sf.net/qsynth/qsynth-0.5.5-16.rncbc.suse.src.rpm - binary package: http://download.sf.net/qsynth/qsynth-0.5.5-16.rncbc.suse.x86_64.rpm - AppImage [16] package: http://download.sf.net/qsynth/qsynth-0.5.5-7.x86_64.AppImage Git repos: https://git.code.sf.net/p/qsynth/code https://github.com/rncbc/qsynth.git https://gitlab.com/rncbc/qsynth.git https://bitbucket.com/rncbc/qsynth.git Change-log: - Refactored all singleton/unique application instance setup logic away from X11/Xcb hackery. - HiDPI display screen support (Qt >= 5.6). - Bumped copyright headers into the New Year (2019). ** Qsampler - A LinuxSampler Qt GUI Interface [3] ** Qsampler 0.5.4 (pre-lac2019) is released! Qsampler is a LinuxSampler [10] GUI front-end application written in C++ around the Qt framework [6] using Qt Designer. Website: http://qsampler.sourceforge.net Project page: http://sourceforge.net/projects/qsampler Downloads: http://sourceforge.net/projects/qsampler/files - source tarballs: http://download.sf.net/qsampler/qsampler-0.5.4.tar.gz - source package: http://download.sf.net/qsampler/qsampler-0.5.4-28.rncbc.suse.src.rpm - binary package: http://download.sf.net/qsampler/qsampler-0.5.4-28.rncbc.suse.x86_64.rpm - AppImage [16] package: http://download.sf.net/qsampler/qsampler-0.5.4-7.x86_64.AppImage Git repos: https://git.code.sf.net/p/qsampler/code https://github.com/rncbc/qsampler.git https://gitlab.com/rncbc/qsampler.git https://bitbucket.com/rncbc/qsampler.git Change-log: - Refactored all singleton/unique application instance setup logic away from X11/Xcb hackery. - HiDPI display screen support (Qt >= 5.6). - Bumped copyright headers into the New Year (2019). ** QXGEdit - A Qt XG Editor [4] ** QXGEdit 0.5.3 (pre-lac2019) is released! QXGEdit is a live XG instrument editor, specialized on editing MIDI System Exclusive files (.syx) for the Yamaha DB50XG [13] and thus probably a baseline for many other XG devices. Website: http://qxgedit.sourceforge.net https://qxgedit.sourceforge.io Project page: http://sourceforge.net/projects/qxgedit Downloads: http://sourceforge.net/projects/qxgedit/files - source tarball: http://download.sf.net/qxgedit/qxgedit-0.5.3.tar.gz - source package: http://download.sf.net/qxgedit/qxgedit-0.5.3-14.rncbc.suse.src.rpm - binary package: http://download.sf.net/qxgedit/qxgedit-0.5.3-14.rncbc.suse.x86_64.rpm - AppImage [16] package: http://download.sf.net/qxgedit/qxgedit-0.5.3-7.x86_64.AppImage Git repos: https://git.code.sf.net/p/qxgedit/code https://github.com/rncbc/qxgedit.git https://gitlab.com/rncbc/qxgedit.git https://bitbucket.com/rncbc/qxgedit.git Change-log: - HiDPI display screen support (Qt >= 5.6). - Old deprecated Qt4 build support is no more. - AppStream metadata updated to be the most compliant with latest freedesktop.org specification and recommendation. ** QmidiNet - A MIDI Network Gateway via UDP/IP Multicast [5] ** QmidiNet 0.5.3 (pre-lac2019) is released! QmidiNet is a MIDI network gateway application that sends and receives MIDI data (ALSA-MIDI [8] and JACK-MIDI [7]) over the network, using UDP/IP multicast. Inspired by multimidicast [14] and designed to be compatible with ipMIDI [15] for Windows. Website: http://qmidinet.sourceforge.net https://qmidinet.sourceforge.io Project page: http://sourceforge.net/projects/qmidinet Downloads: http://sourceforge.net/projects/qmidinet/files - source tarball: http://download.sf.net/qmidinet/qmidinet-0.5.3.tar.gz - source package: http://download.sf.net/qmidinet/qmidinet-0.5.3-16.rncbc.suse.src.rpm - binary package: http://download.sf.net/qmidinet/qmidinet-0.5.3-16.rncbc.suse.x86_64.rpm - AppImage [16] package: http://download.sf.net/qmidinet/qmidinet-0.5.3-7.x86_64.AppImage Git repos: https://git.code.sf.net/p/qmidinet/code https://github.com/rncbc/qmidinet.git https://gitlab.com/rncbc/qmidinet.git https://bitbucket.com/rncbc/qmidinet.git Change-log: - HiDPI display screen support (Qt >= 5.6). - Old deprecated Qt4 build support is no more. - AppData/AppStream metadata is now settled under an all permisssive license (FSFAP); also updated to be the most compliant with latest freedesktop.org specification and recommendation. - Fixed for some g++ >= 8.1.1 warnings and quietness. License: All of the Qstuff* are free, open-source Linux Audio [11] software, distributed under the terms of the GNU General Public License (GPL) version 2 or later [12]. References: [1] QjackCtl - A JACK Audio Connection Kit Qt GUI Interface http://qjackctl.sourceforge.net [2] Qsynth - A fluidsynth Qt GUI Interface http://qsynth.sourceforge.net [3] Qsampler - A LinuxSampler Qt GUI Interface http://qsampler.sourceforge.net [4] QXGEdit - A Qt XG Editor http://qxgedit.sourceforge.net [5] QmidiNet - A MIDI Network Gateway via UDP/IP Multicast http://qmidinet.sourceforge.net [6] Qt framework, C++ class library and tools for cross-platform application and UI development http://qt.io/ [7] JACK Audio Connection Kit http://jackaudio.org [8] ALSA, Advanced Linux Sound Architecture http://www.alsa-project.org/ [9] FluidSynth - A SoundFont Synthesizer A real-time software synthesizer based on SoundFont 2 specifications http://www.fluidsynth.org [10] LinuxSampler - The Linux Sampler Project A modular, streaming capable, realtime audio sampler http://www.linuxsampler.org [11] Linux Audio consortium of libre software for audio-related work http://linuxaudio.org [12] GPL - GNU General Public License http://www.gnu.org/copyleft/gpl.html [13] Yamaha DB50XG http://www.soundonsound.com/sos/1996_articles/may96/yamahadb50xg.html [14] multimidicast - sends and receives MIDI from ALSA sequencers over network http://llg.cubic.org/tools/multimidicast [15] ipMIDI - MIDI over Ethernet ports - send MIDI over your LAN http://nerds.de [16] AppImage, Linux apps that run anywhere http://appimage.org/ [17] LAC2019@CCRMA-Stanford, March 22–26 2019 https://lac.linuxaudio.org/2019/ See also: https://www.rncbc.org/drupal/node/1989 Enjoy && Keep having fun! -- rncbc aka Rui Nuno Capela

6 years

[Jack-Devel] jack errors with firewire saffire pro 24, help please ?

by lunatikos

hello, i have problems to configure jack : i tried deleteing ./.config/jack/ folder but when i modify config, jack shows errors. so i tried to setup my saffire pro 24 (firewire) , and i got this error : can you please help me ? -- Sent from: http://jack-audio.10948.n7.nabble.com/Jackit-f3.html

6 years, 1 month

[Jack-Devel] Mailing List

by Matthew Kightley

Hello, I am no longer using Jack and was hoping to be removed from your mailing list. Thank you.

6 years, 1 month

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

JackAudio March 2019