grdGo33

Yeah also you might want to check into IRs for bass cabs, I've downloaded a few which sound absolutely horrible with a guitar (LOL) but for bass, that could open a few new options.

The more time I spend with Go, the less and less I find it important to have dozens and dozens of amps...  It just takes so much time to familiarize yourself with an amp, then you even have to factor how boosts, distortions, mics, cabs, etc., fit the equation.....  I do understand the 'more is better', but am slowly drifting back to just a couple good/great amps is all you need.   Seems to be 14 bass models, hopefully they're good...

And last thing, you might want to get creative...  I was watching a vid where a compressor (tube) as a drive pedal.  I mean, there's just so many things you can do, the limit is your imagination, knowledge, creativity, etc, with all the options on the Go...  The Go is a tool in the end, so it's what you create with it, and how you use it, having just more and more tools...

Ex;

So yeah, at one point, wanting more is ok, but, are you even using 100% of what you could be using?  There's countless things you might not have thought of, so maybe getting creative, reading forums, checkout out vids, etc., might give you new options you didn't think of before, which could expand the Go's capabilities in ways you didn't think of before...

I know that for just guitar, you can do so much with just 1 amp.  Hell, that was the standard for decades; just using 1 amp. 

In b4 posting on ideascale suggestion!

I think the issue is that a minority of PGO users are bass users, so if 95% play guitar, you'd kinda expect 95% of the energy to be put towards these users...  If it's 300h of work to bring a distortion pedal to fruition, are you going to introduce a feature that 95% of Go users want, or a pedal that maybe 3% (maybe not all bass players want that pedal) would want, the answer is fairly obvious where the energy should be spent...  I guess it could open more sales if bass players would get the unit if it had more bass features, but yeah, you bass guys need to be more vocal and post on ideascale if you want to get L6's attention.  :)

IRs are basically a  'snapshot' of the sound of a amp & mic.  So say you feed a signal to an amp, and then record the sound with a mic, both the cab & the mic will have their own sound (their own distortion characteristics) and that is what the IR simulates.  So when you run your Go's signal chain through an IR, the output of the IR block would be the same as if recorded through studio's amp/mic/room setup. Basically, they measured how cab + mic change the signal, and the IR changes any signal the same way.

So if you're buying an IR from Studio X, in theory, you're basically getting 'the same sound' as if you were using their amp + mic setup.

Welcome!  :D

You might also want to read this thread! 

Yeah, just place the looper block at the complete end of your chain!  As any effect which is after the looper, as you said, will affect the looper block looping your recorded sound!

On 7/12/2021 at 3:03 PM, voxman55 said:

A shopping tale 

Once upon a time, there was a supermarket customer (me! lol)

...

That was quite the tale.  LOL   :D

13 hours ago, lawrencetovarjr said:

either way it’s not acceptable to me and if it can’t be addressed and fixed quickly I would have to return

But to be honest, you shouldn't be really using these these controls; they should be more of a last resort.  Meaning:  Everyone should just be using Pod Go Edit, as even if the buttons were working 100% correctly, it's still a PITA to setup anything with the button controls and built-in GUI. 

And honestly, not sure if I'm contradicting myself here (lol) but it's not really a big issue imho.  I have in my office/computer/guitar room 2 setups, a typical PC setup with desk and chair, and a 2nd 'work' station; where there's a keyboard, mouse, studio monitors and 4k screen ready to use standing up  (~4.5 feet high?  Elbow height) and around desk height just underneath the pod go.  So for editing patches; Edit is the way, but, if I'm just playing, there's no issue using the Go interface just to do some minor change; like increasing/decreasing patch volume, lowering treble, etc.  In that case, honestly, the knob bug isn't a big deal.

But fully editing patches ...  Errr... No thanks.  For the first month I wanted to learn the built-in controls and used it exclusively for a month.  And man, PGO Edit is just plain better.  I mean, scrolling through lists of 100 items, having to hit 'page' constantly, not being able to see all amp/effect settings at a time, anyway, just PITA.  Even with 100% working knobs, it would still be PITA.  Honestly, if you're not using PGO edit, use PG Edit!  That's probably how L6 intended people to use it also.

Yeah you might as well just buy a looper pedal and put it in the chain, especially when you can get a looper like the Ammoon one for $45.  One block out of the Go is kinda 1/4th of the Go's effect capabilities, so in some sense you can value it at ~$100.  Also yeah as vox mentioned, it's just more practical to use overall; you always have it, don't need to change patches, etc.  IMHO, for the price, no-brainer. 

For the looper L6 Go looper to be effective, imho, it would require it's dedicated buttons; which would not interfere with the regular Go usage; if you have to sacrifice activating/deactiving effects, exiting snapshots, etc., just too much clicking and not viable in real use...  So 100% spend $45 if you want to use a looper; the built-in exists, but just doesn't compare to a real looper, later on you can upgrade if you want to, but honestly, great little pedal which really fills your basic looper needs.  :)

5 hours ago, voxman55 said:

We don't want our users obsessing over which amp or effect uses more or less DSP; we want them choosing what sounds best to their ears. We also want POD Go users to almost never run out of DSP; opening more blocks to maybe squeeze in an extra compressor for the 10% of users who understand dynamic DSP (decidedly not POD Go's target market)—at the risk of the other 90% hitting the wall much sooner—is a non-starter. Ease of use and predictability are key here.

That seems like a terrible response... Or maybe I just don't understand the logic behind the comment.  My take on it:

1) We don't want our users obsessing over which amp or effect uses more or less DSP -- And yet people already do because as we're trying to build patches all of a sudden we can't add the 4th block we wanted and we have to go online to try to figure this sh!t out and work around these limitations.

2) we want them choosing what sounds best to their ears. --  Everyone also wants this.  Adding a % value of a DSP would not stop people from choosing what sounds best to their ears, but it would help them build patches that in the end sounds best to their ears.

3) We also want POD Go users to almost never run out of DSP  -- Well that's a fail because most people will quickly run out of DSP, then it's a PITA to work around the issue without knowing which effect uses less/more DSP.

4)  opening more blocks ...  90% hitting the wall much sooner—is a non-starter  --  Not sure what he was responding to, but if you give the DSP % and add a block slot if there is still room for another effect, you don't "hit the wall much sooner"...!

Anyway, just imho a very bad take.  It really sounds like someone doesn't want to do something and is looking for excuses, rather than having pertinent and logical reasons. 

- They say they don't want users to run out of DSP, but they don't give users the tools not to run out of DSP. 

- They say they want users to choose what sounds best to their ears, but they won't allow them to make the patches they want because they're locking out blocks even if DSP is available, for absolutely frivolous reasons. 

- They say they don't want users to obsess about DSP, but they make DSP management as obtuse as possible, and force users to go online and research that sh!t to death because the product as is is incomprehensible and they don't give users the info they need to use it properly...!  

Very disappointing answer, as you said, features the majority of users would love to have implemented.

Too bad we can't make a poll here, can we on ideascale?  % of users who want the features vs don't want the features.  And if really some users, for whatever reason, just can't handle seeing a DSP % usage or having an extra block appear if they have room (LOL does such a person even exist?!) then you can make the 2 options disabled by default, and allow users to activate it if they choose in the global settings.  And in all honesty, I can't imagine a grandpa/grandma that wouldn't welcome the features.  But yeah, that notion is so silly, it's obviously looking for excuses for not doing it.

Cuuuuute!

15 hours ago, voxman55 said:

To not believe it's software  and still stick to your belief it's physical

I said I'll believe it is software when it is fixed.  Until then, there are 2 possibilities, 1) it's software and 2) it's not software.  I don't know for sure which it is as the evidence points both ways. 

It's possible that the Lead Product Tester did not give you a correct answer...  In your quote, he said the issue was logged and that he hoped that it would be fixed, but he did not confirm that it was a software issue:

Quote

"Hey Rich, Yes this is a known issue we have logged and hope to have fixed for the next firmware update. I can't say for certain that it will be addressed, but it is logged and the team is aware of it."

When QA finds an issue, unless they've done some particular tests to confirm it's hardware/software, which he did not mention, they'll often simply log it.  Not sure what L6 QA department is like; if they have experts who can confirm hw/sw using test rigs to test the knobs, check source code, etc., but "we've logged the issue, let me close this support ticket because I've got 10 other things to do and 20 other tickets to respond to" is often kinda the way it goes in tech.

So yeah, while I won't blame you for being certain that it is a software issue, I'm withholding judgment until it's fixed, which I'd be willing to bet it won't.  I mean, the issue is pretty darn blatant, anyone who's ever used the physical unit will notice and likely get frustrated with the issue, and it's been that way since day 1, and you can be certain that it was also that way when they tested the Go before it's release.  Yet, still not fixed...  Maybe they also don't want to admit there's a hardware fault with the Go, as that would be opening a can of worms.

Anyway, yeah, I really hope you are right and it's software which will get fixed, but until it is, I'm not ready to believe it's software just yet.  :) 

P.S.  How many firmware updates without a fix will it take for you to question your belief that the issue is software?  Since our last discussion on the issue, there were 2 firmware releases right?  You really think they weren't aware of the issue?  lol    ;)

3 hours ago, voxman55 said:

Hi guys, I've just heard back from Line 6 (their Lead Product Tester), and this IS a software glitch as I suspected

 

"Hey Rich, Yes this is a known issue we have logged and hope to have fixed for the next firmware update. I can't say for certain that it will be addressed, but it is logged and the team is aware of it."

Hahaha!  I'll believe it when they fix it!  :D

23 hours ago, Kenny202 said:

From what I understand from various you Tube videos is you set up the patch as normal. That by default become snapshot one. Then select 2, make adjustments and save....3

Yeah that would have been the intuitive way to design the feature, but then if you wanted to change a setting globally (for all snapshots), you couldn't really do it that way...   So you have to tell PGEdit which parameter is linked to snapshot, here's a howto vid:

On 7/2/2021 at 10:19 AM, conradmarshall said:

it sounds almost as good as the real gear but haven't really heard the claim that it sounds better. 

