FR - controller-mapping presets
-
- KVRAF
- 1615 posts since 28 Mar, 2005
save, recall and switch between sets of mappings.... (tricky I know because the mappings are edit-dependant but still...)
-
- KVRAF
- 4644 posts since 28 Nov, 2002 from Chicago
I've got a feeling that this isn't a single FR...
two scenarios :
1) you are only mapping controllers to plugins that are present in an a new edit by default.
In this case controller info could be saved with the edit as you describe, but this is the case anyway. So what you would really be asking for is user definable edit templates.
2) you are mapping controllers to filters that aren't in an edit by default.
This one logically can;t work as if you placed three instances of a given filter in an edit, Tracktion would have no way to know ahead of time which filter the control mapping referred to.
So basically you are looking at an FR for template edits/projects.
If you wamnted to be able to switch between banks of controller mappings within an edit, and all of those mappings had been created specifically created for that edit, then that would be another thing entirely.
So possibly you have two different FRs here?
two scenarios :
1) you are only mapping controllers to plugins that are present in an a new edit by default.
In this case controller info could be saved with the edit as you describe, but this is the case anyway. So what you would really be asking for is user definable edit templates.
2) you are mapping controllers to filters that aren't in an edit by default.
This one logically can;t work as if you placed three instances of a given filter in an edit, Tracktion would have no way to know ahead of time which filter the control mapping referred to.
So basically you are looking at an FR for template edits/projects.
If you wamnted to be able to switch between banks of controller mappings within an edit, and all of those mappings had been created specifically created for that edit, then that would be another thing entirely.
So possibly you have two different FRs here?
Someone shot the food. Remember: don't shoot food!
-
- KVRAF
- Topic Starter
- 1615 posts since 28 Mar, 2005
The problem is how to save time remapping your controller for different common purposes.
First I would say that having multiple mapping sets within an edit would be a great start and very useful. You could for example have "folders" of mappings within the window that could be enabled and disabled.
the problem of how to implement a more general solution is tricky I admit.
Here are some initial thoughts: what if there were three fields in the mapping window - cc, track number, and parameter. You could then have a mapping preset, which might map 32 controllers to a synth, which was plug-specific and could be assigned to a given plug in one action (ie select track number). Likewise you could have mapping sets specific to a vertain track configuration, ie if you use a stock channel set up. Finally you could have a map set for the volume / pan filters for tracks 1 through n.
Perhaps there is a clever way to implement something like this in racks only...
whats really needed is something a little cleverer than I am able to imagine at the moment. Jules?
First I would say that having multiple mapping sets within an edit would be a great start and very useful. You could for example have "folders" of mappings within the window that could be enabled and disabled.
the problem of how to implement a more general solution is tricky I admit.
Here are some initial thoughts: what if there were three fields in the mapping window - cc, track number, and parameter. You could then have a mapping preset, which might map 32 controllers to a synth, which was plug-specific and could be assigned to a given plug in one action (ie select track number). Likewise you could have mapping sets specific to a vertain track configuration, ie if you use a stock channel set up. Finally you could have a map set for the volume / pan filters for tracks 1 through n.
Perhaps there is a clever way to implement something like this in racks only...
whats really needed is something a little cleverer than I am able to imagine at the moment. Jules?
-
- KVRAF
- 6490 posts since 14 Jun, 2004 from Rochester, NY
hmm itd be tough to figure out. i think its fine at a project per basis, i mean ... come on. its like each project is going to be different and will want to have different assignments.
-
- KVRAF
- Topic Starter
- 1615 posts since 28 Mar, 2005
but there are a few setups that I would use all the time: a setup to control a particular synth - a setup for volumes and pans - it would be great to have a library of these.
-
- KVRAF
- 4644 posts since 28 Nov, 2002 from Chicago
the problem is though that the method chosen for cc mapping does not lend itself well to the kind of hierarchical model that you'd need to be able to build assignable presets.
I'm not sure it can be done without either breaking the existing system, or being horribly cumbersome and fiddly.
I'm not sure it can be done without either breaking the existing system, or being horribly cumbersome and fiddly.
Someone shot the food. Remember: don't shoot food!
-
- KVRAF
- 6490 posts since 14 Jun, 2004 from Rochester, NY
-
- KVRAF
- 9096 posts since 5 Feb, 2004
I made a default edit that I import into new projects with the basic setups I need. I'm waiting on my UC33 and since that has presets for the Pro53 I'm wondering how that will work with T2's way of doing things.
If you have requests for Korg VST features or changes, they are listening at https://support.korguser.net/hc/en-us/requests/new