Integration withv GigPerformer

Bernarada

New member and first post... Years ago I played around with the first iteration of Mobius while I've been using mainly hardware loopers, and I'm glad that it's back and renewed. I downloaded it with the intent of using it inside GigPerformer, which is the main platform I use as a guitarist, with the addition of MIDI Guitar 3 and a Morningstar MC6 Pro foot-controller to control them.

Someone in GP5 forum actuality posted a rackspace file that hosts 6 tracks of Mobius, and also shared the CCs bindings that goes with it to have it work. At this point I’m only trying to get the mapping of the Record button to trigger. That would be a start. GP and the MC6 do communicate (the MIDI monitor in Mobius shows that and if I assign a MC6 switch that I’m trying to map to Record to the Bypass parameter, Mobius does bypass), but I can’t figure out how to get Record to trigger.

One thing I’ve been wondering is that though the person who shared the rackspace wrote that, on track 1, Record = CC11, in the parameters window of Mobius in GigPerformer the numbers appearing are different. It's 2 numbers separated by a slash, like 0/1, 0/2, 0/3. I’ve never seen those as CCs apart from plugins that use banks and presets where 0 can be a bank and the next number a preset, but anyway, I can only conclude that CC11 corresponds to “14 - MIDI CC 0/11” in the parameters list, but maybe I’m wrong.

In any case, I bring this up in the hope that someone here has been or is using Mobius in conjonction with GigPerformer and can be of help. If so, I'd greatly appreciate it.

benT

I just did a quick test wit GP and it works if you set up the corresponding MIDI-bindings in Mobius:

The number before the slash is the midi-channel. But it starts at 0 in the parameter-list in GP, so 0 would be channel 1 when you set up the bindings in Mobius. You can verify that Mobius gets the widget/button-press from GP if you open the Midi-monitor from the Help menu in Mobius.

A random example - setting GP-widget to parameter 4/2 MIDI CC4|2 for instance should work if you set up a binding for Record that has channel 5 and CC value 2 in Mobius. (The midi-monitor in Mobius outputs: Host: CC 5 2 0 and Host: CC 5 2 127 on button release and button press.)

Bernarada

benT I just came across your reply. Thanks for taking the time for that.

First, that's helpful. It's the first time that I get more indications on how to set it up in GP5. I'll experiment with what you wrote about the setup in GP, but about the setup in Mobius I'm at a loss. Looking through all the menus, I can't find where I can set the MIDI bindings (like channel 5 CC value 2) the way you describe it. What am I missing ? If you could share a screenshot of the Mobius window where you entered your bindings, that would be helpful.

