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.

Sign up for GitHub

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

Jump to bottom

Remember/Save CC mappings #1678

Closed
bit-101010 opened this issue Apr 4, 2020 · 1 comment
Closed

Remember/Save CC mappings #1678

bit-101010 opened this issue Apr 4, 2020 · 1 comment
Labels
Feature Request New feature request MIDI MIDI support related UX Issues related to user experience (UX) - mouse, touch, keyboard, MIDI inputs, etc.
Milestone
1.7.0

Comments

@bit-101010
Copy link

Surge clears out the CC mappings for parameters on reload. For anyone who sets up custom mappings to parameters, these must be re-set every time the synth reloads.

Possible solutions
Ideally, the synth should restore the CC mappings when it reloads, just like it restores modulation and parameter data.
Additionally, Surge could have a menu item for saving the current CC mappings that can be loaded into other instances of the synth.

These would be two separate but related features that would improve the synth's utility in a variety of production and performance settings.
@mkruselj mkruselj added Feature Request New feature request UX Issues related to user experience (UX) - mouse, touch, keyboard, MIDI inputs, etc. labels Apr 11, 2020
@spurkopf spurkopf mentioned this issue May 2, 2020
Closed
@baconpaul baconpaul added this to the 1.7 beta 1 milestone May 2, 2020
@baconpaul baconpaul added the MIDI MIDI support related label May 30, 2020
This was referenced May 30, 2020
Closed
Closed
baconpaul added a commit to baconpaul/surge that referenced this issue Jun 8, 2020
@baconpaul
Path to Persistent Midi Mapping 1: Save in DAW State
9eae4b7 
With this change, if your surge sets up a MIDI mapping for
either a param or a custom controller, it is saved and retrieved
from the DAW state. This means that learn / save in REAPEr or Logic or
what not / quit / restore and that learn sticks.

Closes surge-synthesizer#1774
Addresses surge-synthesizer#1678
Addresses surge-synthesizer#1994
@baconpaul baconpaul mentioned this issue Jun 8, 2020
Merged
baconpaul added a commit that referenced this issue Jun 8, 2020
@baconpaul
Path to Persistent Midi Mapping 1: Save in DAW State (#2073)
a293503 
With this change, if your surge sets up a MIDI mapping for
either a param or a custom controller, it is saved and retrieved
from the DAW state. This means that learn / save in REAPEr or Logic or
what not / quit / restore and that learn sticks.

Closes #1774
Addresses #1678
Addresses #1994
@baconpaul
Copy link
Collaborator

I pushed user settings today also, so this is closed! Enjoy.

@bobobo199733 bobobo199733 mentioned this issue Mar 5, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Feature Request New feature request MIDI MIDI support related UX Issues related to user experience (UX) - mouse, touch, keyboard, MIDI inputs, etc.
Projects
None yet
Milestone
1.7.0
Development

No branches or pull requests
3 participants
@mkruselj @bit-101010 @baconpaul