voxman55

I think its fair to say that Pod Go has been a victim of its own success. 2 yrs ago, at that price point, there really wasn't too much, if anything, to compete with it. It offered Helix quality modelling in a light, compact unit, with a great screen and good features at half the price of a Helix LT. It had some initial bugs that took a few goes to resolve, and the improvements in v1.30 that added footswitch and snapshot naming and colours made it way more useful for gigging. It's still a very good unit and I'm very pleased with it. I did research thoroughly before buying it so I pretty much knew what to expect from it. But 2 yrs on, competitors have got into the Pod Go target market, and attacked Pod Go with a vengeance. The Mooer GE300 has come way down in price, Zoom launched its G6, the feature packed Valeton GP200 is offering some top end features at an incredible price point, and the new Boss GX100 has really set the cat amongst the pigeons at the sub £500 price point from a quality provider, with touch screen, up to 15 non fixed blocks, fully programmable control switches, all metal construction, blue tooth capability, MIDI, and polyphonic pitch shifting. And its simpler approach to align certain amp tones with specific IRs has proved popular and appears to give more dynamic tones with less effort. Obviously, and as always, views may differ here but customer feedback on the GX100 has been very favourable. Pod Go still has many good things going for it, e.g. snap shots, light weight, compact footprint, ability to hold 128 IRs, huge choice of amps, cabs, mics and fx, decent footswitch layout, global volume/ wah switching to name but a few. But it's lack of DSP power, fixed block design, part plastic construction, lack of proper XLRs, issues with the optical expression pedal in sunlight etc now regretably means that its 'new' shelf life isn't going to be very long. The PGW version has always puzzled me and I still really dont 'get it'. My view is that for new customers, its now less likely go be attractive. The input impedance debacle hasn't helped here, and neither has Line 6s intransigence not to add 2 additional user blocks and free up the amp and cab blocks away from fixed status to give more flexibility as a straight fx platform. Views may differ but IMO I think Line 6 has now squeezed every ounce it could from Helix technology that is now 7 yrs old. Large Helix size units are not really wanted now by most customers, and I fully expect to see Line 6 coming out fairly soon with a new range of MFX with touch screens and enhanced quality, DSP, XLR, blue tooth, and improved feature sets with fully programmable control switches and no fixed blocks...that concept has now well and truly flown, as users want control and choice.

Yes there are of course some other disappointed users, but that disappointment is entirely down to them, not Line 6. They either did not adequately research what they were buying and just made assumptions, or they bought it in the hope that a future firmware upgrade would give them what they want. Trust me on this, Line 6 was completely open about who Pod Go was for and it's limitations as compared with Helix. If I thought for one moment that they had misled customers, I'd be the first one to take issue with them!

As this relates to a design and/or manufacturing component issue, it isn't relevant whether Pod Go is under warranty, other than the process to have the fault rectified. FYI the UK service centre put the following in its repair report: "Fault info: Input impedance issue. Action taken: We have identified a component issue in your unit that results in an audible roll off of high frequencies in certain scenarios. We can't get into component details because of the proprietary nature of our products". So there you have it, evidence that it is a component issue!

I think there are 3 options. 1. Enjoy Pod Go as is. For most users this is unlikely to be an issue. For those wanting more top end on cleans: 2. Use a buffered device in front of Pod Go. This might be e.g. a Boss pedal or a wireless system like the Line 6 G10 Relay, which is a buffered device. 3. Arrange to have your Pod Go rectified by a Line 6 authorised service centre. If your Pod Go is under warranty, contact the retailer you bought it from, in the first instance. If the retailer isn't helpful, or if you are out of warranty, contact Line 6 support to make appropriate arrangements. To be clear, this is a design issue and accordingly it is not a warranty issue, which is why Line 6 has made no public comment to address this. They and the Line 6 authorised service centres are fully aware of the input impedance issue, and it is straightforward and quick to remedy. The service centres are not allowed to share details but various sources seem to concur that this involves (not necessarily solely) a capacitor removal or capacitor change. I had mine done a few weeks ago by the UK Line 6 authorised service centre who arranged collection from and return to my home, with a total turn around period of 5 days. The repair report said: FYI the UK service centre put the following in its repair report: "Fault info: Input impedance issue. Action taken: We have identified a component issue in your unit that results in an audible roll off of high frequencies in certain scenarios. We can't get into component details because of the proprietary nature of our products". So there you have it, evidence that it is a component issue. The service centre confirmed that the fault had been rectified; It now sounds similar with cables as it does via my buffered G10 Relay. Excellent customer service btw.

