MPE Status stored in patch #890
Labels
Host Specific
Issues related to specific host(s) or host features
Milestone
Comments
|
not sure if this is feasible for example if a project has multiple instances of Surge it could be that one track may use Surge with a preset having MPE enabled and another track with a preset having MPE disabled |
|
Yeah totally feasible but requires us to store mpe status in a patch so I want to wait until after 1.6.0. Also can’t you use an rpn midi message to do this today out of curiosity? |
baconpaul
added
the
Host Specific
baconpaul
changed the title
baconpaul
added a commit
to baconpaul/surge
that referenced
this issue
Aug 16, 2019
Some features of the synth - notably, zoom, MPE Enablement, and Tuning - are features of the DAW environment you are working in and were not persisted. This fixes that by adding a dawExtraState section to the streaming protocol which is only populated and read at DAW time not at general patch time. Closes surge-synthesizer#890 Closes surge-synthesizer#914 CLoses surge-synthesizer#915 Mostly wraps up surge-synthesizer#828
baconpaul
added a commit
that referenced
this issue
Aug 16, 2019
Some features of the synth - notably, zoom, MPE Enablement, and Tuning - are features of the DAW environment you are working in and were not persisted. This fixes that by adding a dawExtraState section to the streaming protocol which is only populated and read at DAW time not at general patch time. Closes #890 Closes #914 CLoses #915 Mostly wraps up #828
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
currently if MPE is enabled and saved in a project Surge will open with MPE disabled
would it be possible to have a setting in SurgeUserDefaults.xml
similar to
<default key="mpeEnabled" value="1" or "0">so that if MPE is set to enabled in a project it will open with the MPE feature enabled
The text was updated successfully, but these errors were encountered: