-
Notifications
You must be signed in to change notification settings - Fork 404
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
FL Studio crashes when copying LFOs two times #1425
Comments
I didn’t even know you could copy an LFO! Will look. |
Oh yeah I introduced this in the nightly with a half-completed thing which I realized I don't need anyway. Will fix this morning. Thanks! |
baconpaul
added a commit
to baconpaul/surge
that referenced
this issue
Dec 17, 2019
The helper I introduced to handle KeySplit UI changing was both wrong and unnecessary. So remove it, thereby killing a crash and also making the code ready to finish the split mode. Addresses surge-synthesizer#1413 Closes surge-synthesizer#1425
Awesome. Thanks! :) |
Yeah refactored that half finished code to (1) be less clumsy and (2) not crash anymore. Pull request in now. Should be in the nightly in an hour or so. Thanks - great catch! |
baconpaul
added a commit
to baconpaul/surge
that referenced
this issue
Dec 17, 2019
The helper I introduced to handle KeySplit UI changing was both wrong and unnecessary. So remove it, thereby killing a crash and also making the code ready to finish the split mode. Addresses surge-synthesizer#1413 Closes surge-synthesizer#1425
baconpaul
added a commit
that referenced
this issue
Dec 17, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
FL Studio crashes (simply closes unexpectedly without any error message) when doing the following:
To Reproduce
Steps to reproduce the behavior:
Surge version
NIGHTLY-2019-12-16-aa75776
VST3 x64
Desktop config:
Additional context
Weird crash that probably only happens since recently. Tested in 1.6.4.1 VST3 in the same environment and it works fine (the crash does not occur).
The text was updated successfully, but these errors were encountered: