Good morning,
I continue to have difficulties implementing Ardour7 in Fedora37. I noticed yesterday that in Qjackctl, I could see only outputs for Ardour. No trace of input to connect to, no trace of my tracks that I usually can connect to in Qjackctl. I use Focusrite scarlett 2i, never been disappointed by this material.
Thanks a lot for your help.
Ludovic
Since @sanji have the same pb, I runned the command provided by @paul 
cd /tmp && wget https://ardour.org/files/adevices.sh && bash ./adevices.sh
And the answer i got is below. Thx a lot for your help !
-2023-05-05 20:48:38-- https://ardour.org/files/adevices.sh
Résolution de ardour.org (ardour.org)… 54.235.123.47
Connexion à ardour.org (ardour.org)|54.235.123.47|:443… connecté.
requête HTTP transmise, en attente de la réponse… 200 OK
Taille : 2249 (2,2K) [application/octet-stream]
Sauvegarde en : « adevices.sh »
adevices.sh 100%[===================>] 2,20K --.-KB/s ds 0s
2023-05-05 20:48:39 (31,2 MB/s) — « adevices.sh » sauvegardé [2249/2249]
========================================
Part I: ALSA
Advanced Linux Sound Architecture Driver Version k6.2.14-200.fc37.x86_64.
Card 0 (HDMI):
* Playback Device 3 (HDMI 0):
- Subdevice 0 (hw:HDMI,3,0):
closed
* Playback Device 7 (HDMI 1):
- Subdevice 0 (hw:HDMI,7,0):
closed
* Playback Device 8 (HDMI 2):
- Subdevice 0 (hw:HDMI,8,0):
closed
Card 1 (PCH):
* Playback Device 0 (ALC3226 Analog):
- Subdevice 0 (hw:PCH,0,0):
closed
* Recording Device 0 (ALC3226 Analog):
- Subdevice 0 (hw:PCH,0,0):
closed
Card 2 (USB):
* Playback Device 0 (USB Audio):
- Subdevice 0 (hw:USB,0,0):
used by: pipewire (PID 1615)
access: MMAP_INTERLEAVED
format: S32_LE
subformat: STD
channels: 2
rate: 48000 (48000/1)
period_size: 480
buffer_size: 24000
* Recording Device 0 (USB Audio):
- Subdevice 0 (hw:USB,0,0):
closed
========================================
Part II: jack processes
So what I gather from that output is that you are using Pipewire, not jackd and not Ardour ALSA backend, but Pipewire has opened your audio interface for playback only, not playback and input.
Do you need the routing capabilities of using JACK API? If not, then using the Ardour ALSA backend may be the easiest solution, Ardour will make clear in the Audio/MIDI setup window if it is using the device for playback only, or playback and recording.
If you do need the routing capabilities of JACK, you could remove Pipewire-jack modules and use jackd, which can be configured and started with QjackControl and might be easier to verify that the settings are what you want.
If you want the routing capabilities of JACK, and you want to use the Pipewire JACK implementation, then you will need to use whatever audio settings utility is provided in Kubuntu to set your audio configuration for output and input.
You are using Fedora Linux 37.
Fedora uses Pipewire as default audio backend since v34…
Make sure your Ardour uses JACK as “Audio system” (Window → Audio/MIDI Setup).
I don’t think this:
* Recording Device 0 (USB Audio):
- Subdevice 0 (hw:USB,0,0):
closed
means anything. I have almost the same output:
Card 2 (A14):
* Playback Device 0 (USB Audio):
- Subdevice 0 (hw:A14,0,0):
closed
* Recording Device 0 (USB Audio):
- Subdevice 0 (hw:A14,0,0):
closed
and inputs work.
If you are using Qjackctl then probably you have jackd installed manually. So maybe something is messed up between pipewire and jack…? You don’t need jackd if pipewire is installed in your system, the pipewire-jack package should do the job. Do you have a directory named /etc/ld.so.conf.d/ and config files inside? Is there some config related to pipewire-jack?
I have this:
/etc/ld.so.conf.d/pipewire-jack-x86_64-linux-gnu.conf
with this content:
/usr/lib/x86_64-linux-gnu/pipewire-0.3/jack/
which means that system sees and uses libs: libjackserver.so, libjacknet.so and libjack.so
provided by pipewire-jack instead real jack server.
If you have installed jackd and pipewire-jack simultaneously, then maybe this is the cause…
Just guessing…
Hello friendly people,
In fact, I did not mess with pipewire and jackd. I just set up fedora 37 and ardour and qjackctl.
Anyway, I changed in the midi audio settings to Alsa. Inputs worked fine but i could not get outputs to work again… As I read your proposal, I went back to Jack in the audio/midi setup and by a kind of mystery, all the tracks were running again with inputs and outputs.
Happy, but what happened …WTF !?
This time, when I put in the terminal Paul’s command I get this :
Card 0 (USB):
* Playback Device 0 (USB Audio):
- Subdevice 0 (hw:USB,0,0):
used by: pipewire (PID 1594)
access: MMAP_INTERLEAVED
format: S32_LE
subformat: STD
channels: 2
rate: 48000 (48000/1)
period_size: 480
buffer_size: 24000
* Recording Device 0 (USB Audio):
- Subdevice 0 (hw:USB,0,0):
used by: pipewire (PID 1594)
access: MMAP_INTERLEAVED
format: S32_LE
subformat: STD
channels: 2
rate: 48000 (48000/1)
period_size: 480
buffer_size: 24000
which is much better !
I think qjackctl package installs jackd automatically - and that is not desirable when your system uses Pipewire.
I have a system with Pipewire too, and just using qpwgraph for my audio routing needs. No need for qjackctl at all - so I guess you could uninstall it and be good?
That’s not true, qjackctl requires libjack.so.0(), pipewire-jack does supply this requirement and qjackctl works with that.
In fact JACK and pipewire-jack are marked as conflicting, at least in pw-jack’s rpm spec.
In the working case your USB audio device is opened for playback and recording.
In the non-working case the device is opened only for playback, not for recording.
Possible that you just made a slight mistake in the settings and did not select the device for input when setup, only for output. Hard to tell without seeing the audio setup window to see how your system is configured.
This topic was automatically closed 91 days after the last reply. New replies are no longer allowed.