[footcontroler] any ways or tricks to have CCs banks with Line6 FBV3 ?
Hi everyone :D
I recently purchased a Line6 FBV3 footcontroler (which is quite the same than the FBV MK2 Shortboard), and I try (hard) to properly use it in Live.
Despite it provides 13 footswitches, I really miss a way to cycle through banks of midi presets (one with all footswitches triggering Looper's functions and Live's transport tools, another for my guitar effects, and so on).
Is there a way or an obscur trick to manage CC banks function in Live with the FBV3 ?
The Line 6 FBV Control App is a pain the *** considering that you have to exit Live to load new Midi preset in the FB3, then re-run Live... takes years, no needs to explain why it's not suited with live purposes.
You can create different Effect chains in Ableton Effect rack. Then use the footcontroller to increase or decrease the chain selector to select the different Effect. If u are using a vst plug like guitar rig u can create presets which could be switched with program change commands.
Increasing/decreasing chain selector will reassign CCs to another set of parameters for each effect rack ?
If my footswitches are mapped like FS1 -> CC1, FS2 -> CC2, FS3 -> CC3, and so on…
And I have an effect rack for Looper with CC1 = trigger rec/overdub/play, CC2 = stop loop, CC3 = clear loop,…
And another one for guitar tone (Neural DSP in my case) with CC1 = overdrive, CC2 = delay, CC3 = chorus,…
Moving chain selector from « Looper » effect rack to « Neural » effect rack will reassign CC1 = overdrive, CC2 = delay, CC3 = chorus,… and then if I move it back to « Looper » effect rack, it will reassign CC1 = trigger rec/overdub/play, CC2 = stop loop, CC3 = clear loop,… ?
That way, each footswitch will keep the same CC# and I can reassign this CC# on the fly to another parameters in Live ?
ohh.... you want midi mapping presets. You can program this in m4l. Maybe i have some time for an example, next days.
Since you can't macro map the Loopers trigger rec/overdub/play it would be more work to do. You have to dive into live.API check out all the commands for the looper.device and make the correct routing which can be switched by gates. Most elegant way would be a small midi remote script and maybe some edits in the _generic/devices.pyc midi remote script. There is a little bit information in the net about how to create simple midiremote scripts for ableton.
Looper rec/overdub/play is triggered by a "Momentary" midi CC. When I hit 1st on the corresponding FS, it records the loop, the 2nd time it overdubs, the 3rd it plays the looped materials without overdubing. This by pressing 3 consecutive times on the same FS.
I'm not sure why you thought about macro mapping it, as it's not an actual problem for me, it works well like this (or maybe I didn't get what you mean).
Yes, I'm actually craving for midi mapping presets I can switch on the fly during live performance! I can't find any function that can handle this natively in Live, I'm a total newbie to M4L, but I'll gladly begin to learn with this goal in sight! If you manage to find some time next days, it will be a pleasure to take a look at any template or example you can find/think of.
Yes. I tried to build a small patch where you have two banks with 12 free mapable CC inputs each bank, and one for switching between these. This mapping is called macro mapping since it's no direct midi mapping. (Its like the green map mode in Effect and Instrument Racks) ...Its no problem mapping Volume sliders or pan encoders, or even Feedback encoder in the Looper device... But unfortunatly the Trigger Play/... Button isnt mapable.
With my knowledge i dont know a simple solution with M4L only. Its also not possible to edit _generic/devices.pyc for your needs because the trigger play/... button isnt included in the mapping.
One solution would be an external Max/msp patch which takes your midi controller cc messages and changes it if a certain pedal button is pressed. If you then route midi to Ableton you can map two different parameters with one pedal.