Hello all,
As you know, JackPilot cannot be launched anymore on modern macOS systems, and Stéphane Letz told us he won’t work on it anymore.
I missed it so much (I never liked very much qjackcontrol on macOS) and feared that this would be a sign that Jack would be abondonned some day on mac, so I decided to rewrite it from scratch in Swift language.
So Jack Copilot is born,and I hope it will be useful for mac users that enjoy the use of the Jack server on mac, even without JackRouter, which is my case on a day to day basis.
This is my very first mac app and my very first use of the Swift language, but I think the jack developers and community gave me so much in the last years that it would be worth the effort.
You will find it at https://gitlab.com/ericbavu/jack-copilot .
For the mac users that do not want to compile the xcode project for JackCopilot, the repository also contains a dmg installer<https://gitlab.com/ericbavu/jack-copilot/-/raw/master/JackCoPilot.dmg> for JackCopilot and Patchage.
Of course it is open source, and I also discussed with David Robillard (drobilla) and compiled a working version of Patchage 1.0.2 on Catalina and newer versions for use as a companion with Jack Copilot.
Feel free to fork, patch, and submit a pull request !
The next step for me would be to add a menubar companion so that simple actions can be accessed more easily, and to implement a save/recall settings, but so far the app works as expected on Catalina and Mojave.
I’m interested by testers on BigSur also, but I won’t upgrade before 6 months to this version so if anyone is ready to tell me if it works on this version (and with Apple Silicon also), you’re welcome !
I’m still happy with Jack 0.92b3 compiled by Stéphane Letz, so this has not been tested with the latest releases by Falktx, but I don’t see any reason why this should not work. Of course testing is also welcome by the community on this front.
Best regards,
Eric Bavu
Maître de Conférences HDR - Acoustique
Laboratoire de Mécanique des Structures et des Systèmes Couplés
LMSSC / EPN 04 Bureau 31.0E.02, 2 rue Conté, 75003, Paris, France
Hi, I have a question about the difference between
1: Targeting a driver using Port Audio
2: Selecting an interface in Jack Control
This is the situation.
I have PortAudio setup to target ASIO4ALL:
"C:\Program Files\Jack\jackd.exe" -R -S -d portaudio -d "ASIO::ASIO4ALL v2" -r48000 -p512"
What I really want to do is target Dante:
"C:\Program Files\Jack\jackd.exe" -R -S -d portaudio -d "ASIO::Dante Virtual Soundcard (x64)" r48000 -p512"
When I try this, i get the following error:
* Could not connect to ASIO::Dante Virtual Soundcard (x64) using default.
So, I tried thhe following.
I left my PortAudio to target ASIO4ALL
And in Jack Control I selected Dante as an output under advanced settings.
No errors this time.
So what is the difference between "targeting a driver" and selecting a default IO?
Thanks in advance.
Marijn
Hi, I have the following setup;
Jack, running with asio4all target interface. (target in portAudio)
"C:\Program Files\Jack\jackd.exe" -R -S -d portaudio -d "ASIO::ASIO4ALL v2" -r48000 -p512"
This works.
Now I attempted this:
Then, in Jack Control:
Under advanded settings, I have set my output to Asio Dante VS.
This appears to be working.
What exactly is the difference bet
Groet, Marijn
Hi all!
I know that looping via JACK's transport is not supported so I hacked
together a small tool for pseudo-looping https://git.fds.im/-/snippets/7
It just relocates the transport after a number of bars. I'm no JACK export,
so I'm wondering if anyone has any pointers or suggestions. It already
works well enough for our needs but would be cool to improve it if possible.
Thanks,
Peter.
This is a program to reset qjackctl settings. The program can make it
easier to make jack work again.
Source code, binaries for macos, and binaries for windows, are placed here:
https://github.com/kmatheussen/reset_qjackctl
jackaudio(a)lists.linuxaudio.org
When I start qjackctl (1.9.16) on W10 and set portaudio interface to my USB soundcard, the Graph screen shows me my 2 input and output ports (plus MIDI) - but no other devices on my PC.
How can I get the Graph or patchbay to show other devices such as my built in speaker, USB webcam/speakers or Voicemeeter, etc?
Please help
Richard Hughes
Hello,
I'm new to audio production in Linux, so apologies in advance if I will
use wrong terms and bad jargon. I'd like to record my guitars and bass,
but I've found a problem which I think it can be JACK-related.
I bought 2 USB audio interfaces, a 2-channel Behringer which I returned
and a Focusrite Solo 3rd gen, which I'm testing right now.
The issue that I have is with the programs that use JACK, like Guitarix
and Reaper. It seems I can only get distorted sounds out of them and
both have JACK as input source.
Instead, Audacity, which lets me choose the hardware audio interface
directly, lets me hear the sound of my instrument just fine.
What I've tried so far:
- my everyday Ubuntu 18.04 with low-latency patch: Guitarix and Reaper
distorted audio and Audacity just fine
- live AVlinux: Guitarix distorted audio and Audacity just fine
- live Ubuntu Studio: Guitarix distorted audio and Audacity just fine
Can someone please help? What else can I try?
I'd like to stick with Ubuntu 18.04, as it is my main everyday desktop.
Thank you.
Roberto
Hello I am using Jack on Windows machine. I am using the Jack to process audio in real time with few very CPU hungry VST plugins. I have a computer with 4 cores CPU but it is old machine. The playing software did not utilise the cores as it suposse to be. I have got an idea to use VST hosts, connect them and with Process Lasso to force the right core utilisation. And I have succeded the goal. All cores are utilised almost at the same level. My card is an USB interface with max buffer 4092 and ASIO driver. I have configured the Jack with maximum possible frames/buffers. With full set of VST plugins I am getting DSP load 100% what is total disater and in the same time CPU core utilisation in around 30%. Is there any way to solve that problem. Or it is just a kind of bottelneck connected with my USB interface or Jack? Regards
Hello jack community,
I am trying to run two separate Jack instances, one for low latency monitoring using Carla as a plugin host and one for recording using Ardour with a higher buffersize for performance. The two jack servers are connected by zita-njbridge.
Its working quite well so far, the issue is that I cannot compensate for the latency of the zita-bridges, 2*10ms. To my knowledge, jack provides latency information to Ardour, so i need to inform jack about the latency happening. I tried the following setups:
Main Jack, alsa backend using USB Interface (Presonus Audiobox USB96)
Ardour Jack, dummy backend
and
Main Jack, alsa backend using USB Interface
Ardour Jack, alsa backend using onboard audio (Intel 8 Series/C220 if it matters)
Signal way in both cases for recording is:
System in Main Jack - Zita to Ardour-Jack - Ardour - Zita to Main Jack - System out Main Jack
So I never use the onboard physical connections.
The first setup is problematic because the dummy backend doesn't have extra latency options, the latter seems to be ignoring the -I -O numbers in the Ardour-Jack, at least jack_iodelay tells me the same frame count no matter what I enter, which is not the case in the Main-Jack, where I can get it to 0 with the correct settings.
So I get late recordings by 20ms from zita + the latency of the Main-Jack, that the Ardour-Jack doesn't know about.
Is there any way to make this work? And why is the Ardour-Jack ignoring my extra latency settings?
Even though I don't think it matters too much, I'm on Arch Linux, and using jack2 1.9.16-1 and Ardour 6.3-3.
Looking forward to your replies, stay safe and healthy!
Best regards,
Robin
Hello, all
I'd like to introduce you to a new midi tracker that I wrote. It's very
minimalistic, a glorified repeater really. The main idea of the program was
to have something to put between Carla and an external MIDI controller.
selling points:
- it only knows Jack
- fast workflow
- designed for live performance
- irregular looping of tracks (have to see to believe)
- funk mode (nice for triplets)
- midi triggers
- freewheel rendering
Of course it is released under GPL3, otherwise I wouldn't be bothering you
kind people. It compiles and runs on latest Ubuntu and Fedora (developed
under Mint). Gnome app written in Python. The sequencing engine is in good
ol' C (with jack being the only dependency).
You can find the project at:
https://github.com/rdybka/vht
You can also check out:
https://sourceforge.net/projects/vht
for a current tarball and a deb for Ubuntu
Hope someone besides me will find it useful
Regards, Rem