voxman55

Interesting, and not something I was aware of. That sounds a bit worrying, and must have been very disconcerting at a gig. I think some kind of 'visor' cardboard or plastic box with a lid to angle to shield the Pod Go should help solve the problem. Or even, as below, using a gig bag positioned to cast a shadow and shield it. Bright sunlight can cause various problems with MFX/pedals not least because it can make some displays and LEDs difficult or impossible to see. In addition to similarly having optic sensors, the Helix and Helix LT displays both give problems in bright sunlight, including issues with seeing the Helix scribble strips. I did a gig in bright sunlight with my Vox Tonelab SE. The main display is LCD which was fine, but you couldn't see the red and green LED display for the tuner which normally are pretty bright. Whilst I had a separate tuner in my gigbag it wasn't a pedal type ie that I could connect in front of the TLSE. So I then sussed that if I put my gig bag behind the TLSE to cast a shadow over it, then I could see the tuner LEDs sufficiently well. If I'd have taken my Tonelab LE I wouldn't have had the tuner problem because it uses the main LCD display and in addition to LEDs you can see the LCD tuning meter in bright sunlight.

@NMON1234 I think @phil_m nailed it. I would however gently suggest that if you intend to submit further posts here: 1. As Phil suggested, paragraph breaks make posts much easier to read 2. Try and keep your posts a little briefer and a bit more succinct so it's easier for folk to read and thus to help you. There were large segments of your post that seemed to go off somewhat at a tangent (some might say a 'tirade'!) and deflected from what you wanted to know. This could deter folk from reading it or responding, and thereby you could miss their opportunity to help you. 3. This is a very helpful community with a lot of very knowledgeable folk - so all you need do if you have any queries is ask in a simple and straightforward manner, and folk here will always be pleased to try and do their best to help, just as Phil has done. Nuff said

Interesting - Jason is spot on; I've just checked it and it does go down to 400Hz in Pod Go and then displays 400Hz in PG Edit. But the moment you touch the High frequency on PG Edit it only goes down to 2.0GHz again. As you say, it's a glitch in Pod Go Edit that no doubt they will correct in the next firmware upgrade.

I don't necessarily agree with that statement as an 'absolute'. It can give good results but it very much depends on what you want to achieve. It also depends on what FX you use and the type of FX loop. A serial FX loop will usually give better results than eg a parallel loop that might only give you a 70-80% maximum 'mix'. If you connect a MFX unit into the FX return, you are bypassing the amps input stage and purely using the amp as a 'power amp' which makes using your MFX and set-up much simpler. It's often just a case of experimentation to figure out what option sounds best for you. Of course, if you want to use your amps natural distortion then 4-cable is the way to go. The biggest downside of 4-cable is that it's more awkward and 'messier' to set-up, not just needing more cables but also setting up your pedal board or MFX unit in a way that gives you the results you want. There's some good articles here on 4 cable, inc set up details: https://guitargearfinder.com/guides/use-four-cable-method/ https://rolandcorp.com.au/blog/4-cable-method-4cm https://blog.andertons.co.uk/learn/what-is-4-cabl There's a good video here too, with a line 6 Helix:

Might possibly be added in the next firmware update....whenever that might be. Line 6 never really give any advance notice though so we'll just have to wait & see.

Keep it simple. If the borrowed amp has an fx loop, I'd just go into the FX return to use it as a power amp, and let Pod Go and your normal settings do the work. Otherwise, go through the front, keep the amp clean and your normal patches will still likely be OK. But in case, set up a basic fx only patch with what you need, e.g. a distortion, reverb, light delay, and modulation e.g. phaser or chorus, and I'd set the EQ as a lead boost at the end of the chain. That way you have a simple stomp arrangement to control your tone as you need it. In my view 4 cable is a pain and I honestly don't recommend it. It's hard enough to get everything balanced with your own amp, let alone with a strange rig.

I think this enhancement is only in Helix, not Pod Go, as far as I'm aware.

I just found out that HX Stomp didn't have SS and footswitch naming until the last firmware update. That could well explain why Line 6 didn't want to give these to PG until all the Helix units had it. I can well appreciate that Line 6 might have got some stick from HX Stomp owners if PG had these first.

