voxman55

??

Many thanks for the update @Digital_Igloo and all the guys at Line 6 that worked so hard on this for us. Really great to have our first proper Pod Go update - rockin'! Not sure if it's just me but I might have found a BUG in Pod Go Edit v1.21 So, I've upgraded pretty much without a hitch although for some reason, possibly drivers, I had to reboot my Windows 7 PC. But its upgraded fine. Love the Horizon Drive, Princeton and the acoustic sim. However, when I add the acoustic sim I don't get the little 'x' next to the little round on/off button in Pod Go Edit so once added, I can't delete it. If I select the block with Acoustic Sim and try to select 'None' effect from the FX options, it comes up with an orange warning line at the top of Pod Go Edit saying "Failed to clear model,function not implemented [code-3]". If I add it and then try to remove it by undoing, I get a warning box that says "Failed to undo edit buffer. function not implemented [code-3]". If (before I've saved the patch with Acoustic Simulator added) I select another patch and then go back to that patch, then the Acoustic Simulator doesn't appear. But once I've saved it, I can only remove it via Pod Go.I can remove it in Pod Go itself.(Actually, I can remove it in Pod Go Edit indirectly by first replacing with another fx model and then deleting that model, as everything else does have the 'x'). Is anyone else having this glitch on their new Pod Go Edit v1.21 or is this just me? Also, and this could of course be intentional & due to the acoustic simulator using more DSP than the fixed EQ allowance, but in the fixed block you don't see it as an option - only if you go to the EQ models in a user block. Bit of a shame as you can't then swap the fixed EQ for the Ac Sim. UPDATE I think I know what Line 6 have done - because they've added the Acoustic Sim to the EQ section, which is a FIXED BLOCK, the Acoustic Sim has been categorised in Pod Go Edit as a FIXED BLOCK and can't be deleted directly, hence no 'x'. But because (I'm assuming) it's using more DSP than the fixed DSP allocation in the EQ section, it doesn't appear in the FIXED BLOCK EQ options. So I suspect it's an unintentional 'bug' that Line 6 needs to fix. I'm also getting Pod Go Edit connection problems that I never had on the previous version. I don't know if this is a bug in Pod Go Edit or Pod Go but I think there's definitely something wrong somewhere.

Or delay it of course.

The G30s battery door is the problem most cited by users and is just down to a weak design aspect of an otherwise very capable and popular little unit. Rubber bands seem to be the most popular 'fix'.

Update: the numerous reports on various forums that even brand new units seem to only give around 2.5-3 hrs battery life would appear to be accurate. Having waited a month for a new replacement, my brand new G10T holds charge for only 2.5-3hrs. Line 6 this is simply not good enough. If the Boss WL20 and WL50 can give 10-12 hrs battery life, I'm struggling to understand why there is a problem with the G10T. Needless to say, I have logged a ticket with Line 6 support requesting either G10 II to try out ( before having to return the new G10T) or a full refund because the G10T is no longer the unit I bought and the severely reduced battery life means it is no longer fit for purpose.

This is a copy of my post on 'The Gear Page' that I think is self explanatory. In short, I'm getting only 2.5-3hrs on a brand new replacement G10T: " My original G10T worked perfectly but was ruined by the v1.06 firmware safety upgrade. I had no doubt Line 6 would replace it, but I raised concerns with Line 6 Customer support at outset that battery usage reported on various forums from those who had their G10T's replaced was around 2.5 to 3hrs. However, they wrote to me 11/2 assuring me that: " Hi, on firmware 1.06 the correct playtime of a working/functional G10T is 5.5 to 6 hours (8 hours is not possible anymore)". After having waited a month (my original G10T was picked up by UPS on 18/2), I received a replacement from E&M Electronic services on 18th March. I made sure the G10T was fully charged before I used it. I fully charged the G10T when I received it, and again when power had gone. I can now confirm that i'm getting only 2.5-3hrs, exactly as reported on numerous forums. It was the same both times. Needless to say I am far from happy. When I bought the G10 (it cost around £139 UK I think when I bought it) it was with the expectation of an 8 hr battery life. I am not prepared to send the replacement back again and wait for another unit. It's clear that the v1.06 significantly reduces the charging time and battery life between charges. I'd have accepted 5.5 to 6 hrs as being reasonable, but I don't accept 2.5 - 3hrs. This is no longer the unit I purchased, and I have no confidence it will last through a 3 hr band practice session or a gig. I understand that the G10T II has a larger battery and should give better battery life. I've therefore written to Line 6 customer support today requesting that they provide a G10T II for me to try and if that unit lasts 5.5-6hrs I will happily keep that and return the G10T to Line 6 - but not until I've received the G10T II and had a chance to test it. Alternatively, I asked Line 6 to refund me £139 which will allow me to buy a replacement unit from eg Boss that seem to have no problems with their battery life. Currently, the Boss WL-20L Wireless System is £143 and the WL50 is £154 from GAK. Battery life is up to 12 hours of continuous playing time. If Boss can provide a unit with that length of battery life I simply don't understand why there seems to be such a problem with the G10T or even G10T II? I appreciate the tonal quality from G10 may be a little better than eg the Boss unit, and I would need the WL50 for equivalent range (based on youtube reviews/tests) but if the G10T only lasts 2.5-3 hrs, then it is simply not able to do the job I need it to do. This is such a disappointment because before the firmware change I was very happy with my G10T. @Frank Ritchotte if you're looking in, I'd be most appreciative of your comments on this please. "

I've just received a brand new replacement G10T from Line 6 via their UK distributor partner. I am only getting 2.5-3hrs battery life before recharging. I have contacted Line 6 accordingly.

The factory presets are not 'terrible', but factory presets are always problematic in MFX units - you'll find some you really like, some you'll think are average, and some you think are dreadful. It is the designers view of what sounds good but with their gear and are also intended to help give users an idea of what the MFX unit can do. Some users love the presets, others hate them. You also need to check whether the preset has expression pedal control as that can change it totally. Aside from personal taste ie we all have different ears, the biggest problem is inconsistency of gear and how you are using the patch ie type of style. It depends on so many variable factors that it is simply impossible to allow for when designing factory patches and very often the patch designer is trying to come up with a compromise that will be decent sounding for the majority. For example: 1. The guitar you are using - some patches will sound better with single coils and worse with humbuckers - and vice-a-versa. The pickup output will also impact on what you hear. 2. The type of headphones you have (you need good studio monitoring headphones eg Audio Technica ATHM50X, or Beyerdynamic 770 Pro - too many folk think their expensive or great sounding headphones that sound terrific when listening to you tube or mp3's or CD's should sound great with Pod Go and blame Pod Go for what they are hearing - studio monitor headphones are very different - not expensive, the two mentioned are around £120 UK, but can transform what you hear from Pod Go) 3 Your amp and how you connect it. If you are putting Pod Go through the front end, the pre-amp stage of your amp will colour tone and add distortion. If you have an FX loop, put Pod Go through the FX return for a less coloured tone 4. Your speakers - either desktop or amp will colour tone 5. The factory presets will have typically been designed in the studio using FRFR (full range, flat response) so if you are using anything else, it will sound different to what the patch creator had in mind. To prove the point watch the demo vid of Pod Go at NAAM with Phil Hindmarsh. Now, load down Phil's patches that are available free from Line 6 Custom Tone and play through your rig? Do they sound like Phil's tones? (put aside his fabulous playing and just focus on tone). I'd be amazed if they did and you might even think the patches are 'terrible'. Even though one of my guitars is a Yamaha Pacifica 611VFM (not wholly dis-similar to his HSS Pacifica) I still had to tweak them a bit and that was with my ATHM50X headphones and going through a Headrush FRFR108 powered cab. Through a guitar amp with a different guitar, they sound totally different. So, if you want to hear the presets as intended, use studio monitoring headphones and/or an FRFR speaker. Also, here's Paul demoing some Pod Go factory presets - do yours sound like this with your gear? Re the part of your statement above that I've put in bold - utter and complete nonsense. Once you have an understanding of how Pod Go works, and build up your experience and knowledge of tone building (I had to go through the same learning curve, and I've been playing some 50 years and have used DSP gear for around half of that) yes of course you can. Even just changes to the cab model and/or mic type & placement, and upping the cab dB levels can transform the patch. If you've ever wondered why an IR can sound so different to the stock cabs, a big difference is the cab output level that helps give a bigger sound. Setting the frequency range to match the real speaker is another good 'trick'. I've tweaked most of the factory presets to suit inc adding snapshots and footswitch settings. There are loads of vids on youtube by some very experienced, knowledgeable and helpful folk - it's well worth starting off with the Pod Go vids for user tips/tricks and then looking at tone-building videos - you'll find them a huge help. But here's the thing - Pod Go is NOT a simple 'plug n play' MFX unit that will give you instant tonal gratification. Just like any other MFX (and I've had Boss, Zoom, Yamaha, Vox and Line 6 units) you have to invest the time to really learn and understand how to get the best out of them - and that applies for any modelling unit out there.

No it's absolutely not. Pod Go and HX Stomp are fundamentally very different units and the architecture and DSP processing are both quite different. You can't put 4 pints of milk into a 1 pint bottle or a square peg into a round hole. That's exactly why Line 6 has quite correctly positioned Pod Go as 'Pod' family and not part of the Helix family - it has Helix modelling, but it is NOT a Helix.

Have you gone into task manager to see if there are multiple tasks for it? if so, close them all down & then try & reopen Pod Go Edit. If they won't delete, reboot your computer. Even if there are no multiple tasks, reboot your computer. If still a problem, remove Pod Go Edit, reboot, then reinstall it.

It's exactly the same with any MFX through the front end of an amp, because the amps input stage is colouring your tone. You might get away with it if you have a super clean Fender with high headroom but otherwise going through the front end isn't recommended for exactly the reason you are finding. You can try turning off the amp modelling and cab in the Pod Go and just use it for fx, or just stick with very clean amp and cab models in Pod Go. As I said, I don't put MFX through the front end, only the fx return. Alternatively, use 4 cable method with fx loops of amp and Pod Go.

Guys, there is nothing wrong with Pod Go via headphones. You need studio monitoring headphones, period. Two of the best for Pod Go (or any MFX) are the Audio Technica ATH M50X (32 Ohms) and the Beyerdynamic DT770 Pro Headphones - the 770's come as 32, 80 & 250 Ohms. For Pod Go most folk prefer the 32 or 80 Ohm. 250 is too quiet and you'll need a headphone amp to get the best out of these. 32 Ohm should be fine but 80 Ohm seems to be the best balance for MFX re volume & sound quality. The 32 Ohm 770's for some reason are not quite as detailed as the ATH M50X - I have the ATH M50X which are superb and the 770 80 Ohm are likely to be the better 'equivalent' sound quality wise albeit will be a little quieter. Both are excellent and both have pros & cons. Biggest downside of the 770's for me is that the cord is fixed - if that goes, you'll likely have to buy a new pair. The ATH M50X has a detachable cord and comes with a choice of 3 - long straight, shorter straight, and coiled. Also, the 770's don't collapse, whereas the ATH M50X do. You'll read conflicting reviews re comfort - some prefer one, some the other but you can always change the ear pads on either. Reportedly the 770's have a bit more mids definition, whilst the ATH M50X has more bass. Just be mindful when you read the reviews - they are using it to listen to music - remember, your main target is Pod Go. But I don't think you'll go far wrong with either as these are considered two of the best headphones out there not just at this price point (both are around £115 UK) but even compared to headphones at 2 or 3 x the price. These are two biggest sellers and the comparisons are probably the most discussed of any headphone. At the end of the day there's no rights or wrongs and it comes down to a personal choice.

The DSP processing difference is the problem and there are some key differences in functionality too.

The G6 has some interesting features, but I suspect the Pod Go will still likely be better sounding and easier to use.

You say 'the' wah. Theres about half a dozen to choose from so try changing the model.

See here: https://www.thefretboard.co.uk/discussion/201331/new-zoom-g6-v-pod-go#latest A word of caution re my observation: "subject to DSP limitations, the G6 allows up to 9 effects or 7 if an amp and cab is selected". Having had a Zoom G5 and a Zoom G5n (that also allowed up to 9 effects), if the G6 follows a similar Zoom approach all may not be what it seems. Why? OK, with Pod Go you have fixed blocks, including: EQ Amp Cab Volume Wah EQ And whilst not a 'block' a noisegate is an effect but is standard in Pod Go So, that's 7 effects. Now, on top of this you have up to (DSP permitting) 4 user slots (and I can get 4 slots on all my patches - there are always options to juggle DSP if you need) which is a possible 11 effects In the G5n, the above would have used up 8 slots (amp is 2 slots, cab 1 slot), leaving you just one extra slot - but if you chose the 7-band EQ, that used up 2 slots - so the G5n could look like this: EQ - 7 band graphic (2 slots) Amp (2 slots) Cab Volume Wah EQ Noisegate And some of the Zoom G5n FX take up 2 slots! Now 9 slots doesn't sound quite so good does it? If the G6 follows a similar approach, whilst it might give more choice for some (as it has no fixed blocks) it could be a backwards step for others. For example, I love that Volume & Wah expression pedals and a noisegate are available automatically on any patch! In G5n & G6 I'd have to manually programme these on and they would use up 3 of my 'up to 9' patches. I'm also unclear how easy it is to the switching between volume & wah in G6 - as it was fiddly & a real nuisance in the G5n. My honeymoon period on the Zoom G5n was very short lived as you can read here: https://www.thefretboard.co.uk/discussion/138564/

You need a good studio monitoring headphones like the Audio Technica ATH M50X (that I have, 32 Ohm) or the Beyerdynamic DT770 (32 or 80 Ohm) that are very well thought of too: https://www.headphonezone.in/blogs/buying-guide/comparison-beyerdynamic-dt-770-pro-audio-technica-ath-m50x

Have you upgraded to the latest v1.12 firmware? If not, I strongly recommend you do so becauwe v1.12 should fix the freezing issue. If you have, you might have a filepath glitch so reset your PG back to factory using C and D buttons. If you are still having problems after the above, log a ticket with Line 6 customer support.

Jay, have you tried the reversing polarity setting referred to in another thread? I'd also suggest it would be good to see if Line 6 confirm it's a genuine bug or whether it's merely a settings issue. Have you raised a ticket and has Line 6 responded?

What is the best way to do this? Guitar > Pod Go > Amp out > Input of the Mesa? - Experiment - through the front end the preamp stage will colour tone, so you have to keep the amp clean. If you want to use the Mesa's gain stage, 4 cable method (see Pod Go manual & youtube vids). Also, try Pod Go into FX return and use the Mesa as a power-amp only. Also, do you guys still use cabs/irs when going through a real amp? Yes, although past tense as I no longer put my MFX through an amp. I use my MFX units straight through the FOH PA, no amp. I also have a Headrush FRFR108 to use as a monitor or for small club gigs - unbelievable volume & tone quality from such a small unit.

A Pod Go update is definitely on the way as confirmed by Line 6's chief designer. Last month he indicated 'soonish' and that there would be 'no surprises' which indicates Pod Go may be getting some of the less DSP hungry upgrades from Helix v3.0. Pod Go only came out in around May/June in the UK and there were 2 firmware releases to fix bugs. Personally I'm less interested in extra amp or fx models, as there's already loads of options in Pod Go. But I'm pretty sure the upgrade will include some. For my gigging needs there are 2 priorities. I'm told by Line 6 the first will not be coming with this upgrade but is high up on their to do list, so perhaps the upgrade after this, and that's the ability to name snapshots and multi switch assignments. At the moment snaps are simply numbered one to four, and multi assignments are just 'multi' so that's not helpful. The other feature that I want is for the 4 user fx slots to be expanded to 6. It won't increase DSP but with prudent selection of amp and fx selections, we would have more flexibility to get more out of the DSP in Pod Go. Because HX Stomp was expanded in v3.0 to 8 user fx slots, up from 6, I'm hoping Pod Go will get some extra flexibility here... even 1 extra slot would be very useful. But we just have to wait and see and be patient I'm afraid. Bear in mind too that everyone, including Line 6, has been affected by the global pandemic, so they are likely to have been slowed down just as so many other busineses have been.

As far as I'm aware the only difference as between preamp and full amp models is that the latter has wider parameter control and hence use up more DSP than the preamp.

Glad you're having success with it - both cracking speakers and huge bang for buck.

Exactly, amp out is for connecting Pod Go to the front of an amp. Noise gates cut your volume as the output drops below the gates sensitivity threshold. So for maximum touch sensitivity and control when using your guitars volume controls, either turn the noise gate off completely, or if you are getting too much noise, set the noise gate threshold low. One of the problems of going through the front of an amp is that you'll likely get some noise, particularly on higher gain patches, as you're going through its preamp stage so use the noise gate only as much as might genuinely be needed. It's exactly the same if you were using stomp pedals in front of your amp. All effects in the Pod Go chain can add noise, especially distortions and compressors. So only use pedals if you really need them, not just because you have a spare slot. And don't overdo amp gain, distortion gain or compressor levels. All my amps have fx loops so if I put my MFX through an amp I go through the FX return and use the amp as a power amp only, although it depends on the type of fx loop. However, when playing live I don't use an amp and I just put the MFX straight through the main board PA. For times when there's no PA, or when I need a monitor cab, I put the MFX through an FRFR ( Full Range Flat Response) powered speaker. I recently got a Headrush FRFR108 which is superb. Can be whisper client for home use, or incredibly loud for rehearsals or club gigging (when we get back there post lockdown). Incredible clarity and bottom end from a compact unit that weighs just 19lbs. And in the UK its under £200. Your Pod Go will never sound so good.

I have an excellent powered speaker for use with my Pod Go, which is the Headrush FRFR108. The quality, fullness bottom end and volume is staggering. The first time I plugged in, I simply could not get my head round that this huge, huge sound was coming from such a compact unit with a mere 8" speaker. These are under £200 each and I'm so impressed that once gigging and rehearsing start again, I'm buying a second without hesitation. These can be angled in different positions on the floor as a stage monitor, or mounted for PA projection. There is a 12" version too, the Headrush FRFR112, that are a more expensive, with the same 2000w power rating but these are around double the size and weight of the FRFR108. When gigging, I put my MFX straight through the main PA so I'd only need one as a monitor for me, but I could position a second one for others in the band at a different volume level or send it to the audience if the PA was limited. Staggeringly good, I'd recommend these without hesitation for home or gigging.