poodad

Use a 1/4" Y cable to "jump" the pod go's effects send to effects receive. Place your effect send/receive block after your effects but before your amp block. Turn effects send on and remove the stomp pedal from it so that you don't accidently turn it off. Connect the Y cable female jack to your guitar amp with a guitar cable. Connect the pod go's main out to your FoH. Et Viola! Your signal splits after your effects out to your amp and also continues through your amp and speaker sim blocks to FoH. NOTE: I've been told you can do this without the Y cable by playing with the effects send/receive settings. But I haven't tried it. If anyone form Line 6 reads these messages, please note that the current AMP OUT settings needs a third choice: "before amp block"

Line 6 knows that if knowledge of this defect becomes wide-spread some lawyer will whip up a class action lawsuit which will cost them millions of dollars. Think that wouldn't happen over a falsely advertised input impedance? Sole just got nailed for $3.6M for advertising their treadmills with incorrect horsepower rating. Considering the impedance problem was created by putting a 1nF shunt capacitor in the analog input, it would be impossible for Line 6 to argue the advertised 1Mohm was somehow an honest mistake.

You don't need a BOSS pedal. Any pedal that is not true bypass will work to isolate your guitar signal chain from the relatively low input impedance of the go.

But you aren't under non disclosure. Tell us what was involved from your point of view.

No, the Pod Go's input impedance has been measured independently by a couple of people (at least) including me. It is around 250K Ohms. This is far lower than the 1M Ohm stated by Line 6. There is no need to drag the Helix into the debate - that is a red herring. One can simply turn off all the blocks on the Go and compare playing directly through the Pod Go verses playing with a buffer buffer pedal in front. The difference is striking. Someone on the facebook Pod Go group posted a snippet of the Go's schematic clearly showing a 1nF capacitor shunting the input to ground, and a picture showing the location of the offending cap (C126 if memory serves). The post was removed within hours - Line 6 probably threatened legal action. That cap would definitely cause the low input impedance. And no amount of firmware changes can remove that cap. I suspect that if Line six does anything at all to address this, they'll simply add a generic high end boost in the signal path in an attempt to mask the problem. But so far, Line 6 is ignoring the problem. They have not addressed it here even though it was brought to light in February. There's a thread on The Gear Page discussing this issue and the Line 6 employees who regularly participate on TGP have not commented despite being directly asked.

The official response is no response. There's been nothing official here, and the two Line 6 contributors active on The Gear Page have refused to comment.

That's how I do it - with the effects send/receive. I don't see any reason you couldn't connect the Go's effects send to your effects chain, then come out of the last effects unit into a MFM Y cable. Run one side of the of the Y into your amp. Run the other back into the Go's effects in. Main out goes to mixing board. Remove the stomp button from your effects send block so you don't inadvertently disable send/receive. For the life of me, I can't figure out why the AMP OUT doesn't tap the signal in from of the AMP block by default.

I have also measured the input impedance and found it to be around 205K at 1KHz. Someone posted a clip of the the Pod Go's schematic on one of the facebook Go groups showing a 1nF cap to ground in the input section, which would explain the low impedance and tone suck. The person also showed pics of the board showing where the offending cap was (C126 if memory serves). Unfortunately, the post was deleted shortly after it was posted. Of course, it could have been a fake, but it looked legit to me. Two people on the gear page have opened support tickets because of this issue, The first person says Line 6 "repaired" their unit but they have no way of measuring the input impedance, so they don't know what line 6 did. The other person was told to pound sand. This can't be fixed with a firmware update. My fear is that Line 6 will band-aid a fix in the form of adding a hidden compensating curve in the output EQ to digitally boost the attenuated high frequencies. I really wish Line 6 would address this issue.

The default setting for amp out is to include the speaker simulation. Goofy default, but it works for what you need. Another option would be a splitter cable. Either way you may need to use a DI box with an isolation transformer to prevent a ground loop.

The pod go isn't going to contribute to a ground loop because its signal ground is not connected to mains earth ground. I suppose you could get a ground loop condition from your guitar amp and the powered speaker. In that case, I'd recommend connecting them both to the same outlet to minimize the size of the ground loop. You can also use ground loop busters, or an isolation transformer in one of the signal paths.

Use a 1/4" Y cable to jump the go's effects send to effects receive. Out of that Y connect to your guitar amp. Place the effects send/receive block just before your amp simulation black. Turn effects send on and remove the stomp button from it so that you can't accidently turn it off. Put all of your effects before the send/receive block. Now you have signal with no amp/speaker simulation going to your amp, and signal with amp/speaker going to the powered speaker.

Lol, you wouldn't happen to be John Paul Jones, would you?

The only thing I can think of is to use the effects send for the mandolin output. and either the amp out or main out for bass. Your mandolin presets would have the effects send turned on. The bass presets would have it turned off.

The AMP out options do seem to be the wrong things. You'd think there'd be a global option to make the AMP out tap the signal before the amp simulation block. In fact, that should probably be the default. I guess there are three possibilities: 1. It was overlooked by the programmers. If this were the case, I think it would have been fixed by now. 2. It was an error in the circuit design. If that's the case, it can't be fixed in existing models. 3. This is an intentional misfeature put in place to keep the go from becoming too much of a threat to the Helix business.

Old laptop bag for me as well. Nicely padded and lots of storage for cables, extra strings, tools, etc.