beats me wrote:
I’m almost always mousing shit. So I think I could make things a lot more interesting if I was tweaking parameters with hardware more often, but I’m probably not going to do that if it involves a bunch of manual mapping BS.
It takes some work only if you want to do a super detailed template of a big synth with 10 pages of parameters or something. And the reason that takes work is because you need to figure out the best layout and grouping of controls for each page. The actual act of mapping is extremely fast. So much fast than making midi templates. With midi you need to edit a template, set cc's to the different controls, name each control, then go and map the hardware to the controls you planned. With auto map you hit the learn button, touch a control on the unit and click the control on the plug-in. The name shows up automatically (you can change it if you want). You just keep doing this for as many controls as you want for as many pages as you want. No worrying about how many cc's you have or what channel it's on. For plug-ins it's the only to go. Plus for most effects and those simpler analog style synths, you actually get a workable hands on control surface.
For plug-ins is that a one-time thing? Like the next time I open an instance of that plug-in everything will still be mapped the same? What if I open the plug-in in another DAW? And do I have to page through shit or is it as simple as I click on the plug-in on the screen and it automaps to it?
I seem to remember some template malarkey with the first automap. “No, don’t use template 2. Use template 6.” or something like that.