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

When editing individual Mappings, shortcut to "save and go to next Mapping" #224

Closed
vonglan opened this issue Mar 12, 2021 · 12 comments
Closed
Labels
enhancement New feature or request next

Comments

@vonglan
Copy link

vonglan commented Mar 12, 2021

(Maybe also previous)

@helgoboss helgoboss added the enhancement New feature or request label Mar 12, 2021
@helgoboss
Copy link
Owner

One question: What does next and previous refer to? The complete compartment, the group, the filtered mapping list?

@helgoboss helgoboss added the question Further information is requested label Mar 19, 2021
@vonglan
Copy link
Author

vonglan commented Mar 19, 2021

I guess the filtered mapping list, would be the most useful default.
The Use Case I encountered was this:

  • Autolearn many, from an NRPN source
  • So after learning everything initially I need to go back to refine: add specific NRPN max value (different for many knobs on Sequential synths), add specific Virtual Target

@helgoboss
Copy link
Owner

helgoboss commented Mar 20, 2021

I'm so happy that someone uses NRPN :D I put much work into that for the sake of completeness (supporting even exotic MIDI features). But so far I actually didn't stumble upon any controller in the wild that actually uses this (at least not as a default).

@vonglan
Copy link
Author

vonglan commented Mar 20, 2021

Again, all Dave Smith (Sequential) synthesizers use NRPN. They also offer CC, but only for a subset (about 1/3) of the controllers, and sometimes with less range. Yes, I think CC is the factory default. But they recommend to use NRPN in the manual.

@helgoboss
Copy link
Owner

helgoboss commented Mar 21, 2021

I guess NRPN (although a bit more complicated and bloated than other types of MIDI messages) makes sense for any synthesizer that has more than 32 high-resolution controls. If it would be up to 32, they could just as well use 14-bit CC spec. If it would be low resolution, they could just use normal CCs.

When you build your standardized set (#205), I think it would be great if you would rely as far as possible on the synth defaults. Unless you hit limits. E.g. one rule I have with my "official" controller presets: If the factory setting is to have encoders transmit absolute values, change it to relative ones. Otherwise stick to the factory settings.

@grnprplorngyllw
Copy link

Yeah! "Next" and "Previous" buttons would be awesome! That way we don't have to leave de EDIT window to edit other mappings

@vonglan
Copy link
Author

vonglan commented Apr 16, 2021

Just saw your comments now again.

I guess NRPN (although a bit more complicated and bloated than other types of MIDI messages) makes sense for any synthesizer that has more than 32 high-resolution controls. If it would be up to 32, they could just as well use 14-bit CC spec. If it would be low resolution, they could just use normal CCs.

The Sequential synth (OB6 and Prophet 6 and I think the others follow the same principles):

  • don't use all 14 bits, only up to 8 (don't know why - maybe the differences wouldn't be audible anyway?)
  • but much less than half of the controls are exposed as CCs
  • so it's definitely necessary to change from CC (which I think is the factory default) to NRPN
  • it does not offer any other "controller settings" apart from CC/NRPN and MIDI channel

When you build your standardized set (#205), I think it would be great if you would rely as far as possible on the synth defaults. Unless you hit limits. E.g. one rule I have with my "official" controller presets: If the factory setting is to have encoders transmit absolute values, change it to relative ones. Otherwise stick to the factory settings.

@vonglan
Copy link
Author

vonglan commented Dec 7, 2021

I just notice again how much I would like to have this feature.
Quite often, I have to go over multiple mappings again, to change just one field.
Does anyone else want this?

There is enough space on both sides of the "OK" button

@vonglan
Copy link
Author

vonglan commented Feb 19, 2022

"question" label can be removed

@helgoboss helgoboss removed the question Further information is requested label Feb 27, 2022
@vonglan
Copy link
Author

vonglan commented Nov 5, 2022

I just notice again how much I would like to have this feature :-)

@helgoboss
Copy link
Owner

Someone in the forum was asking for it as well, so I guess this issue gets some new traction. I'll see what I can do.

@helgoboss helgoboss added the next label Nov 10, 2022
@PucksEvilTwin
Copy link

Yes this would be great to have!

Basically a similar use case for my OSC layout. Say I learn a bunch of buttons but now need to make one small tweak on each of them. Prev/Next mapping buttons would be great for that.

When you do this with Realearn as it sits now, it feels clunky and it's easy to miss a mapping. However, if you only had one mapping panel open and were clicking next to cycle through them all, that should feel less clunky and minimize mistakes of small edits to a bunch of different mappings.

helgoboss added a commit that referenced this issue Nov 11, 2022
- #224 Added previous/next buttons to the mapping panel
- #747 Added menu and help buttons to the header panel
- #485 Renamed takeover mode Normal to Off
- Fixed bottom section of main panel (was causing artifacts on Windows
  because of overlapping areas)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request next
Projects
None yet
Development

No branches or pull requests

4 participants