voxman55

New Helix models (darker shading), Legacy models (lighter shading) - the manual does explain this. Older legacy models will use up less DSP and although there may be a very slight difference in tonal quality, most users won't notice. This gives some good options to have an effect you like but at a lower DSP cost giving you a bit more flexibility. Effects POD Go has nearly all the effects of the award-winning HX family of modelers, as well as selected effects from the classic DL4™, DM4™, MM4™, and FM4™ stompboxes and M13®, M9®, and M5® processors (indicated by the lighter shaded background rows within the following effects tables). Re the Rat, Line 6 discovered that the first Helix version was modelled on a faulty Rat, so they fixed it and added a 'correct' Helix version but they left the first version on as some folk liked it and had it in their presets. So you have 2 Helix versions and a legacy version of the Rat. It was covered in the release notes. Per v1.30 release notes ( https://line6.com/support/page/kb/pod/pod-go/pod-go-130-r986/ ) Distortion > Ratatouille Dist (Mono, Stereo), based on* the 1984 Pro Co RAT. Turns out our Vermin Dist model was broken. Sorry! We were going to replace it completely but a bunch of people had presets with the old version. On top of that, we found out our RAT's LM308 chip had crapped out since we modeled it last so we decided to get it into perfect working order and start from scratch.

You need to install Pod Go Edit v1.40 on your computer and then upgrade through Pod Go Edit if you are not already on the latest v1.40 firmware. You will then be able to see each patch in Pod Go Edit and see the parameters and settings for every fx, amp, cab etc. Please ensure you follow the upgrade instructions here: https://line6.com/support/page/kb/pod/pod-go/pod-go-140-r1037/

This has come up before. It's not a fault per-se - it's just an odd 'quirk' that's the same with all Pod Go units, mine included.

I use simple pitch for Eb tuning, eg 'Sweet child of mine', and have played it with a band. Works perfectly.

Odd - I can see the patch on custom Tone but the .l6t files are for POD Farm and/or the POD X3 series. They won't work with the POD Go. I can't immediately think why the file type has changed to this if it was created in Pod Go. After work I'll try changing file suffix to .pgp and see if my Pod Go recognises it. When you loaded it, did you go into Custom Tone and select the Pod Go Wireless icon first (see link below)? If you loaded it from a different Custom Tone device section, I'm just wondering if that might be the problem and might explain why Custom Tone is converting the file type automatically? https://line6.com/customtone/

See here: https://line6.com/support/page/kb/general-faq/studio-tone-vs-live-tone-and-the-fletcher-munson-curve-r448/

I recommend you raise a support ticket with Line 6 - I'm pretty confident they'll arrange to change it for you.

Personally, I would never buy Pod Go Wireless, at least certainly not 'as is'. I get the concept of having wireless built in for compactness and to avoid the need for an extra cable and PSU. But in my view Line 6 has missed the target and it's wireless delivery approach is flawed whereby PGW limitations far outweigh its advantages. Its three biggest issues are: 1.You can't charge it unless PGW is full on and there is no charge only option to conserve power. 2. You can't, certainly as far as I'm aware, use PGW whilst charging the transmitter, even with a cable. 3. You cant use PGW wireless 'as is' with any other gear because its receiver is by definition built in and non removable. Now add to this that a lot of users have reported problems with range, signal strength and channels. That one I'm puzzled by, because you'd think an integrated system would if anything be more efficient. But for whatever reasons, this doesn't appear to always be the case and reports suggest that most issues are not down to user error. The G10 Relay system doesn't generally appear to have signal or range problems. The only solution, which involves additional expense and defeats the very premise of PGW, but one that solves all the above, is to buy a G10 receiver base or even better a full G10 Relay or G10S which will then give you an extra G10T11. I use the Line 6 G10 Relay with my standard Pod Go, and I have 2 x G10T (Mark I) transmitters. So I always have a spare charged G10T, I can use my Pod Go with cables whilst the G10T is charging, and I can use wireless with any of my gear...any amp, any other MFX, pedal board etc. In addition, and as I mentioned, G10 Relay does not appear to have the signal issues experienced by some PGW users.