I would say the facilities are not unusable, but certainly their intended utility value is more limited. Its not unlike mfx units that have 200 user slots but just patch numbers with no patch naming. Even the latest Boss ME80 suffers from this which in my view is by today's standards archaic and why I never even considered that unit even though I liked its design of essentially being a collection of stomp boxes. I have a 32 patch memory in my Vox Valvetronix that had patch numbers only. It didn't stop me from gigging, I just set the patches in gig order and showed the patch number by each song on the gig song list. So, these facilities are still useful to a point but I agree are quite restrictive. On my PG I have added 2 momentary switches in FS7 and FS8. I would like to see an option for the 6 slot display to be 8 so that these footswitches can be seen. I'd also like to see an option for FS7 and FS8 to be selected as patch up and patch down controls when in the 6 stomp window. Its a nuisance to switch in and out of stomp mode to scroll patches. The 4 stomp mode is pretty useless unless you've set your patches to fit. My biggest disappointment is that for a unit that is supposedly designed for pick up and go to take to band practice and gigs, falls short from a functionality perspective. Whilst I don't need all the extras in Helix like dual routing, more processing power, more amps or fx, etc, I do need functionality to use effectively at a gig. Sadly, my view is that Line 6s focus in 1.21 was largely influenced to satisfy bedroom players that are ever wanting more amp and fx models to play with. It seems to me this was an easy win for them on the back of Helix models. Because bedroom players are the majority target market for Pod Go, there has been less attention to features that home players don't really want or need, but gigging players very much do. So I think there needs to be a better balance here and we can only hope that Line 6 does recognise our genuine needs here and provide us gigging players with some meaningful improved functionality that we need. After all, hopefully we are important customers too and we are not being unreasonable here?

Lol! A bit extreme, but I think most would agree with the sentiment 're functionality. Snapshot and multi switch naming are by far the most requested enhancements needed in Pod Go. Line 6 have said it's high up on their list of to dos on Pod Go. I'm not sure why these weren't included from outset. Its possible the extra programming could have delayed it's launch. Or it could be that Line 6 wanted to keep a bigger differentiation between PG and Helix. But with Helix now on firmware 3.1 the gap is now pretty big so I dont think giving this enhancement to PG now will impact on Helix sales.

Studio monitoring headphones are most likely to sound similar to an FRFR speaker but as @silverhead pointed out, you'll never hear exactly the same thing. That's because headphones send audio straight to your ears in an enclosed, focussed manner. With a speaker including powered FRFR you are hearing tone that's being pushed through the air before it reaches your ears. It's quite different. And it's why no recording can capture what you feel as well as hear, when you are e.g. standing in front of a 4x12 cab pushing all that air! But, I can recommend the Headrush FRFR cabs that come in 2 flavours - a 1x12 (FRFR112) and 1x8 (FRFR108). I opted for the latter as I wanted something very compact and light. The quality of tone and volume from something that small is quite astonishing - I was stunned when I heard it. Although both variants kick out 2000 watts, the 112 is as you'd expect a fair bit louder as it's pushing more air. It's not that much more expensive, but it's a fair bit bigger and around double the weight. Virtually identical to the Headrush are the Alto Truesonic FRFR powered cabs, that are probably made in the same factory as they have near identical looks & inputs and control layouts. The TS312 is the 1x12, the TS308 is the 1x8", but they also now offer a 'middle' 1x10 version too - the TS310. In the UK these range from around £190 for the 1x8" to £240-250 for the 1x12". Any one of these will sound great with your Pod Go. It just depends on the size you want. I've been so pleased with the FRFR108 that I may well buy another one!

The Sony MDR7506 headphones are studio monitoring so these should sound good. See here for links to some free IR's:

Interesting question. As far as I'm aware it's 'either or' but as I don't have a PGW, I stand to be corrected. But even if you could, as you only have a single signal path in PG where both guitars would use the same tone, I'm not quite sure how valuable that might be anyway?

Before you start paying for patches, you should consider the following: 1. There are lots of patches shared on the Pod Go section of the Line 6 Custom Tone 2. Patches are created using the sellers gear and tastes. You may love them but you may hate them and could find your purchase disappointing 3. Almost certainly you will need to tweak patches 4. You could be better off reading the manual, and watching videos on how to build patches. Pod Go is intuitive but it's not plug and play, and learning yourself is the very best thing you can do 5. Try some of the free IRs that can help you find your tone too. 6. Be wary of sound clips and video clips promoting patches. These almost certainly will sound quite different with your gear. 7. If you use headphones invest in a good set of studio monitoring headphones. Something like the Audio Technica ATH M50x 32 Ohm or the Beyerdynamic DT770 Pro 80 ohm are both only around £120 and are two of the most recommended for Pod Go. I'm not saying you shouldn't buy patches. But I am saying you don't need to, and if you do buy, that they may not be the instant plethora of tonal satisfaction you might have hoped for. But your money and choice of course.

The base receivers are fine and will charge the G10T II. It was only the G10T mk1s that burst into flames. Lol

Could be a software corruption. Do a full back up in PG Edit, reset back to factory by pressing footswitches C and D as you power up, reimport your saved patches and see if the issue is still there.

No probs, glad to help.

I think it can be 'corrected' by placing a buffered pedal (eg a Boss pedal) in front of Pod Go, which you can leave switched 'off'. I use a G10 Relay with my Pod Go which I believe does the same thing.

I must admit it did seem odd. But no, I don't think it would have been an over reaction to hold off until it was remedied - for a bedroom player it's one thing, but its highly inconvenient for gigging/band practice. But assuming its fixed, then that's academic now. For my needs I'd always require an independent wireless capability anyway as I have other gear. Thanks for the explanation re bluetooth latency.

I completely get your last point, and it's actually the point made in this review vid: But if all you are using is PG, doesn't that make your observation on latency somewhat academic? The video raises 2 good points: 1. It should have had Bluetooth for complete wirelessness with earbuds. 2. I don't know if this has yet been fixed, but there appears to be no global wireless setting and you have to set each patch for wireless. If that's right, it's nuts and seems the biggest reason not to buy PGW until fixed?! I don't agree with his third point though. Many customers, me included, have wireless gear already or dont want wireless, or want independent wireless, so why be forced to pay quite a bit more for something you dont want?! I think both options are right, to give customers choice. If there was only PGW I definitely wouldn't have bought it.

But you lose flexibility if you want to go wireless with e.g. a straight amp, a conventional pedal board, or any other MFX unit. With the G10 and G10S the charger is independent, and you can use the G10 wireless without having to charge from PGW. I'm also not sure I quite follow your explanation re how the PGW would differ from using e.g. the freestanding G10 or G10S? Would there be any discernable difference in tone or range? I appreciate you need a cable to connect PG to G10, but you only need a short pedal cable and I can't see that will make any discernable difference?

This is partly why I was struggling to see the point of the Pod Go Wireless, as it would make more sense if the G10T II receiver could be powered when PGW was plugged in but without having to power up PGW.

Thanks for the clarification - I didn't realise that buffer = preamp; interesting, so I looked it up after your post to better understand how it works and it said: "a buffer pedal is a tiny amplifier that isolates the incoming high impedance signal sent from the guitar into a unity level. Put simply, it preserves the strength of the signal running through your setup". Which is simple enough even for a nonce like me to understand!

Interesting solution ...I have a Boss CS3 and GE-7 EQ and will give that a try. Sorry if this is a silly question, but does the pedal have to be powered to benefit from the buffer? Hold on, just had a thought...I play wirelessly via a Line 6 G10 Relay...I think this acts like a buffer as the tone seems a little brighter than with a cable and might be why I haven't experienced the problem you've been having?

The latest version is 1.21 that has some additional amp and fx models including a very good acoustic simulator. But unfortunately there are no functionality improvements with this upgrade and some users have reported difficulties with the upgrade installation. I'm on windows 7 with destop PC and had no difficulties with the installation although I had to reboot my PC to see the new models.