Here is what my window looks ![like—both under the MIDI (which shows nothing) and Plugin Parameter tabs...

https://imgur.com/a/p8IHfpA

Bernarada

benT So, I'm a little confused now—which is nothing new.

I found the way to add Mobius functions to the Plugin Parameters window in the Bindings/Edit bindings tab. once I restarted Mobius, the functions I selected showed up in Mobius parameters in GP5 Panel/Edit. So the situation now is different then when all I was seeing are the numbers I mentioned earlier (like 0/1, 0/2, etc), which is what you responded to.

What confuses me is that it seems that there are two ways to go about it. If I don't add Functions in Mobius Bindings' Plugin Parameters, then those functions don't show up in the Parameters of Mobius in GP5 Panel/Edit, only the numbers I mentioned. If I do add them in Mobius, then I get them in the Panel/Edit.

I'll experiment, but if you have any input about this, it would be useful. I include a screenshot of what the window in Panel/Edit looks like with Mobius functions showing.

https://imgur.com/a/g1ZPeDt

benT

(Sorry about late reply, I haven't been able to test this any more the last few days.)

Thanks for pointing that out(!), I haven't tried that until now. Seems that would be the exact purpose for this function - providing the plugin host (GP in this case) with access to triggering functions directly without MIDI-bindings.

Yes - so it seems there are two ways to do about it. Setting up the functions in Plugin Parameter I think would be cleaner, because you get the function name into GP. So you don't have to remember all the MIDI bindings when setting up widgets.

I'm not sure if you could get the midi-bindings to work, but you have to drag the function from the list into the MIDI pane, and then fill out the values. For the GP scenario, Type would be "Control", and channel and value would be the numbers according to the chosen parameter from the list in GP ( midi channel shifted +1) as discussed above.

For me both ways seem to work fine on a quick test. Where are you having trouble?

Bernarada

benT I'll start with a first question—I'll have to come back to the bindings once I've sorted that out.

In GP I have a synth wired to Mobius, which is wired to an EQ, which is wired to the Audio Out (my interface). When I bypass Mobius, I hear the synth. When Mobius is active or engaged, I don't anymore—although the volume bar in Mobius shows that it's getting sound. So there must a setting in Mobius that is not set right, that doesn't allow it to pass or output the sound through.

Any idea what it could be? I guess it could be many things. I still have a long way to understand what each settings in Mobius does, which are so numerous.

benT

Yes, I guess you are looking for passing through the audio. The setting is in the Sessions menu --> Edit sessions --> Globals -->Miscellany --> Monitor audio

Bernarada

benT Great. That did it. Thanks. Now to the bindings. I'll experiment with the 2 ways mentioned earlier and be back if needed. Though I could ask: Is there or are there any general settings in Mobius other menus that need to be set in certain ways to have the bindings work?

PS: As I think about it, what controller do you use with GP and Mobius—a keyboard, foot-controller?

benT

I got the MIDI-bindings working without any special setup. I'm pretty sure you will work things out if you click around a little bit and get to know how things work.

Personally I actually have just started using Mobius myself, although I have been aware of it since many years ago. Been on the lookout for something suiting my use case, and very happy Jeff revived it. For controllers I am in the process of modifying my FCB1010 using a custom setup, but haven't had time to finish it yet. I found the latency was too high for both input (LEDs) and button press on the Eureka-PROM firmware (from what I can see on other forums the stock firmware has lower latency), so I had to change the setup a bit. The ideas are too many, time too short. 🙂 The plan was to use it for a looping-setup with my NS design Nxt5a cello. We'll see how it turns out. For keys I use Kawai VPC1 as a controller, mostly Pianoteq-use (via GP).

Bernarada

benT Ah, you play cello. Wonderful.

So, I spent time clicking around and still can’t get it to work. I've tried the way of having Record dragged in the parameters and showing in GP5, but couldn't get it to work. So now I'm trying the other way, the way where you used the 4/2 parameter in GP as an example previously. I used the same numbers since MIDI channel 4 isn't used yet in my setup.

Mobius monitor shows that it responds when I step on the switch on my foot-controller (a Morningstar MC6 Pro), but all I get when I do is that the words "Synchronize" (in place of Reset) and "Record" appear for a moment then disappear.

Here's a screenshot of that happening, plus some screenshots of my settings. Maybe you see something I'm missing...

https://imgur.com/a/h7c1FS2

Bernarada

benT After spending hours clicking around, reading some more of the documentation and some of the posts here, I finally managed to map Record to my Morningstar MC6 Pro and have it work. Pressing Record works, and it plays when I press again. I was also able to map 2 switches to Next and Previous track.

There's an issue though that, so far, I haven't been able to resolve. Which is that when I switch to track 2, which works, and press Record, it doesn't record on it, it starts to record, still, on track 1. I might find the solution by clicking blindly around, but if you or anyone knows what I'm missing, please let me know.

jeff

I'm catching up after a long absence, and I haven't gone through this thread in detail yet. But when running Mobius as a plugin in any host, there are two ways you can use to run functions. By far the most common is to make MIDI bindings. You configure the host so that MIDI passes from the host into the Mobius plugin, then you set up a binding between the MIDI event and the Mobius function. I haven't used GigPerformer in a long time, but that is what I did at the time, and as far as I know all the other GP users use that method as well.

The other way is to create Plugin Parameter Bindings. This is not often used for functions since it's usually easier to just pass in MIDI, but it is possible for hosts that might have difficulty getting MIDI through, or if you wanted to use host parameter automation to call Mobius functions. VST3 and AU plugins can advertise some number of parameters to the host which the host can then use to control the plugin. For Mobius, this is usually done for things like input/output/feedback levels where you want to sweep the value of a parameter over a range of values. If you create a plugin parameter binding to a function, what has to happen is that when the sets that parameter to any non-zero value the function starts, and when it sends a zero value the function ends. To Mobius this looks similar to pressing and releasing a MIDI note. The problem I've had with this in the past is that almost all plugin parameters are continuous value ranges, not on/off buttons and it's up to the host to visualize what the UI for that parameter is. Ableton for example will still show a value slider even if the only values allowed are 0 and 1, and you have to move the slider to the right, then back left to mimic the pressing of a button.