Will the Mobius Looper work with or within Gig Performer? I’m looking to add a VST looper and I’ve read good things about the Mobius; I’d appreciate your help; thank you!
@edm11 might be the one to ask.
Thanks @rank13.
@tenthumbs Mobius will work inside GP. The stock version is a 32 bit plugin that needs to be bridged to 64 bit.
This updated release candidate is 64 bit however, and I use it inside GP.
Thank you!!!
@edm11 I’m looking at every post—everywhere—to try to find some help to setup Mobius 3 in GP5 and just came across this one.
One basic thing I’m struggling with to have it work is how to map its functions to widgets in Panel/Edit given what parameters the plugin it offers. I don’t know if you still use it, but any help would be appreciated.
In the plugin, select Bindings > Edit Bindings > Plugin Parameter tab. There you can select the Mobius functions/Scripts/Parameters you want exposed in GP by dragging them into the Plugin Parameter window.
You’ll need to restart Mobius for those parameters to become visible to GP for mapping to widgets.
@edm11 Now we’re getting somewhere—I’ve been at it for quite some time and it was starting to feel impossible though I’d come across people who managed to have it work. Thanks a bunch for dropping in.
“Dragging them into the Plugin Parameter window.” That’s a vital piece of information nobody was bringing up. Guess they took for granted that I’d know that or think about doing that. Which I didn’t.
OK. Restarted and I see the ones I dragged in the plugin Parameter window. Nice. Now I need to map them to widgets and to my MC6 Pro. Am I understanding rightly that I can freely choose any CCs and MIDI channel as long as it doesn’t conflict with what I’m already using?
Another question. In Mobius, in the “MIDI Devices” I’ve set the Input to the MC6. Should I leave the Output blank or should it be also set to it ?
When you’re using Mobius inside GP, you’re not using the MIDI device assignments inside the plugin. Instead, you’re assigning Mobius parameters to widgets and then learning the messages from your controller to those widgets. All control of the plugin should happen via widgets, as sending MIDI directly to the plugin from your controller can have unpredictable results.
@edm11 OK, you lost me there. So practically what does that mean ? In Mobius, in the MIDI Devices I don’t set the MC6 as the Input and Output?
I understand that “All control of the plugin should happen via widgets.” I’ve been working on my first laptop-based setup (using MIDI Guitar 3, GP5, and a MC6 Pro) for about a month now and had to program a lot of them. I’ll start experimenting with mapping Mobius’ controls in GP and my MC6 today and see how it goes.
Correct. Your MC6 will control the widgets, which in turn controls Mobius. When you use host automation there’s no need to send MIDI directly to the plugin.
@edm11 OK. Got it.
I started to look into the mapping in GP. I’m not clear how it works. Say that in the Panel Edit I chose the “record” parameter of Mobius. As I brought up earlier, can I freely use any MIDI channel and CC# to map it—as long as it doesn’t conflict with the others I’m already using?
You should spend some time with some simple tasks in GP, and also some time with the user manual. Most of your questions can be answered as you gain more familiarity with the app in general.
If you do not understand host automation and controlling plugins with widgets, then you can read more about them in depth in the user manual
a) Widgets
and in particular the two subjections
How to connect a widget to a plugin parameter?
How to connect a widget to a MIDI device?
b) More in these videos