wpostma

The longer I use my PodGo the more I love it. And now with firmware 1.30 adding ability to name my snapshots, and 1.30 and the last others adding more and more effects (I love glitch delay so much) and amps, this thing is just stunning. Would I also probably enjoy a Helix LT? Yes, but the PodGo was half the price and does all that I need. It is so great.

I have several acoustics: 1. A sigma dreadnought with passive piezo pickup, no onboard pre-amp and the levels from this piezo are very weak, and yet the PodGo does a phenomenal job of giving up to +24 dB of boost to the weak signal just by setting up my presets. 2. A borrowed one from a friend (Yamaha) that has an onboard electric preamp and onboard EQ. With this one, the PodGo doesn't need to provide much gain but the reverb and delay (used subtly) add a lot to it, and the EQ on the PodGo is far more flexible than the onboard EQ. As a side note if you just want a credible acoustic sound the "acoustic simulator" in pod go does a passable job within the context of a full band mix, of giving me a strummed or arpegiated acoustic part, suitable for country or folk accompaniment, without changing to an acoustic. The big drag with acoustics is they are giant feedback magnets in a loud-stage environment. If you have a big resonant acoustic, and you can play it on a big quiet stage, great, but if you just need to not be the guy the sound guy is having problems with, you can get by without a real acoustic when you're not the center stage person.

Right. It's a combination of the workflows that you like and don't like, and the learning curves you can adjust to, and the actual capabilities. It is sad to me if someone gives up on the pod go before learning how to use it fully, because "plug it in and surf presets" is not a good way to figure out what it can do. If I had a Youtube Channel I think I'd do some tutorials, but I can't be arsed, to be honest, the video would go something like: Learn to build from scratch, read the whole manual, learn about the global settings FIRST not after 2 years. Learn to tear down and rebuild your signal chains. Learn to work with your amp without pedals, and learn the quirks of your amp or FRFR as well as the quirks of the pod go. There's something to be said for simplicity. For some guitarists, any modeller/multifx is going to be the wrong thing. You can see this clearly all over the guitar world. There are multi-effects players, and non-multi effects players, and many of the people who would hate the PodGo or any multi-stomp would have a lot in common. You can spend 10K on a pedal board including a GigRig effect loop switcher, midi foot pedals, and still not have capabilities that you can get in a Helix Floor. I think it's interesting that some people are more into an all in one "workstation" as the core, and many want to mix and match a dozen or more discrete boxes to build their floor boards.

You can get some hum and ground loop issues doing this Y cable thing.

Which podgo output did you use into the FRFR, and which global settings (line versus instrument) are you using for your inputs and outputs (read back all global settings for inputs and output levels).

> it has a specific amp out for this. My experience has been that the amp out sounds terrible into every amp I own, but your mileage may vary. Your ears, your rules. Do check out the global settings and make sure you have them set up right for your application.

Why don't you just use the four cable method in the manual? There is no advantage to a single cable into the amp, only disadvantages, such as the one you have discovered above, which is not getting sound when the FX loop block is on. Wired up four cable method, when the fx loop is ON, it will be sending out the signal to your preamp of your combo amp. WHen it's off, it will bypass that and you can use the modelled amps. If you get no sound, and you turned OFF THE PodGo PRESET'S FX BLOCK then you wired your cables up wrong. Check them. If you can't figure it out, draw a picture and post the picture.

For me the thing is I would want a VDI cable so I don't have to worry about the variax battery dying during a performance.

The expression/volume pedal sensor is an optical sensor. It is probably out of calibration. I have a similar problem with my older Pod XT Live.

Whether used as a volume or wah mode, the optical sensor on the internal built in expression pedal seems to have a range from 60% to 100%. The easiest way to see this is to move the pedal while editing a patch, and go to the wah page of the patch and watch the wah position value on screen as you move the pedal. All the way up to the toe position is 100%. All the way back to the heel the position reads 60%. Here's the thing, I own two of these and they are both doing this. Is there a trim pot inside the line6 podxt live that can be used to recalibrate the foot sensor? The external input also appears to be not working, but maybe it's just that m-audio volume/expression pedals are not compatible with the pod xt live. I have a Pod XT Live (guitar floor board) and Bass Pod XT (looks identical, but has different printed material, and different firmware). It would be useful to me to get the volume and wah working 0-100% somehow. No it's NOT the problem of having a minimum volume set above 0%, even with minimum volume set to 0%, yes yes I checked it, the volume pedal won't go below 60% of maximum volume. I'm thinking this 20+ year old pod xt live has experienced sensor drift/calibration issues. Ok. After removing all the bottom and side screws and removing the lid the mechanism is a simple metal bar in front of two optical sensors. Bending the metal tab closer reduces the minimum from 60% to 40% but it's NOT possible to do this without some kind of factory max/min calibration, I think. Perhaps the surface mount IR LED is not outputing the same intensity of light it once had. THERE ARE NO TRIM POTS on here, and I am not sure where the system recalibration menus were hidden in this dealy.

I did read it and it didn't help. Installing old versions didn't fix it on win10, and it works fine on win7.

That doesn't make any sense because using the SAME exact download for Pod Go Edit 1.21, it works FINE when I do it on Windows 7, so if what you're saying made any sense, then it wouldn't work on Windows 7, on a machine that has never had pod go edit v1.0 or v1.1 on it either. The PROBLEM is that WIndows 10 does not work with the PodGO with the provided usb drivers in the download. There is NO UPGRADE ONLY, if you go to the downloads page and ask it to give you a download the download it gives you for 64 bit WIndows WORKS FINE with Windows 7 and NOT with windows 10. If what you're saying is true then Line6 is to be chided for doing such a silly thing as shipping an "updater program" that would install fine without checking if there was all the existing content there it needed to upgrade. I happen to be a professional software developer and I know a thing or two about making installers for applications. (a) It would be a failure of their developers to actually CATCH this, (b) it would be user hostile of them to give you an UPGRADE-only binary, without asking if you already have a v1.0 updater. Imagine I just came home from the shop today with a brand new pod go. I go online, and then, what? I have to go wade through forum posts to find a series of binaries that might even install? I'd be sad and dismayed if Line6 was that lame.

This screenshot says it all. It's not a bad usb cable, because then the device wouldn't show up at all in Windows. Instead it's an issue where the device DOES show up in windows, but despite that, Pod Go Edit does NOT see the device. Pod Go Edit version 1.21. Pod Go USB driver 1.0.0.7. Yea yeah, we rebooted, yeah yeah we tried a different usb cable and also sacrificed 3 chicken sandwiches, using the approved Santeria ritual guides.

This is also happening with Pod Go. It seems to be a Line6 USB driver issue with certain Windows 10 versions. I am experiencing it with Pod Go driver 1.0.0.7 dated 12/1/2020, and pod go edit 1.21, but the same exact issue reproduces for other people using Helix and Helix's software. Windows 10 version 1909, build 18363.1440.

PodGoEdit was not open but I did have the usb cable attached to my pc. Will try leaving the USB cable unplugged but I wanted to leave it online so that I could use it to record audio from the podgo into my daw when I want it. I have seen another weird glitch with the footswitch colors. IN snapshot mode the four footswitches that show which snapshot is active should be white but sometimes they are another color. (Yellow or blue, or red).