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.

Almost certainly you are experiencing strange behaviour due to code conflicts between old and new firmware. Did you reset back to factory after the update? It's very important to do this because it's like a clean install.

When you say it's gone, do you mean it's greyed out and not available to select, or do you mean the icon itself has gone. If so, just in that patch or in every patch? Is it the same in both Pod Go Edit and the unit itself? UPDATE Just seen your pic and post on Facebook. As I suspected, you meant It's greyed out not disappeared ie you ran out of dsp to select it. First, you must make your posts clearer as you'll confuse people. Second, you really must read the manual and watch some vids to help you better understand how Pod Go works.

It's TRS so it should be balanced - but odd the ad doesn't actually say balanced (you'll notice the GAK link made it clear), hence I'd be inclined just to double check with them.

It seems to me that you likely have some software corruption. I recommend: 1. you back up your patches & do a reset back to factory again. 2. If the above doesn't resolve the issue then I recommend you re-install v2.0 & factory reset after the re-installation. 3. If none of this works you should then raise a ticket with Line 6 customer support.

@silverheadsaid "And I don’t believe there’s any difference between a speaker cable and an instrument cable" - huge, HUGE difference! If you get it wrong you can damage your speakers! Guitar cables are unbalanced microphone cables are balanced Speaker cables are unbalanced BUT they are heavier duty with thicker gauge wire because they carry a heavier load In theory, unless your FRFR and Pod Go are more than say 10m away you can use an unbalanced guitar cable and it shouldn't make a difference. However, I recommend you use a TRS stereo balanced cable ( I use a Stagg balanced stereo TRS cable) because some guitar cables simply don't give as good signal strength and sound. Note: A powered FRFR speaker is NOT like a guitar speaker cab, so you do not use a speaker cable. https://www.gak.co.uk/en/stagg-sac-stereo-jack-balanced-cable-6m20ft-sac6ps-dl/117208 See this video: And this one: And this is good to understand balanced v unbalanced if you want a bit more techy savvy.

When upgrading firmware, did you reset back to factory as recommended by Line 6? (backing up patches first, of course, to re-import). This is essential to get rid of any code 'remnants' from previous firmware versions that can cause odd behaviours (think of it as a 'clean install' when upgrading a PC's operating system)

When you updated did you reset back to factory as recommended by Line 6? If not, back up your patches and reset back to factory.

No it hasn't. The Prize Drive has only just been introduced in Helix v3.70 and as Pod Go has only just had its big v2.0 firmware upgrade, on past timescales I doubt Pod Go will receive this update for some 4-6 mths. Even then, not all the goodies in v3.70 will come into Pod Go because of its DSP limitations. So even assuming Pod Go continues to benefit from future upgrades the Prize Drive might not 'fit' into Pod Go.

Nope, it's not you - it's a great update and really makes a huge sonic difference!

Adding further to @silverhead post: The back up that the upgrade does is an all or nothing backup. I still do this BUT before I do anything I also back up every user patch, factory patch & IR individually so I can import back & can get into the settings of any individual patch I want because I'm saving each patch as a separate .pgp file. See here how to do this, and this guarantees you won't lose your patches even if the 'bulk' back-up done by the upgrade process didn't work for any reason. https://line6.com/support/topic/65646-tips-on-backing-up-your-pod-go/#comment-453863 Now, its recommended after the upgrade to reset Pod Go back to factory by pressing buttons C&D whilst switching Pod Go on. This will do two things. First it will upgrade the factory patches to the new cabs. Second, it will clear any residual unnecessary code. Pod Go is essentially a computer so think of it like this - on a PC, if you upgrade from windows 7 to windows ten, you can keep all your settings and programs or you can clean install for best results - so a Pod Go factory reset is like a clean install. "Now, if you import back the patches in the way I do, you'll put back all your user patches and IR's. If you've changed factory patches and want them back, you can still do that but now you can pick & choose which patches you import back. I had a load I didn't use so it was quite cathartic to only bring back what I wanted. If you create an 'all or nothing' backup (as you should) before doing the update ie the backup that Pod Go edit creates, that backup will include the old factory presets in the Factory folder ie without the new cab models. So if you do the factory reset after updating (again, as you should), & re-import the 'all or nothing' back up, you'll overwrite the new factory presets with the old ones unless you do the following simple procedure. All you need to do is expand the Presets tab under the Restore from Backup dialog and uncheck the Factory box. This way the old factory presets will not be included in the restored backup, and the new factory presets with all the new cab models will remain. Voila!"