@thiagofenderand @Clsc There are thousands and thousands of customers who are happy with their Line 6 gear. However, no manufacturer can please everyone. I'm sorry you are both unhappy but you both need to move on and buy another mfx that you like. But these pointless posts have to now stop please. These are doing no one any good. If you persist, I will have to ask the moderators here to remove you.

No, I dont work for Line 6. Ive openly been quite critical of Line 6 on a couple of themes, so do a search for my posts and you'll see them. My criticisms relate to Line 6s 'vision' for Pod Go that hasn't adapted to competition. Key themes are that I believe Line 6 should add 2 more user blocks, and to 'free' the amp and cab blocks so that they are not fixed. Also, to provide DSP info with each model plus an overall DSP meter, in the way that the Zoom and Mooer pedals do. I am always ready to help folk, and support sensible rationalized views that are balanced. What I have absolutely no time for is people who rush to buy gear without doing the proper research to ensure they understood what they are buying, and then blame Line 6 and Pod Go unfairly. Its akin to buying a 1.6 litre BMW with no sat nav and only front powered windows, and then moaning because a car that sells at half the price doesn't have the same power and extras as a 3.0 litre 525i with sat nav, all round electrics, cruise control etc. People that expect that are quite frankly just plain stupid. In other words, you can't expect a unit costing a third of Helix to have the same power and options. Line 6 has always been completely open about the limitations of Pod Go right from the off, and made it abundenfly clear that is is a POD and not a Helix. For those wanting more processing power and access to all Helix models and features, Line 6 has always said those customers will need a Helix. I researched Pod Go thoroughly so I knew exactly what it could and couldn't do before I bought it. As I've said, once a successful mfx comes out it's then relatively easier for competitors to come up with their own MFX that offers improved spec. You have to appreciate that Pod Go did lead the market at this price point when it was launched more than 2 yrs ago, and it's simply not fair to criticise it as against later units. Choosing an MFX today is a different proposition with much more competition e.g. Zoom G6, Mooer GE300 ( much cheaper than 2 yrs ago), and the Boss GX100. So, you need to be realistic and understand what has happened since Pod Go was launched. Blaming everyone but yourself for your lack of research is simply not a mature approach. If you are unhappy with your Pod Go, sell it and get something else.

If you want your Pod Go repaired and are under warranty, in the first instance you should refer back to the original retailer to make the arrangements. If you are outside your warranty, or if the retailer is not providing assistance, you should refer directly to Line 6 who should agree to arrange for the repair. Remember, this is a design issue rather than a warranty issue.

OK. But firstly there is no excuse for being rude. Secondly, I appreciate the difficulty where languages might be different. However, tools such as Google translate are available. Most importantly, if there are features that are crucial to you like poly pitch shift, then it is 100% your responsibility to ask specific questions. Line 6, or folk here on the Line 6 community page or any Pod Go Facebook page or Pod Go or Line 6 board or forum anywhere on the internet, and even folk on youtube would have been pleased to help and answer any queries you might have had. Then you would have been in an informed position when choosing which MFX to buy. I appreciate your personal disappointment but language differences are not an excuse for you not to have undertaken proper research, and to ask specific questions...you should never assume things about any piece of gear, because every manufacturer is different and every piece of gear, and at all price points, will have pros and cons. Anyway, Nuff said...and I genuinely wish you well in finding an MFX that more closely fits your needs.

Well, thanks for your gracious response to my offer of help. Good luck with your new unit. If you'd researched Pod Go properly before you bought it, you'd have avoided your disappointment and bought something else from outset that suited you better. I think it's safe to say that no one here will miss your posts.

No probs. Ideascale is the best place to float ideas as its where Line 6 looks.

Oh, I fully agree. That's pretty dire and clearly he doesn't know how to use it correctly...it's nothing like the way I have my drop Eb tuning set up. Once I'm back from hols next week I'll post my Sweet Child of Mine patch for you to try.

None of that in v1.40. See the Helix 3.15 update which is largely what Pod Go will get.

I use simple pitch in Pod Go for drop Eb tuning e.g. SRV, Sweet Child of Mine. Works really well. You need to put it right at the front of the signal chain though, even before the volume and wah, and you need to set it correctly. Once I'm back from hols I'll post a patch for you to try.

What famous woman in which band? With the possible exception of one effect (possibly Heliosphere but tbc) Pod Go will get all the new amps and fx in Helix v3.15. You can see all these if you go into the Helix support section. If you are expecting polyphonic pitch shifting in Pod Go, Line 6 has confirmed ad nauseum that Pod Go will never get this because it doesn't have sufficient processing power.

I don't know what the delay is. Last month there was just one bug they needed to fix.

Does sometimes feel like Pod Go is a 2nd class citizen when it comes to firmware upgrades.

Not sure why v1.40 is taking so long. A month ago there was a single bug to sort.

No need to research. Pod Go has an inbuilt noise Gate at the beginning of every patch signal chain. If it's not switched on, switch it on and adjust it's threshold and decay settings until you find a good balance as between noise reduction and playing dynamics. See the bottom of p16 of the Pod Go Wireless manual 'input settings.

Just as in the real world, chains that include high gain amp settings, distortion, compressors and boosted EQ will be noisier and require a Noise Gate. This is far worse for single coil guitars (unless these are noiseless pickups). Every user also has a different tolerance for noise, and it also depends on how you are using Pod Go, which eg will be noisier through the front end of a tube amp than through FRFR or a FOH PA. So it's a combination of factors. And its an issue with buying patches that someone has created to sound good with their gear, but if your gear is different then you will always need to tweak it. Noise gates are a useful tool but the trick is to find a sensible balance as between acceptable noise levels and dynamics, and not just set the noise Gate to maximum which will kill dynamics.

@Ashman86by all means try this but I'm not sure if this will make any difference as the amp & cab are turned off. The manual says: "AMP OUT This unbalanced output is meant to send directly to the front of your guitar amp. By default, it reflects the same output as the MAIN outputs (except in mono), but it can be globally switched to be tapped off directly before the Cab/IR block. This way, you can send a cab-emulated signal to your mixer (or FRFR speaker) while simultaneously sending a non-cab-emulated signal to your guitar amp." So unless you want to send a cab emulated signal out to the mixer or an FRFR, which you can't do with the Princeton anyway, as far as I can see there's no difference (other than a mono signal). I'd suggest using the Main Out but moving the delay to after the chorus. I'm not sure if the white block is the EQ; if it is, I'd place the looper after it so it's at the end of the signal chain. The EQ can be set to cut the high end and add bass and mid frequencies, so I'd use the EQ to help you get a better tone. Also check that the tube screamer isn't set with too much treble. However, check first that you've set Pod Go's Global Settings 'in/Outs' to 'instrument' and not 'Line'. If you're set to Line it might account for the more trebly tone. " Main Out Level: Choose “Line” when connecting the MAIN OUT jacks to powered speakers or mixers; choose “Instrument” when connecting to stompboxes or the front of guitar amps. When using a single speaker or amp, connect only the LEFT/MONO 1/4" jack.

Well, we're now a month on from Line 6 saying that v1.40 was essentially done and that they were just ironing out some bugs. Can only assume that these bugs were more problematic than they first thought. Or perhaps they've decided to modify in some way what v1.40 might include. Either way, lets hope that we hear something soon from Line 6 're v1.40.

I play in cover bands. I simply create a gig set and call the patch by the song name. Lets say I create a patch for rolling stones 'Brown Sugar' and I use the same patch for 'Honky Tonk Women'. 3 songs later My Gig set of patches places each one in gig set order, and I'll duplicate a patch where it's used again - so when I get to HTW 3 songs later, I don't have to worry about going back to Brown Sugar, or remembering its the same patch - I just go to the next patch which is HTW. It makes no difference if I've used a completely different amp model or effects set up to someone else's patch called Brown Sugar...if I think the tone I've created works, then that's all I need. If someone created a patch for something else and I thought, hey, that would work well for a completely different song, then I'll use it and rename it.

It doesn't happen automatically - you have to set the snap shot name and the colour of the footswitch it relates to. Colour is only on the footswitch. It would be cool if Line 6 changed the colour in the snapshot window to correlate with the footswitch colour.

Since v1.30 footswitches can be named and colour coded. Unused footswitches in snapshots can be set not to light up and you could name them 'empty'. So if you have done so and go into snapshots, you'll immediately be able to see, of the 4, which ones are 'live'.

Agreed - but generally to sound better you'll want a wah at the front of your signal chain.