Please ensure Javascript is enabled for purposes of website accessibility Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Posts posted by grdGo33

  1. Fixed! I remembered that there are 2 FX loop blocks in the Go.  A mono and a stereo.  But the pedals hooked to the FX Loop aren't Stereo, and the patch had a Stereo FX Loop configured...  So it might explain why when you send a stereo signal to a mono pedal, only the left channel is returned... 


    So, fixing = changing Stereo FX block to Mono.  What's weird is that I don't remember having to do that in the past, maybe the default block is mono and that 1 patch for some reason had the FX configured as Stereo...  Yep, looks like that's the case, basically all of the patches I typically use the FX block with had it configured mono, and only a couple of others had Stereo...


    Strange I never noticed the issue before the amp change!

  2. [edit:  TLDR; Not an amp issue; FX Mono vs Stereo block issue.  Setting to Mono fixes left muted channel.]


    I don't get it...  I just switched amp, everything is working beautifully, except now when I turn on the FX loop, which is sitting at the end of my block chain, now the right speaker goes mute...  What's really strange is that with my previous amp, it did not do that..  Turning on/off the FX Loop did not mute the right speaker, so it must have converted the signal to mono for the FXLoop Out, and then played the FX Loop In (mono) but through both speakers, which it is no longer doing...  And I can't really figure out what could be causing it... 


    On my previous mini-amp, it was:  

        Go headphone out 6.35mm -> adapter ->  3.5 mm cable ->  Amp 'Audio Input'  (3.5mm)



       Go headphone out 6.35mm -> adapter ->  3.5mm to L&R RCA -> amp L&R RCA in


    Any idea?!  Thanks!


    Check out this page:


    It's actually something that's pretty fun to do;  looking up which is the original pedal/amp in the Go, doing some research on the original and watching videos about them, then using the Go as if it was the real thing, which it is but at the same time isn't.


    Some of the newer models are documented in the release notes of the patch.  But yeah, that sort of documentation is lacking, as L6 doesn't really have one place with the info.

  4. On 11/7/2022 at 1:02 PM, daveaphotopod said:

    If those are good specs


    Sensitivity ~= how loud they play given a signal.   Higher = less loud.  So it's not whether it's good or bad, just how hard they are to drive.  You have $5000 headphones that are 80 ohms and $30 headphones which are the same, doesn't mean much other than the higher the number, the harder to drive and the more likely you're to require an headphone amplifier to drive them properly (loud).


    Did the test and reported the results in a previous thread, basically, you should be able to go deaf with the Go + V6.  I had acceptable volume with 600 ohm headphones, but it was not loud; like almost bare minimum.


    Note that the Go is a bit ...... lame when it comes to volume, some patches are loud, other are not, so you might have to fiddle with amp & cab & effects volume to get 'normal' volume.  And don't be afraid to go 100% volume on Go.  It's not worse than 50% volume, hell, Line 6 should have the foresight to make the volume go to 11.  11 is always better than 10 or 100%...

    • Like 1
    • Haha 1
  5. On 11/4/2022 at 12:32 AM, voxman55 said:

     historically we could be looking 4-6 months for the next Pod Go firmware update. 


    Version 3.50.0 -  Released 11/3/22 ->  ??? 

    Version 3.15.0   Released 2/8/22 -> Version 1.40.0 - Released 7/19/22 

    Version 3.10.0  Released 4/15/21 -> Version 1.30.0 - Released 10/5/21  

    Version 3.01.0  Released 12/4/20 ->  Version 1.21.0 - Released 3/25/21 


    Yep! 4-6 months is pretty much spot on!


    For which will make it in, traditionally, it's been 'everything' except what is too intensive to fit in the go, so you could use this to see what costs what, comparatively tow what we got or didn't, can give a good idea:


    For the new cabs, reduction in DSP sounds great.  If I'm reading the table from above correctly, it appears that an IR costs 10% more DSP than using a cab, so yeah saving that 10% for an IR plus whatever new cab saves, would add up to a ton of DSP!  Hopefully it makes it..  And yeah more tweak ability can't hurt.



    New Cabs and IRs now use 66-80% Less DSP

    Helix Floor, Helix Rack/Control, Helix LT, Helix Native, HX Effects [IRs only], HX Stomp, HX Stomp XL




    Due to further improvements to Helix Core, new Cabs and 1024-point IRs use roughly 66% less DSP as older Hybrid cabs and IRs in 3.15 and earlier versions. A new Cab > Dual block uses less DSP than a single Hybrid cab block and the new IR > Dual block uses less DSP than a single IR block in 3.15. 2048-point IRs use roughly 80% less DSP, although they still use a lot of memory, so they're still limited to one instance per path. NOTE: Older Hybrid cabs use the same amount of DSP as in earlier firmware.


  6. Different ways; simplest is simply disabling the cab block in all of your patches.



    Do you use Amp out into the PCAB or main out (mono)?

    Yes.  In the global settings, you can set in  "ins/outs", "amp out source" "pre cab/ir" to disable everything before the cab block, but you'll lose any effects blocks after cab, but if this is set to "main out", ti's the same as main out.



    Where does CAB go in signal chain in Podgo?

    Off; if you're using external cab emulation and you don't need podgo cab emulation.


    Typically;   OD/compression pedal -> amp -> cab -> modulation/reverb/delay.  It does make a difference where the cab is in sound, so if you decide to go always last, it is a compromise in terms of flexibility. (not that it'll sound 'worse', but it has an effect on tone, so just different, ppl typical are more used to this config, although Go allows anything)



    Am I able to keep the cab active so I can take the PODGO home and plug it directly into my DAW, or do I have to toggle it back on when I don't have my powercab? 

    Yep..  Unless you setup the cab to be the last effect of your chain in all of your patches and use the "pre cab/IR" settings in the ins/outs, you'd have to manually turn the cab block on/off depending. 


    With the setting on, you'd just have to plug the cab with amp out when you want no cab.  But, you need cab to be your last effect since you`ll lose all effects after cab.

  7. On 9/13/2022 at 11:32 AM, voxman55 said:

    I use simple pitch for Eb tuning, eg 'Sweet child of mine', and have played it with a band. Works perfectly. 


    Yeah I think the issue I was mentioning was more specific to the String Synth, the tracking itself (which note) seemed to be working well.  Maybe SS related to pickups or usage too;  location of the block, etc.  I remember seeing a vid about optimizing the synths; basically was all about creating a square wave before it hits the synth.  But anyway, totally different from just pitch shift!  For tracking, it was pretty good. Not perfect perfect, but very likely 'good enough'.


    Did you end up trying it @daveaphotopod

  8. On 9/30/2022 at 5:20 PM, Sky_Island said:

     Right now I've got it plugged into my MacBook Pro (Monterey M1 OS) via the USB cable that came with it and have it running into GarageBand as a DAW. My Pod Go and Pod Edit software are both updated to Version 1.40, and my laptop and GarageBand are both up to date. Is anybody else having a similar issue, and if so, is there any troubleshooting I can try? I really want to like the Pod Go but this problem is pretty big, because as is I can't count on this thing for live play or recording. A full second or two of latency isn't exactly workable!


    Are you sure it's not an issue with the software side of things?  Because it kinda sounds like it is...


    I would try to plug in just some headphones or output the sound directly to some other device; amp or monitors or something and see if you can reproduce the issue.


    When you're having the issue, restarting the software and unplugging the Go USB cable would be a good test.


    Also reminds me of an ultra cheap 15$ USB guitar adapter I once bought, works for 10-20m then it because unusable.  Just have it in a box somewhere..


    And last also, a DAW is not typically used for live, I think the delay thing is pretty much 'built-in', it can be minimized using different drivers and settings, but from what I recall, it'll never be perfect; it's more for recording than anything else.  But I might be wrong as I'm on expert in the field!  "A DAW or "Digital Audio Workstation" is any digital software or device that allows you to record, edit and compose your audio tracks."


    Confident this is your issue.  Using audio out of the Go, I'm pretty sure it'll work correctly, so DAW latency = DAW issue...  I tried and pretty much gave up the idea when I got the Go myself; when with amp/speakers setup.


    IMHO, For live, outputting audio from Go would work.  Go -> laptop -> house audio / speakers very likely not best route.  But laptop/DAW users might chime in and contradict this though!

  9. It's not, but it tracks pretty well 1 note.  My extremely limited experience with strings is that it often seems to bug out though; sometimes where it's supposed to go from soft to loud it doesn't go loud, just stays soft.  So...  I guess could work for recording or to play around, but I wouldn't say it's reliable enough for live or the such.

    • Like 1
  10. On 9/4/2022 at 9:07 PM, silverhead said:

    I’m not persuaded but don’t want to debate it. There may be others who share your opinion on this. Why not post the suggestion on Ideascale? 


    I'm cynical, so doubtful it would change anything.  I was mostly curious if other users thought it was as much as a PITA to use as I do. 


    Maybe I'll re-check it out, last time I tried posting I couldn't due to account validation.  But honestly... I have zero faith, so the only motivation I would would be rather embarrassing and puerile; à la "See?  I knew it wouldn't work..."   :/

  11. On 9/4/2022 at 4:55 PM, silverhead said:

    So first off, your base/global preset would have to (presumably) be Snapshot 1, leaving 3 editable snapshots.


    PGO edit is external software though, so it doesn't need to be matched 100% with the Go's Architecture, as long as the end result is.  So, you could have global/base 'snapshot' that does not exist in the Go device; simply exists in memory space of the PC.  This base settings would then be used to change the base values and reset the 64 variable parameters of each snapshot.  Ex;  SS1 -> Gain 2.0, SS2 -> Gain 5.0, SS3 -> Gain 1.0, if you set the Gain of the base to 4.0, it would effectively change the 'base' Gain to 4.0, and remove the Gain param of all the snapshots.


    And yeah, looking at a .pgp file, looks like that seems to be exactly how it works internally; 'base' settings for all blocks, and 4 lists of parameter values for each snapshot.


    In the GUI, in the base settings, the params which are modified by snapshots could be in red or orange, just to highlight the fact that modifying this value would reset snapshot values to this value.



    But that requires the user to be aware of how things work, and be intentional about it. Right there, you have to deal with the other side of the ‘practical’ coin you mentioned where you mistakenly made a change to all snapshots when you only wanted to change one but forgot to do something first (assign the parameter to the Snapshot controller).


    Yeah, using background colours, large titles "BASE SETTINGS" vs "SNAPSHOT 1", it could be very obvious where you were. 



    So what’s the gain in practicality? Problematic to justify when people are already used to how things work now. Would cause a lot of confusion for dubious gain.


    It's much more practical IMHO to open Snapshot1 and then edit Snapshot1, rather than always being in snapshot X, and changing settings changes settings for all snapshots, unless you manually set the controller to 'Snapshots' for each param you change...!  Just explaining the existing logic is painful...



    Secondly, how would you deal with the 64 parameter limitation? Currently the Snapshot Controller assignment provides an indicator of the parameters assigned. I think you’re suggesting to do away with that. Conceivably, your parameter edits in Snapshots 2-4 could exceed the limit - and you would have no indicator to show you which 64 are being used. What to do?


    There would be no change for the 64 params.  You could still display in white under each snapshot the snapshot values.  If you run out, you could easily go back to Base and change a value currently set by snapshots.  Ex; 64 used, you go to base, change Gain to 4.0, it resets the snapshots, and if I understand correctly you're now using 63 and can choose a different param to control with snapshots.  (Could also have a right click, 'reset to base' under each snapshot)


    Again, under the hood; it would work the exact same way as now.  This would really be a PGO Edit only modification, nothing to change on the Go.  It's just an intermediary step difference, but end result to the Go is the same.



    Personally I’m not sure it would be any more practical or intuitive.


    Yeah IMHO, far more intuitive to be in Snapshot #1 and edit Snapshot #1, rather than being in Snapshot #1 and having to set a controller for every param you're changing for Snapshot 1...   Maybe it's legacy from earlier L6 products and long time L6 users are used to it, but from a software design point of view, it's really just quirky / dubious design...


    Just the "explain it to me" makes it pretty obvious!  Existing logic is really kinda twisted, and you really have to wrap your brain around the;  even if you're editing SS1, you're not really editing SS1 unless you set a 'snapshot controller' because otherwise even if you're in SS1 you're editing the base settings.  VS, base you're editing common base values, and under SS1/2/3/4, you're editing value for that particular snapshot.  Just so much simpler!


    There's just so many improvements that could be made to PGO Edit...  It really would be great if L6 would release some sort of open source PGO API where users could improve software themselves!

  12. Just curious if people think that editing snapshots on PGO edit is far more trouble than it should be? 


    IMHO, the way snapshot editing should work is that by default, you should be editing a 'base' patch, like 'global' patch settings.  When editing this base patch, changes would be applied to ALL snapshots.  Alternatively, you could edit a particular snapshot.   So, if you switched to patch 1-4, any/all changes should be applied only to the snapshot.  None of that assigning 'snapshot' to every single parameter so that it changes the param value only for this particular snapshot...  It would be automatic.  To edit a value for all snapshots, simply go back to global/base patch, and overwrite all snapshot param value.


    Would seriously this not be way more practical?  I can't count the number of times I forgot to assign a parameter to 'snapshot' and ended up messing up the settings for ALL the other snapshots...  The only logic I can see behind this design is that PGO Edit has to be somewhat compatible with editing directly on the Pod, but yeah, this simple change would make editing snapshots so much better...!

  13. On 8/15/2022 at 11:04 AM, phil_m said:

    I’m sure they didn’t do that, as that would cause more problems than it’s worth. For one thing, with the POD Go Wireless, there is no high end loss to begin with when using the G10 wireless.


    Yep, plus supposedly fixed on newer units, and they wouldn't know even if it's an old unit if was fixed or not, not to mention it would mess up the Go's for everyone who has a correct unit or anyone using a buffered pedal.


    But again, if Root's only hearing an EQ issue, global EQ would fix it.

  14. On 8/14/2022 at 12:11 PM, Root6t6 said:

    The only thing they could have done was to fake it by putting in an overall high end increase.  Which is what I thought I was hearing with the update on all my custom patches.  May still be.  The world may never know....


    If it was just that, then fixing it with the global EQ should be pretty easy.  Maybe you had set it up and it got reset?


    On 8/12/2022 at 12:53 PM, Root6t6 said:

    Oddly enough, its one of my Marshal main rhythm 70s crunch tones thats the most offensive.  All it is is a TS into a Marshal with a little delay and plate.  It just sounds very gritty and artificial now where it used to smooth as glass.  I worked a long time to get that one right :(  

    Also had a crunchy AC30 Brian May tone that used to be awesome and now feeds back alot more and is very brittle.

    If nobody else is having these issues I may just redo the firmware load and reset and restore to see if it clears it up. 

    I can't find anything else that changed.

    Also I just got thru checking the Guitar Input pad which was off but I noticed no change in mixer input level on or off.  This doesn't seem right either.


    Btw did you open a support ticket with L6 or try to rollback firmware?


    I'm still unconvinced that they updated some of the amps models (or could be mic, cab, etc.) without putting it into the patch notes...   As far as I'm concerned, I have another explanation; I did go through my patches to try to adjust volumes and tweak stuff, but when you equalize settings for guitar A, tends to unequalize for guitar B...  So pretty sure that's what happened in my case.  Many guitars is problematic in this way...


    Also, you seem to be the only one to have noticed the issue...  Pretty sure again that if L6 tweaked or improved something somewhere, they'd have mentioned it, and you'd have more people noticing...

  16. On 8/12/2022 at 11:55 AM, Root6t6 said:

    Yes, I did just that.  I updated PODGo edit to the latest first,  did the backup, installed 1.40 firmware, did the factory reset with the button pushes while turning the unit on. they installed the backup.  I definitely hear a major difference on all my tones.  especially the clean ones.  They are much brighter and even a bit louder signal in the mixer.



    First time I heard of it was here...  I didn't notice any tonal change since the updated (updated 1st day update was available), but a string broke on my HSS, then lots of work, so by the time I switched its strings (D'Addario EXP 110 XL coated strings) and redone the setup because the action was all messed up, I didn't get much single coil strat tone usage lately with the GO; mostly HH, and didn't notice any tonal change.


    But yesterday, once the HSS was back up, played a bit and yeah I did notice some patches (Fender/clean) yes seemingly sounding brighter, but it did correspond to new coated string and reading your comment the day before soo....  Placebo/strings could very well be 100% of the change I perceived...


    But yeah before that, I don't recall hearing a tonal change before...   Anybody else noticed a change?   If there was a change, might have been more audible on cleanish tones, and maybe also make a bigger change with single coils, as as I said, didn't notice much change using humbucker guitars and mostly heavy distortion patches.


    Oh yeah, could it be also a switch on or settings on the PA speakers?  Such as bright switch or someone who messed with the speaker's EQ settings?



    1) maybe EQ on PA speakers

    2) maybe some Go amps are affected more than others (likely clean Fenderish amps more affected)

    3) maybe even no change, and placebo is just one hell of a drug.

  17. On 8/8/2022 at 5:28 AM, albberca said:

    I need to know what the impedance of the pod go is so that I can connect it to a guitar cab before a power amplifier and thus know which cabinet to buy.

    Yep...  In your logic, you would need to know the impedance of amp so you would know which power amplifier to buy, and then you would 'need' to find out the the impedance of the cab so you would know which cab to buy.  


    Of course, that's not really how it works, as the difference/gain with 'optimal' impedance of the amp would be largely inaudible and so insignificant.


    The PGO will work with pretty much any amplifier, and as long as you get an amplifier suited to respond to your speaker's impedance & sensitivity you'll be fine..  Ex;  don't buy an amp only rated for 8 ohms if your speakers are 4 ohms..  And don't get a 10 watt amp for speakers with 81dB sensitivity.

  18. On 8/7/2022 at 8:39 PM, JimKalin said:

    it's unlikely that the unit will stop working (what we call in the industry, a "bricked" unit).  But it's not impossible.


    Pretty sure it would be nearly impossible to brick a unit with the patch.  The patches are very likely one of the last things which are loaded in the Go, so in the worse possible case, as you said, you would have to reset your unit to factory settings, which resets the patches to patches that don't contain the 'hack', and as it's done via buttons while booting the Go, would happen before loading any patch.


    At worse, still very unlikely, it could cause some unforeseen glitches; maybe affect effects, other patches, visual GUI glitches as you've shown, etc.  Bugs are part of the nature of software design, and you're using it in a way which was not foreseen by the devs, and not tested by L6 QA...  But yeah, that doesn't seem to be the case; as you'd likely have seen warnings about it.  But you never know, maybe one day, when L6 updates its software, it might cause new glitches.


    FWIW, I'm running out of DSP far more often than blocks, so in my case, haven't bothered yet playing with it.  If you want more blocks though, the new 'feature' should over weigh the risks by miles IMHO, as the risks are very minimal IMHO.  Risk of bricking the unit is almost null, and any bricked unit after the 'hack' would likely be coincidence rather than the patch, again imho.

    • Like 1
  19. Nope.  The different channels of amps are in the Go 2 different amps; ex; 

    Revv Gen Purple based on : Gain 1 (purple) channel of the Revv® Generator 120
    Revv Gen Red based on: Gain 2 channel of the Revv® Generator 120
    Das Benzin Mega Based on: Diezel VH4
    Das Benzin Lead Based on: Diezel VH4


    Some of the amps clean up way better than others; more responsive to volume.  So play softer and it'll be clean/cleanish, play harder and it'll distort; so you can control gain via guitar volume.  The new Ventoux for instance can go from clean to gritty. 


    Might also want to check out The Derailed Ingrid based on Trainwreck Express.  It's interesting that some amps you might just glance over have some story and might be more interesting than their original preset might make you think.


  20. Which delay are you using?  Simple Delay?  If so it's normal, just badly documented or a bad name...  The Simple Delay is Stereo..  You could try the Digital delay, I'm not at my Go so not sure which are Stereo delays, but there's quite a few delays, some are bound not to be stereo. 


    Also from what I recall, some delays are stereo and you can adjust the Left vs Right, so setting them to center could be a workaround to get mono sound, but I'm pretty sure some delays should be mono by default, just try other delays!

  21. On 7/22/2022 at 7:33 PM, voxman55 said:

    Ah, then it won't solve the impedance issue. The pedal has to be buffered. Pretty much any Boss or Behringer stomp pedal will do the job, or a buffered wireless unit like the Line 6 G10 Relay. 


    Are you sure?  I mean because it's true bypass, it won't when it's off, but when it's on, it's got the same impedance output as a BOSS (1 k ohm), so it should at least work when it's turned on no?

  22. On 7/20/2022 at 2:33 PM, Bahnzo said:

    It appears to be a true bypass pedal though, so, does it only work when it's turned on? 

    It seems to work just plugged in. I use mostly clean tones, and it's a very noticeable difference on the high ends.


    Are you sure?  Technically, it should not!   Is this your pedal? 


    JOYO JF-38 Roll Boost Guitar Effect Pedal - True Bypass





    Basically, all true bypass is, is when your pedal is in bypass mode the signal going through your pedal is not routing through any other circuitry in the pedal. It’s basically making a straight line from your input to your output. That’s it, post over. Not very complex at all. Off means off.


    The signal reaching your amp through the pedals will be just the same as if you’d plugged your guitar directly into the amp.


    So unless your guitar is not true bypass, it should not affect your tone in the Pod Go at all when the effect is turned off.  Specs from amazon say "Output Impedance: 1KΩ", so same as buffered pedals, so yeah when the effect is on, it would likely have an affect, but not when off.  :)


    Anyway, interesting conclusions to draw:

    1) power of placebo.  Never underestimate its power!!!

    2) the PGO impedance issue isn't traumatic; if users can't notice if it's on/off,


    Maybe some think they can hear the issue with their own Go, when in fact their Go doesn't have the issue lol

  • Create New...