Please ensure Javascript is enabled for purposes of website accessibility Jump to content

Can you split A/B exclusively?


tcamuso
 Share

Recommended Posts

Is there any way to have an exclusive A or B?

 

I can assign a foot switch to the A/B split and get 100% B, but when I toggle the foot switch to bypass the split, I get B merged with A, when what I want is 100% A.

 

So, I want an A/B split that gives me 100% A and 0% B, or 0% A and 100% B.

 

In truthtable terms:

Footswitch State      :   OFF      ON

Output from split A/B :  A only    B only
                         No merge  100%

 

Link to comment
Share on other sites

2 hours ago, SaschaFranck said:

You don't need to control the bypass status of the switch (I really wish it was that easy, would allow for some more trickery, too) but the value of the slider.

Take a look:

1533097945_HXEdit-HelixFloor.jpg.1fb0cfb6b28e8005285ba2566f164941.jpg

 

No joy. I can get A-only, but when I flip the switch, I still get an A/B merge.

 

Link to comment
Share on other sites

18 minutes ago, themetallikid said:

Yes, I do this with my multi amp presets when using snapshots for clean/dirty tones.  I just have the slider for a/b % set to 100% either direction and attached for that snapshot.  I'm sure you can attach a min/max setting as well so that they are a100 or b100.

 

Doesn't work for me.

 

I don't know what I'm doing wrong, but I cannot select an exclusive A path or exclusive B path with one switch.
If the footswitch makes one exclusive, flipping the switch ALWAYS gives me a merge of both.

 

Link to comment
Share on other sites

When you use "Route to" as a target, the control assigns automatically come up as in the picture I posted. So it's not *that* much of an effort (yet, doing it via bypass straight on the split would be great as I could then exclude it from snapshot bypass - which isn't possible this way).

  • Like 1
Link to comment
Share on other sites

OK, gang, I finally got it to work using saschafrank's suggestion to route the A/B split to a switch and set the max/min.

 

I did this in the Helix Editor, and it took a few cycles of the assigned footswitch before it actually did anything, but now it's working.

 

I don't know why the switch did not immediately respond to the configuration in the Helix Editor, but it seems to be working as expected now.\

  • Like 1
Link to comment
Share on other sites

2 minutes ago, SaschaFranck said:

Guess you'd have to update your Helix - as I'm sure that's what rd2rk already did.

 

Being intimately familiar with software updates, I'm gonna wait a bit before I commit.

;)

 

I will be looking forward to seeing what those new models are in that patch, though!

 

Link to comment
Share on other sites

Just now, tcamuso said:

I will be looking forward to seeing what those new models are in that patch, though!

 

My guess would be that the patch would be not compatible even if it was empty. From all I know, there's never been downwards compatibility of Helix patches.

Link to comment
Share on other sites

Never had backwards compatibility problems as long as it's not a missing model issue, next time you reboot it just optimizes for the newer FW.

Anyhow, the preset is just what Sascha suggested, which you now have working.

All good!

Link to comment
Share on other sites

28 minutes ago, rd2rk said:

Never had backwards compatibility problems as long as it's not a missing model issue

 

Oh really? So in case I create a patch with 3.0 using just older models, that patch would be compatible with older FW versions? I thought that was different and the patch was kinda "tagged", so it'd only load in FW versions as new or newer.

Link to comment
Share on other sites

22 minutes ago, SaschaFranck said:

 

Oh really? So in case I create a patch with 3.0 using just older models, that patch would be compatible with older FW versions? I thought that was different and the patch was kinda "tagged", so it'd only load in FW versions as new or newer.

 

I'm basing that on having restored setlists created with previous versions after an update. They always worked fine, then rebuilt after a reboot.

Link to comment
Share on other sites

8 minutes ago, rd2rk said:

I'm basing that on having restored setlists created with previous versions after an update. They always worked fine, then rebuilt after a reboot.

 

Sure, that's the normal way. But I was thinking whether it'd work the other way around. As in patches (or setlists) created in, say, FW3.x and then loading them in FW2.x.

I thought that way it wouldn't work.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...