-
Notifications
You must be signed in to change notification settings - Fork 39
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
Crash on "Save Master" #93
Comments
Thanks for reporting the issue. I suspect that it's fixed in a development copy, but I'll get you an updated binary to verify if that's the case or not. To confirm, typing in the text field with any key triggers the crash, correct? Or is it just certain keys like delete/backspace? |
Correct, it's literally any key. In the meantime, I have discovered a workaround: create an empty file using a file manage or terminal ( It'd be cool if it were fixed in a new version, though, and I'm happy to test it. |
https://fundamental-code.com/tmp/zyn-fusion-linux-64bit-3.0.6-git-demo.tar.bz2 should have a demo built from the current master. For some reason I was encountering some hiccups from the build scripts, but it looks like everything in the resulting tarball is ok. You should be able to run it without installing to see if the problem is installed. Usually for development I go to the directory and run './zynaddsubfx -I null -O null -U -P 1337' and then run './zyn-fusion' in another terminal. In case there is still a crash this version of zyn-fusion will print out all OSC messages received via a hexdump like mechanism. The line numbers with regards to backtraces will also be consistent between this version and my local system. |
Downloaded, testing. |
OS
Linux
Zyn Version
zyn-fusion-linux-64bit-3.0.2-patch4-release.tar.bz2
Downloaded and installed using
install-linux.sh
from Gumroad.To reproduce:
zynaddsubfx --auto-connect
(Note that my username is not
mark
, despite the errors listing/home/mark/code
)Workaround
So far I have not discovered a way around this bug. It seems I cannot save any session information without a crash.
The text was updated successfully, but these errors were encountered: