voxman55

You're welcome No, presets are just memory slots which is different.

The following might help you to better understand how modern MFX units and Pod Go in particular, work. Similar to all modern MFX units the Pod Go gives you a huge choice of amp and fx models, but there is a finite amount of processing power ( DSP) available. Even Helix (whilst more powerful than Pod Go & can do a lot more) still has DSP limits. Although Pod Go uses Helix modelling, it is not a Helix. In Helix units like Helix floor, Helix LT, Helix stomp, Helix Stomp XL and even Helix FX, you have complete choice of what amps, cabs, & effects you can select - there are no 'compulsory' amps or fx you have to have. Pod Go is different. It is designed with a number of fixed blocks such as EQ, wah, volume pedal, noise gate, and fx loop. These use up very little processing power and whilst you can change the type of EQ or wah etc, you can't change these into anything else e.g. a reverb or distortion and you can't save processing power by turning them off. Think of all these fixed blocks as using up DSP power equivalent to a tennis ball, and all the other fx and amps as being a football. You can't put a football inside a tennis ball and hence you can't turn a wah into a distortion pedal or a reverb. Next is the amp block that you can't remove. Each amp model uses up different amounts of DSP and full amps use up more DSP than their preamp version, because full amps have more parameters which take up more DSP. If you choose jumped amp models these will use up more DSP ie they are like a beach ball, whereas other amps might be a football and pre-amps will be smaller footballs. Turning off the amp model doesn't save the amount of DSP - its a fixed block so Pod Go will reserve the DSP for the amp you have selected even if you turn it off. If you didn't need an amp model you could reduce the DSP being used by the amp by selecting the pre-amp model that uses up the lowest amount of DSP processing power. See the link from @grdGo33 Finally, you have up to 4 'user' fx blocks that you can choose and you are free to select any of the effects you want ....but again each fx uses up different amounts of DSP and using the same balls analogy these can vary from say a half size football to a beach ball. Now, all of your balls (amp and fx) have to fit into a box. That box is the total DSP processing power limit you have available. Think of the box as being able to hold say 5 normal size footballs (1 amp and 4 fx) but only if you fill it with average size football's. If you choose 2 beach balls you might only have enough space in the box left for 2 more normal size football's or 3 smaller size footballs. And if you chose 3 beach balls you might only have room left for a smaller football. If you wanted to get a bigger football into the box there would be no room...but if you changed one of your beach balls for a football, you'd now have room for the extra football you wanted in the box. In Pod Go, effects like Spring Reverb and Horizon distortion, and jumped amp models use up a lot of DSP (ie these are big beach balls). So if you select several of these 'beachballs' you'll only be able to get lower DSP hungry effect options ie smaller football's, into the box and sometimes there might even be no room left at all. In Pod Go some options will be greyed out to tell you that you don't have enough processing power left to have these (too many beach balls hogging up the room). But if you change one or more of your choices to something else and change a beach ball for a football e.g. replace spring reverb with hall or room reverb, or a jumped amp model to a non-jumped version, or Horizon drive to a tubescreamer or other distortion, then you'll free up DSP. It would be so much easier if Line 6 MFX units showed you the DSP cost of your selection as a percentage eg Spring Reverb 33%, Brit Plexi Jump 41%, Horizon Drive 25% etc so you'd know the DSP cost - even Helix users have asked for this. Unfortunately Line 6 don't provide users with DSP information - Pod Go has no DSP percentage indicator next to each amp/fx model or even an overall DSP meter so there is no way to see the DSP cost of your selections. If it wasn't for the excellent work done by Benvesco we'd have no info on this. But manufacturers like Zoom in the G6 and G11, and Mooer e.g. in the GE300 have a different philosophy and they do provide DSP info to help their customers. It's purely an ideological issue and a conscious decision by Line 6 not to show DSP usage...and it's something where I think Line 6 are just plain 100 per cent wrong and is why we regularly get posts like yours because Line 6 is not helping its (esp new) customers to understand about DSP and how Pod Go works. (I've written several posts here on this topic including one with a shopping analogy, so look at past posts and have a read). Anyway, hope this helps you.

The fixed blocks in Pod Go cannot be changed. You can choose eg wah type but you cannot change the wah to something else. There is loads of info available on this, but the amount of DSP used in total by the fixed blocks (wah, volume, eq, noisegate, fx loop etc) is very small and not enough to power other fx. Think of the DSP used by all of those as a tennis ball, and each of your other fx as a football. You can't fit a football into a tennis ball. You can have up to 4 user fx on top of the fixed blocks and amp/cab block so you can choose 2 distortions and a compressor and potentially a further fx. But that is UP TO 4 user fx...if you choose amp and fx models that are very DSP hungry, you might only have enough DSP power for 3 user fx. But Pod Go is designed so that most of the time you should be able to select 4 user fx blocks. Don't forget that you can also add one or more external pedals into the Pod Go fx loop, which will give you more fx options if you need it. So if you have a favourite distortion or compressor pedal of your own, you can use these. There are lots of threads here on DSP usage, including links to a table by Benvesco that shows you the DSP cost of amp and fx selections. Although Pod Go uses Helix modelling, it is a Pod and not a Helix. So if you want greater processing power then you need to look at a Helix unit e.g. Helix floor, LT, Stomp, Stomp XL. If you just want fx and not amp/cab modelling then Helix FX is a good option. But the Helix units have pros/cons e.g. Helix floor and LT offer a lot more power and features, but these are big, heavy units, and are much more expensive. HX Stomp/Stomp XL have no expression pedal, HX FX has no amp modelling or expression pedal. The Pod Go has the nicest display of any if these IMO, and it's 'form factor' including size, weight, number of footswitches, built in expression pedal, and overall features, are what have made Pod Go so attractive to customers. So it's a matter of researching carefully to choose the best product option for your needs at the right budget, and accepting that each option has pro's and con's and accepting and adapting to any limitations.

That's ridiculous. Where are you geographically and where and to whom did you hand it in? I recommend you contact Frank Ritchotte who is the Senior Director of Operations at the Yamaha Group (Yamaha own Line 6) Frank is a top man and I think he'd be mortified to hear if Line 6 Customer Support still hasnt sorted this. @fritchotte Frank, if you're looking in, can you possibly help @Sigbjorn ??

I had the same problem. I was using the front USB ports on my tower PC but discovered that their power was less than the rear USB port. Apparently this is very common, is not a fault, but has to do with how some PC's wire up the front USB's. The rear ports were already 'occupied' but as I needed some more easy access front USB ports anyway, I bought a 4 way USB hub for a few pounds, and connected it via a USB cable to the rear USB port so that I now have easy access to 6 ports. Pod Go Edit now works perfectly through the rear port via the hub. If you use a laptop, a mains powered hub should solve the problem for you.

As mentioned earlier, using a buffered pedal with the Pod Go should remedy or significantly alleviate the problem. I use a Line 6 G10 Relay that acts like a buffered pedal and is even better. Any Boss pedal will do, but if you use a Boss GE7 EQ you'll be able to dial the highs back in too.

Looks like Line 6 asked Sweetwater to pull the vid. They probably had an advanced beta version but as Line 6 found some bugs this has delayed the official roll out. Hopefully shouldn't be too long now.

The rollout has been slightly delayed because Line 6 found some bugs. Sweetwater 'jumped the gun' and probably had an advanced beta version from Line 6. The formal role out hasn't happened yet and it seems that Line 6 likely asked Sweetwater to pull the vid. But to avoid unnecessary multiple threads it is best to look at the threads here first before posting. There is already a thread on here that I set up 're v1.30 with the latest and greatest info.

See here for the latest info on v1.30 'leaked' by Sweetwater somewhat prematurely. The video has been taken down (I suspect at Line 6's 'request'): https://line6.com/support/topic/61582-pod-go-130-update-nearly-there-26-sep-sweetwater-v130-video-and-some-info-on-upgrades/

I'm with @spaceatl - it sounds like your settings may possibly have gone awry somewhere eg you may have set up snapshots and/or made certain assignments that might not be quite right to achieve what you need. If your patches are simpler with no snaps or assignments, then I'd suggest recreating these (but don't use the 'copy' facility in case you recreate the problem) and allocating these to different patch numbers - if those work correctly, delete the other patches. If you were using snaps/assignments you could still try to recreate these but there may be no benefit doing this as you might inadvertently simply repeat a possible error (not saying you have, but it's probably the most reasonable possibility at the moment). If you are positive you have set up your patches correctly and it's only since v1.22 that you've had the problem on patches that were otherwise working fine, you might have a software glitch. I recommend you back up your patches and try a system reboot back to factory & then reload your patches. If you still can't solve the issue, then I'd back up your patches and reload v1.22 to see if that solves the problem. If that doesn't work, then raise a ticket with Line 6 Support and give them a full description of your problem and the actions you've already tried, with a full backup file, to see if they can replicate the problem or spot where your patch settings might possibly have gone awry. Are you using Pod Go Edit? If yes, great but if not I'd strongly urge you to use this as it makes creating patches and troubleshooting much easier. One last thing - we are expecting v1.30 'imminently' (see here for the latest & greatest info: https://line6.com/support/topic/61582-pod-go-130-update-nearly-there-26-sep-sweetwater-v130-video-and-some-info-on-upgrades/ )

Still not officially launched but must be imminent now as Sweetwater seems to have 'jumped the gun' here. Not a full list of upgrades but the following is gleaned from the video (Update 27/09/21 - looks like the vid was pulled, sorry!): New amp & cab: Mandarin Rocker (Orange Rockerverb MkIII dirty channel) & Mandarin 4x12 EM Cabinet New effects: Ratatouille distortion, Retro-reel modulation (Line 6 reel-2-reel), Euclidian delay (mathematical delay), dynamic hall reverb, hot spring reverb New features: ability to rename models/effects, customisable colour stomp switches, snapshot naming, external footswitch and volume control enhancements (no clear details here yet)

You're more than welcome & I'm glad if any of my posts have been helpful. Re studio monitors, if you mean small studio speakers you should set these to a comfortable listening level combined with Pod Go output level. If you set any device to maximum by definition you are 'pushing it to its limits' which means you might get some unwanted distortion or other sonic irregularities. No difference really to e.g. how high you set your computer speakers. Obviously depends on the quality of your studio speakers. When listening through headphones, don't overdo the volume as longer term exposure to high headphone volumes can cause damage to your ears. For Pod Go you need studio grade monitoring headphones for best results. These are different to headphones you might use for normal music listening. Probably the two most popular and best value are the 32 Ohm Audio Technica ATH50Mx (which I have) and the Beyerdynamic DT 770 Pro Studio Monitor Headphones (these come in various impedance 'flavours' - opinions vary as some folk go 32 Ohms and some 250 Ohms but most folk tend to favour the 80 Ohm versions for a sensible balance of audio quality and volume levels - the 250 Ohm impedance might give a tad more definition, but volume levels will be lower). Although you might think the 32 Ohm Beyerdynamic and 32 Ohm ATH50Mx are 'equivalent' reports by those with both suggest the 80 Ohm Beyerdynamic is closest to the ATH50Mx.

Have you checked that you're in factory presets and not user presets - the latter will be blank until you create presets. You should also upgrade to the latest firmware v1.22 - see here: https://line6.com/support/page/kb/pod/pod-go/pod-go-121-r976/

I've had my Pod Go for around 15 months and it's incredibly quiet even with single coil guitars. When you've been on boards as long as I have you see that it's always pedals/mfx units that get blamed for noise and unless you're unlucky enough to have a genuinely faulty unit, the cause is ALWAYS either down to settings, connections or external causes. Very often, noise is a combination of different factors so here are some thoughts that I hope might be helpful: 1. How are you using Pod Go? With a real amp and fx if you max out amp gain and then add a compressor and or then add one or two maxed out distortion pedals, of course you'll generate noise. So, exactly the same can happen with Pod Go as all it's doing is modelling the real gear! That's not the fault of Pod Go, that's your pedal selections and settings. 2. Your Pod Go is only one part of your chain. Properly check your cables and guitar earthing and ensure you are using good quality cables; cables can deteriorate over the years so try some new ones and see if this helps. Poor guitar earthing can be a big source of noise and can be more apparent with some gear even if it seems ok with other gear - so just because 'my guitar and cables are fine with other gear' doesn't necessarily mean that your cables and earths are all good. Particularly important with single coil guitars, make sure your pickup and control cavities are shielded properly eg with shielding paint and/or aluminium foil. Many guitars, even name brands, will usually benefit from some attention here. Also, use plastic safe electrical switch clean to clean your guitar input and pots, and your Pod Go inputs regularly eg every 6 months. Dust, oxidisation etc can all contribute to poorer signal quality and noise. 3. Have a look at the signal chain in your Pod Go...the positioning of distortion and compressors can impact on noise, and make sure that your noisegate settings are reasonable for the fx chain and guitar type you're running. 4. Another common reason for noise is noise picked up from a ring mains and other electrical devices eg computers, lighting, washing machines etc. This can be particularly problematic in countries such as the US with 110v mains and which can be notorious for difficulties with 'dirty electricity' that digital gear can be very sensitive too. It's why the US is the single biggest market for line conditioner units. Look to see what else you have switched on in your home and try your Pod Go in different rooms and different locations e.g. friends and family homes, to see if the noise level changes or even goes. If you are in an area that suffers from 'dirty electricity ' you may need to invest in a line conditioner such as a Furmen that will filter out noise and provide a consistent voltage and current to your gear. 5. It's possible your Pod Go PSU might be picking up noise or might be damaged. Sadly, it's a budget unit with a thin short cable and is the weak link of Pod Go where any deterioration in the cable, connection or transformer can create noise. 6. Make sure you are using the right cables and that these are good quality. E.g. if you are connecting to a FRFR powered speaker, you'll need a balanced stereo TRS cable(s). So these are some things to look into and I can almost 100% guarantee you that Pod Go as a unit is not the problem.

All eminently sensible, I set my Pod Go main volume to 50-60% too, to allow for live quick adjustment. Re the Output block this can have a number of uses. Examples might include: 1. Where you have a quieter amp model that you want to keep clean eg the Princeton, and where even with the Channel option maxed out it's not loud enough as compared to other patches. Here, you can up the Output block to compensate 2. I often use the Output block as a clean lead boost for solos. Typically I do away with the FX loop and make that a level increase by 3db. The advantage is it's completely clean and doesn't colour tone, and you can kick in with any fx combinations. Although you can use things like EQ, and distortion pedals to give a boost, a) these colour/distort tone (fine of course if that's what you want) and b) unless you engage that pedal you have no volume boost. It's actually very difficult to balance patches for volume. Even if you used a volume meter, this only gives you a relative volume level. It doesn't allow for the level you might need to punch through the mix in a live setting and that can be different from patch to patch depending on gain levels, room ambience etc. In a live setting, you'll often need to dime down reverb, delay, modulation & gain levels to help make the patch punchier through the mix. A lot also has to do with your mids that are what you need to raise to help punch through the mix (Fletcher Munson Curves - loads of info on the internet on this). Home and gig tones can therefore be very different - patches that sound great at home can be awful in a band mix and vice-a-versa. I haven't played live yet with my Pod Go, but on my Vox Tonelab SE and LE my patches are set for gig volumes.

All good stuff from @grdGo33 . Learning about tone takes time, how long have you been playing? Don't forget too that you have volume and tone controls on your guitar; so don't always expect Pod Go to do all the work. But I suspect a lot has to do with your amp and how you are using Pod Go with it, not your guitar or pickups, so let's start there. 1. Which model of Marshall amp do you have exactly, including whether it is valve or solid state, wattage and speaker size? 2. Does it have an fx loop? 3. How are you connecting Pod Go to it? 4. If you are going through the front end of the amp, are you using the Amp out on Pod Go?

Going through the PA should sound similar to your headphones although it will never sound the same because the PA and headphone speakers are very different, and with speakers your ears are hearing sound through the air rather than via encased headphones. But if gains are turning clean then it sounds as if you might unintentionally be bypassing the amp model in your Pod Go. This is difficult without seeing your set up and settings, but some thoughts: 1. To connect Pod Go to the PA you should be coming out of the Pod Go Main out (Left for mono) and connecting Pod Go to PA board via a balanced TRS cable (2 if stereo) . Set the main outs to line level. Through the front of an amp you should be connecting to Amp Out in Pod Go Main out set to Amp. 2. Have you been using the fx loop? If so, your settings might be bypassing the amp model. 3. Is it behaving this way just with your Vox patch or with all factory patches? If the latter, I'd suggest backing up your patches, and rebooting back to factory settings and trying your Pod Go before reporting your saved patches.

Update from Digital Igloo on the Gear Page board: (Voxman55) Any hints DI as to how near we are to v1.30? "Hopefully not too much longer now; I've been approving web copy and stuff. Some new bugs popped up this week."

Works fine on mine. Is your Pod Go Edit otherwise working OK? Just check too that you're not trying to load it into a patch where DSP is maxed out. Also check youre not trying to drag n drop a zip file.

I think we're a month or so on now from going into Beta testing for v1.30, so fingers crossed we're not too far off v1.30 being released (unless of course Line 6 have found some bugs that need fixing).

Headrush and Alto are virtually identical but afaima Headrush do not currently offer a 10" variant. However, for band purposes the Headrush FRFR112 or the equivalent and virtually identical Alto TS312 are likely to be your best option for bottom end and overall volume. Both units are however close to double the size and weight of the Headrush FRFR108 or Alto TS308. Have you considered perhaps two of the 108 or 308s which will give you flexibility 're spread, more volume, and you'll have the option of perhaps using one outward facing with the other as a monitor cab?

When you select tuner if it's not muting, go to tuner settings, knob 1, and you will see the option to set the tuner to mute. See p15 of the Pod Go Wireless manual.

A Headrush FRFR112 (12" speaker) should be perfect for you. Later, you could even add another FRFR112 if you needed it, or add a FRFR108 (1x8") to use as a monitor if needed. Lots of options. The Alto TS308 (8" speaker) and TS312 (12" speaker) are virtually identical to the Headrush range, but they also do a TS310 which gives an additional 10" speaker option. But assuming there is a PA in the room, you can simply go through that and you don't need to panic and buy gear. Going through the PA is exactly what I do for both rehearsals and gigging; prior to buying my Pod Go and Covid lockdown I used my Vox Tonelab SE straight through the main PA for gigging - no amp, no FRFR speakers of my own - and our second guitarist/vocals used a Vox Tonelab LE straight through the PA. If I hadn't pointed it out would you have realised we weren't using 'real' guitar amps?:

Did you log into your Line 6 account?

Each time there is a firmware upgrade, you have to load the latest Pod Go Edit onto your computer first and then upgrade Pod Go itself via that latest Pod Go Edit. The latest version 1.22 is here (for both Windows & Mac), with instructions. The latest version of Pod Go Edit will always be in the Pod Go section of 'Knowledge base': https://line6.com/support/page/kb/pod/pod-go/pod-go-121-r976/