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 controller settings in profile #401

Open
rsjaffe opened this issue Nov 12, 2017 · 3 comments
Open

Store controller settings in profile #401

rsjaffe opened this issue Nov 12, 2017 · 3 comments

Comments

@rsjaffe
Copy link
Owner

rsjaffe commented Nov 12, 2017

For example, twos complement, range 3000.

Allows different ranges per control when profile switches.

@asettico
Copy link

Very useful, in my opinion.
Can I help in its implementation?

@rsjaffe rsjaffe closed this as completed Jun 10, 2019
@rsjaffe rsjaffe reopened this Jun 10, 2019
@Surfingserenity
Copy link

I use more than one controller with Midi2LR and the "Adjust CC dialog" information I've set up keeps getting mixed up when I load a different profile.
It's been driving me batty, because it means right clicking on all my pad controls to readjust their maximum value and all encoders changed to 2s complement, also very confusing as I didn't know why they had all gone out.
Saving the "Adjust CC dialog" information in the XML would make sense.

@onegrasshopper
Copy link

since @rsjaffe kept this as reopened, upvoting @Surfingserenity. Sharing profiles should include sharing a possible associated controller. Two people on the same computer, more than one controller (different ones for at desk vs on the road), etc.

A user's usage (profile and associated CC control settings) should trump in priority to sharing the profile xml with others.

if the base profile.xml is to be kept tidy, then there can perhaps be a profile-deviceadjustments.xml or such next to it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants