voxman55

This has a longer, thicker cable than the Line 6 PSU and is straight pin too. I have one, and works at least as well as the original: https://www.ebay.co.uk/itm/165299950217?hash=item267ca51289:g:decAAOSw31Jfyl4n&amdata=enc%3AAQAIAAAA8H1v15g%2Ff%2FHhVIn8cMlf2h7MHf4y4tR6wA%2F5Oi8Wo9wyK3XcxdiFxiXJ2RsIE3WfvMqWTGRd6q1kdGls%2BYGPOs4eWdE9KRPCHEnqCjQlOefkdwEZ8V%2BT422eecMi6H%2FTg22Q0XLUNp77OU3UpwoGSUdJXC%2F9TDGSwIleNDCPeCkq3SRZSPdVA9bccqpo89urmEMVIdxw4yW%2FPsvoTdaFdEWVQIpZ1l8iqjRqtZBzsckGj2%2FLD5mPt3%2FjRbnQ0zjmTaIgtXNEoIm9vkIWokBkim5Y5oH7whT15%2FTqsPQQLtK1OrYtNyDBQGaDz0B2hIRixQ%3D%3D|tkp%3ABFBM6v33rc9i

Just an idly curious & probably silly thought here Silverhead, but Pod Go has been designed to accept external momentary footswitches to perform as latching footswitches (I use two with mine for FS7/8). So I was just wondering what would happen if you connected a latching foot-switch (I don't have one to try) - would it (a) behave the same as a momentary (in which case why would you need a momentary switch?) (b) not work or work unreliably/oddly, or (c) act in reverse like a momentary switch?

When you say 'no matter what settings' are you using a lot of gain and are you gain stacking ie your patches have amp, distortion and compressor and these are all set high? Are you using external pedals? Is this happening only at eg gig volumes, or is it happening even at bedroom volumes? Is it happening on cleaner patches too? Now, when you say feedback, there are two kinds - good and bad feedback. Good feedback is normally only achievable at higher volumes and/or standing close to an amp, its 'musical' & its controllable by damping strings, ala Jimi Hendrix etc - but if your guitar is giving a horrible unmusical 'howling' even at low volumes that you can't control, then one or more of your guitar pick-ups may have gone microphonic and need to be potted/repotted. In case you're unfamiliar here, pickups go microphonic when the (normally) tightly wound pickup coil wires begin to 'loosen' and vibrate, causing 'howling'. Potting is a straightforward & inexpensive process (but best done by experts) where the coil is dipped in hot wax so that when it solidifies it fixes the wires in place and stops the vibration & the horrid howling. What guitar are you using? Assuming it has more than one pick-up, does it feedback on both? If only one then that pickup has likely gone microphonic. Do you have another guitar to try it with to try & narrow down whether its your guitar or your Pod Go or possibly even something else?

The amp out is factory set to be the same as the main out except in mono. If you want to cap off anything from the cab onwards in your signal chain you have to set Pod Go up for this. Unless you want to simultaneously send the full chain with cab model to the FOH PA, it's pointless using amp out - simply use main out and turn the cab model off: p7 of the manual: 20. 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.

Is this just on one patch, or on every patch? It could be your polarity needs to be changed. See p38 of the latest manual "If your external expression pedal appears to work backwards—for example, a Volume pedal block is loudest with the heel all the way down—set this to “Inverted.”" Go to: Global Settings > Switches/Pedals>page 2, knob 3 - EXP 2 polarity

I think what Silverhead was alluding to re 'soon to be outdated manual' is that Line 6 are working hard on Pod Go v1.50 - we don't know when it will be released, but as its been some time since the last upgrade fingers crossed it's not too far away now - so I'd certainly save your paper & ink for the moment as its likely there will be a revised v1.50 manual and Pod Go Edit manual once it is released.

Do you mean incompatible i.e. you are opening & seeing Pod Go Edit but that it's actually telling you it's not compatible with your Pod Go? O(r are you unable to connect to & Open Pod Go Edit. If the former, what version firmware do you have in Pod Go? If it isn't v1.40 you either need to update Pod Go to v1.40 (highly recommended - there isn't a 1.41 - that was just a minor tweak to Pod Go Edit) or use a version of Pod Go Edit that's compatible with your Pod Go firmware.

I suggest you contact Line 6 support as even if the unit is out of warranty, it's always possible Line 6 might consider extending good will & dealing with this as a warranty repair.

I haven't done this myself but try removing the volume pedal assignments and turning off the volume block.

You posted, got a fair and reasonable response which pointed you to Ideascale. The place to raise requests for Pod Go enhancements is not here -its on the Line 6 Ideascale site. And for the record I do not like rude people who act like a child and have a hissy fit and call people names because they don't like the response. You are a new contributor who has only made 4 posts. If you are to remain a contributor here please act like an adult. This is a safe, friendly, knowledgeable and helpful community and its important it stays this way without rudeness, harassment or bullying. I've never had cause to report any post on this community before but I consider your post has crossed that line, & is inappropriate. @Line6Tonyperhaps I can leave this with you to action as appropriate, thanks.

This applies only if the amp out is specifically set to do this - otherwise the factory default setting is that the Amp out is the same as the main out (except it's in mono & unbalanced). Per p7 of the latest manual: 20. 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. There was an enhancement in v1.30 that changed the way the Pod Go volume knob worked - I can't recall if this also affects the volume pedal behaviour: Global Settings > Ins/Outs > Volume Knob Prior to 1.30, POD Go’s Volume Knob only controlled the Main Outs (and Phones out, of course). Now you can choose whether it controls the Main Outs, Amp Out, or both. IMPORTANT: When connecting POD Go's AMP OUT to the input of a guitar or bass amp, we strongly recommend leaving Global Settings > In/Outs > Volume Knob to "Main Outs," as turning the Volume knob with any other setting will be like adding many boost pedals or attenuators between POD Go and your amp; that is, it'll probably sound totally wrong. Only set this to "Amp Out" or "Both" when connecting the Amp Out to a full-range, flat response (FRFR) speaker, studio monitor, or similar playback system.

Your headphones are fine. Check your global output settings.

I haven't tried it but in theory if you add 1 or 2 external momentary footswitches in FS7/8 you should be able to do pretty much do anything with them that you can do in FS1/6. The disadvantage is that FS7/8 don't show in the LCD display and you typically can't see when the switch is on or off. A big advantage is you can engage these in any mode ie preset, stomp or snapshot modes. This is particularly useful for lead solos at a gig where you can set a boost to kick in without eg having to go into stomp mode.

Even with comparable amp, cab and fx models and assuming DSP is within Pod Go parameters, tones will be similar but not exactly the same. Key differences are: 1. New cab engine in Helix v3. 5 that Pod Go doesn't yet have (but anticipated in forthcoming Pod Go v1. 50 in some form) 2. Notwithstanding the above, Helix already gave more mic control than just distance in Pod Go 3. Helix benefits from some tonal fidelity improvement from over sampling. Pod Go DSP allocation was already maximised so oversampling not possible. BTW, if you need more user fx slots, although DSP isn't increased, there are. Pgp patch files with modified JSON script available from face book groups and YouTube that will offer this with a trade off of swapping for something else eg fx loop or wah pedal etc. These are not hacks, are nothing to do with firmware, and are perfectly safe to use. Those on the FB Pod Go free patches group have been checked and are stable. Others may give odd results, but it's just for that patch only.

Seems to have been removed from YouTube, sorry.

Looks interesting guys but I can't help thinking that its going to be somewhat limited in practice as most Helix users will be using longer FX chains, FX, amps & cabs that Pod Go doesn't have, dual routing, dual amps/cabs, and then there's the cabinet engine and over-sampling differences which will make it virtually impossible to match Helix tones. The forthcoming Pod Go v1.50 will help to level the playing field here but we are still awaiting this from Line 6 (in fact, it's a year to the day since Pod Go got v1.40).

"I of course eliminated amp and cab emulation in the Pod Go onboard and have ONLY effects" And there's your problem!! - why on earth did you do that?? I think you are getting a little confused. When you go through a real guitar amp, you will want to turn off amp and cab because you are already going through the preamp & poweramp section of a guitar amp (if you are going in front of the amp) or if you go through the FX return to use your guitar amp as a power amp, you'll turn the cab sims off (because you're going through a real cab) but may still want to use the amp models because you're now not going through a preamp section - but you could just run effects because you are running through a poweramp but your tone may be bland. But if you are going into the main board you are NOT going through the preamp and/or power amp section of a guitar amp and your tone will be 'flat' - its similar to going through an FRFR set up that adds no colour - and because you are NOT going through a real cab you will need cab models to give some girth/dynamics to your tone, but going through front of house is also ideal for running an amp model. Even if you just want to use effects, you should still add eg a clean amp model & cab in your Pod Go - it will change everything!! I gig either through FOH and/or through FRFR powered speakers and its precisely because I'm not going through a guitar amp that I'm now free to use my Pod Go or other MFX to their full potential and run amp/cabs. That's how you should be using your Pod Go through the board.

For whatever reason, there is no explanation of when to use pre-amps in the manual. Some folk use it to reduce DSP load in exchange for having more basic amp controls. If you are going out the FX return of your amp, & this using it as a power amp, you might be thinking that if you are using your amps power section you only need a pre-amp Pod Go model. However, its the full amp model that delivers the relationship/interaction of that specific amp models power amp & pre-amp sections & its that combination that gives that amps character - just going through your FX return doesn't really give you that. So the simple answer is, just use what sounds best to you - if you prefer the full version use that, & if you prefer the preamp version with your amp, use that. But using the pre-amp model can be a useful option when using certain cab IR's and this vid might be helpful to explain why.

Helix v3.5 came out on 3/11/22 i.e. around 8 mths ago. For more straightforward firmware upgrades it normally takes 4-6 mths on past history to transfer across to Pod Go. So, why is v1.50 taking so much longer? It's because Pod Go v1.50 is very different to any other Pod Go firmware upgrade that Line 6 has done previously because the new cab engine requires some fundamental restructuring of the algorithms in Pod Go, and Pod Go Edit also has to be re-designed to manage it. Although Helix v3.5 was marketed as a brand new cab engine, in practice Helix already had a cab engine so it had the right 'base' that supported the enhancements in v3.5. Pod Go is sort of a half-step behind in that it doesn't have that same underlying cab engine structure so the redesign is taking longer. I did wonder, although I accept this is very unlikely, that because Helix is now on v3.6 whether Line 6 might even do both at the same time. At this juncture we simply don't know what will be in v1.50 e.g. whilst Pod Go is single routing might Line 6 find a way to give some form of dual cab facility in a single routing format? But following a number of posts complaining that Line 6 was treating Pod Go as a less important product, and that it's customers weren't as important to Line 6 and 'could wait', & querying why Helix was always first with upgrades, Line 6 responded on 12th June 2023 on the Gear page: Far be it to obligate myself to post in one of several dozen places I frequent every X weeks to keep the kids at bay, but... yes, we're still working on POD Go 1.50. Not including the new cab engine would mean we're stupid enough to not understand the advantages in making POD Go the best-sounding multieffects under $500... by a not inconsiderable amount. And we're not stupid. The reason POD Go's update cadence follows Helix/HX's is that its DSP is a subset of Helix/HX; that is, we have to develop for the Helix/HX platform and then figure out how to port as much as possible from it over to POD Go; it doesn't work the other way around. We've been transparent about this from the get go. <Heh. Get Go. I'll see myself out.> At no point has anyone at Line 6 ever said anything like "Oh, it's the cheaper box. Let them wait." Eric Klein, Chief Product Design Architect, Yamaha Guitar Group | Line 6 | Ampeg | Córdoba | Guild

I have a patch for Sweet Child of Mine on Custom Tone you can try that lets you toggle between standard tuning and Eb in stomp mode. Seems to work really well for Eb - it's important to have the pitch shift right at the start of your signal chain. Let me know how you get on? https://line6.com/customtone/tone/5868979/

Line 6 are most certainly not stopping upgrades, they are still commited to Pod Go, and are still working hard on v1.50 that will have the new cab engine. The difference with v1.50 as compared to all previous upgrades that focused on eg amp/fx is that the new cab engine means there are some fundamental changes needed to Pod Go's underlying architecture - it's not easy to do, and hence the time lag from Helix v3.50. Posted by Digital Igloo (Line 6) yesterday on The Gear Page (to various posts around the internet suggesting Pod Go was less important for them, folk saying why does Helix always get stuff first, & it might not have the new cab engine etc): " Far be it to obligate myself to post in one of several dozen places I frequent every X weeks to keep the kids at bay, but... yes, we're still working on POD Go 1.50. Not including the new cab engine would mean we're stupid enough to not understand the advantages in making POD Go the best-sounding multieffects under $500... by a not inconsiderable amount. And we're not stupid. The reason POD Go's update cadence follows Helix/HX's is that its DSP is a subset of Helix/HX; that is, we have to develop for the Helix/HX platform and then figure out how to port as much as possible from it over to POD Go; it doesn't work the other way around. We've been transparent about this from the get go. <Heh. Get Go. I'll see myself out.> At no point has anyone at Line 6 ever said anything like "Oh, it's the cheaper box. Let them wait."

"Bias Bias Changes the bias of the power tubes. Lower values achieve a “colder” Class AB biasing. At maximum, the amp is operating in Class A. Bias X Determines how the power amp tubes’ voicing reacts when pushed hard. Set low for a tighter feel. Set high for more tube compression. This parameter is highly reactive with the Drive and Master settings."

I bought one of these - actually better - thicker, longer cable: https://www.ebay.co.uk/itm/164036024339

Are you sure its not showing in the display but just not turned on or not assigned to the expression pedal? If it's physically missing in the Pod Go display i.e, there is no volume and/or wah icon in the display, the patch you've loaded down could be a modified patch to give more than 4 user blocks with the volume and or wah pedals removed to make way for additional blocks? (did the patch have any text explaining this?). A modified patch is perfectly safe to use, these don't void warranties, they cannot damage your Pod Go, and cannot affect other patches. A modified patch is just where the JSON script code in the patch file has been modified (you can learn all about these patches on the internet and forums - sometimes unkindly called 'jail-break' patches).

Unfortunately this is not an uncommon issue, with umpteen reports of problems with Pod Go Wireless on every guitar forum that I'm on. Some are simply set up issues, but others are just inextricable. For example, where a second guitarist is using the Line 6 G10 Relay with no problems re range, signal quality or drop out, the guitar using PGW has the same issues as you regardless of channel. Even Line 6 customer support haven't come up with a plausible explanation as to why PGW seems to be less reliable than the Line 6 G10 Relay when on paper it's the same wireless system albeit with PGW giving channel control. Logically it should be more, not less, reliable. I have a PG and G10 Relay, and have to say if anything happened to my PG I'd only replace it with a PG and would never buy a PGW. Sorry this isn't helpful but other than checking set up, or rebooting your PGW back to factory and/ or changing the channel it's difficult to offer you any other guidance than suggesting you refer to Line 6 customer support. But based on what I've read on many forums I'm not sure how helpful they can be. Needless to say there are loads of PGW owners who are delighted with it, but I appreciate it's no consolation to those having problems.