voxman55

So glad you got it all sorted, updated & working properly. And thanks for the off-line tip.

Sadly not directly. You can create a group of favourites to export and import for eg gig sets but you can't label individual patches as a favourite.

The term edit is just to signify that you've made a change from the original patch starting parameters, so it will flag up with expression pedal changes, as you could edit and save different ranges if you wanted to. It's just a minor quirk, so best to ignore.

I'm a little confused as there's no D displaying on my Pod Go tuner between notes. Which tuner mode are you in? Just a thought...you don't perhaps mean the 'b' that signifies 'flat'?

This is the Pod Go section. You need to go onto the Helix pages please.

You've simply come up against the DSP ( digital signal processing) limit. You've selected options that use up a lot of DSP, and the greyouts in Pod Go simply tell you that you don't have enough processing power to run those options. If you want them you'll have to choose different options in your current selections. For example if you've chosen a jumped amp model, spring reverb or Horizon drive, these use up a lot of processing power. Seems to me you've got a bit of research to do so you can understand how Pod Go works. This includes reading the manual, watching Pod Go vids on youtube, and looking at the Pod Go DSP useage charts published by Benvesco. In the latter, it's not fully up to date for v1.30 Pod Go but it will show you how much each of your selections costs in terms of DSP %. Look in the Pod Go columns, here: https://benvesco.com/store/helix-dsp-allocations/

Have a read here to see if this might help: https://line6.com/support/topic/62713-gt10ii-cutting-in-and-out-on-pgw/

This was added in v1.30, ditto snap shot naming & switch colour options.

It's a known issue - see the v1.30 notes here right at the end. It will be fixed in the next firmware update but temp fix as below: Known Issues in 1.30 If many parameters are assigned to the expression pedal, POD Go Edit may fail to reflect some parameters' correct Min and Max values In some cases, loading a .WAV file into the currently active IR slot can cause the block to cease passing audio until a different IR location is selected When Modulation > Chorus' WavShape is set to "Saw Up" or "Saw Down," the block collapses the signal to mono when after the Amp block A minor thump may be heard when loading a Distortion > Kinky Boost, Dhyana Drive, or Tycoctavia Fuzz In rare cases, if Delay > Glitch Delay is in the active preset, performing a firmware update can cause POD Go to freeze on the splash screen Renamed footswitch assignments that are at the character limit and also contain special characters may cause lines to temporarily appear along the bottom of the screen when toggled. Please shorten the customized name by 1 character to avoid this as a temporary workaround until this is addressed in a future release. POD Go Edit—After copying/pasting an Input or Output block “Failed to undo edit buffer: …" can appear POD GO Edit—Adjusting some parameters can fail to display the preset name in a dirty state (italics)

Use the acoustic simulator with a clean amp. It's pretty good. There are also some acoustic patches on Custom Tone.

I've seen this reported before. Is this brand new or did you buy it used? If new I suggest you return it and request a replacement. You could try a factory reset that might bring these back. What firmware version is shown at start up in the kidney window? I suspect you'll be better to upgrade or reinstall the firmware to v1.30. Line 6 Customer Support will help you get it sorted if you can't return it or can't resolve it, so raise a ticket with them and they'll guide you.

There are Pod Go Facebook groups that have a number of these .pgp template variations you can load down. Some can be a bit quirky e.g. the 6 block I mentioned earlier, but some work as described. Very useful if you need a bit more flexibility. Frankly, my view is that Line 6 should add an option for two further blocks and the ability to remove the amp and cab blocks. But they are entrenched in their view as to what they think Pod Go should do and who it's aimed at. I personally think they are absolutely 100% wrong and are not listening to what it's customers want, but that's just me. I also think they should add DSP info to help customers but again it's something they are vehemently against.

If you can't recognise a tone and its non-descript what possible difference does it make? You either like a tone and think it might be good for certain things, or you dont. Either way it's irrelevant what it's called or what it's supposed to be.

There have been a number of bricking problems reported here and on other sites. I therefore asked Line 6 Support how these can be fixed and I thought it might be helpful to share their response: --------------------------- ========= Message from YGG ========= Hello voxman55. Your Line 6 Support Ticket was updated with the following message: Hi, in case of an update failure: 1. reinstall the latest version of POD Go Edit and Line 6 Updater: https://line6.com/software/ 2. boot the unit into "Update Mode": press and hold PAGE > (page right) and then power on POD Go. 3. reconnect the POD Go via USB to the computer. Use another USB cable and try different USB ports, don't connect to an USB hub. 4. shut down all Line 6 software including POD Go Edit, or any programs that use audio, like DAWs, iTunes, Spotify, video games, etc. 5. launch Line 6 Updater only and select "POD Go Unknown version", then (re-)install the latest firmware. 6. perform a factory reset on the POD Go (will delete all user patches, IRs, globals): while holding footswitches C+ D turn on POD Go. Wait for "Will reset Globals and restore stock Presets..." to appear and let go. 7. if this should fail, the same procedure should be tried again offline. For this you have to download the latest POD Go flash memory file, then launch Line 6 Updater, choose "Offline Mode", then choose the downloaded flash memory file for the update. 8. if it still fails, it needs to be tested with another computer. You can update directly from any version to the latest firmware version. In rare cases a gradual update via previous versions may help but normally that's not necessary. If none of the above should help, the unit should be checked by a service center. But please note that normally, even when an update attempt fails, the unit can be returned to operational state with the above procedure. Best regards Line 6 / Ampeg Support Europe - Line 6 Customer Service

Aside from people's ears being different, another factor is that we all have different guitars, pickups, amps, cabs, headphones etc. Someone may have a great patch for e.g. a Gary Moore tone that they created for their Les Paul with Pod Go via a set of studio grade headphones e.g. Audio Technica ATH m50x (these are mine). But if you a Strat and just use HiFi headphones or if you run your Pod Go plugged into the fx return of a 5w Marshall head and are going through a 2x12 greenback cab, it will sound totally different through your headphones or amp and with your guitar. In addition, some patches are made using a third party impulse response (IR) and not a stock cab model in Pod Go (which are IRs too that are incorporated into Pod Gos modelling directly). So unless you have the same IR you can load, it will sound very different. For those who may be less familiar, a third party IR for Pod Go is a separate file in .WAV format that cannot be incorporated into the .pgp patch template file. Sometimes the patch creator will tell you which IR was used and give a link to it. If it's a free IR you can load it down and upload to one of your Pod Go's 128 IR memory slots. Otherwise you will have to buy it. You might be able to get close to it though with a stock cab if you know things like the cab and mic model used. In Custom Tone there are sections to add helpful info and text about the patch, eg if there are snapshots, that they were using volume roll off, etc, but not everyone bothers completing this, which is a shame. There might also be snap shots in the patch so it's worth trying snapshot mode to check.

It's not an official group - just facebook pages. As @silverhead rightly said, the best thing you can do is to vote on Ideascale - there are some links here: but as the same requests get made by several people, read through these first & vote/comment on the ones you like, and only make up a new topic once you're sure it's not already been covered. My wish list items are already on, so please look for these & vote on them - and any duplicates from others too! I also added one more to my list above, that I forgot.

I was just curious as he had a similar wish list. But suggest you change the title to Wish list for Pod Go 1.40 as it makes it look like a Line 6 post ( and we wouldn't want folk to get too excited! Lol) And I'm right with you on 5! I'd also like to see: 6. Two extra user blocks 7. Option to see 8 sections in the display when 2 additional Foot Switches are added in FS7 and FS8 including naming. 8. Control options for the tap delay switch. It seems a bit of a waste that all it does is tap delay! 9. Allow users the option to remove amp & cab thus freeing up DSP if eg they want to create a stomp FX patch using the extra blocks as above

So, some progress. It sounds like the USB signal isnt strong enough. If you have a PC and have been using front USB ports, use the rear USB port as it will provide a much stronger signal. Do not use a USB hub.

Are you John Phoenix from the Facebook Pod Go pages?

Where did you read that out of interest? OK, so I found this whereby you use the line 6 updater not Pod Go Edit: Also found this helpful video:

I totally appreciate your frustration. The v1.30 was a big update so was well worth going for. OK, couple of things. Restore to C&D is no good because you have a failed update. First thing to try is the PAGE> reset "Here are the common button combinations for POD Go when attempting a factory reset or troubleshooting. To perform any of these, start with the POD Go turned off, then flip on the power switch while holding down the buttons below for 5-8 seconds. It's helpful to have your presets backed up or saved to your PC or Mac computer, before performing a factory reset. C & D - Factory Restore (Restores all factory settings) A & B - Clears Everything (Clears all presets, factory settings will not load) PAGE > - Update mode (helpful for any interrupted or failed updates)" If Pod Go still won't allow an update, what was the firmware version in your Pod Go that that you were trying to update from? Was this the first update you've done since buying your Pod Go? If it was a much older version eg v1.10/1.11 you might not be able to jump to v1.30 & I have a suspicion this might be the problem and the reason you've bricked might be because v1.30 didn't recognise your older firmware. It's possible you might need to upgrade to an earlier version first eg v1.21 and then go to v1.30 (which means an earlier version of Pod Go Edit too). This is because the Pod Go updates are intended to work cumulatively - in other words, Line 6 assume that you've gone through all the previous updates. Some updates might therefore be partial 'building blocks' to update from the previous version but aren't the whole (for lack of another expression) 'operating system'. Therefore, try installing (or reinstalling) v1.21 first. If that doesn't work, go right back to v1.11 - if it takes it, upgrade to v1.21, and then v1.30. All the links with instructions & the relevant PG Edit versions for that update are here:https://line6.com/support/page/kb/pod/pod-go/ Keep us posted as to how you get on.

Suggest you log a ticket with Line 6 support, explain exactly as you have here and they should be able to help you resolve. If you connected to a front USB on your PC, try connecting to the rear USB and see if via PG Edit it might update. How new is your Pod Go? If it's still very new see if the retailer might be prepared to replace it.

If I go into a high gain patch with amp & distortion block with Pod Go Volume dial at 3 O'Clock and turn off PG whilst wearing headphones (which I never do) I can hear a slight 'pop' but nothing loud or alarming. With clean patches it's almost nothing. But you should always do as @silverhead said above. Particularly with a real amp and cab you could actually damage a speaker if you don't turn off gear in the right order.

Bonnie uses: Amps Bad Cat Black Cat 30R 1x12 combo (Raitt uses only the EF86-driven channel 2) Effects Boss CS-2 Compression Sustainer, Pro Co Rat So in the Pod Go, the nearest compressor to the CS2 is: Blue Comp: BOSS CS-1 Blue Comp Treb: BOSS CS-1 (Treble switch on) V1.30 of Pod Go now has the Ratatouille Dist based on the 1984 Pro Co RAT. Don't use the older vermin distortion - Line 6 admits it modelled a broken ProCo Rat, hence the new model But you could experiment with the other compressors too, to see which you prefer For amps, the Pod Go doesn't model any of the Bad Cat amps but the nearest equivalent to try would I think be: Matchstick Ch2: Matchless DC30 (channel 2) Vox AC30 But it's just a case of experimenting to see what works best for you. However, the key to her tone is the mix of compressor & ProCo Rat so the amp is secondary & I'd suggest that the above two amps will be absolutely fine to get you close enough. I'd also suggest you listen to her live tones - the problem with studio tones is there's a ton of engineering, EQ, compression etc that goes on and even she can't sound exactly the same live. In fact, I much prefer it - it's completely different - less compressed and with much more punch, clarity and mids than her studio recording. from her first bit of slide just hear how that hits you in the mix! Don't over do the distortion - she uses much less than you think. Start with lower gain settings on the Rat, the amp should be set for slight break up only. She uses Ch 2 just to give the base clean sound a bit of edge, not for distortion- that she leaves to the Rat. And the Compressor is to smooth her tone just a tad from the Rat roughness and add sustain. Again, don't over crank the compressor or you'll lose the dynamics/punch & your tone will be too squishy and less defined. Regarding reverb, a touch of spring reverb is all you need. As it uses up a lot of DSP in Pod Go, if you should find any DSP issues, you'll probably find that room, hall, or plate reverb all work well too. She doesn't use much so again go easy. The biggest problem folk have when building a patch is that they over crank everything and it all sounds muddy & indistinct. A lot of tones are far more subtle than you might think. I'd start off with the amp first, then add a touch of reverb, then Rat, then compressor (that's order to build, not chain order!). Re chain order, I'd suggest starting with the following more 'traditional' order of compressor, then rat, amp, cab, & reverb. But don't be frightened to experiment with the chain order as it can make some big differences eg compressor after the Rat or even one or both after the cab. For Spring Reverb many favour placing this between the amp and cab. There really are no rules here - let your ears be your guide. And to help you hear the differences, here's a suggestion - create multiple similar patches but with different chain orders so you can switch & hear the differences quickly & easily. Re parameter changes on amp & FX you can make these in snap shots so you can quickly switch between them to hear which you prefer. If you create a 'base' in Snap 1 or preset 1, then if you do lose your way in different versions, you'll always have your base reference to refer to. A lot is down to trial & error - just be patient. Re EQ block, I'd be inclined not to switch this on unless you need to but if you do I'd try it right at the end of the chain so you're total EQing your tone. It might help to add mids/punch but see how you go. Re cab settings, I'd experiment with adding 50-75% reflection - you might find this is adding enough ambience & you don't need a reverb block. I'd suggest start with a 57 dynamic mic for a more punchy live type tone, at 1-2", and on the cab raise the dB level to 3-5dB for a fuller cab tone. But these are starting point suggestions only - it's so important to experiment to help you better understand what different parameters do. Best way is to take a parameter and try it far left, in the middle, then far right - and then you'll say 'ah, so THAT's what it does" lol - that's how I've learned (and am still learning!). Ditto with effects order. It's all part of the fun - and the beauty of Pod Go is you can do this in seconds instead of having to physically connect, unconnect, & reconnect real pedals/leads. When building patches, it is SOOO much easier in Pod Go Edit - it's way faster, and is much more visual. Also, it has an undo function so you can undo parameter, FX model changes or chain changes one at a time - or put them back. That's not something you can do in Pod Go itself unfortunately. I don't know what gear you're going through. The above is if you are using headphones/FRFR but if you are going through a real amp/cab you will probably want to turn the cab section off. Through a real amp, go through the FX return if you have one to bypass the pre-amp stage so that you are using your amp as a power-amp only. If you can only go through the front of the amp, remember that your tone is going to be coloured by your amps pre-amp section so keep it as clean as reasonably practical or perhaps with just a slight break-up. Hope this is helpful to get you started, and good luck.

Only way to do that as far as I'm aware is to use headphones with a built in volume control, or use a headphone pre-amp that will allow volume control. You don't need to spend a fortune - the Behringer MicroAMP HA400 Headphone Amplifier is under £20 and is reportedly very good and lets you run up to 4 headphones: https://www.amazon.co.uk/Behringer-HA400-Microamp-Headphone-Amplifier/dp/B000KIPT30/ref=asc_df_B000KIPT30/?tag=googshopuk-21&linkCode=df0&hvadid=309964054975&hvpos=&hvnetw=g&hvrand=10449276594829026263&hvpone=&h