I have a Casio CTK 7200 at home and one I use for rehearsal/gigs. (I also have a home and away Casio PX350 weighted keyboard).
While I was using my home keyboards, I set up a Rig (in the Rig Manager) for the the CTK-7200 and a Rig for the PX350. I have 9 faders and 3 buttons on the CTK-7200, so assigned the virtual controllers F1.-F.8 to the 8 faders and B.1-B.3 to the three buttons. I did this while I was homing using my home CTK-7200.
While at gigs sometimes, I think the two keyboards (CTL-7200 and the PX350) got switched. So, I would go into into the Rig Manager, double click on the CTK-7200 in the RIg Manager and hit a key on the keyboard and now the keys responded properly when I played my CTK-7200. I did the same with the PX350. All good.
But, I have had situations where widgets still did not respond properly even though I thought I assigned the faders and buttons as controllers properly in the Rig Manager. Even when I made sure the widget (in the widget panel) was associated the correct fader/button number, it did not seem to work, I had to re-learn for each rackspace and each widgets at the gig. (Partially because of this I have not used widgets for often).
After thinking about this, I am wondering if the problem is I need a separate Rigs for my home CTK7200 and my away CTK7200. Maybe the is why my away CTK-7200 faders/buttons do not respond properly,
So, I would need the following rigs: CTK-7200 HOME and CTK-7200 AWAY
Then at a rehearsal/gig I would make sure the correct precise rig (CK-7200 Home vs. CTK-7200 Away) is selected.
Does this diagnosis of the problem and resolution make sense? (I plan to try tomorrow, but I figured I would see if I could get some feedback first). [I don’t think I need to bother doing this with the PX350 because I don’t use any controllers on that keyboard].
Paul, I started the process of creating separate rigs for my duplicate CTK-7200s (home and away).
But, then I got concerned that the midi in blocks would not recognize the new Rig. So, if I activated my “CTK-7200 AWAY” if would not be recognized in the midi blocks that reference the “CTK-7200 HOME”.
You need the same MIDI Device Alias and that you use as MIDI In plugins.
Now in the different rigs you associate the physical MIDI devices to you MIDI Device Alias.
I am wondering if their is simply idiosyncratic about my hardware. Things are just inconsistent.
Sometimes, it recognizes both CTK7200s as the same rig and controllers work as expected. (Especially if I just remove a connection to a keyboard and connect to the duplicate right away).
There are times that it recognizes the keyboard (or I use Rig Manager to connect it to the proper keyboard), but they controllers do not function even though they were assigned to buttons…
This also happens with the previous song/next song/next song part in the setlist manager. (I also assigned them to specifics controllers (B.1, B.2 and B.3).
If someone could point me to a step by step way of creating two different rigs (for two duplicate keyboards) and assigning the same device alias to them (as Paul suggested) I would appreciate it. I would try that (but I am not convinced this is the issue).
I feel like I am floundering here. Like I said I am wondering if this keyboard is just flaky in terms of the Rig Manager “remembering” the hardware controller faders that are GP is supposed to respond to.
I feel like this is pretty important to get the most out of GP. Up to now, I have basically avoided heavy use of widgets.
My test case now is organ settings where I have faders set up to control drawbars. If I set up the duplicate keyboard at a rig, sometimes it works, sometimes it doesn’t.
Like I said, I am also having the same problem with next/previous song/next song part in set list menu. But, for this one thing, it is less of a hassle to correct it at a gig. I can’t go through every rackspace making sure every widget is working.
Let me simplify my question try to do what Paul suggests.
Right now I have two rig aliases: CTK-7200 and PX350.
When I connect the home or away physical CTK-7200 it is usually recognized as the CTK-7200 rig alias. (If not, it is incorrectly recognized as the PX350 rig alias. If that happens, I just swap them out in the Rig Manager (no problem).
So, in order to create “two different rigs” for my home and away CTK-700s maybe I should I start fresh in the Rig Manager. (Maybe create a new Gig File first to be safe). Lets say I start totally fresh and remove ALL rig aliases.
When my home physical CTK 7200 is connected, the RIg Manager will recognize that. Should I give it the alias (let’s say) “Generic CTK 7200”. This would be the alias recognized in my midi in blocks.
Then i should dissociate my physical home CTK-7200 with the alias “Generic CTK 7200” and create a new alias: “Home CTK-7200”. Then associate that “Home CTK 7200” alias with the “Generic CTK 7200” alias (which is recognized in my midi in blocks).
Then connect my CTK-7200 I use for gigs/rehearsals. I will probably automatically be recognized as either the “Home” or “Generic” CTK-7200 alias automatically when I connect it.
So, should I disassociate it from those aliases and create a new “Away CTK-7200” alias and then associate that with the “Generic CTK-7200” that is recognized in my midi in blocks.
I am probably missing something. Is this how I should proceed?
BTW: If you should be Windows user, you should always connect the the same controllers into the same USB-jacks… if you change that “pairing”, bets are good that Windows will use internally another name to access those controllers, which then would make Gig Performer not recognize the controller anymore (since it got another name). Probably this is what happened to you from time to time…
Yes, if I can do this, I would be able to rely on widgets.
I do try to set up using the same usb ports and I wait until everything is connected before starting starting up the computer and GP. (But it still happens).
I wonder if Paul’s idea of setting up different rigs for the two duplicate keyboards would avoid the issue entirely. For some reason I am not sure how to exactly do that.
But, yes, this should work. (And sometimes it works fine so I can just check quickly by opening the Rig Manager and moving the controllers).