(Background) I use one controller keyboard with gig performer. A Roland A800pro.
(Issue 1) Despite only using the one controller if I map buttons/knobs etc to GP widgets, I can use what I have mapped to control those widgets which relate to various plug in parameters. if I power down my kit and turn it back on again, the controllers no longer change the widgets or the adjustments to the plug ins previously mapped. Often the MIDI block looking for note information etc is no longer receiving any data.
(Issue 2) Because of the above, I was advised to use “Rig Manager” (even though I am using the same keyboard all of the time) to store midi input settings in a way which helps to recall &
reset everything lost each time I power up. I have tried a few times to set up a NEW Rig and create the button/knob relationships needed. When I connect my controller and open the Rig Manager I am seeing 3 x device aliases for the single A800 controller I have (see image attached)
I also notice after a restart, the number at the beginning of the device description is different each time. (in the attached example it is using #4 as the pre-fix)
Does anyone know how I can set up my system so the mapping to buttons/knobs, AND having the correct MIDI IN block ready & working, is consistent?
Using a Roland A800pro controller - someone else has already posted about the rig manager definitions never operating the Roland A800pro widgets which had been set up successfully before.
TIA
Yes, because the A800 Pro has three ports! (I have the same controller)
This is a known issue on Windows (which will be improved at some point) but in fact this is precisely why you would use the Rig Manager. When you connect the controller, just relearn the connection for the port and everything will then just work again.
Thanks for your reply. Can I ask if the A800 is unusual in having 3 x ports? I think it would help me to figure out the Rog Manager logic if I had a controller with just 1 port for now.
And on this advice…
“just relearn the connection for the port and everything will then just work again”
I have been through every video & tutorial I can find AND the user guide back to front and I cannot find anything about “relearning connections”. I don’t know how I would make my system “relearn” that?
TIA
Lots of devices have multiple ports – it doesn’t matter — the whole point of Rig Manager is to define an alias so that when a port name changes (typically due to changing a controller but can also be an issue with Windows adding extra numbers to a name), you can just have Rig Manager learn the new controller and then everything else will work without change.
The page about the rig manager in the user manual explains exactly how this process works — what part did you not understand when you read it? Is there something we are not explaining properly?
There is a specific video that explains exactly how to use Rig Manager. What part did you not understand? Again, is there something we are not explaining properly in that video?
Thanks again DHJ. Again, I do not understand the steps involved to “relearn the connection for the port”. Locating the necessary actions within the User Guide is proving impossible? The user guide does not indicate it would ever be necessary to “relearn” a port and in fact it actually says "you will need to map aliases to the desired controllers, but only once, since you can save them.
For the video, I have watched this many times to try and find some clues on “relearning” a port. Do you know the chapter where this is covered?
Time Stamps​:timer_clock:
[0:00] - Welcome
[0:47] - Rig Manager Anatomy
[1:13] - Creating “Rigs”
[1:31] - Creating and Labelling Controls
[2:17] - Map Controls To Physical Devices
[3:00]- Remapping Second Rig
[3:36] - Faster Mapping With Rig Manager
[3:48] - LiveKeyboardist Gig Performer Set Up Options
I did notice that the Guy in the video is offering private sessions to help people set up their Rig’s correctly. This could be the way I go with this. You can imagine that having to set up all of my controller mapping for every rackspace is becoming a huge problem. It’s taking the majority of our available time in the sound check schedule.
I’m also going to consider a new controller without 3 x ports. I tried the rig manager out with a small basic Alesis controller and after powering down and back on again, everything was stored and recalled with no issue at all!
So on my office machine, I have a single Roland A-Pro 800.
If you look at the first image below, you will see that there are three references, the first with no alias (because I don’t use) and then the second and third with aliases. My Roland sends control info (buttons, knobs, sliders) on port 3 and the keyboard itself is on Port 2
Simply press any key on your controller and the association between the name will be learned.
Then as long as all your MIDI In blocks are named MainKeyboard (or whatever name you want to use), you’re good to go. If they’re not named already, then you can right-click on the plugin block and set it
Once you are using aliases, then if the port name changes, simply open rig manager, learn the new controller (see above) and everything will then just work again.
Amazing walk-thu. Thank you. Some of this is slowly making some sense for me and I will try it out in an hour or so when I’m done with work. Your comment on the A800pro using different ports to send out key messages and knob/slider messages is a BIG revelation to me. I had no idea the signal types were being categorised that way and represented across 2 ports…and so does that mean I have to “relearn/reconnect” 2 x different aliases? 1 x for the keyboard midi signals and 1 x for the Maincontrols?