-
Notifications
You must be signed in to change notification settings - Fork 403
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
raspi4b rpios surge crashes upon note input in reaper #5884
Comments
You mention version 1.7, that is not Surge XT. Please try with latest version, which is Surge XT 1.0.1. 1.7 is quite old now and it's likely that whatever was problematic with it is fixed in latest. |
is there a version compiled for arm7l or arm64? it doesnt specify. please offer one if not! thank you! |
All our releases are here: https://github.com/surge-synthesizer/releases-xt/releases But for RPi you might need to self-build. We have instructions in our README. |
You do need to self build for pi. We don’t have a compilation environment in the pipelines. 1.7 is 2 years old nearly? You should ask your repo maintainer to update. If xt doesn’t run on your pi in 64 bit mode please open a fresh issue! That should work and I did test it running into the xt install |
Bug Description:
A clear and concise description of what the bug is.
surge xt crashes upon note input within reaper. you can make changes to the gui but when you play a note, surge and reaper crash. surge is installed from kx studio repository and is reproducible on other raspi4 running raspberry pi os current
Surge XT Version
This information is found on the About screen, which you get to from the bottom right menu.
1.7
Reproduction Steps:
Steps to reproduce the behavior: load surge in reaper and play a note
Expected Behavior:
A clear and concise description of what you expected to happen..
i expect to hear sound
Screenshots:
If applicable, add screenshots/GIF/videos to help explain your problem.
Computer Information (please complete the following!):
Additional Information:
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: