Switching Lag Time with GCP, GCX and TC G-Force

[Copper1]

I am using a GCP, GCX and G-Force to run a live rig.
I had originally hoped to set up presets to change sounds during a song..For example playing a clean rhythmn with no pedal on the GCX and the gforce supplying chorus, then during the solo selecting the next preset where the GCX adds a distortion pedal and the g-force adds delay. It was a great dream but the reality is the lag time makes it unusable live.
So plan B is where I am using the 4 preset mode of the GCP to switch the G-Force effects blocks. Back to tap dancing, but at least there is now no noticable dropout on the g-force.
I still would like to add and subtract pedals on the fly if possible. I notice when I press a switch on the gcp, it seems to send two signals. In other words, I can see the light on the GCX and hear the pedal go on, go off and go back on again. Almost as if the switch goes through a two step process to switch. Is this normal? The sonic double hit really brings attention to the
switch and adds to the lag time. Any suggestions?

[JohnClark]

Is your trouble with a GCX loop or with a G-Force effect block? If the GCX, is the light you see the loop status LED?

[Copper1]

Hey John,
Switching between presets lag time is mostly a G-force lag. I can live with just turning on and off control blocks, but it is disappointing with the amount of money that thing costs.
However, if I set up the g-force with the exact same routing in back to back presets, the lag time is much less noticable. What is noticable in that senario is the lag time coming from the GCX switching between loops. As I tried to explain, I can see the main LED on the GCX blink twice, I can hear a pedal turn on, then turn off for a millisecond, then turn back on for good. Like a real fast double hit. Do I have something set up wrong?
Mike

[JohnClark]

The G-Force patch load time can certainly be reduced by switching between similar routing as well as eliminating any effects blocks you will not be using from the patch.

On to the GCX...
The Active LED will blink whenever there is any MIDI signal hitting the GCX Pedal In jack.
What is the exact MIDI routing you are using... Ideally you should be running from the Ground Control Pro MIDI Out to the Pedal In on the GCX, then from the GCX MIDI Out to the MIDI In on the G-Force.
Do you see the Loop Status LED for the GCX Loop you are activating follow the same behavior you are hearing?
Are you switching between Ground Control Pro presets when you hear this problem or are you using a Ground Control Pro Instant Access button?

[Copper1]

John,
I hooked up everything this am without the g-force, just the GCP switching the GCX and the lag time between pedal switching is gone. So I am going to have to do some more experimenting tonight.
The Staus LED , when I make a change, Blinks off, back to on, off and then stays on when I do a preset change (I don't know if does the same thing when I do an instant accesschange). I hear that sound switch on/off/on that mimics the light coming out of the G-force..but I need to run few a few different senarios to see if it is just another inherent glitch with the G-force or some type of midi message deal.
Any suggestions on things you would try?

[JohnClark]

Are you talking about the Active LED or the Loop status LED?

The Active LED will flash whenever there is MIDI signal coming into the GCX. The number of blinks is sort of arbitrary and is really based on the length of the MIDI data coming into the GCX.

The loop status LEDs should indicate the bypass/active state of the numbered GCX loops.

You now say that without the G-Force, the GCX problem went away... so did you have the MIDI connections set up as described above when the G-Force was in the setup? Were you perhaps creating a MIDI loop and returning to the Ground Control Pro MIDI In jack?

What Control Change messages are you using to control the G-Force effects blocks?

[Copper1]

John,
thanks for your patients. I double checked my midi connections to make sure I was set up properly and then started hunting through the G-Force settings. When I first was trying to get the blocks to toggle on and off I selected a global effects muting setting..which of course mutes the g-force in between presets.
I also realized that I can set the GCP to just change the GCX and not change the G-force at all. It was a "duh" moment, but I have to admit that I am quite the impatient idiot when it comes to this type of set-up. These three pieces of gear seem to work really well together, but it is not the kind of rig that I can have set up in an hour before a gig..which is what I did. I keep expecting to hit the wall like I have with so many rigs..my latest being the line6 podxt live..where it falls apart live. I am not a tweaker just because of time constraints, but I will have to change that to get the benefits of this rig.
So, thanks again for your help.
One last question..is there a place online where I can download the schematic to the tap tempo pedal?
thanks Voodoo John

[JohnClark]

Once a rig like this is all set up and programmed, it is quite easy to set up at a gig. The whole idea of a setup like this is to be able to connect the controller to the rack and the rack to the amplifier... then start rockin'. There will be some tweaking to do at the beginning to get everything sounding good in a live setting with the rest of the band, but that is true of any setup.

Schematic sent via PM. Good Luck!