Posted: Wed Apr 25, 2007 12:24 pm
+1
Fractal Dimension wrote:+1
This is a real showstopper for all Novation Automap Universal users.
hoffman2k wrote:Do a simple test.
Build a rack with loads of devices, then try to automate 1 parameter. Or even find it for that matter.
You'll notice Live will be getting a bit sluggish too.
Removing the limit is not the solution. Letting us specify which 128 parameters we want (and the ability to save that pref.) is what we really need.
The Live browser seems perfect for it.
I've been thinking about this a lot since I feel your pain and have the same problem.
Though just removing the limit will bring us more problems.
How about this?
- Right-click on a plugin and select "show list of parameters"
- A browser pops up, very similar to the MIDI learn or macro browser in Live 6
- It lists all the parameters of a plugin, be it 3, 225, 10 000,.....
- You have to ability to arrange the order of the parameters. Simply drag the parameter you want to automate, to one of the first 128 parameter positions.
- Once everything is arranged, you can save a preset of your arrangement.
Now this brings us to the juicy bit of my suggestion.
Since we arranged our parameters in custom sets of 128, the next logical request would be MIDI maps for devices..
No need to look hard, our parameters are already arranged to match CC's.
All we need is an option on the device to "receive MIDI from port x channel x"
If we want to control more then 128 parameters with a midi controller... Instead of switching presets on the controller, we could just switch them in Live.
Preferably by MIDI
2 birds killed with one elegant stone?
And one more................sunrahrahrah wrote:+1
this is really bothersome
Exactly, I've the same problem myself as well, trying to figure out which slider parameter in Live is the one you're tweaking in the VST gui is really frustrating at times, particularly given the parameter-naming conventions for a lot of the VST's on the market out there.jasefos wrote: Great suggestion! Personally I find the default layout of the Parameter list (as presented by plug-in devs) to be quite illogical. In fact I often find it necessary to "discover" a parameter in the list by tweaking the appopriate control in the plug-in GUI to see which parameter in the list reacts.
It would be great to hide parameters in the list which you don't intend to ever automate in order to make parameter indexes higher than the first 128 to be included.
Absolutely, this seems the most efficient and usable way of implementing this.hoffman2k wrote:How about this?
- Right-click on a plugin and select "show list of parameters"
- A browser pops up, very similar to the MIDI learn or macro browser in Live 6
- It lists all the parameters of a plugin, be it 3, 225, 10 000,.....
- You have to ability to arrange the order of the parameters. Simply drag the parameter you want to automate, to one of the first 128 parameter positions.
- Once everything is arranged, you can save a preset of your arrangement.
Now this brings us to the juicy bit of my suggestion.
Since we arranged our parameters in custom sets of 128, the next logical request would be MIDI maps for devices..
No need to look hard, our parameters are already arranged to match CC's.
All we need is an option on the device to "receive MIDI from port x channel x"
If we want to control more then 128 parameters with a midi controller... Instead of switching presets on the controller, we could just