voxman55

Re (2) don't forget you can still use stomp mode in any snapshot and kick in any fx or parameter changes you want using FS1-6. However, you can also add 2 external momentary foot switches and you can do the same thing with FS7/8. Whilst you can't (currently) see FS7/8 in the display (which would be a good upgrade if Line 6 could add it) and typically momentary switches don't have an LED, there is a very important advantage for gigging in using FS7/8 - and that is that you can activate these in ANY MODE without having to tap dance in/out of preset/stomp/snapshot modes. So, lets say you want to kick in a clean volume boost for solos (I do this by using the main out level, jumping from 0-3dB) you can set FS7 to do this & kick it in wherever you are. Or you might want to change mic models with FS8. Anything you can do with FS1-6 you can do with FS7/8 including multiple changes. It could be a perfect solution for you, and is what I do. I already had the Bespeco switches and Y cable but you can buy a small 2-button momentary switch complete with a single TRS cable (eg the Hotone Ampero switch) for only around $17 from Amazon https://www.amazon.com/Hotone-Momentary-Footswitch-Controller-Switcher/dp/B08H1NQCGJ

When did you buy your Pod Go?

When you backed up it should have backed up everything including your user presets. If you've reinstalled the backup and the user presets are definitely blank, I'm afraid this pribably means it didn't back up properly and your patch is lost. However see suggestion 4 below. If you have a favourite patch or patches it's always best to back these up as an individual .pgp file so that you can import back into Pod Go. However, I'm puzzled as to why the upgrade to v1.4 lost your user presets in the first place as that shouldn't happen. The fact that it did and that your backup lost the user presets suggests one of four possibilities: 1. That there is a possible issue with your Pod Go and it is not backing up properly. Contact Line 6 support, explain the problem and see if they can identify if there is a problem and how best to resolve. 2. That you didn't create the backup properly ie user error 3. That you created the patch in the factory settings section without realising it. Check the factory patches just in case your file is in there. 4. Your back up was good but that there could be a software glitch that is stopping Pod Go 'seeing' the user presets. When you upgraded to v1.40 did you reset your Pod Go back to factory before importing your saved backup. If you didn't, reset back to factory and then try reimporting your backup file. Are you just looking in Pod Go? Have you checked how it looks in Pod Go Edit? How did you upgrade firmware? Did you follow the instructions to install Pod Go Edit on your computer first, and then upgrade through Pod Go Edit?

I hear you, completely empathise, and you're quite right. Customers have had to pick all this up from boards, facebook, youtube etc because Line 6 has made no public comment on this whatsoever - it's approach has been that if customers approach them, the fix will be arranged free of charge. So they are responding well to those customers requesting a fix, and the issue in new units appear to have been remedied. Although we can all voice our theories in reality I'm afraid that no one, other than Line 6, knows why it has not adopted a more open & transparent approach.

Although Line 6 has not formally commented, you do seem to be somewhat out of touch with how Line 6 have been addressing this. There has been lots of info and discussion on the internet on this, including boards, Facebook, YouTube etc. In fact, if you'd read back just on this very thread you'd have seen 're the 2nd point below. First, the issue has now been corrected on Pod Go's being manufactured currently, but older stock sold as new may not have been changed. Secondly, for almost a year now Pod Go owners have been able, through Line 6 Support, to arrange for a free fix, irrespective of any warranty. I'm UK and had mine done with only a total 5 day turnaround, back in June. The fix is very simple and involves the removal of a capacitor in the input circuit although no one is very sure why the capacitor was there in the first place.

Can't answer that but there has to be something else going on eg perhaps the global EQ was on/set differently - but it's definitely hardware & not software.

Just as in real life, different guitars (esp with different pickups) react differently to different amp models. Don't think of them as similar guitars and disregard they each might sound similar direct with your amp. I recommend you create 3 sets of gigging patches, one for each guitar and set your 2nd & 3rd patch group to match your 2nd & 3rd guitars. If you switch to guitar '2' it's then a simple matter to switch to the 'matched' 2nd patch set and ditto guitar '3'. This is what I do re gig patches if eg I might use both my Les Paul & Strat.

With Pod Go Edit and Pod Go connected to your PC you can play Pod Go in live time through your computer and use it to play along to e.g. YouTube backing tracks, music vids etc. And it will play through your PC speakers.

As per our facebook chat, its hardware. Fixed by removing a capacitor on input circuit. Contact Line 6 support and they will arrange the fix free of charge.

My headphones are really loud, so it could be your headphones - what make, model and impedance are they? To get the best from Pod Go and other MFX you need studio monitoring headphones. Two of the best & most popular at a sensible & similar price are the Audio-Technica ATH M50x (38 Ohm) and the Beyerdynamic dt 770 pro headphones that come in 32, 80 and 250 Ohm flavours. The 32 Ohm is fine, 80 Ohm is the most popular with MFX like Pod Go, and are very similar to the 38 Ohm ATH M50x. The 250 Ohm are not recommended as these are too quiet. So if your headphones are straight hi-fi headphones for music/mp3 listening (i.e. not studio monitoring quality) and/or your impedance is too high, that could be your problem. Re studio-monitoring, it's not exactly the same thing but think of these as akin to a FRFR speaker cab re frequency response.

I think it's pretty much accepted now that when Helix gets an upgrade, Line 6 will then consider what might be able to come across to Pod Go but always subject to limitations of its lower DSP & memory, and different architecture to Helix. However don't hold your breath re timing - historically we could be looking 4-6 months for the next Pod Go firmware update. v3.5 Helix has new amp and fx models and so I think it's a safe bet these will come over to Pod Go (but same caveat re DSP/memory - Pod Go may not get all the effects but to date it has always got the amp models). Speaking purely personally, I'm really not excited re new amp/fx models simply because Pod Go has so much in it already and a lot of amp models and even some fx do sound very similar anyway and as a gigging player lots of subtleties get lost in the mix anyway. However, what's really interesting is that Helix has an all new IR based cab engine with dual cabs and movable mic positions off axis. Pod Go's 'weakness' (IMHO) is its stock cab models. I suspect this new IR cab engine is unlikely to be available to Pod Go (it was kind of already in Helix, but this is new and enhanced) but if Line 6 was able to give Pod Go some IR enhanced quality cab engine facility even in a watered down form, that would be really great. You can see Helix v3.5 upgrades here:

Or a foot-switch (internal or external eg FS7/8) - and with external foot-switches you can kick in the IR change, or indeed any change, from any Pod Go mode without having to tap-dance.

Alternatively you can add gain with a distortion pedal and/or mix the amp and distortion pedal gains to layer in different levels of distortion.

Sure, I understand the different options - but basically I just wanted to sense-check I'm not missing anything.

The default setting for these 5 knobs when you select a patch will depend on the amp, cab or fx highlighted in the view window. So if you always want the amp parameters to show whenever you select a patch, if you select the amp in the view window and save the patch it will always default to show the amp parameters. But here's a related question. I've selected a patch and the 5 knobs show amp parameter. I now want to tweak the reverb whilst I'm playing. In Pod Go, because it's switches are not touch capacitance type as in Helix, in stomp mode I'd have to switch the reverb off and on again for the 5 knobs to show the reverb parameters, which is a nuisance and clumsy. Am I missing something or is it just a limitation of Pod Go not having touch capacitance switching?

You can't swap snapshots, which is a nuisance. But you can copy a snapshot and paste it over another. But it means if you have all 4 snap slots filled, you'll end up losing one. Be great if Line 6 would fix this and give a swap facility whereby you can swap snaps around. You can do this with the footswitches so there's no reason this can't be done for snaps.

Look for the series of short Line 6 Pod Go videos that are perfect for what you need. But I also recommend you read the manual. It's well written and illustrated. There are other short videos too that are also very good.

Having an audition with a band next week - they play SCOM in D and was worried that simple pitch might struggle. Tried it, and seems to still work OK, hopefully it still sounds good 'live'.

Sadly no, but it's a great observation. Suggest you post suggestion for larger graphics, on 'Ideascale'.

One thing to try is to use the rear USB port of your PC, not front USB port. On many PCs the rear USB signal is stronger. Had this problem on my PC and using the rear USB port fixed the problem.

Yup, agree with you both and my eyes are not what they were either. Option for larger fonts would be a huge help.

Forgot to add that usually the mini fooswitches only require a single cable.

