phil_m

This is where the new Mute All and Dry Kills options under the Operation parameter that was added to the Poly Sustain model in the 3.10 update comes in. It was added for this sort of thing. You put the Poly Sustain on the parallel path and rather than control the bypass state with a footswitch, you control the Operation parameter and set the Min to Mute All and the Max to Dry Kill. That way, even though the block is on, it’s not passing signal when Mute All is active (footswitch unpressed), the sustain effect comes through when you hit the footswitch while killing the dry signal.

Yes, the Guitar In is the charging input for the G10. Line 6 used to sell a little USB to TRS charging cable, but they recalled it for potential safety concerns. I think they were concerned about the possibility of over-charging.

If you have a regular TS cable plugged into the effects send, the right side won’t receive any audio, so, yeah, that’s the issue. Or more accurately, I guess, is that there’s no connection being made to right send, so the Send R block in your preset will mute the signal when turned on.

Going to need some more details here... Where are you hearing or seeing clipping and how do you have things connected?

No the sends and returns will all work independently of each other. Do you have a TRS to dual mono breakout plugged into the Stomp’s send jack?

No, those aren’t per preset settings. For all intents and purposes, I guess you could think of them as global settings, but, I tend to think of it as the footswitch modes exist outside and independent of the preset. You can, however, assign snapshot and preset function to footswitches in Stomp Mode using the Command Center.

No such setting exists. Hit the Mode footswitch.

The latency with Bluetooth is so high that using it to monitor guitar isn’t viable. Even the lowest latency Bluetooth systems at the moment are still pushing 100ms of latency. He must have been using a beta firmware for this review. This was changed with the firmware that was released shortly after the PGW announcement. It’s not a global setting, but all the factory presets have Guitar + Wireless set as the input setting now. I believe it’s also the default setting for a blank preset now. Basically, the beta firmware for the PGW was the PG firmware, so all the details for the wireless implementation hadn’t been ironed out with that firmware... I mean, even so, I think not buying it because of that particular reason seems a bit over an overreaction. If you like the rest of the feature set, changing the input setting for the presets you want to use is a simple thing to do.

Please don’t take this the wrong way, but are you sure you’re saving presets properly? I haven’t seen this come up anywhere else that I recall. Anyway, if you’re sure you are, open up a support ticket.

Discernible? On its own, I’m sure not not. But latency is additive, so anytime you can reduce, it’s a good thing. The difference between using the PGW compare to the PG with a separate wireless system is that with a separate wireless system, there’s a conversion at the transmitter, and then another one at the receiver’s output. Then there’s an additional conversion going into the PG’s 1/4” in. With the PGW, there’s only the analog to digital conversion at the transmitter. So its bypassing an entire round of conversion. Beyond that, there’s simply the convenience factor of being able to show up at a gig and literally only plugging one thing in and being ready to go. I mean, sure if you want to do other things with a G10 system, than do that, but if someone wants to gig just with a POD Go, having the PGW is just a great convenience.

Well the point is you get a digital wireless audio without any additional A/D-D/A conversions compared to using a standard 1/4” cable.

If the storage well charged the battery, it would also drain the battery while the unit was powered off. This is just how the G10 transmitter works. So in that case, it wouldn’t really be useful as a storage well.

Have you done a factory reset since receiving the unit? Doing the firmware update doesn’t reset the factory settings.

I don’t understand what you’re saying the bug is. The EXP1/EXP2 state is saved with the snapshots. That’s the expected behavior. If you have a dummy cable in, you’re telling the Helis that you have an external pedal connected to EXP2, and the on-board pedal is always EXP1. Basically, the saved snapshot value overrides the pedal state when you change snapshots. This was actually something people asked for after snapshots were introduced, because it meant if you switches snapshots while the wrong state was active, the blocks tied to the toe switch got out of sync with their saved states in the snapshots.

Did you do a factory reset and restore from backup after updating?

Remember that the Global EQ isn’t applied to the USB out, so if you have that on, what you’re hearing over the analog outs is not what’s being sent to the USB audio stream.

I would return it or open up a support ticket. When new, you should be getting close to the expected 7 hours life. That’s what I’m getting with mine. Are you sure you’re charging it to full capacity?

You need to have the Stomp Footswitches setting under Global Settings>Footswitches set to 10 Stomps. This is only available on the Floor and the Rack, not the LT.

Yes, there is. It would require additional processing power. Think about the signal flow. You'd have one signal going through, passing through the bypassed cab block and then get processed by whatever blocks were after the cab block. Then you'd also have another signal, going though the cab block, being affected by it, and then that signal would need to get processed separately from the non-cab signal. It would require additional DSP. In order to do something like this on the Helix, you'd have to set up dual paths, with at least the blocks after the cab duplicated on both paths. So that's why it's not possible on the POD Go.

As already mentioned, I don’t see how anyone could accidentally change those global settings at a gig, as they require multiple button pushes just to get to the menu. It would mean they were trying to change some other setting, and in the process changed something else, which even if that were the case, having a settings lock wouldn’t really help them... As far as the tuner reference pitch, I suppose it’s within the realm of possibility. I’ve seen it mentioned maybe three or four times over the last 5 years that someone accidentally changed the reference pitch. I’m not sure why your foot would necessarily be near that knob while tuning; though. Anyway, I don’t think it’s something that’s going to change at this point. It seems that making changes to the basic operation and use of a device after it’s already been on the market for five years isn’t all that likely.

I don’t know about that... I can’t recall any multi-FX processor that ever had any sort of prompts like that for changing various settings. Usually, you just set them, and that’s that.

Set the output for paths 1A and 1B to Path 2A. Then set the input block for Path 2 to None. I’m not entirely sure what your intention is regarding stereo separation here, but with what you have shown here, both signals will be summed together when they hit the amp block in Path 2.

You can’t disable the cab block, per se, but you can set the Amp Out 1/4” output to tap off right before the cab block in the Global Settings menu. Of course this means that any blocks you have after the cab block wouldn’t affect this signal. So if you wanted to still use all your blocks in this scenario, you’d need to have the cab block as the last thing in your presets.

Um... You’re lucky you didn’t burn up your computer as well. The RJ45 jack on the amp isn’t an Ethernet port. It’s sole purpose is to connect one of the Line 6 FBV foot controllers. It sends power over one pair of wires, so you probably created an overload condition. You may very well have actually damaged your computer’s Ethernet port as well.

Yes, you can do that.