Skip to content
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

Closed
esaruoho opened this issue Jan 31, 2019 · 4 comments · Fixed by #4086
Closed

Store polyphony limit in patch #429

esaruoho opened this issue Jan 31, 2019 · 4 comments · Fixed by #4086
Labels
Feature Request New feature request UX Issues related to user experience (UX) - mouse, touch, keyboard, MIDI inputs, etc.
Milestone

Comments

@esaruoho
Copy link
Collaborator

Surge manual says

The state of the polyphony limit setting is not stored in patches.

We could have the polyphony limit state saved in the new patch format, right?

@baconpaul
Copy link
Collaborator

So if we do this, there's one state transition which is weird.

Lets say you set poly to 16
You load a new style patch which sets it to 3
Then you load an old style patch
What do you want poly to be.

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.

@baconpaul baconpaul added this to the 1.7 or later milestone Feb 28, 2019
@mkruselj
Copy link
Collaborator

mkruselj commented Mar 7, 2019

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...

@baconpaul
Copy link
Collaborator

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

@baconpaul baconpaul modified the milestones: 1.7 or later, Currently Unscheduled Oct 4, 2019
@baconpaul baconpaul modified the milestones: Currently Unscheduled, 1.6.6 Feb 1, 2020
@baconpaul
Copy link
Collaborator

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.

@mkruselj mkruselj changed the title feature request: store poly limit in patch store poly limit in patch Feb 5, 2020
@mkruselj mkruselj modified the milestones: Currently Unscheduled, 1.7.n Jun 18, 2020
@mkruselj mkruselj modified the milestones: 1.8.n, 1.9.0 Oct 8, 2020
@mkruselj mkruselj changed the title store poly limit in patch Store polyphony limit in patch Oct 8, 2020
@mkruselj mkruselj modified the milestones: 1.9.0, Surge XT Jan 24, 2021
@mkruselj mkruselj added the UX Issues related to user experience (UX) - mouse, touch, keyboard, MIDI inputs, etc. label Feb 8, 2021
This was referenced Mar 15, 2021
@mkruselj mkruselj modified the milestones: Surge XT 1.0, 1.9.0 Mar 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature Request New feature request UX Issues related to user experience (UX) - mouse, touch, keyboard, MIDI inputs, etc.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants