-
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
Add option to choose default patch #4502
Comments
We should add a single function like "int SurgeStorage::idForDefaultPatch" which does
then call that from the two spots. this way if you delete your default patch you startup. Then have the clients be resilient to a -1 return value. |
The initial load would ignore the patchid-from-name guess since we had already found Init Saw. Make it so we beleive the name with various checks to make sure that is reasonable. Closes surge-synthesizer#4625. Also puts the inti patch name and template as a member of storage and uses that consistently, which is part of the way to surge-synthesizer#4502.
So in the PR above I added a initPatchName and initPatchCategory variable to SurgeStorage which is consistently used.
and bobs your uncle. |
Actually I'm just gonna add that to the PR and close this issue along with the other one |
The initial load would ignore the patchid-from-name guess since we had already found Init Saw. Make it so we beleive the name with various checks to make sure that is reasonable. Closes surge-synthesizer#4625. Also puts the inti patch name and template as a member of storage and uses that consistently, and allows a user default for the patch to use there. Closes surge-synthesizer#4502.
And done |
On the heels of #1824, we will finally gonna have properly loaded Init Saw by default.
Add an option to User Settings > Patch Defaults > Set current patch as default. Also add it to CPatchBrowser context menu (both LMB and RMB variants), right after "Initialize patch".
The text was updated successfully, but these errors were encountered: