Skip to content
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

Sometimes Tidal Modulator will crash the DAW if frequency range button is clicked after adjusting the frequency knob, while receiving clock input, Cardinal VST3 23.02, REAPER v6.67, Windows 11 #504

Open
GBaige opened this issue Mar 6, 2023 · 4 comments

Comments

@GBaige
Copy link

GBaige commented Mar 6, 2023

image

@GBaige GBaige changed the title Sometimes Tidal Modulator will crash the DAW if frequency range button is clicked while receiving clock input, Cardinal VST3 23.02, REAPER v6.67, Windows 11 Sometimes Tidal Modulator will crash the DAW if frequency range button is clicked after adjusting the frequency knob, while receiving clock input, Cardinal VST3 23.02, REAPER v6.67, Windows 11 Mar 6, 2023
@GBaige
Copy link
Author

GBaige commented Mar 6, 2023

Trying to reproduce the issue, and I've found the crash only happens during playback. Upon further testing, the crash may occur outside playback, and it seems to only happen when the frequency knob is set very low.

@GBaige
Copy link
Author

GBaige commented Mar 6, 2023

image
Here is an example patch; to reliably reproduce the crash, you have to (in this exact order):

  1. turn the tidal modulator frequency knob all the way down or to a low value, e.g. -36 to -48
  2. patch the host time step output to the tidal modulator clock input
  3. press the frequency range button

It may be necessary to cycle through the frequency range modes in order to trigger the crash.

@rafaelferreiraql
Copy link

Can confirm, although I'm still on version 22.12 (REAPER 6.75, Windows 10, Cardinal VST3)

@falkTX
Copy link
Contributor

falkTX commented Jul 27, 2023

Please recheck with 23.07, many fixes happened in there.

I tried this myself and cannot get it to crash.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants