Volume Sliders
Yes you can use a nanoKontrol. Instead of mapping manually you can also install the "Control Surface" for it, which is available in Logic. This would automatically map volume, pan etc. in groups, like other control surfaces. But if you also want to control plugins, you rather do NOT want this option because the functions are fixed and not easy to change. In this case better assign the faders/knobs manually.
But be aware that the nanoKontrol and similar devices (also many keyboards) have tiny faders and the knobs are potentiometers. One little push or turn and your parameter is somewhere you don't want it to be. And second, these controllers don't process feedback from the DAW. This means, that the faders and knobs on the controller are not necessarily in the same position as the DAW’s faders and knobs. If you move something on the controller, the controlled parameter may suddenly jump or you have to move the element until Logic catches the controller roughly around the current value.
If you want more precise control, you may consider to spend more money and get a
Faderfox EC4 which is a kind of standard. It has only knobs, is solidly built and configurable in various ways. For Logic volume faders you could use 14Bit (high resolution) or stick to 7Bit (0-127) and (for example) set the volume fader to 0 dB by pressing the same knob. And it gets feedback from the DAW. MIDI goes over USB and via direct output and input. For live applications such functions and a solid device are better than wobbly little plastic sliders.
Remote Tempo Control
In the Logic MIDI Environment is a "Tempo Slider" available which you can map to an external controller. It works quite roughly from 50-177 BPM. But again, you won’t be happy with the Tempo Slider and a nanoKontrol fader. It is practically impossible to set a certain tempo this way. It isn’t funny with a Faderfox either, but better. If your music allows it, you can configure some push buttons for a couple of tempi to get them exactly on demand. To describe the "precision": With a fader you cannot go reliably from 78 BPM to 142 BPM and back again, unless you map the two values, which is possible. With a "free" fader you would go from ≈80 to ≈140 and back to somewhere around 80 BPM. 70 BPM? 90 BPM? Bad luck ...
The tap tempo function is too unreliable. You can try it, though.
We also have "Smart Tempo" in Logic, which claims to be able to adjust the tempo. I've never used it and I don't understand the short explanation either. You'd have to take a closer look.
———
Faderfox are not the only good controllers. Apart from the bigger and more expensive devices with several motorised faders such as Mackie or FaderPort, a few good small controllers are also popular at the moment. The
MIDI Fighter Twister is one example. Depending on genre and style of your performane the
Novation Launchpad Pro could also be suitable. It is relatively easy to configure, in the custom modes it has assignable buttons and can combine rows of 8 buttons to form faders. This works surprisingly well and smoothly if you don't put much emphasis on fine gradation.
Yes, what I'm suggesting is much more expensive than what you have in mind at the moment. You don't have to follow me
🙂 But I've seen a lot of MIDI controllers on my way and I've also used them live. So I'm cheeky enough to establish two rules for live usage:
- If knobs, then they should be endless encoders and process (and preferably display) feedback from the DAW.
- If faders, then either motorised faders or touch faders.
Anything else will always lead to operating errors. As long as you only have one fader and two buttons, almost any controller will work. But with 4 faders (presumably more, with plugins?) and a handful of buttons, you can easily make mistakes on stage. At least if the controller is not the main instrument, but is used only for control. Then it is allowed to be a little more complicated to configure, but you have to be able to operate it reliably on the side, without focussing on it all the time.