View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0009252 | ardour | bugs | public | 2023-02-20 09:51 | 2023-02-20 09:51 |
Reporter | kamilner | Assigned To | |||
Priority | normal | Severity | major | Reproducibility | always |
Status | new | Resolution | open | ||
Platform | Ubuntu | OS | Linux | OS Version | (any) |
Product Version | 7.3 | ||||
Summary | 0009252: Does not create audio Hardware outputs on startup | ||||
Description | When starting up Ardour 7.3 with an empty session and setting the audio setup to use ALSA, it does not seem to create the hardware output endpoints. This results in the hardware bus being disconnected, and unable to be connected to the hardware. | ||||
Steps To Reproduce | 1. Start up Ardour 7.3 2. Create a new empty session. 3. Set the audio driver to ALSA and the input and output to an audio device (same device) | ||||
Additional Information | I have sometimes found that restarting the audio or messing around with the settings will cause the hardware endpoint to be created. However, in this case, the metronome, auditioner, etc. are not connected to the audio device. I have not yet found a consistent "recipe" to force the hardware output endpoints to be created. I have tried this on a couple of different audio devices and get the same issue on both. I am using KDE Neon which is based on Ubuntu 22.04, with Pipewire enabled. LSB Version: core-11.1.0ubuntu4-noarch:security-11.1.0ubuntu4-noarch Distributor ID: Neon Description: KDE neon 5.27 Release: 22.04 Codename: jammy | ||||
Tags | No tags attached. | ||||