View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0009069 | ardour | bugs | public | 2022-11-04 21:42 | 2022-11-06 19:28 |
Reporter | CraigPid | Assigned To | |||
Priority | normal | Severity | minor | Reproducibility | always |
Status | new | Resolution | open | ||
Platform | GNU | OS | Linux | OS Version | (any) |
Product Version | 7.1 | ||||
Summary | 0009069: Cannot select inputs in the connection matrix after opening a video and extracting the audio | ||||
Description | After opening a video and choosing to extract audio only, when another audio track is added I cannot select any inputs in the connection matrix. The workaround is to save and close Ardour. After restarting Ardour and opening the project I am able to select inputs. I have reproduced this in an up to date version of Mint with the 6.9 bundle from ardour.org and also in Arch with the 7.1 version from the Arch repo. Both systems are using pipewire. When attempting to select an input, a green dot appears when hovering but when clicked, does not make the connection. | ||||
Steps To Reproduce | 1. Create new project 2. Open video and extract audio to a new track 3. Create new audio track 4. Open the grid and attempt to select an input | ||||
Additional Information | Both systems are running pipewire-jack at 44.1 khz. The video I imported was 48k and resampled by Ardour when importing. | ||||
Tags | No tags attached. | ||||
|
Seems that it's not dependent on importing audio from a video but just importing audio in general. Or maybe random. I've noticed that when I click the square on the input, the green dot does not appear but I actually am getting input from the mic, even though it says it's not armed. There doesn't seem to be a way of disconnecting it though. |
|
Can you reproduce if using the ALSA or PulseAudio backend? |
|
When Ardour starts I don't have an option of choosing a backend. Do I need to disable Jack? |
|
You can always open the backend dialog in Window -> Audio/MIDI Setup. "Close" the old backend and "start" the new one. (The ALSA backend should connect directly to the device after telling PipeWire to back off.) (My hypothesis is that this could be a JACK/PipeWire issue that I also have seen, apparently related to timing issues between creating JACK "channels" in PipeWire and being able to use them for signal routing.) |
|
I tried it with the Alsa backend and was not able to reproduce. |
Date Modified | Username | Field | Change |
---|---|---|---|
2022-11-04 21:42 | CraigPid | New Issue | |
2022-11-05 15:55 | CraigPid | Note Added: 0026853 | |
2022-11-05 22:29 | kiilerix | Note Added: 0026855 | |
2022-11-05 23:24 | CraigPid | Note Added: 0026856 | |
2022-11-06 01:13 | kiilerix | Note Added: 0026857 | |
2022-11-06 19:28 | CraigPid | Note Added: 0026859 |