These are safe provided their firmware has been upgraded to v1.06 or later, following the Line 6 alerts ('Corrective Action required immediately for Relay G10, Relay G10S, and Relay G10T wireless products purchased prior to March 2020 '). See here: https://uk.line6.com/g10recall/#english

I think anywhere in front of Pod Go should be fine, but just experiment.

Yes. You can set the expression pedal to sweep through all 5 vowel sounds or any combination. But you won't get the Frampton/Walsh effect as you need the proper voicebox with the tube in the mouth for that.

Essentially, you can't actually use the Katana as a power amp simply because without an FX loop you can't bypass its pre-amp stage - which, for a modelling amp like the Katana, the pre-amp is within the digital amp model - even set clean, it's still modelling a clean amps pre-amp. But if you are looking for your Pod Go to do everything, by choosing a clean amp model with low gain, that's the best way to try and give your Pod Go a 'clean palette' to work with, with as minimal amp colouration as possible. Use the Pod Go main out and initially set your Pod Go for instrument and not 'line' - but by all means try both to see if there's any difference that you might prefer. Set and use all your patches as normal, with your signal chain in Pod Go just as if your Katana was a power amp. Typically, you'll want time based effects such as reverb & delay after the amp & cab model, and possibly even modulation too - just experiment to see which sounds best with your Katana. Re cab, because you are going through an actual amp cab with a real speaker, you'll essentialy be mixing two cab types - the one you select in Pod Go and the real cab of your Katana. So, you might not want to use a cab sim - but again there's no 'rights & wrongs' here - it's about experimentation to see what sounds best, so just trust your ears. Re gain/distortion you may prefer to use the Pod Go amp model, with or without a Pod Go distortion pedal, or you might prefer to use just the distortion pedals and turn the amp block off. If you decide to make a patch with just FX and with the Pod Go amp/cab blocks 'off', I recommend you select the del sol 300Sunn® Coliseum 300 pre-amp (not full amp) model. That's because you can't remove the amp block (as it's a fixed block) and even though you've turned the amp block off, it's still 'reserving' DSP for the amp model - & because this amp model uses less DSP than any other option, you'll have more DSP available for your effects.

Mine was within its 2 year warranty (it was bought from Yamaha Music London, who give a 2 yr warranty on all musical equipment....which is why I bought it from them, & they also beat the price of the then best price available which was great too). But it's irrelevant as Line 6 will fix it regardless of warranty because its a design/component issue and not a warranty issue.

Interesting 're tonal change following update to v1.40. I didn't notice it myself but then I have had my Pod Go 'done' re input impedance prior to the update. As you say, there's no mention of this officially in the release notes. The fix was a huge improvement and I'm now very happy with the Pod Go tones.

No you don't. The Pod Go is just a digital MFX unit so impedance of the Pod Go is irrelevant. What is relevant is the impedance relationship between the power amp and speaker cab. Impedance is vitally important if your power amp is valve because a valve amp has to have a correct load and an impedance mismatch could seriously damage your amp and or cab. But impedance is generally less important to consider with a solid state/digital power-amp that doesn't need to have a speaker load and where impedance will typically only impact on efficiency ie volume output. Some cabs will give you an impedance option eg one input socket might be 8 Ohms, and another 4 Ohms or 16 Ohms, or it might even have an impedance switch and/or a stereo connection option.

I use 2 Bespeco VM22 momentary switches that are clones of the Boss FV5 and half the price. In Pod Go external momentary works exactly like the on board switches.

Yes you do need to spell out when you come in from nowhere telling the guy he needs to change his phone when you had absolutely no idea what phone has has, and talking about towers! Then you're surprised at being queried. I think its a reasonable assumption that pretty much everyone will have a smart phone...even my 90 yr old dad has one. So to wade in assuming the OP was using an out of the ark G1 phone is simply ludicrous.

