voxman55

Digital Igloo has confirmed Pod Go will definitely be getting a big update. I suspect as per v2.0 Line 6 will be doing a 2 for 1 combined update again to incorporate the last two Helix updates (subject to dsp limitations). I can't think it will take too much longer so fingers crossed.

This always confuses people, but you have to read the manual. Main out and amp out are the same in standard factory settings other than amp out is mono. You have to change global settings to cut off the cab/Ir and anything after these when connecting to amp out. IMO it's a very misleading labelling, and what Pod Go really could benefit from is a simple global option to turn off cab and/or amp modules when going through the front of an amp or the fx return. The current option means you'll lose any fx after the cab in your patch. See p8 item 20 in PG 2.0 manual.

As Helix now has the 2203 model, it's anticipated that the next Pod Go firmware upgrade will have this as its not using an excessive amount of DSP and should fit into Pod Go. Users were hoping it might be released by Christmas this year as its been over a year since v2.0 but nothing has yet been announced. Hopefully it's not too far away.

If all you need is a clean volume boost, it's easy to do by adding a 3-5dB main out level increase and assigning it to either an on-board pedal in stomp mode, or an external momentary switch which you can kick in regardless of mode (snap, patch, stomp) you're in. Simples!

Yes. It's how I often use my Pod Go. I keep it in stomp mode and use F7/8 for patch up down. Details are in the manual, top of p44. Global switches and pedals, you can set how FS7/8 functions.

I'm afraid not. I don't like two button presses either, but I must admit it works well with Pod Go and although I thought it would be a problem, it's worked very smoothly.

I think the Pod Go is hard to beat at it's price point, but Line 6 mfx aren't for everyone. The thing about Pod Go is that there is so much in it and every update adds more. Whilst that's great for most of us, Pod Go isn't 'plug 'n play' and there's a lot to learn. Some folk want something a bit simpler to use with less 'option paralysis' and they are prepared to accept a bit less functionality as a trade off. I was very curious to try out the Valeton GP200, made by Sonicake, and I bought one on approval to put through its paces and compare with my Pod Go. I actually liked it a lot. The GP200 seemed well made, sounded as good as Pod Go, was largely easier to use, and it had some excellent features that Pod Go could benefit from. Of course it also lacked certain features in Pod Go. Ultimately I returned it because it didn't meet my gigging needs, but for home users the issues I had with it may be less of a concern. And if Sonicake can fix the main issues I had, I could well be tempted to buy it again. You can read my detailed assessment here: https://drive.google.com/file/d/1Cq8dk60mWy5gJ_1YveeRtM4-701y0pd7/view?usp=sharing

Yes. there are certain modified patches available where the JSON script file has been modified. This is NOT a firmware 'hack' - it's simply an alteration to a single patch file. There are various versions of these freely available and Line 6 is fully aware of these (in fact they were actually surprised folk didn't figure this out sooner!). These modified patch files will give you more 'user' blocks but at the sacrifice of something eg the fx loop or a wah pedal. This could even include sacrificing amp and cab blocks. However they do NOT increase Pod Go's processing power, but will release some of the DSP allowance previously 'reserved' for the removed item. JSON modified files that remove volume, wah or EQ won't save much though because these use very little DSP to run them. That's why you can only change the model of volume, wah or EQ in these blocks and can't eg put a reverb or distortion in them - it would be like trying to fit a football into the space set aside for a tennis ball! Some of these JSON modified files are more 'stable' than others. By less stable, these can't harm your Pod Go and they can't affect any other patch file. But for example you might find a file offering 7 user blocks with amp/cab blocks deleted might be fine with 6 blocks but give odd behaviour eg it won't let you use the 7th block, or if you put a looper in it the looper functions might not work properly.

Yes, provided you don't save your changes, when you press the patch selection again it will revert to the original but your changes will be lost. If you want to toggle back and forth then you can do this with snapshots. If your parameter settings are being automatically saved, if you go to global settings you can choose for Pod Go to automatically save or not save your parameter changes. As I said, you really need to read the manual.

V2. 01 fixed a single bug, which was incorrectly explained in the release notes. In v2. 0 when you changed patches there was a very slight DROP (not a ramp up) in volume. In my view it was almost imperceptible and when it was pointed out to me I had to go back and listen carefully to hear it and even then it was only there if you changed a patch whilst eg holding a chord or holding a lead note. Line 6s 'fix' was to replace the split second of volume drop with a split second of silence. I'm still not sure which is preferable but frankly for the odd occasion when you might want a seamless patch change, using snap shots might be fractionally faster. BUT even then it depends on how many and which parameter changes you've made. Particularly when changing delay parameters and multiple parameters, Pod Go does this in an order sequence and because of its more limited single chip processing power, even with snapshots you'll sometimes hear an odd artefact for a split second. Only mfx with significantly more processing power like Helix or the Boss GT1000 can deliver truly 'instant' switching with no lag, at least not that the human ear can detect.

It's unlikely to change as even Helix doesn't have this.

I strongly recommend you invest time to read the manual and watch some videos. The manual explains that you can use snapshots to tweak parameters and go back and forth with the original to compare your changes.

Just the volume on the FRFR - the FOH main board controls the XLR signal

You could connect a 2 in 2 out simple switch box that acts as a kill switch. Any decent tech could make one up for you if you can't find one ready made.

There is no problem with Pod Go Edit or updating through it. The problem is with your computer, USB port, cable or a combination. It sounds as if there might be some conflicts happening and or possibly file path corruptions. Your computer might benefit from maintenance including disk cleaning, defragmenfing, and if its a PC running disk check.