View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0010299 | ardour | bugs | public | 2026-04-27 15:03 | 2026-04-27 15:03 |
| Reporter | youki | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | new | Resolution | open | ||
| Platform | Debian GNU | OS | Linux | OS Version | (any) |
| Product Version | 9.2 | ||||
| Summary | 0010299: Ohlhorst Digital Linux VST3 plugins don't behave the way they should | ||||
| Description | Jan Ohlhorst is currently porting his plugins to Linux VST3 versions. As i use sometimes a couple of them in their Win versions I tried his Linux Beta versions with Ardour 9.2. The Linux versions doesn't behave the way it should while it works fine in Reaper and Bitwig. | ||||
| Steps To Reproduce | - Download the plugin on the website https://beta.ohlhorstdigital.com/ - Install the VST3 - Open Ardour and use the plugin, check the values displayed and the values in the generic UI. | ||||
| Additional Information | On the attached screenshots, on the left is the plugin running through WINE/Yabridge, on the right the native Linux VST3, both with the exact same settings. - As seen on the Ancora_Linux-beta2_Bands.png, the number of bands per octave is displayed as 18 in the Linux version, when it should be 12. The “Bands” section almost always displays an incorrect value in the Linux version. At the minimum setting, it displays “-nan” instead of “2.0”. If I type “12” on the keyboard, it displays “6” in the knob's GUI. If I type “18”, it displays “12”. If I type “21”, it displays “18”. However, if I type “24,” it displays “24.” - As seen on Ancora_Linux-beta2_Target.png, the "Target" value displayed is 3 in the Linux version when it's 3.5 in the Win version. In any case, it is always displayed with a slight discrepancy from the value assumed to be correct, regardless of what that value is. - As seen on Ancora_Linux-beta2_Timing.png, The “Timing” value displayed is -2147483648. The "Timing" parameter is actually set on 50ms and is shown properly on the Win version when the parameter is highlighted with the mouse cursor. All the values above 50ms are displayed wrongly on the Linux version, for instance if i enter "250 ms" the line on the GUI is shown closer to 50 ms than 250 ms, same on the knob. - The same settings are displayed as well with the same wrong values in the generic UI. - The same Linux VST3 plugins work perfectly and as expected with Reaper and Bitwig, BUT just as poorly with Qtractor. | ||||
| Tags | No tags attached. | ||||
