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

midi mapping enhancements #126

Open
cyberboy666 opened this issue Mar 12, 2020 · 1 comment
Open

midi mapping enhancements #126

cyberboy666 opened this issue Mar 12, 2020 · 1 comment

Comments

@cyberboy666
Copy link
Owner

the midi current midi mapping could do with a lot of improvements. i will try to keep the ideas here. there was a lot of useful discussion here #102 ;

quickly some suggestions off top of my head:

  • auto detect of 'default' mapping for a number of popular midi controllers
  • an option in setting to select which map you want to use
  • a midi-learn function so you can edit your map within recur
  • a way to edit the map , maybe in the remote server ?
  • currently there is a lot of duplication both within the default map (coz everything is mapped to multiple things to maintain backwards compatibility ) and also between , analog ins., midi ins , key ins and osc ins ... and also also will be between multiple midi mappings for controllers etc. so adding a new function will involve changing a bunch of files... we need some way to auto gen this ?? or some kind of meta midi map mapping ? lol i dunno
@doctea
Copy link
Collaborator

doctea commented Mar 13, 2020

auto detect of 'default' mapping for a number of popular midi controllers

Already got rudimentary support for this in the current branches, not sure if you've spotted how to work it :)

All the other things sound good too -- I can imagine it being easier to set up controls (and config generally) via a remote web interface. You could backup configurations easily that way too by downloading/uploading json files. I also find myself wishing there was a 'bind to last touched control' feature when setting up modulations too so midi mapping that way makes sense.

There's a tradeoff between having mapping features easily accessible for live performance and having the controls so overloaded that it gets confusing/detrimental too. More than once I've accidentally cleared my shader or video banks when I was reaching for another control.. maybe be good to have an undo feature, or be able to take snapshots of configs..

I've had thoughts of the 'meta midi mapping' too, if I'm thinking of the same thing as you then like having 'virtual' inputs 1-4 with the osc, analog, midi inputs feeding into those rather than directly mapped? Kind of like a virtual control surface that exposes the different modes too. But on the other hand the way it is currently you could feasibly set it up so that analog, osc and midi inputs can all control different elements of recur independently, so there's advantage in that flexibility too...

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

2 participants