There are some comparisons of amps on yt and they are very close (not exactly the same as even two amps of the same model don't sound exactly the same because of differences in tubes, manufacturing, components, etc.) but people rarely can identify the real amp from L6 in blind comparisons so they definitely can sound (do) sound like real amps.

Issue with Go though is that with its amp + cab + mic design, it's more designed to sound like recorded guitar than simulate a full guitar rig in the room.  Guess if you have a cab, you can disable cab/mic and go straight through the amp, and in theory should sound 'perfect', not sure in actuality though.... 

But through studio monitors, there is no way to tell the Go to sound just like just a real amp and cab.  So you're always getting recorded sound, which would be kinda weird if you're used to hear the sound of a real amp+cab in a room...   Maybe that's what the OP was referring to.

On 6/28/2021 at 12:39 AM, Kenny202 said:

By the way can the pod Go be simply used as a pedal board where I can select or unselect 4 individual pedals rather than preset banks? Eg Select A...Distortion   B....Delay   C....Chorus etc

Yeah, there's a snapshot mode when each 'patch' can have 4 'snapshots'.  Basically, there's a delay where the sound cuts off when switching patches, but no delay/cut when switching snapshots, and with each snapshot you can change settings on multiple pedals/amps/etc., so for using live without cuts in sound, people tend to use snapshots.

The mode you're describing is pretty much default mode, where the 6 footswitch buttons can all be assigned to 1 effect and can turn it on/off, with a colored light indicating if the effect is on/off.  So compresser on/off, reverb1 on/off, distortion pedal on/off, FX Loop on/off, etc.

Ok hopefully it's software and will be fixed lol   But honestly I'm 99% sure it's hardware.  Just the nature of the knob L6 has chosen.  Another argument for hardware; have you ever pushed a button on the Go (Page, footswitch, etc.) and had the software 'bug' and not do the action?  Plus there's basically 3 screens used by that rotary knob;

• switching patches
• scrolling through your effects chain
• scrolling through effects when editing a block

And all of these show the intermittent rotary knob issue; if it was just one screen when scrolling very fast and hitting DSP limit, ok, but yeah the odds are extremely low that there's a software bugs in all those screens which just happen to coincide with this particular knob...!

And the 2nd knob has the exact same issue, the one used for scrolling up/down in effects, etc.  So yeah, I'd say 99.9% certain it's hardware.  L6 should know, but the support tech likely doesn't have the answer on scrip, but for sure their QA must be well aware of the issue.  

Another proof it's hardware; again, just navigate left/right on your effects chain, that has zero impact on any setting and isn't altering anything, yet you'll still get a ~10% knob failure rate.  Now do the same with each footswitch, which actually impacts effects, modifies lights, also move the selected block in your chain, you'll get 0% failure rate.  99.99% certain it's hardware.  ;)

3 hours ago, voxman55 said:

No, but it's intermittent and if you go back on a stuck click it works. Feels like a software issue as the knob clicks firmly & correctly. 

I really doubt it's software..  From what I recall you can wait 1 second between each knob turn and you'll still get the issue. 

Quote

it doesn't occur depending on speed; if you turned it super fast for 5 clicks and it moved 3-4 blocks because Go can't process that many clicks per second that could be something, but if you're waiting 1s for each click while the PGO is doing nothing and it bugs, it's more indication of hardware glitch.

 

Pretty sure it's similar mechanism to this:  https://www.youtube.com/watch?v=MHfiCqwdVYo

 

The other knobs which rotate but don't have clicks are kinda annoying also; as I find it quite hard to regulate the turning speed to get to what you're trying to get.  Ex; 0-100, you spin it slowly and it goes 1,2,3, then you spin fast, and it goes 1,2,22,33,78,100 ...   But you want 50..  So go back..  99, 98, 97 ... ok gotta go faster ...  90, 85, 84, 83, 82,6 3, 43, 23, 3, 0   grrrr!

On 6/26/2021 at 10:12 PM, voxman55 said:

Hi, this is the same on all Pod Go's so it's not specific to your unit.  I think it's just a minor bug that's mildly annoying.  I've raised this previously with Line 6 support but I've just asked Line 6 support again to try & fix it in the next firmware upgrade. 

Was there ever any confirmation that this is a software and not a hardware issue?

Btw you should definitely be controlling the go via PGO Edit if you aren't, makes things way more practical.  Then, if you do need to change some settings on the fly, you should do it via snapshots, or less-recommended solution of binding values to a button; which you can do; for instance, you can bind changing the drive of a distortion pedal, gain and volume on amp on a single footswitch.  So what you're attempting to do 'live' by scrolling can likely be achieved via footswitch assignment; but snapshot is just the superior function imho.

Otherwise, yeah, selecting amp before saving will work, but if you press a footswitch you'll lose your amp selection and be back to manually selecting amp + scrolling.  So yeah, snapshots!

Quote

POD Go 1.22 contains several stability and performance improvements as well as bug fixes. Updating is highly recommended.

Please click here or copy/paste this link into your browser to view the 1.22 Release Notes in their entirety.

Bug Fixes:

• POD Go Edit: Improved stability and performance on macOS Big Sur.

• POD Go Edit : Acoustic Sim block added to signal flow did not display 'x' icon to delete.

• POD Go Edit: Tapping tempo from for an extended period of time could eventually freeze POD Go.

• Guitar In Pad global setting was not recalled across power cycles.

• Other minor improvements and bug fixes.

https://line6.com/software/index.html?hardware=All&name=POD Go Edit&os=All&submit_form=set

Damn, just updated thinking we'd get new goodies lol   

Plus just noticed it caused vox more stabilities issues...  *cries*!

Not so bad I think, it's ~3% more expensive than the Double Tank, so good chance it's included in the next Go patch, as it's nowhere near as expensive as the poly effects.  Last time, think it was 6 months before getting the new Helix 3.0 in Go...  But hmm, the legendary drive has the same % as the hot springs, and I don't think it's in the Go...  So who knows!  50/50?  Less?   30%?

https://benvesco.com/store/helix-dsp-allocations/

On 5/16/2021 at 8:12 PM, kgreel said:

I read somewhere that there's a way to start the older Spider Amps with no processing:

"Basically to get into TEST mode you hold down the TAP button as you pwer the amp ON.

Beware that having no master volume control from the amp"

I just tried the TAP + power button.  I think it's pretty much the same as using the CD/mp3 in in terms of sound characteristics; so imho, doesn't sound very good in my case with the Spider 3. 

I think it's because the Spider 3's speaker, unlike probably the speakers in a Marshall cab or whatever, aren't really designed to sound good by itself?  I think it's more tailored to work in conjunction with the Spider's emulation software; so the driver has to have a more generic, or bland (flat; neutral?) sound so that the drastically different Spider sounds can all be reproduced with some sort of credibility.  But for some reason, even with IR or Go Cab, just sounds meh... maybe tweakable via Go EQ, but I think it's just a bad idea to use it with Go; as it's a tremendous bottle neck.

So yeah, for someone wanting to use a Spider, I think I'd use a Spider 3 Amp model; like one of the 2 Crunch channels (depending on style) with Spider EQ at noon, no reverb, etc., and maybe bypass the cab in the Go.  To my ears, sounds better than CD or Test mode.  But IMHO, it just sounds way better with a pair of studio monitors though, so if going Go, definitely think buying some FRFR, Studio monitors or amp + speakers to get the best out the Go! (or at least not make it sound like pooo...)

Nice demo of what it's possible to do with snapshots!   Crazy the range with just 1 preset, way more than you'd normally need for a song!

A bit weird to have to work around the small gap between switching presets, but yeah when snapshots are used creatively, it's impressive the range of sounds/tones you can achieve.  Always compromises and workarounds lol    But yeah also in one sense, we're talking changing 50 different settings with 1 button press, something you never would be able to do with a real pedal board.  (ok ok with MIDI controller you could, but just the controller likely costs the same as the Go lol)

And how do you like it?  I have a way older Spider which I did initially try to use, and wasn't really happy with the aux.  Guitar in seemed a better choice, but using Spider's amp block you would have to manually change them along with your PGO settings...  Anyway, if the later Spiders have a better speaker, might work out better... 

But I kinda feel like the Spiders and maybe other digital processing amps might 'correct' for the speaker with digital processing, but maybe that's just my assumption and giving too much credit.  (would make sense to correct driver FR in the system using software, which you would lose bypassing the digital processing section)

10 hours ago, grdGo33 said:

Annoying oversight?  As you're probably using the wireless adapter when you're playing with the Go and turning off the Go when you're not playing it...  I'd be kinda disappointed if I learned of this behavior..  Just extra hassle to do what most people would have assumed it should have done in the first place...  (charging even if off)  :\  And since the charge port is the guitar in, you can't use the PGO using a cable if you're charging the transmitter? 

 

But yeah I guess the G10 comes with its own charger, so using the external charger is an easy fix, likely not a big deal then!   It's even likely much more practical to just plug the G10 in its charge station, rather than having to plug it in the rear of the Go...

Mistakes were made!   The PGO wireless comes with a G10 dongle, but it comes with no charging dock...  So if you just buy a PGO wireless, you have to charge the G10 in the PGO...   I thought the PGO might have just cost slightly more to support wireless, and you had to buy the wireless G10 kit (dongle + charger) to use with PGO...  

So yeah...  Sold as a kit, the part I had crossed of the above post isn't as irrelevant as I thought.   Just looking at the rear ports; I'd have expected it to charge in the storage compartment; and that there would have had a distinct circuit for the charger, allowing it to charge when plugged even if the Go is shutdown...  Oh well.

Still, sweetwater & musicianfriend have PGO 479 vs 579 with wireless.  99 for G10 dongle, 180 for G10 + dock.  So if it's 100 extra with PGO, the price of the dongle, but with wireless support...  Not bad if you want wireless I guess... 

Do all L6 products that support the G10 also have to remain powered on to charge the G10?  Or is this specific to PGO?

Quote

If you try to just plug the G10 and play, you get no sound.   You have to go to each preset, and change the input for wireless.  FOR EACH PRESET...

Ugh... Like...  Seriously?  Ah ok that was from some of the pre-production unit, might not have make it to production, hopefully...  Oh no!  From the manual: "Select the Input block on your POD Go Wireless device, press the lower knob, and choose either the “Guitar+Wireless” or “Wireless” as your input source.".  So it appears that they didn't change it.  Nothing about changing it globally in global settings either... OUCH!!! 

Annoying oversight?  As you're probably using the wireless adapter when you're playing with the Go and turning off the Go when you're not playing it...  I'd be kinda disappointed if I learned of this behavior..  Just extra hassle to do what most people would have assumed it should have done in the first place...  (charging even if off)  :\  And since the charge port is the guitar in, you can't use the PGO using a cable if you're charging the transmitter? 

But yeah I guess the G10 comes with its own charger, so using the external charger is an easy fix, likely not a big deal then!   It's even likely much more practical to just plug the G10 in its charge station, rather than having to plug it in the rear of the Go...