Hi @BlademanRH4 Pod Go offers the facility to add 1 or 2 external momentary switches in FS7 and FS8. Although called momentary/unlatching, in Pod Go they act as definite on/off switches and you do NOT have to keep them pressed down. These work exactly like the onboard FS1-6 footswitches which means you can assign any effect or parameter to these in just the same way, but with two important differences. First, currently Pod Go cannot display FS7/8 in the 'stomp mode' window. However, and this is a big plus that meets what you (& I) need, FS7/8 switches operate in ANY MODE including stomp or preset mode ie these can function just like the control switch you're used to. So if you are in pre-set mode you won't need to go back into stomp mode to eg switch an FX on/off or alter a parameter. There are different types of momentary ('unlatched') switches available ranging from smaller mini-switches to the Boss FS5U (single), FS6 and FS7 dual switches. However, these are quite expensive. Boss FS5U is a single pedal but 2 can be slotted together. There is no battery/power required but there is no LED to let you know when the pedal is engaged or not. Both the dual FS6 & FS7 can be set for latched or unlatched (ie momentary) mode but it is the latter mode you need for Pod Go. FS6 is battery powered only and has an LED. It will not function in any mode without a battery. This has the advantage of not needing an external PSU to power it but unless you remember to unplug it when not in use, the battery will drain. FS7 is mains powered only with no battery option. The PSU is an extra that you have to buy separately. However, you only need power in latching mode and/or if you want to see the LED. In momentary mode it does not need power to operate but no LED will light up. There are a variety of smaller mini 2 button momentary switches available in the market that have the advantage of being compact and typically cheaper than the Boss pedals. For example the Hotone 2-button Ampero momentary switch is only £19.99 UK but has no LED (most mini switches don't have LED's). The potential disadvantage of these smaller pedals is that they may be less stable on the floor (eg carpet) and in some types the switches can be quite close together which means they can be more awkward, especially if you have bigger feet, live. These will be conventional 'click' type switches and some makes/versions might have a noisier click than others that some users might find a bit annoying. As a gigging player my preference is to use 2 x Bespeco VM20 momentary pedals slotted together. There is no LED, but also no PSU/battery to worry about. They are all metal casing, lay flat, are very stable and the switching is smooth & silent. These are Boss FS5U clones but at a fraction of the price at circa £15 each UK. Connection to Pod Go is via a Y Stereo TRS (single end to Pod Go) to 2 mono cable (one for each VM20). Here's my Pod Go with these.

First, reboot your computer and then try Pod Go Edit. Sometimes a reboot will fix any corrupt system files. If this doesn't work, see next bit. What computer/laptop/operating system do you have? If you have a windows PC/laptop do a search for MSVCR100.dll to determine if the file is missing or if it is there but not being recognised. Go to command prompt, right click and open in admin mode. In the command window type in sfc /scannow (the space before the slash is intentional). This will check the integrity of your windows system files (inc .DLL files) and will repair or replace any missing or corrupt files. Takes a few minutes to run so be patient but you can still use your computer in the meantime). This is a safe bona-fide Windows check and cannot harm your computer. (see here: https://www.lifewire.com/how-to-use-sfc-scannow-to-repair-windows-system-files-2626161 ). Once finished, restart your computer and run Pod Go Edit to see if this fixes the problem. If it doesn't, search for MSVCR100.dll to see if the file is in your system. There are numerous youtube and website help sites to guide you re how to install MSVCR100.dll into a folder that programmes like Pod Go Edit will recognise. (This is a windows system file by the way, so reinstalling PG Edit probably won't help).

To clarify, it is in ALL the Pod Go Owners Manuals, the latest of which is the Pod Go v1.20 Rev D and the subsequent Pod Go Wireless and Pod Go combined manual Rev D. There is no v1.40 Pod Go Manual. You are referring to the Pod Go EDIT Pilot's Guide v1.40 which is A guide to the features and functionality of the Line 6 POD Go Edit application and it assumes that users have first read the Pod Go manual. Hence it doesn't duplicate the fx model background - but as it is only a short descriptor and the Edit Pilot Guide does duplicate the FX model tables, perhaps Line 6 should add it to the Edit manuals too for consistency.