Rachet Delay - Parallel path bleed through during Mute All

[themetallikid]

So my STP tribute band is doing the song Meatplow.   During the 2nd verse there is what sounds like an open E string (I dont know for sure, havent learned the note yet, Probably an F# as the rest is going off that, heh, idk) going on during the 2nd verse.  I was just going to ignore this part, until I watched Jason Sadites video of the Rachet delay block walkthrough.  When I heard him doing his thing, it immediately stood out as an ear candy effect to add that overdubbed part into the 2nd verse.   Simply capture the note, let it sit there in the background under the 'Mute All' parameter until the 2nd verse, tap tempo the song once we start and add it in when we get there.....mute again when its done via a Stomp foot switch.

 

Programming is all good.  I have 

 

1) Bypass set to footswitch 5 to engage the effect and capture the audio before the song starts

2) Mute All > Normal switching set to footswitch 7 for toggling during 2nd verse.  

3)  Set on a parallel path so I maintain my dry guitar

 

I have attached my preset.  As soon as I record the audio, even with Mute All engaged, I can hear it in the background.  When I click FS7, it certainly comes on at the 'normal' FX level, but engaging the Mute All function again goes back to much quieter, but not muted.  

 

What am I missing on this??  

 

Appreciate any help.  

Meatplow.hlx

[arislaf]

That is normal behaviour sincMeatplow 2.hlxe you put it on parallel. One way to mute all, is to assign on the same footswitch, a volume effectb set to 0, on the other chain.

[themetallikid]

shouldnt the 'mute all' parameter mute ALL of the signal though?

[datacommando]

On 4/8/2022 at 12:39 PM, themetallikid said:

shouldnt the 'mute all' parameter mute ALL of the signal though?

Hi,

 

From the 3.15 Release Notes:

 

• Operation—Determines what happens to your signal when Ratchet is turned on (remember, it's bypassed by default)
  • "Mute All"—When Ratchet is on, THE ENTIRE PATH IS MUTED
  • "Dry Kill"—When Ratchet is on, only the effected signal is heard. TIP: With Ratchet on a parallel path, assign a second stomp switch to toggle between Mute All and Dry Kill. This lets you leave the block enabled and bring the effected signal in and out by switching between the two values
  • "Normal" (default)—When Ratchet is on, both the dry and effected signals are heard

 

In the “Know Issues” section:

 

• When Delay > Tesselator and Ratchet's Operation is set to "Mute All," the entire path is muted, regardless of whether the block is active or bypassed

 

 

Hope this helps/makes sense.

[themetallikid]

On 4/8/2022 at 6:46 AM, datacommando said:

Hi,

 

From the 3.15 Release Notes:

 

• Operation—Determines what happens to your signal when Ratchet is turned on (remember, it's bypassed by default)
  • "Mute All"—When Ratchet is on, THE ENTIRE PATH IS MUTED
  • "Dry Kill"—When Ratchet is on, only the effected signal is heard. TIP: With Ratchet on a parallel path, assign a second stomp switch to toggle between Mute All and Dry Kill. This lets you leave the block enabled and bring the effected signal in and out by switching between the two values
  • "Normal" (default)—When Ratchet is on, both the dry and effected signals are heard

 

In the “Know Issues” section:

 

 

• When Delay > Tesselator and Ratchet's Operation is set to "Mute All," the entire path is muted, regardless of whether the block is active or bypassed

 

 

Hope this helps/makes sense.

It does, but I'm missing how that applies to my preset.  I got it 'fixed' by also assigning FS7 to the Level B parameter in the merge block after the effect.  However, when I initially removed it from the Mute All/Normal function and only had it on Level B, it was also still present in the signal (all be it low enough to not be heard while I was playing).  It was only when both were assigned and engaged that it killed the entire signal so only my dry signal came through.