Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


voxman55 last won the day on August 7 2022

voxman55 had the most liked content!

Contact Methods

  • Website URL

Profile Information

  • Gender
  • Location
    London, UK
  • Interests
    Guitar, music, Football, F1, TV, Films, science fiction, puzzles, cryptic crosswords, word games, Sudoku, swimming, eating out, cinema.
  • Registered Products

Recent Profile Visitors

1,752 profile views

voxman55's Achievements


Mentor (12/14)

  • Dedicated Rare
  • Week One Done
  • One Year In
  • One Month Later
  • First Post Rare

Recent Badges



  1. You're in demo mode; to get out, Hold down Bank/Preset Down and "D" footswitches during power up
  2. Regardless of warranty I recommend you both raise a ticket with Line 6 Customer Support.
  3. I strongly recommend you have a good read of the manual & watch the Line 6 series of quick vids first. Although Pod Go is reasonably intuitive, there's still a lot that isn't obvious. Also ensure you are on the latest firmware - but only update through Pod Go Edit. Latest version is v1.40, but follow the Line 6 instructions here: To by-pass the pre-amp stage of your amp, simply plug Pod Go 'main out' into the FX return only. The real speaker of a combo will still colour the Pod Go tone so you might prefer the tone without the cab model - easiest way is to just turn the cab model in a patch off. Don't use the Amp Out - it isn't what you think it is: 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.
  4. Hi all, I recently posted this on a couple of Pod Go Facebook groups, so thought it might be useful for folks here too: NEW YEAR TIP: POD GO BACKUPS, SETS for GIGS, FRFR, AMP, HEADPHONE Hi guys & gals, and a very Happy New Year to everyone. Although I’d kind of assumed that this was pretty much common knowledge I’ve since picked up that it’s not, so the following might be useful especially for those who’ve used up all their Pod Go slots, & who need patches to suit different guitars, amps, FRFR, headphones etc and are worried about tweaking/over-riding settings and losing the originals. OK, I think Pod Go users are pretty familiar that when there’s a firmware upgrade (which incidentally you should only ever do through the latest Pod Go Edit) the process creates a back-up for you. You can also create a similar back-up if you go into ‘file’ in Pod Go edit and select ‘create backup’. These backups are a total backup of everything in your Pod Go and are convenient from a ‘safety’ aspect as these will get all your patches and IR’s back into your Pod Go if there was a glitch/failure & you lost everything. But it’s an ‘all or nothing’ backup and you can’t see and access individual.pgp or .wav (IR) files within the back-up file, which is a bit of a nuisance if you mucked up a single patch and wanted it back how it was. Now, I think most folk know you can save an individual .pgp file and export it to share or put on Line 6 Custom Tone etc. But some folk are under the impression that it’s a long and laborious process to save every .pgp and .wav file in their Pod Go – with up to 128 files in User, factory & IR sections that’s 384 files. But it actually only takes a minute to create a full back-up of all your user & factory patches & IRs in their proper .pgp and .wav format. Here’s how – I’ve made this step by step but the whole thing takes less than a minute: 1. On your PC or Mac create 3 folders and name them e.g. ‘My factory’, ‘My user’ and ‘My IRs’ 2. Connect your Pod Go to Pod Go Edit 3. Select ‘user’ patches in Pod Go 4. Click on patch ‘01A’ to highlight the whole entry in grey including the patch number (don’t select just the name where it highlights in blue) 5. Using the scrolling bar on the right of the patch list, not your mouse, scroll down to the last patch (let’s say you have used all 128 slots and its 32D but if you have less just go to the end of your list) and just hover the cursor over the patch name and it will highlight it in grey. 6. Now, hold down ‘shift’ on your keyboard and left click your mouse on the patch – you’ll now see ALL 128 factory patches grey highlighted. Now right mouse click and select ‘export’ or ‘Control+E’. 7. A ‘browse for folder’ dialogue box will appear. Go to the ‘My user’ folder you created in step 1, select it and press ‘OK’. ALL your patches will now load into that folder and they will be in full .PGP format that you can import back to Pod Go as individual files, or as a group set, or the whole list. So if you mucked up say patch 24B all you need do is go to that patch in your backup and drag and drop it back in to the relevant slot in Pod Go Edit. 8. Repeat the same process for your factory and IR patches, and you’re done. What’s great is that you can create groups of custom patches eg gig sets, patches for different guitars, patches for headphones tweaked for FRFR etc. Even if you’ve run out of blank slots, once you’ve backed up your original patches, it doesn’t matter if you copy these over other patches you don’t currently need because you have all of those patches backed up. And there’s no limit to the backups you can create. If you wanted to have 15 gigging patches for your Les Paul and 15 for your Strat and 2 for your acoustic, you can import and export these patch groups easily with no risk of losing anything you have. You can use the import & export set-list option within the Pod Go Edit ‘File’ tab, or just drag & drop these in. You can create umpteen patch groups eg those you’ve tweaked for FRFR or with your amp v those you’ve created for Headphones use. The options are virtually endless. You can even create template patches based on your favourite settings so that you don't have to start from scratch when you are creating a new patch.
  5. Within Helix this can be achieved utilising dual-routing with a separate EQ in each signal path. As Pod Go is a simpler unit with single routing that option isn't available to it. Line 6 will not give Pod Go anything that Helix doesn't have. When Helix gets a firmware upgrade, Line 6 then considers what can be incorporated within Pod Go after taking into account its lower DSP and memory capabilities. You could post your idea for a stereo i.e. 2-channel EQ on the Line 6 'Ideascale' site. This is where Line 6 looks for ideas/feedback so if it attracts sufficient votes perhaps its something they might look into adding in a future update. However, unless strong support is there from Helix users for a stereo EQ, Line 6 is unlikely to consider adding it to Helix, and as this isn't a problem for Helix users (as they have dual routing) this probably isn't something that they need and thus it's unlikely to be added.
  6. @Titleist050If you are referring to the Pod Go impedance issue, this is now well known to be down to a single capacitor in the input circuit that just needs to be removed. Line 6 arranged for the UK service centre to pick up, fix and return mine all within 5 days. All the high end is back and sounds great. In truth I nearly always use a G10 Relay that acts as a buffer and so I never suffered the loss of high end anyway. But the fix was free and quick so I had it done in case I use cables.
  7. I use this all the time on my patches. Typically I swap the default fx loop fs2 for the main out clean post when the display shows 'level'. You have to remove the fx loop assignment first though. I do this via Pod Go Edit which is quicker and easier than via Pod Go. But here's another tip. If you add 2 momentary pedals you will have FS7/8. You can assign these to do most anything FS1/6 can do but these work in ANY mode. So you don't have to tap dance between preset, stomp and snapshot modes. If you set FS7 as your clean boost you can be in preset mode and still kick it in. Unfortunately FS7/8 don't currently appear in the display but I'm hoping that Line 6 might give this option in a future firmware upgraďe. Also, momentary pedals don't usually have Leds but even if you bought a unit that did it wouldn't help because the Led will alternate between being lit for on and off.
  8. This - and you can also change the mic type in the stock cabs & you can assign the change to one of the footswitches. And whilst you can't change the stock cabinet in the same patch, if you are using IR's you can change these in the same patch. These options can make a big difference to your tones.
  9. voxman55

    New effect

    The forthcoming firmware upgrade to Pod Go is in current development with Line 6. Historically, Line 6 will always do its best to give Pod Go users as much of the Helix upgrade as it can subject to limitations of memory, processing power & underling software architecture. Historically, the Pod Go upgrade typically comes 4-6 months after the Helix upgrade. Helix 3.5 was released 3rd November 22. You can see what this included here: As far as I'm aware Helix does not currently have the effect you refer to but if you log into & post your suggestion in the Pod Go section of the Line 6 'IdeaScale' website they will see this and depending on how many folk vote for it anythings possible in the future. But be clear that Pod Go will not get anything that isn't in Helix, and even if the effect you like is added to Helix in a future firmware update, it may not 'fit' the more limited capabilities of Pod Go. Firmware upgrades are far from straightforward and take considerable time to design and test, so please don't be under any illusions that this is 'easy' to do. IdeaScale is here: https://line6.ideascale.com/a/index
  10. I generally concur although I'd suggest perhaps the following caveats. Notwithstanding the more recent sampling rate upgrade to Helix, when Pod Go was launched it had the exact same amp models as Helix and these are superior in quality to those in the HX500. Those Helix fx models that came over to Pod Go from Helix are also sonically superior to the legacy version. However if you compare the legacy effects in Pod Go with the equivalent FX in the HX500 you should find that these sound much more similar because these are effectively the same modelling generation. There are other factors in that the underlying modelling architecture in Pod Go is different to that in HX500 so even when comparing the exact same legacy effects in both units side by side, I suspect there will still likely be some differences. Some folk may hear no discernible difference whilst others might favour one or the other so what's 'better' can be quite subjective & simply down to personal taste.
  11. Interestingly I've had that issue with certain IR's eg where the on Axis and 3" distance works perfectly but where another variation in the pack and in the same .wav format is 'silent' when loaded (and where the IR dB parameters etc are all fine).
  12. I don't think so at all & clearly Line 6 are working on an update for it.
  13. Well, I dont want to falsely raise hopes, but Digital Igloo popped into The Gear Page earlier, and when asked if there was any news 're Pod Go firmware upgrade, he said ( cryptic as always of course): "No points for guessing, but it's a lot trickier adding [obvious thing I can't technically divulge] to POD Go. It might take a while, but it's still coming." We'll have to wait and see of course, but I wonder if Line 6 might be working hard to try and give Pod Go owners a 'Cabby New Year' ?!
  14. It's a valid question but as far as I'm aware other than having a Line 6 service centre check it for you I don't think there's any way of really knowing. It's possible the serial number might help here & you could try asking the question of Line 6 Support, but I honestly don't know if they would have access to production lists and even if they did, how reliable these might be.
  15. Hi Puni, I think I responded on The Gear Page too, but for anyone else looking in: "On past track record of Pod Go upgrades you can reckon between 4-6 months from the release of Helix firmware upgrades. Helix 3.5 was released on November 3, 2022. So I'd estimate anytime between early March to early May 2023. Line 6 will try to give Pod Go users as much as it can subject to processing and memory limitations - if it's just a few more amps/fx I suspect it might be on the earlier side - if there's any way of giving Pod Go some of the new cab facilities I suspect that will take longer - the bigger the firmware upgrade, the longer it takes hence the historical 4-6 month range". But as @silverheadsaid, it was a pretty major upgrade re cabs on Helix so we'll just have to wait & see whether Line 6 can give Pod Go users something here.
  • Create New...