-
-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Oversampling Crashes the DAW #234
Comments
Thanks for the detailed report! Unfortunately this is a bit tough for me to debug at the moment since I don't have a non-headless Linux setup at the moment. If possible, would you be able to share a the log file from an instance of the plugin that crashes in this way? The log file location is discussed here. By the way, sorry it's taken me so long to get to this... usually I get email notifications for GitHub Issues, but for some reason I never got an email for this one? |
Hmm, it seems like I'm unable to open the log file. Are you able to open it locally? If so, it would be great if you could paste the contents into this issue (either directly, or using something like pastebin) |
This log file is currently being written to... Version: BYOD 1.0.9 State contains processor: Trumble Drive, which is currently locked! Plugin crashing!!! |
Great thank you! The stack trace was super helpful. I was able to get a little testing set up worked out, and I think I've gotten to the bottom of the issue. Basically, when the oversampling parameters are changed, the plugin has to tell the host that its latency has changed. Previously, I was doing that synchronously with the parameter change on the audio thread, which the other plugin formats / hosts seemed to handle in a thread-safe way. Unfortunately when the plugin does the same thing in Ardour, the host invalidates the audio buffer that is currently being processed, which was causing the crash. Personally, I really like how CLAP plugins handle latency changes, where the change has to be reported on the main thread (the CLAP "misbehaviour handler" enforces this), but the API provides a way for the plugin to do the call on the main thread without having to manage it's own message passing between threads (here's how the clap-juce-extensions does it). Anyway (feel free to ignore all that technical business), I'm planning to merge the fix with #242. I'm going to be testing with other DAWs to make sure the change doesn't break things elsewhere, but if you'd like to test as well, feel free to build from the main branch or install the new nightly builds (probably available in an hour or two). |
Changing Oversampling Filter to Linear phase or changing oversampling rate crashes the DAW (in linux ardour 6 and ardour 7)
version BYOD: 1.02
Commit: 2af063a
JUCE: version 7.0.1v
build: october 23 2022 7:43
plugin format: VST3
samplerate: 44.1Khz
block size: 1024
GNU version : 9.4.0
processor cores: 6
processor: ryzen 5 3600
bits: 64
The text was updated successfully, but these errors were encountered: