grdGo33

I was also thinking about shielding the 112V guitar; since it's mostly worse with that one.  And I actually just did that, just using some aluminum foil on the pickguard and in the cavity of the 2 single coils.  The way the humbucker cavity is routed, there's not even enough space for 1 layer of aluminum!  So I thought this would do nothing since I couldn't really shield the humbucker, but lo and behold, it seemed to have worked!  I think it did a good difference, should have been more scientific and do a test before and after, but being lazy, I just did it, and I think it made a difference...

Oh yeah just compared with another guitar and it's definitely fixed.  Even with 2 distortion pedals + amp drive maxed, well, there's obviously a lot of noise, but no more of that "you need to touch the strings so that it doesn't hum like a mofo!"  :D  So yeah for me at least shielding the guitar made a big difference!

I guess this is where the L6 native comes in?  (https://shop.line6.com/software/helix-native.html?___store=ww_en&___from_store=ww_en&___store=eu_en)

I don't quite understand though how you could send your guitar sound via audio interface, then have the L6 Native crunch the bits to output the processed sound without latency, but you couldn't send your processed sound from POD Go to your DAW and then just play it in a DAW without noticeable latency...  So I'm thinking that the L6 Native also has serious latency issues and it's fixed in video editing?  After some search; some people are having latency issues with it too, others claim to have none...

Also these types of latency issue just sound kinda silly... I have a DAC which has pretty much zero latency, 3D games today seem insanely more intensive than just playing the sound from the POD Go, so I can't understand wtf is so complicated to play already processed sound from the Go without latency...!  Blows my mind.  Definitely something I'm missing here.

Reading up I've now see < ASIO Drivers > mentioned, not sure I was using these or even had these installed, maybe that's part of the issue...  I mean I had massive latency, like >0.2s or something...

24 minutes ago, phil_m said:

The delay, or latency, occurs because the audio is being processed through your DAW and then to your speakers. If you connect your speakers directly to the POD Go, you’ll have no latency.

Yeah obviously...!  ;)

So there's no DAW or setting or whatever which can reduce the latency enough so that you can effectively output the Go's sound via USB to computer speakers?  I vaguely remember that you can reduce the buffer size (or buffer number?) of the DAW, which reduce latency, haven't tried it yet, but in the same breath he said it also reduce the sound quality, haven't gotten to test it out yet, wonder if it's usable... Hmmm...

I was trying to find some DAW which would allow me to use the Go to output direct from computer speakers, but I haven't really found one which can do it, for instance Audacity has massive delay which make nearly impossible to use live.  Is there any way to do it?  Something I'm missing?

Yeah, that's the point of snapshots!

11 hours ago, bassrunner said:

I also have problems with all of the amplifier sounds giving me a odd distortion sound when I take the Drive above about 4. Sounds like an amp with a 4 X 12 speaker cabinet with one blown speaker. Almost a rattle type of sound.

Could it be clipping for some reason?  Are you running other effects or have you boosted the volume anywhere else on the chain?  I think it's probably user 'error' as this isn't really the type of 'bug' you encounter...  It's dedicated software + hardware so if it's working on one unit, should work on all, unless your unit has some physical defect somewhere, but then it would likely apply always and not with just a specific setting like 'drive > 4'...

Could you try just starting from a new preset, with just amp + cab, say Cali Rectifier, increase the drive to 8, should be fine...  I even added EQ +12dB and no issue on my end.  Maybe check your global EQ...   Plus lastly, if you record anything using a DAW, same thing?

You probably looked it up yourself, but main differences; the outputs inputs are limited on the GO, there's no parallel amp in the chain (so couldn't run two different amps to have two different amps in stereo), limited number of blocks compared to helix; you have 4 'anything' block (delay, distortion, effects, compressor, etc.  So you could put 4 distortions ,4 reverbs, etc.), the other blocks (volume/wah pedal, EQ, amp, cab) are static and although they can be moved you can't say replace EQ with reverb.  Also out of I don't know 250+ amps/effects/etc., there's maybe 5 or something missing from helix.

That's pretty much it, besides price, size of unit, etc.  The sound quality is 100% the same as the big helix.

Quote

this is not user friendly for live gigs.

Yeah you shouldn't be editing or saving anything during live gigs imho...  There's 2 features which could be useful; snapshots, allows you to save different states, so you'd be better off having a couple snapshots to deal with whatever you're having to deal with.  Also there's min/max values instead of on/off, so maybe that could give you whatever adjustments you would need to do live...   Or, just go with the 100+ user patches!

I just started to use the Pod Go Edit software and boy does that make a huge difference...  My thought process was better start with just the unit itself, learn how to use it as is, and once I'm fairly familiar with how to use it properly on its own, then move on the to the Pod Go Edit.  But I think that was a mistake as honestly, editing patches with Go Edit is 10x better than directly on the unit...  Just having the list of amps, cabs, etc., with pictures makes a huge difference, especially with amps where there's 100+ different ones and scrolling to find one takes forever!  

So suggestion for improving POD Go:

1. Add an interface to show the effects/amps/cabs/etc., with pictures in a grid, for easy selection.  Ex:  If the amp select page was fullscreen and showed say 12 or 18 amps (2 or 3 rows of 6 amps) with the same pictures as Go Edit, and you could scroll through the next/previous 12 or 18 amps using the pages, man, that would be a HUGE plus for usability!  As is, scrolling through 100+ amps or dozens and dozens of cabs, effects, etc., is PITA!
2. Fullscreen page for setting up amps, effects, etc.  If you could have 2-3 rows of parameters, and the page would select scroll from row to row, that would be a lot better than always showing the top chain, which you're not going to edit if you're editing a distortion, amp, cab, etc.  Seeing more parameters in one page would be a an improvement!
3. Improve the min/max values...  It's quite a pain to setup...   Maybe simpler system like pressing one of the footswitch while turning the knob would assign min, and pressing the knob would change the color and assign max?  That way, it would be super simple to assign whatever value you wanted to whatever footswitch you wanted.

But yeah, man, if you're not using Pod Go edit, you're making yourself a huge disfavor!  It's so much faster and more enjoyable than fiddling on the unit itself!  But I think that with better UI, editing on the Go could be a lot more enjoyable!  #2 and #3 above would be nice to have, but the #1 is really essential IMHO to make editing on the unit itself a lot more practical!

Ah no!  I also updated with the Pod Go edit, but it failed and threw the error, then Pod Go Edit would not detect the Go anymore, even in update mode...  So only then did I start using L6 update software, which did recognize the Go, and was eventually able update and un-brick the unit!

Just a regular PC (parts build), Windows 10, the other was a Dell laptop, also Win10, but I think the updater didn't work on the Dell because I only installed the Line 6 Updater.  I think it requires some of the files from the Pod Go Edit, or maybe the drivers with the  "Fixes a crash that would occur with Logitech's G HUB.".  Anyway, of course it doesn't mention any of those things so it shouldn't... But who knows at this point...

My firmware update failed miserably and I had to spend maybe 1h trying to fix it.  NOT FUN.  (https://line6.com/support/topic/56809-error-while-updating-to-firmware-111-pod-go-wont-boot-up/).   Hopefully the other thread might help someone going through the same.

But I guess it goes to show that the reliability of the unit isn't really there.  From random locks and freezes, the unit not powering on, the firmware updates crapping out and temporarily bricking the unit until you download additional software and try the same thing multiple times, I honestly couldn't recommend the unit for any type of gigging, where you can't afford to look like a loser who's gear stops working in the middle of a show.

I'm hoping that now that it's been updated, it won't crash as often as it did, but I've had it for about a month, used it a couple of hours per day, and I've had maybe 4-5 crashes and 3 booting issues.  Not the end of the world, but I hope the Helix, LT, Stomp, etc., are more reliable because the POD Go sadly doesn't look very reliable...  I hope it won't crap out after a couple of months/years either...  :\

This is infuriating...   I tried on another computer: Installed updater, launched Go in update mode, and it wouldn't even recognized the POD Go.  So much for that solution...

So I went back to my main PC.  The error message I posted above clearly has 3 steps to follow.  I repeated the steps like 5+ times, same result every time.  FAILED.  Seemed to fail almost instantly every time.  The original update failed, but it took maybe 20s and the status bar moved maybe to 40% something...  But it didn't even seem to get to 10% these last few times...

I then closed the updater, restarted the Go, started again the L6 Updater, and got this. 

(So closing the updater is maybe a key step!)

Good...  But man, Line 6...  Come on...  This is not normal, and I'm certainly not the only person this happened to. 

Also, there should at least be the relevant links for recoveries in the threads about the new versions, or the downloads...   Otherwise, it's just an additional pain to find the relevant info and fix the issue. 

That was not fun.  :\

Yeah same thing with updater updating to 1.11...

Firmware Update Failed

An error has occurred. Please try again.

Please follow these steps when updating your Line 6 Product.

1. Turn the power switch off, then back on.

2. Ensure the USB cable is connected directly to your computer and not to a hub or peripheral such as a keyboard or mouse.

3. Click 'Continue' and attempt the update again.

Guess I'll try from another computer...  This is...  Stressful and quite annoying/disappointing...  :(

[edit] some info about POD Go recoveries here...  https://line6.com/support/topic/56008-pod-go-firmware-mishap/

Sigh...  I just tried to update the firmware of my unit and now it's not booting up...  Everything was going fine until it said "Error", turn off the Go power switch, etc., and after turning off the Go power switch, it doesn't boot up anymore...

• When I power on the unit normally I just get the Pod logo and nothing happens
• When I connect the USB cable,  nothing happens

If I boot up the unit in 'update mode' (Page > button),

• I can hear the Windows USB device connected sound, but nothing happens. 
• If I launch Pod Go Edit, it says "no device connected".
• If I replug the USB cable, I get a device connected sound, but nothing happens in POD Go Edit, still "no device connected".
• I tried a different USB cable, different port, same thing.

I tried  "start with the POD Go turned off, then flip on the power switch while holding down for 5-8 seconds: - C & D - Factory Restore (Restores all factory settings)", but nothing happens.  Stuck at Pod Go logo.  :\

What can I do?

[edit] ok I had found this article https://line6.com/support/page/kb/pod/pod-go/pod-go-failed-update-recovery-r944/ and it mentioned the Line 6 updater, it doesn't reference the Pod Go Edit 'updater', it refers to another application, trying that one...  Fingers crossed...

Good post!  A few random thoughts of my own:   I think pro sound engineers or others with actual experience with what is being emulated with the Go will have much easier time.  For instance, I was just creating a patch for the Solo amp Crunch channel, and was playing with cabs, and it's crazy how just the cab settings affects not only the tone (FR) but even distortion characteristics of the amp...  Just changing the microphone distance, or changing the mic type, changes everything, as if you had selected a completely different cab.  And I don't think many people on earth have that type of experience with real equipment.

I think also the Go is so complex, you could spend months trying to learn everything it has to offer and still not come close...  So I'm thinking about not even trying, just go with an amp, find a cab, reverb, delay, etc., and experiment with it, and don't fret everything else and don't try to learn everything...  In that respect, the Go/Helix is one hell of a special type of beast.  There's so much depth...  To know everything about it you'd probably need multiple PhDs on the Helix/Go...  (one for amp models and settings, one for cab 'science' & mics, then effects, compressors, distortions, etc.)  But luckily, it's still simple to use and anyone could configure their own great sounding patches without too much trouble.

As for gigging...  I'd be worried.  It crashed many times on me,  refused to power on sometimes, so for now I'd be weary and wouldn't do it without a backup. But I've yet to patch it to the latest firmware, which I'm hoping should help, and I hope it won't brick the unit as there's been quite a few messages about it...!

2 hours ago, benthere77 said:

When I was using the wrong cable I did have my "Main Out" set to Line.  The cable really makes all the difference.  There are a couple of short but informative YouTube videos on the differences between an instrument cable and a balance/shielded cable.  The volume output didn't change drastically, it just got more consistent when changing between presets.  With the old cable the volume seemed all over the place. 

That's what's really strange, shouldn't make the preset volumes be more or less consistent, and with 10 feet cable the noise difference should be barely perceptible...  Maybe FRFR 108 really doesn't like unbalanced?  Anyway, problem solved is what's important!

2 hours ago, benthere77 said:

Just out of curiosity, what kind of speakers do you like for the Pod Go (or whatever device you use)?  Are you referring to studio monitors or just other powered speakers that aren't "frfr"?

I'm using DIY Seas 2 way bookshelves speakers, but also tried with more budget 2 way Vifa DIY and it also worked perfectly.  I don't think it really matters as long as the speakers are decent, if they do fine with music they'll do fine with Go; music is much more demanding so if you keep SPL reasonable really nothing 'special' required for Go!  (Better speakers = better sound, but diminishing return applies, so I really wouldn't go crazy...)

35 minutes ago, benthere77 said:

It was just a 10 foot cable but it turns out there is a huge difference in sound quality and also really a huge difference between an instrument cable and a balanced/shielded cable.  Actually I'm lucky I didn't damage the speaker from what I've read. 

Also just because that doesn't make much sense to me, if you use that same cable to connect your guitar to the Go, does it change anything to the sound?

Also what was your Global Settings Main Out setting?  Line or instrument?  I'm now thinking that if you had it to instrument and the was still able to amplify the very low signal, that could have very well have killed your sound quality; I don't think the FRFR is designed for instrument level signals.  And maybe with balanced the Go automatically switch to line level? 

Did the volume output change much between both cables?  That or a bad cable would be logical explanations of why it sounded so much worse than balanced...  Otherwise; really really surprised going balanced would make such drastic difference!   o.0   But if you had it set to 'instrument' and tried again with 'line', it really should sound the same, just make sure you lower your FRFR volume before switching!  (could be super loud after changing!)

Wow quite surprising how long an unbalanced cable were you running?  I'd have expected marginally less noise and maybe the tiniest amount of volume...  But if you're not running like 30+ feet long cables, I'd have expected the difference to be barely noticeable, especially if all you're running is like 5 of 10 feet of cable...!

Ok figured it out while typing this and testing for like an hour, but it was quite frustrating, so in case it helps someone... If you want to add/edit multiple min/max values to a footswitch.  Manual states:

So to create:

1) hold a knob

2) press learn

3) press the footswitch (here, values reset to 0-10, annoying but normal)

4) you can alter different parameters to set min/max, but you still need to specify the footswitch for every setting, which is annoying, but necessary...

5) press view to exit, no save required or any other switch/learn required to save

here you should see something like "Multiple(2)" for your pedal assignment if you switch views, and if you press the switch it should change between the values

6) save 'normally' so your saves are saved if you switch patches

To edit, same thing as above, but skip the steps #2 and #3:

1) hold a knob

2) change the different values you need to change (you don't need to press learn or footswitch before!)

3) press view to exit, no save required or any other switch/learn required to save

here you should see something like "Multiple(2)" for your pedal assignment if you switch views, and if you press the switch it should change between the values

4) save 'normally' so your saves are saved if you switch patches

This could have been clearer in the manual... 

Nice!  Great choice I've heard great things about the Katana 100 mk2, it's a fantastic amp on its own!   :)  It even has an FX loop, so make sure you try to the 4 cable method of the Pod Go's manual, that way you'll get the most of the setup.  Not that it's really necessary as you have plenty of choices (too many!) in the Go's amp, but who knows maybe you could use some of the Katana's amps or effects in combination with the Go's, so get a 'free' distortion, boost, or extra effects?  Anyway, worth a try.  :)

Which headphones do you have?  Maybe the crispness you hear is 'fake', as I was saying with the V eq settings, some headphones also have excessive treble which might sound 'crisp' or 'detailed' or whatever, but it's just 'more' treble...  Anyway, bit hard to explain.  But also, buck for buck, you need to spend a LOT on speakers to equal a good pair of headphones; especially in how resolving and how 'crispness' and responsiveness; in the room, there's all kinds of echo, so even with music, a pair of say $300 headphones can sound more resolving and clearer than a pair of $5000 speakers in a room...  Headphones just naturally have a cleaner/crisper/more resolving sound, just the nature of headphones vs speakers, so it might be unrealistic to chase headphone sound in speakers!

Also lastly, sound coming out of speakers is quite directional, and every speaker will sound different depending if you're higher, lower, on the side, etc.,  So if you want to get the most of your speaker amp, instead of having it on the floor, try elevating it by putting it on some furniture or something so that it's at head level and points at your head, that will make a big difference!  Maybe just tilting upwards can help. Have fun!

11 minutes ago, mettlus said:

Thank you Jesus! 

Haha you're welcome, my son!

Haha I had a bit of the same experience when just trying out the presets, but check out this guy, the presets are actually not that bad...  Can really be a guitar & player issue! 

For killer tones, it depends on your taste & music, but I love the tone from these guys, they sell some patches and even have a free one, the AC30 below, so you could download it and tweak/learn from it...

1 hour ago, benthere77 said:

Should that say "Pre CAB/IR" or "Main Out"? 

Main Out.  With "Pre CAB/IR",  your amp out bypasses your cab and any effect after it, so it's definitely not what you want.

Quote

I took your suggestion and just played a YouTube video of SRV playing Riviera Paradise through my FRFR and overall the sound was good but I do notice a little of the same thing I"m hearing from my playing...super "bassy" and not quite the level of crispness I would like on those higher notes coming from the B and E strings.  Still sounded pretty damn good though.  Maybe it's just a matter of tweaking EQ's to tamp down the base and bring out the highs.   Sounds a little daunting.

Quote

This guy at 4m https://www.youtube.com/watch?v=ioFesfEOTR0  describes it as "it sounds like the headrush has a cold", nasal... Anyway, don't expect too much from the FRFR!

Weird if you said it sound pretty damn good...  I'm very surprised!  So compared to your headphones, the FRFR sounds "pretty damn good"?  I'm sad to say that I couldn't find any measurements of the FRFR-108 (ex; frequency response, waterfall graph, etc.).   The 'contour' button just boosts the bass & treble, this is typically a trick for 'cheap' sound systems to sound better, because it boosting bass and treble will make people think it sounds better, even if it does not, the old 'v' EQ trick...   (short term sounds better, longer you realize it's just bumped highs & lows and it's no good...). 

So maybe you could tune your settings so that they sound better on the FRFR, but to me, that's a compromise, as pretty much the Go gives you '99%' sound quality, and then it goes through the FRFR, maybe maybe lowers it to 80% or whatever it is, depending on how good/bad they really are...  But then the issue becomes that if you ever upgrade the FRFR, all of your patches will likely sound like lollipop, because they've been specifically tweaked for the FRFR...  So all this tweaking for FRFR was for nothing, and now you've get patches you've got to un-tweak your FRFR fixes...  So I'd say, try to invest in a decent pair of speakers!  Be it they're studio monitors or just regular stereo speakers, that you'll likely notice right away a big improvement and you won't have to deal with anything FRFR related...

Otherwise, to really know how great/bad the FR sounds, compare this clip with headphones or speakers,  vs FRFR.   This is genuine tone from the Go, and the guy goes through all the presets.  So at least it eliminates the player + guitar.  Me trying out the presets sounds NOWHERE as good as this guy...  So you'll at least get a better idea of how it should sound, vs how it does sound on FRFR...  Quite curious to know how it'll sound let me know!  :)    (btw, what speakers or headphones can you compare with?)

On 7/9/2020 at 9:46 PM, benthere77 said:

sound either completely muddy or too weak and tinny. 

I replied in your other thread headphone vs FRFR I think it was.  But yeah, I'm 95% sure that the poor sound quality is just coming from the speaker.  It is a budget speaker, and from every recording I've heard of it, you're describing its innate sound.

So yeah, the Pod Go is 200% better than the Spider Amp, but your FRFR 108 is killing all of your tone.  Try plugging to your sound stereo if you have one (ex; Go headphone out), and you'll likely notice a dramatic sound improvement if your stereo has decent sound.