PG "penalizes" 4CM users - and how to fix

[jedisb]

I was a bit spoiled coming from a Digitech RP1000, which had a dedicated FX Loop and AMP Loop, neither of which forced you to give up anything else in the signal chain. The problem with the Pod Go is that if you want to use 4CM you are forced to "sacrifice" a block for the effect loop, even though you're not really using it for effects, but an amp. Additionally, the DSP for the disabled amp and cab models are still counted against the total DSP for the patch, even though you aren't using them. 

 

I think a better solution would be the following:

• Create a Global "Send/Receive Function" setting that allows you to choose FX loop or AMP loop as its function
• Create an "AMP Loop" amp model withing the AMP effects block
• When set to FX Loop the PG functions just as it does now, with FX Loop being an effect type that uses a block. The " AMP Loop" model would be greyed out and could not be selected.
• When set to AMP Loop the PG would do the following:
  • Disabled the FX Loop effect type
  • Enable the "AMP Loop" amp model within the AMP effects block - therefore you aren't wasting the amp block on a model that is disabled, and you still have the block that would have been the FX Loop for other effects.
  • When "AMP Loop" is chosen as the amp model the cab block automatically gets disabled as well. (I'm guessing this still wouldn't free up the DSP this block uses.)

 

You could still place external effects in that AMP loop before it hits the external amp, or after the external amp via the amp's effects send, but you would need to engage/disengage them individually with their own footswitches.

 

The only downside I see would be that you couldn't switch between an internal amp model and the external amp within the same patch, but I'd willing give that up to get back the extra block.

[silverhead]

Post this suggestion to Ideascale if you want the Line 6 developers to see it.