AIM

MSN

Website URL

ICQ

Yahoo

Jabber

Skype

Location

Interests

Registered Products

Dear Helix (floor) experts, I need your help, having an issue on the A/B-switch.
I'll describe my setup first: I am using the helix (2.53) in dual mode: 1 signal path goes usually directly into FOH, the other one is used to feed my amp by 4-cable-method (4CM). That gives a nice, fat sound, like 3 rhythm guitarists playing unisono. In my setlist I use a preset for every single song we play and do the in-song-changing (amp channel and master volume [MIDI], FX etc.) with snapshots.
Task & solution:
-=-=-=-=-=-=-=-=-=-
I am supposed to play the opener and I have 3 signal paths planned for this to get huge, spacey sounds out of my guitar and helix. One (path 2) is used for a synthesizer pad sound (no guitar signal in) by 3 OSC synth (XLR out into FOH). This one should not concern us anymore, works exactly as it should. The other signal path 1 (guitar input) is split up (A/B switch): Path 1A (above) is feeding the signal into a FX chain, the output goes directly into FOH (XLR left/right). Works fine, too. Path 1B of this signal path is going by SEND/RETURN 1 and some FX into my amp (1/4" out). This one works as well.
The 4 snapshots and their sequence would be:
1: start with path 1A (FX - A/B switch = [A100%] - of course, with the brackets!!)
2: add path 2 (synth pad - identical to snapshot 1, just turning on the 3 OSC synth)
3: add path 1B (amp - identical to snapshot 2, just A/B switch turned to [even])
4: finishing the opener with just path 1B active (only amp, nothing else - like snapshot 1, just with A/B switch adjusted to [B100%]).
The problem:
-=-=-=-=-=-=-=-=-=-
Helix does not seem to be consistent with this A/B switch. It all works as intended until I get to reach snapshot 3. Once the A/B-switch has changed to [A/B even], it won't accept any other setting anymore (exception: snapshot 1). Means, it stays on [even], ignoring the individual path programming in snapshot 2 and 4. The display DOES show the original programming, but the DSP is simply ignoring it.
Anyone got any idea, what exactly is the problem behind this and how it can be solved??? I am really puzzled here ...