View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0009274 | ardour | bugs | public | 2023-03-09 01:29 | 2023-03-22 23:08 |
| Reporter | cjs | Assigned To | |||
| Priority | normal | Severity | crash | Reproducibility | always |
| Status | new | Resolution | open | ||
| Platform | Redhat | OS | Linux | OS Version | (any) |
| Product Version | 7.3 | ||||
| Summary | 0009274: Analog Obsession plugins running via yabridge crash Ardour when oversampling is selected | ||||
| Description | Analog Obsession vst3 (windows) plugins running via yabridge that have been problem free in Ardour 7.2 and prior, and Mixbus 32c 8.2.66 and prior, now crash in Ardour 7.3 and Mixbus versions higher than 8.2.66 when the oversampling button (the Analog Obsession logo on the plugin GUI) is clicked selecting oversampling. The playback ceases when oversampling is selected, and clicking again on the Analog Obsession logo to turn oversampling back off does turn the GUI's indicator back to show no oversampling, but Ardour (and Mixbus) are un-responsive after the oversampling selection event, and Gnome eventually pops up a window offering a force quit or wait. | ||||
| Steps To Reproduce | Set up a new session, install yabridge, get a plugin from Analog Obsession (they are donationware), such as LALA, insert said plugin in a channel, then click on the Analog Obsession logo on the plugin GUI to select oversampling. | ||||
| Additional Information | I have tried this on a few different kernels and both Fedora based (Nobara) and Arch based (Manjaro) setups and the same crash happens. Also if a session that has been saved for example in Ardour 7.2 with an Analog Obsession plugin activated that has oversampling on, that session will not load into Ardour 7.3, instead, the startup splash hangs and eventually Ardour must be force-quit. I have never submitted a backtrace before but will read the directions attempt to do so. | ||||
| Tags | No tags attached. | ||||
|
|
I did what the manual said about creating a backtrace but I guess this is not a crash, but rather some other state that I do not know the name of, where the DAW simply stops responding and the option to wait or force quit pops up on each Ardour window. So I guess with no crash, there is no way to generate a crash report. |
|
|
Actually, there is. You need to use this command to get the PID of (hung/stopped) ardour: ps aux | grep ardour Then start debugging as you normally would, but at the first gdb) prompt, type: attach PID where PID is the PID (number) you determined Then use: thread apply all bt to get the backtrace |
|
|
Thanks for the further instructions, maybe I can get that done after this album, but for now I found that the VST2.x versions of the Analog Obsession plugins work properly with oversampling activated via Yabridge in Ardour 7.3.x, so I'll just replace the VST3 versions in my current sessions. |