What towers? There was no mention of any towers in the OP and he didn't disclose his phone make and model, so what do you mean by 'doing away with those towers'? So perhaps somewhat premature to suggest a new phone is needed! And at a gig there will be a multitude of different phones around anyway. @Bahnzo Any phone or unit sharing the airwaves or mains can potentially interfere with signals and give rise to noise. But crackling and popping could have other causes that are nothing to do with phones. It could also be to do with lighting or the electrical supply quality ....using a line conditioner e.g. a Furman, can be very effective to clean up and stabilise electricity from the ring mains itself and digital gear is much more susceptible to interference than e.g. a valve amp. (In the US 'dirty' electricity can be a much bigger issue than eg in the UK) There are certain other simple things you can also do to help avoid or mitigate such noise. Check that you are using good quality cables and that your guitar is properly shielded and earthed, and that all inputs of your MFX, FRFR and guitar are clean. These can be safely cleaned with electrical switch contact cleaner but make sure its safe on plastics. I use Servisol Super 10 in the red and white can. Avoid plugging your Pod Go and FRFR into a shared socket with other devices e.g. your computer; use separate sockets for each wherever possible (unless using a Line Conditioner). Ensure you are using a good quality balanced TRS cable to connect your Pod Go to your FRFR, rather than a standard guitar cable, particularly if your cable is longer than say 3m. Also, see if the PG noise gate settings make any difference to the noises you are hearing. Hope this is of some help.

2 cable method? Do you mean 4 cable method? If so, its exactly the same with head and cab or combo. The common requirement is that your amp must have an fx loop. If your amp has a parallel fx loop rather than a series FX loop (you'll have an fx loop mix knob if it does) the design can vary and not all will give you 100% mix. This could impact on the results you'll hear when using 4 cable, or even just using your amp as a power amp only by plugging an MFX like Pod Go into the fx return. If your amp has no fx loop your options are limited to just plugging your MFX into your amps input, or having an fx loop installed.

It's not software; its simply an external independent script file that is patch specific. It therefore can't alter or corrupt the Pod Go firmware. Further, Line 6 is not only fully aware of JSON file manipulation but it has quite openly expressed surprise that this wasn't 'discovered' by Pod Go customers earlier. If there was any risk to Pod Go or that this might invalidate warranties, I'm pretty sure Line 6 would have said something and issued a warning before now!

AFAIK unfortunately not; it would certainly be a useful feature to have though. You can cut/copy/paste but if all 4 snaps have been used, this means you'd lose one which isn't helpful.

Yup, exactly this!

Hi. Firstly, a change in the JSON Patch script change is not a hack. This has nothing whatsoever to do with the firmware and it cannot in any way damage Pod Go. The worst that can happen is you might get some odd behaviour in the modified patch. Provided you don't try changing/ removing the amp, cab and EQ blocks the modified patch should work just fine. If these blocks are modified the patch may act quirky.

You might find that there is some loss of high end when using PGW with cables which is more noticeable on cleaner tones. In non wireless Pod Go's this issue is well known by Line 6 and its authorized service centres. It is due to a component issue on the main board relating to input impedance. On raising a ticket with Line 6 support, non PGW customers can make arrangements to have the issue remedied (Mine was fixed last month). Although service centres are not permitted by Line 6 to go into details, and Line 6 has formally made no comment, it's a quick, simple fix that appears to relate to a capacitor. In PGW, when used with the G10TII transmitter and inbuilt wireless receiver, this acts as a buffered device that brings back the high end. This is the same when e.g. a G10 Relay is used with a non wireless Pod Go. I'm unclear whether Pod Go Wireless has the same issue when being used with cables (do please let us know) but try it and see, and if you do find a high end roll off with cables, refer to Line 6 support in the first instance.

Fully agree. So its good to see Line 6 are fixing units on request regardless of warranty, which is the right thing to do.