Hello,
I have not worked with the Rig Manager yet but before I spend a lot of time on it I’m wondering if I could do the following with it.
I have a lower end laptop that I use for general quick access as it is on most of the day. I have a higher end desktop that I use when I want to be more serious and have more time to work on things. I never run both the laptop and desktop at the same time as I have 1 audio interface on a switch, a UR44C and am on Windows 10 Home on the laptop and Windows 11 Pro on the desktop.
My questions:
Can I set up Rig Manager to recognize different devices that are on or off?
The laptop has the following normally powered on, Korg Nautilus and a nano studio.
The desktop has the Nautilus, nano studio, Akai MPK249, Line 6 HD500, and an expression pedal.
Meaning, these are the devices that I power on when using these computers.
I assume some of this depends if I connect specific hardware to widgets but I’m hoping there is a generic way to make this work. Or I will just use the keyboards for playing and the nano studio for controlling widgets.
I would like to know if I power up the desktop, would it recognize the devices that are powered on and hopefully avoid errors if I forget to power on the MPK249 for example.
If I use the laptop, and don’t power on the MPK249, I’m hoping there would be no errors.
Would I create separate rigs on each computer or on both?
Just checking if anyone has set up something similar. If so, I will try to do this.
Thanks!
Rig Manager was one of the main reasons I moved from Mainstage as it allows moving keyboards/Interfaces/and computer so much easier.
In Rig Manager assign a number of device aliases, I use “Lower_88”, “Upper_49” and “Control_Surface”. Once these are assigned the physical interfaces can be associated to these aliases. The Rig can then be saved and called at any time. Different rigs can be assigned for each setup.
Within the wiring view all MIDI in blocks use the Rig Manager device alias names. Allowing different connections without any changes to the gig files.
I am no expert on Rig Manager.
But, I think whenever you change keyboards, you would just assign the alias that you want to use with that keyboard. Easy.
Since these are your keyboards (not using a keyboard loaned to you at a particular gig) it’s even easier, I think, because you can make sure the controllers are exactly where you want them (you do not have to re-assign them as you might for a new keyboard, which also does not take long).
My understanding is the Rig Manager is not part of the Gig File. So, I think you would need to export and import the Rig Manager so it is used on both laptops.
But, keep an eye on this thread. Maybe someone will correct me if I am mistaken about anything.
I think the rig manager serves a different scenario - when you have the same computer but change controllers which you want to be recognized as if they were not replaced.
I have the opposite problem, more similar to yours - I use different computers with the same set of controllers, rig manager isn’t helpful for this.
That would depend on what you are doing with those controllers, and it has little to do with rig manager. Gig Performer will of course recognize devices connected and disconnected.
If a device is disconnected it just won’t do anything. An error may appear if you have a script that tries to send something to a disconnected device and there’s no check in that script for whether a device exists. I don’t think you would get errors in other situations.
Why not?
What does it do for such a scenario? I always have one “rig”.
If anything, it creates unneeded actions when using midi callbacks. At least I couldn’t find a way to reference midi inputs without aliases (fortunately it works with outputs).
Oh, and I need to copy those aliases to all computers instead of just referencing devices directly.
Also, since I don’t use keyboards, my devices are different controllers with knobs and faders, replacing a Nanokontrol with an X-Touch Mini wouldn’t work anyway.
26 posts were split to a new topic: Using Rig Manager aliases makes scripts less reusable
@vangrieg - Thank you for the reply. I just started a new rig and will be working though this to see how things go. I’m not scripting at this point so I’m not expecting any errors there. I assume I might see a warning message if something is not powered on. I’m still thinking through how I’m setting things up. To start with, I’m just setting up the nanoKontrol to mute and solo a mixer control, open and close VST’s, bypass VST’s, and control pan and volume. I’ll probably have it also start the global play for an SAFP and do some switching of rackspaces and variations. The real test will come later when I import the rig into the desktop and add the MPK249 and figure out what I want it to control.
Thanks again for the help.
Just map nanokontrol buttons to whatever widgets they are supposed to control using midi learn, you won’t get any errors if it’s disconnected.