-
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
Store polyphony limit in patch #429
Comments
So if we do this, there's one state transition which is weird. Lets say you set poly to 16 Your choices are 8 (the default); 16 (the prior non-patch-delivered-version) or 3 (the hangover from the last patch). And even if we add this feature, you want patch streaming versions in place first. Thats #391. So I think I'm going to tag this as "future release" and "new feature" unless you feel very strongly to the contrary. |
In your scenario above, it should be 16 IMHO. Not sure why polyphony is not stored in presets. Makes no sense that it isn't... |
Yeah I think I agree but the fact that it’s not means we need to deal with patch version plumbing before it is. So this one will sit for a while |
Tagging this 1.6.6; but also I think I will include a warning if you load a patch which decreases polyphony so you can override. |
Surge manual says
We could have the polyphony limit state saved in the new patch format, right?
The text was updated successfully, but these errors were encountered: