voxman55

I wasn't aware you could drag and drop...need to check that out as I've always just used the import command.

Depends on what you want to do. 4-cable method is where your amp has an fx loop and is typically for those that might want to use their Pod Go for effects only but who want to use their own amps natural tone for gain and/or cleans, including using their amps natural speaker tone. You can also design patches where the signal chain lets you also use the Pod Go amp/cab models and bypass the real amp/cab. So 4-cable gives the most flexibility with the best of both worlds but requires 4 physical cables and is therefore a bit 'untidier' and takes a bit longer to set everything up including re-thinking your Pod Go set-up and patch design (if you never want to use Pod Go's amp/cabs and always just want it for FX, then in my opinion a pure FX unit such as Helix FX might be the better option). Alternatively, there are those that simply want to use the amp/cab models in Pod Go and just use their combo as a power amp where Pod go is connected to the amp FX return thereby bypassing the amps pre-amp input stage. Finally, there are those that prefer (or have to, where they have no fx loop, or where they might only have a parallel FX loop that doesn't give a full 'mix' and where 4-cable might not sound as good as compared with a serial FX loop) to use Pod Go through the front end of their amp (typically where the amp is set clean on a single channel amp or through the clean channel on a twin-channel amp), where the Pod Go amp/cab models will be coloured to some extent by the pre-amp and speaker characteristics of their combo. This becomes a problem though with single channel amps where the amps gain increases with volume so is best through the clean channel of a twin channel amp. If I use Pod Go with an amp, I prefer to just use the amp as a power amp and connect Pod Go to the FX return. However, for gigs I don't use an amp, just my MFX straight through the PA. I can also put my MFX through a FRFR powered speaker (I have a Headrush FRFR108 which I'll use as a monitor cab or for FOH if it's a small club thing and there is no PA, or if PA channels are unavailable). Speaking personally, 4-cable generally doesn't suit me - I want to use the Pod Go amp/cabs, I don't want the extra faffing around, and I like to have patches designed so that they give me a more consistent tone and approach, hence I go through the PA or an FRFR powered speaker. If I set patches to suit one amp via 4-cable, those patches will sound quite different with another amp via 4-cable because the amp gain stages and speakers are different. So it's very much horses for courses, it depends on how you want to use & set-up Pod Go (or any other MFX), it's down to experimentation, and your needs & personal preferences. There is no 'one-size fits all' solution.

Around 60-70% - that way you have some extra to control the volume instantly if you need to without having to alter main board volume - for example, it can be difficult to accurately balance the volume level for all your patches and even then different ambiences in different venues can affect these. If you go 100% you have nowhere to go but down.

The max total current draw is 1900mA as compared with 2500mA with The Fender LVL5 Engine Room, and the LVL5 is less than half the price. I'm intrigued that you can power Pod Go with it as reportedly it needs 2500mA.

I use a Stagg 1/4" to 1/4" high quality balanced TRS 3 metre cable. There's no difference in quality with an XLR as the Pod Go outs are XLR equivalent quality - Line 6 didn't add the 3-prong XLR out connection because of unit size limitations. The cable you've highlighted is fine as the FRFR108 allows for both 1/4" and XLR connectors. You might want more than a 1m cable though!

Agreed, those that need those features will go Helix LT/Floor, those that don't wont.

These are expected in 1.30

I certainly think there's some truth to Line 6 wanting to keep clear dividing lines in its product range, which is why any improvements to Pod Go will be after the Helix products have had their upgrades, and even then the processing power differential means these upgrades will often be 'diluted'. Line 6 has made it clear that Pod Go is a 'Pod', and not a Helix - so whilst it benefits from Helix modelling, it is a 'poorer relation' of Helix. But whilst there will be some customers who treat Pod Go as a 'Helix stepping stone' the vast majority of users would not want to buy a Helix Stomp, LT or floor, for the same reasons I wouldn't - and the biggest of which is 'form factor'. For me, and I suspect most Pod Go owners: Helix LT/Floor are too big and heavy, too expensive, and contain a host of things i don't need and wouldn't use Whilst Helix Stomp can be used on its own, it is designed for use as part of a pedal-board. As a stand alone unit it originally had insufficient footswitches - whilst there is now a Helix Stomp XL with more floor control, it still has no built in volume/expression pedal and the screen is still too small. The full colour LCD display of Pod Go with its 'solid block' icons is appreciated even by Helix Floor users. I dislike the Helix LT/Floor displays that use 'outline graphics' & which are less clear However, the lack of additional block(s) and DSP info (the latter is not even available in Helix Floor, but is a wanted upgrade even for Helix users as per IdeaScale) are nothing to do with product differentiation, but is, in my view, borne purely from Line 6's stubborn refusal to accept that it's original premise for Pod Go needs revision and its 'anti-DSP info' philosophy is just illogical, flawed, narrow-sighted... and plain wrong. Just look at the Ideascale feedback on this for not only PodGo but also Helix users. See also discussions and my supermarket story in an earlier thread here.

Hopefully, should still be under warranty

Sadly I fear not as @Digital_Igloo has said that additional blocks, as well as connected themes of showing DSP percentage usage, and freeing up the amp/cab blocks, is not something on their 'PodGo to-do-list'. See here: https://line6.com/support/topic/61213-voting-for-pod-go-requests-for-extra-flexibility-the-problem-with-ideascale/?tab=comments#comment-393569 https://www.thegearpage.net/board/index.php?threads/line-6-pod-go.2113195/page-362#post-32405697 For the record I absolutely agree PodGo needs at least one additional block if not two, it needs DSP information, and it needs the ability to remove the amp model to free up DSP for greater flexibility (eg for patches where users might want to go through an amp and only need effects). I go on record to say that on these issues I think Line 6 has got it very badly wrong, it is not listening to what its customers want, it's not adapting to competitors like Zoom and Mooer, and has not bought into the fact that its original premise for PodGo needs review and that it's now well past time to take the training wheels off because users are now much more savvy re DSP management. I had posted on this (as per above link) and tried to raise the profile of IdeaScale to get more votes on these themes as this is where Line 6 considers customer feedback because generally they don't really pay any attention to individual posts on forums eg like this one. So, if you haven't already done so, please go into the Ideascale links in the post link above and vote for every instance (as often there are duplicates) - the more votes, the more chance we have of getting Line 6 to reconsider its position. At the end of the day we as customers can't make Line 6 do anything it doesn't want to do so Pod Go customers will just have to accept that there are some things Line 6 will consider and give us, but there are others it simply won't. Unless Line 6 is overwhelmed for requests on these items, I can't see them ever changing their stance but I'll still try & carry on campaigning for these - I was even thinking of possibly doing a Youtube video on it to try & drum up support. I'm sure at some stage there will be a Pod Go Mk2 that will have more processing power and flexibility but as Pod Go was only launched in winter NAMM January 2020, that's unlikely to happen for quite some time.

Just picked up on 'The Gearpage' that @Digital_Igloo advised Pod Go 1.30 just entered internal beta testing! So fingers crossed, whilst we don't know exactly when or what's in it, hopefully this isn't too far away now.

It's on page 38 of the new combined PG/PGW manual or p33 of the previous PG manual

Are you using the Pod Go expression pedal as a volume pedal, or an external Volume pedal. If Pod Go expression pedal it sounds like you've reversed the polarity in global settings so that behaviour is reversed. If external, you need to reverse the polarity. There is a global setting in Pod Go to do this, which is in the manual.

Something sounds very wrong, as the Pod Go tones are quite frankly excellent and (up until the latest Helix v3.1 that has a slightly higher sampling rate) has exactly the same modelling. Are you on the latest v1.22 firmware? Exactly how are you using Pod Go? Headphones, powered cab, amp? If the latter, what amp and are you going through the fx return, 4 cable, or front end? If headphones, what model? If Pod Go sounds that bad with everything, I can only think you must have a faulty unit particularly if you are using Helix with no problems. Go back to the store and ask them to check it, and if it is defective request a replacement. I use Pod Go with Audio Technica ATH M50x headphones, through a Headrush FRFR108 powered cab, and through the fx returns of my Laney Cub 12R 1x12 all valve combo and Mk1 Marshall 1x12 80v '8080' Valvestate. It sounds really good through all of them and its particularly stonking through the FRFR108. I'm a live gigging player so am not a 'recording/studio' guy and the only thing I've put together was a very simple recording of a patch where, based on an idea by someone who posted a patch on Line 6 Custom Tone, a used a Soldano Clean amp model in a single patch that could cover a whole range of tones from cleans through to rock eg for a covers gig. It's not an amp model I'd have thought of using but it was an interesting experiment. There are 4 snaps plus a chorus to kick-in. Try the patch out in your Pod Go (https://line6.com/customtone/search/?submitted=1&family=pod_go&search_term=Soldclean+SCsnap ) - if it doesn't sound like this then there's definitely a problem somewhere.

No probs, glad to help

Course you can. Go to eg snap 1 and put a snap assignment on the wah, set to wah on, then save your patch. Go to snap 2, again put a snap assignment on but this time turn the wah off, and save the patch again. Now when you engage snap 1 the wah will be on and when you select snap 2, the wah will be off. Exactly the same as with any other pedal. And if you want eg snap 3 with wah in a 'half cocked' position (eg for something like money for nothing), assign snap to each wah parameters you want to change, get your sound, save the patch again and now you'll get the cocked position when you switch to snap 3. (BUT NOTE: the moment you touch the wah pedal in snap 3, it will jump to the tone of its 'real' position).

See here re what IR's are: https://line6.com/support/topic/61397-help-me-understand-paid-irs-and-presets/?tab=comments#comment-395745 And here for links to free IR's: https://line6.com/support/topic/57757-best-free-impulse-responses/?tab=comments#comment-349956 If the cabinet IR is in a .wav format it should be fine for Pod Go Hope this helps & congrats on your new Pod Go - make sure you upgrade to the latest v1.22 if you are not on the latest firmware. Best way is to to load down Pod Go Edit v1.22 first and then upgrade your Pod Go from there.

Hi, there really isn't anything particularly special about that tone which is a typical studio type fusion tone using a compressor to level the dynamics and 'soften' the distortion. He's also using the neck pickup on both guitars. It's not a sound I'd typically use as I'm more a classic rock & blues player. With regards to amp model and fx he's using (distortion, delay, reverb etc) why not post on the youtube link and ask him the components of his tone? He seems to be a nice guy and I'm sure he'd be happy to give you a steer. This afternoon I was playing a Telecaster with my Valvetronix AD120VTX amp, and using compressor, some delay and reverb with the US High Gain (based on a Peavey 5150 I think) it's pretty much there.

Other way round. Whenever there is a new firmware version that impacts on what you see in Pod Go Edit, you should upgrade Pod Go Edit first and then upgrade your Pod Go device firmware via the new Pod Go Edit version (which is the instruction Line 6 gives) as the two are inextricably linked.

I bought my Pod Go from Yamaha (who own Line 6) and had a 2yr warranty automatically at no additional cost. In fact, I even got a modest discount when Pod Go's were in short supply. Although there may be the odd exception, generally buying extended warranties for anything other than big items such as a car are typically poor value for money. If you are in the UK, we have very strong consumer protection that puts the retailer directly in the frame, and if you buy anything on credit card or even part pay by credit card (subject to at least £100 of the purchase on the card I think), you can bring the credit card company into any dispute under Section 75 of the Consumer Credit Act 1974. This means that UK consumers can still have substantial rights beyond a 12 month manufacturers warranty. I can't comment re the US or or other domains though.

Should be on their way in the forthcoming update, as these were top of Line 6s Pod Go to do list. Its been 'extrapolated' on The Gear Page that based on Helix/ Stomp timescales, we should see it in late August. I appreciate that's not official and Line 6 never give much of a clue as even they don't know until a day or so before, but Pod Go really is due a proper firmware upgrade about now. Not counting bug fixes it's only had one since launch and that only imported some models from Helix 3.0 but gave no functionality upgrades. So I do feel Line 6 needs to get this done.

Can you post a link or two to the vids you mean? What guitar is he using, and what are you using? And are you trying to design a patch for headphones, through a powered speaker, or an amp? If the latter, what amp are you using and are you using Pod Go through the fx return or in front of the amp?

I keep seeing requests for DSP info and I can't understand why Line 6 won't show DSP usage in Pod Go or Helix. See here: https://line6.com/support/topic/61213-voting-for-pod-go-requests-for-extra-flexibility-the-problem-with-ideascale/ line 6's response on this is frankly ridiculous, ditto their response to taking off the training wheels on Pod Go and not adding more flexibility by allowing one or two additional blocks and releasing the amp model from being a fixed block so users (especially if they want some patches as a pure stomp box board with no need for amp/cab) can have more effects and/or higher DSP effects in their chain. I understand completely that when Pod Go was initially designed & launched, Line 6 had a set view for its place in the market. But things have moved on in leaps & bounds - not just user understanding/savvy driven by youtube, forums, experience etc, but the market is fast changing too and competitors are cottoning on to all this. For example, Mooer, NUX, Zoom (G6/G11) all now show DSP usage in their latest MFX units. So, as per the post, please go onto Ideascale and vote for all the improvements you'd like to see.

@Kenny202 odd to hear you are finding that delays in Pod Go colour your tone as this isn't something I've encountered with headphones, through a powered speaker, or through the fx return of my amps. I wonder if this is something that is more sensitive when you go through the front of a tube amp? Interesting observation 're the NUX300 as at one time I was thinking if getting the NUX MG20. However, several things put me off. Firstly, in the UK, there is virtually no customer support and having read that quite a few units had been reported with problems, I'd be reliant on the store. Line 6 customer support was a big consideration. Secondly, as a gigging player, the NUX pedals simply didn't provide the necessary floor control without external devices. Finally, fx options in particular seemed somewhat limited. Out of interest, are you a gigging player? If so, how do you manage the limited floor control of the 2 footswitch NUX300 on stage?

Yes. Just experiment with settings. Patches set to sound good through headphones may not always sound good through the front end of a tube amp. Create some patches specifically for your amp and you should be fine. Whether you want to use cab modelling/IR's as well as the amp model will be something to experiment with as you're going through a real amp and speakers. There are no rights and wrongs - just keep an open mind, experiment, and see what sounds good to your ears. You may find that you need to 'tame' fx including reverb & delay settings and even gain levels of any amp or distortion model, because the front end of your amp, even set to clean, will add its own 'tonal colour' and with a real cab/amp pushing real air you'll have natural room ambience which will vary depending on where you are playing. Hence why I think you'll be better off designing purpose built patches, and toning things down to begin with.