Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Posts posted by grdGo33

  1. On 10/10/2021 at 11:57 AM, Vics53 said:

    Pod Go was unable to import preset in this set due to the following errors. -400- file or direction path not found.


    On 10/10/2021 at 7:08 PM, voxman55 said:

    if it's in a Zip file, you need to unzip it first.

    Make sure you unzipped the file, and that you do not just double click the zip file which just opens the zip and shows you its content


    You can also try to copy the .wav file to a simple path; ex;  c:/temp/yourwav.wav, some programs have issues with paths with spaces, permissions, etc.  You can also right click your pod go Edit shortcut and choose 'run as administrator, that might help. 


    10 hours ago, Vics53 said:

    . It shows IR 1024 whatever that is.

    The IR GUI from the Pod Go is different than from the cabs, it's annoying... At one place you select the 1024 whatever it is, and then you use one of the other knobs below the screen to choose the IR.  It is really dumb that the IRs menu/settings does not work at all like the cabs.  Maybe there is a default one, can't remember..


    But if you were able to import the IR, you should see it in the list of IRs in PG Edit.  On the list of IRs on the left, right click, import IR or wahtever hte choice is, navigate to your c:/temp folder, you should see your .wav and be able to import it.  In your c:/temp if you right click the .wav file it should say wave file or whatever, not zip/compressed.


    Also just download a new IR to test it out.  If it works, maybe something is screwed up with the worship IR and you should try contacting them.

  2. 2 hours ago, voxman55 said:


    Sorry. you're right - I'd misunderstood. I certainly wasn't aware of any hack that gives you 6 user blocks - I'm intrigued how that was done because it wasn't referred to in the v1.30 update.  I've loaded down the block & I can get 5 FX in but not 6.  Can't be DSP as I've chosen very low DSP models. No overflow warning but hey, even 5 blocks is a win!  Can anyone else get all 6 blocks to work?


    Update:   I can't seem to add a 6th FX - well, I can add it but PG doesn't 'see it' in the display and even though it's lit in PGE and assigned to the spare FS, it has no impact on sound.  But here's something crazy ....I can add a looper in the 6th slot - even 6 button!  Just testing to see if it works properly, but seems to.  So 5 user FX blocks plus a looper - wow!!  


    Also, & don't know what I did, but for few minutes up popped  10 (yes TEN!) user slots with no amp or cab or wah or Volume??!!  

    Hmm!  Nice!  I didn't try it yet myself, you might be able to control it via snapshots also, and even if you can't turn it on and off, maybe if it's always on it would work?  Anyway, I'll try to give it a shot later on, if just a 5th dynamic block works and you have to disable either EQ or FX that would be great; I'd probably try to do without the EQ block, as I mentioned you can do a LOT of 'EQ' tweaking via amp, pedal's tone setting and even via Cab and Mic for that matter.

  3. 1 hour ago, voxman55 said:


    I created it myself; in PGE go to the footswitch (normally FS2) and click on the 3 dots to see the assignments. Remove the FX loop assignment.  Go to Output, and set your normal value to 0dB and your max value to +3dB (or whatever you want) & assign it to FS2. Save the patch, & you're done. In PG in FS2 in stomp mode you'll now see 'Level'. Press it and when it highlights, your +3dB clean boost is on. 


    I've done this on several patches I've added to Custom Tone, including this patch ( Soldclean SCsnap ) .  So for a 'quick fix' you can just copy the outblock block in this patch & overwrite the FS2 block on any patch you have:




    I think one of us is mixed up...  We're not talking about assignments, we're talking about removing the block.  Normally PGO has 4 dynamic blocks.  The EQ and FX blocks are locked and they can't be changed.  So sure, you can remove the footswitch assignment, but from my knowledge, you couldn't remove the EQ and FX blocks.  If you can, it was likely patched in at one point, because ever since getting the Go, and ever since I've visited the forums, I've always read/thought that the EQ and FX blocks could not be switched out for other blocks; only 4 dynamic blocks.


    Using the 'hacked' presets, you load a patch, and this patch was edited so that it does not contain FX and EQ; giving you 6 available dynamic blocks instead of the 4, which is genius.  This is the first time I hear of this!  Kinda surprised you'd know about it earlier from our other exchanges lol



    (from your "Voting for Pod Go requests for extra flexibility - the problem with 'Ideascale'....")

    2. Give Pod Go 1 or 2 extra blocks. It doesn't increase DSP, but the option will give greater flexibility


    This is it!  Well almost, you lose the EQ, but as I said Amp blocks have it, and effects often have a tone setting, and FX, well, either you need it or you don't...  But you said 1 or 2 extra blocks, so 1 is what you got ;)


    But yeah maybe you did understand correctly and people have been doing it for a while, it's just that I check this forum every few weeks and just learned about it, had no idea it was old news!  0.o    Or maybe this a a new feature of 1.3?  Ah.. Must have missed it in the release notes...  Hmm.. not even https://line6.com/support/page/kb/pod/pod-go/pod-go-130-r986/   from an earlier firmware update?  


    [edit: ok yeah pretty sure it never happened, this is really a 'hacked' preset which allows doing something PGo didn't allow to do by design!  And actually give users 6 dynamic blocks instead of EQ, FX and 4 dynamic blocks!]  8)

  4. 43 minutes ago, voxman55 said:

    I frequently swap the fx block for another function, most typically I use it as a clean +3dB level boost for solos, where it's labelled 'Level'.  The advantage of doing this is that I can kick it in regardless of what other effects are active. 


    Since when?!  lol   I had no idea it was possible to do, was this patched in at one time or you were also using an edited patch?


    2 hours ago, gabriele1990 said:

    Hi all, have you seen the latest YouTube video of Choptones?


    Are you talking about this one?   https://www.youtube.com/watch?v=K3kMXc0tnus  Their 'Out' block is all screwed up also it seems, pretty weird!


    And btw, did not try, but the 2nd block; the wah/volume pedal, is also a block, so who knows if in theory you could also replace them with a different block if you used the same technique as the edited pgp.  You might not be able to edit it in the GUI later on, but maybe by replacing it in the export file (see spoiler);   Not sure how it would behave; if the volume would get switched the the compressor in this case, and if 'clicking' the expression pedal would then revert back to the volume, but who knows...  Could make the Go crash also, likely would fail during import, etc.   so unless you have lots of free time and would not mind losing your Pod Go config and having to do a reset, I would not recommend trying it out, but I'd be curious to know if it would work!  Kinda weary/lazy of going through the testing/GoReset though..



    DO NOT TRY WITH THIS!  if you want do an export and compare files, I used an export I had which originates from an earlier version which could have an effect.  This was just a quick curious check what the files contain kind of thing!


        "block1" : {
         "@enabled" : false,
         "@model" : "HD2_WahFasselStereo",
         "@no_snapshot_bypass" : false,
         "@position" : 1,     >>>>>>>>>>>>>> <----- likely chain position  <<<<<<<<<<<<<<<<<<<<<
         "@type" : 0,
         "FcHigh" : 2155.0,
         "FcLow" : 455.0,
         "Level" : 0.0,
         "Mix" : 1.0,
         "Pedal" : 1.0


    replace with another block from another exported patch, ex; here with a compressor;


                    "block1": {
                        "PeakReduction": 0.55,
                        "Mix": 1,
                        "Emphasis": 0.09,
                        "Gain": 0.5,
                        "Type": false,
                        "@enabled": true,
                        "Level": 0,
                        "@position": 4,          >>>>>>>>>>>>>> <----- likely chain position, likely must be the same as original  <<<<<<<<<<<<<<<<<<<<<
                        "@no_snapshot_bypass": false,
                        "@type": 0,
                        "@model": "HD2_CompressorLAStudioCompMono"



    But yeah maybe during import it would be looking for a Wah at Block1 position, maybe it would be looking for specific values such as which would make it crash;

         "FcHigh" : 2155.0,
         "FcLow" : 455.0,


    Lots of reasons it might not work.   But in theory, could also work, it really depends on how they coded the import function.


    You would also need to do some guesswork to figure out what some of the settings mean; ex; @position, @type vs "type":false, as above in red, @position might be position in the chain, so if you take a block from another position, would have to put the position 1, but maybe that's not what it means also, would need to do some guesswork and testing and in the end might end up not working anyhow...


  5. 2 hours ago, rarellano said:


    That seems pretty damn huge, so it is easily possible have more than 4 dynamic blocks simply by using this edited patch?!    Ah so they just 'removed' the EQ and the FX Loop block and replaced them with empty (dynamic) blocks.  So no 'extra' block, just replaced EQ/FX with empty blocks.  Nice!!


    The EQ block shouldn't be a huge deal as each amp model has EQ settings, the FX loop could or couldn't matter...   Very cool!



    Yeah the pgp is json, so just replace in export file, genius!


       "dsp0" : {
        "block0" : {
         "@enabled" : true,
         "@model" : "HD2_VolPanVolStereo",
         "@no_snapshot_bypass" : false,
         "@position" : 0,
         "@type" : 0,
         "Pedal" : 1.0,
         "VolumeTaper" : false
        "block1" : {
         "@enabled" : false,
         "@model" : "HD2_WahFasselStereo",
         "@no_snapshot_bypass" : false,
         "@position" : 1,
         "@type" : 0,
         "FcHigh" : 2155.0,
         "FcLow" : 455.0,
         "Level" : 0.0,
         "Mix" : 1.0,
         "Pedal" : 1.0
        "block2" : {
         "@position" : 2
        "block3" : {
         "@position" : 3
        "block4" : {
         "@position" : 4

        "block5" : {
         "@bypassvolume" : 1.0,
         "@enabled" : true,
         "@model" : "HD2_PreampMandarinRocker",
         "@no_snapshot_bypass" : false,
         "@position" : 5,
         "@type" : 1,
         "Bass" : 0.50,
         "ChVol" : 0.68750,
         "Drive" : 0.50,
         "Hum" : 0.50,
         "Master" : 0.50,
         "Mid" : 0.50,
         "Sag" : 0.50,
         "Treble" : 0.50
        "block6" : {
         "@enabled" : true,
         "@model" : "HD2_ImpulseResponse1024Mono",
         "@no_snapshot_bypass" : false,
         "@position" : 6,
         "@type" : 2,
         "@uuid" : "ddae067006d0a8e83031509da297837e",
         "HighCut" : 8000.0,
         "Index" : 2,
         "Level" : 1.19209e-007,
         "LowCut" : 80.0,
         "Mix" : 1.0
        "block7" : {
         "@position" : 7
        "block8" : {
         "@position" : 8
        "block9" : {
         "@position" : 9

        "input" : {
         "@input" : 1,
         "@model" : "P34_AppDSPFlowInput",
         "decay" : 0.50,
         "noiseGate" : false,
         "threshold" : -48.0
        "output" : {
         "@model" : "P34_AppDSPFlowOutput",
         "@output" : 1,
         "gain" : 0.0,
         "pan" : 0.50



    Has anyone tried making a gdp with more blocks?  I'm guessing it might not work as it's likely coded for 12 blocks, but if we're lucky and it was coded with as long as the fine contains blocks, it could add extra blocks, but more than likely the extra blocks would just get ingnored, or you'd end up with a patch who's 12th block is a dynamic block instead of out...   (more than likely, even if it worked, the Go's GUI and Edit's GUI likely would not support it so you wouldn't see the last block or something...  Likely would not work well in the end.)

  6. 3 hours ago, joel_brown said:

    I want to make sure I can run the PODGO in stereo and delay the left channel by 20ms.  This give me the stereo effect I've used for years.

    About PG Edit, you can check some sample videos about pod go edit, there's some from L6 and a lot of random people making Pod Go videos.


    For the 20ms stereo delay, I don't think there's a built-in feature that does.  PGO has a lot of stereo delays and effects though, so you'll definitely be able to achieve the effect, but not with a 'free' built-in setting; you would have to use one of the 4 dynamic effects block.  Unless I'm wrong and someone will correct me  :o)

  7. Did you download the IR?  In PG edit you go to impulse, you can right click I think on the list to import, or just drag and drop if I remember correctly.  Yeah and think 1.3 is latest, thread about it should be one of the top comments


  8. 21 hours ago, ATF73 said:

    I have a Telecaster  ...   sounds crap


    I'm guessing you're a newer player?  Even with the Go, a lot of the tone will come from your guitar.  David Gilmour tone is a bit of a challenge...   On his live versions he used active EMG pickups, so it's quite different from a tele pickup...  So not wanting to rain on your parade, but I think it would be a big challenge to get the exact same tone.  Most of the tones from the shop, paid, etc., will all sound very different depending on your own guitar; and often come in two flavors, humbuckers or single coils.  But yeah, what you start off with makes a big difference... (pickups)


    Since I don't own a tele...  I do have a strat, but even then I think its bridge PU will sound quite different.  But for that sort of distorted tone, I've always found bridge strat single coils to be extremely lacking; a bridge humbucker on a super strat (Pacifica, Ibanez, etc.) just sounds and feels just so much more natural to me to get somewhat similar tone/feel to that sound...  DG's active EMG pickups are also completely different beasts, but never tried them.  From the DG page below, even his DiMarzio FS-1 in original recording is apparently darker sounding.


    Is there no CF patch from the shop?  If so, you could just use them as your starting point.  I'd think that with a Tele, you might want to use heavy compression to beef up the sound, lower the treble, but hey, total guess on my part.




  9. Yeah my favourite amps and effects turn out to cost a lot of DSP anyhow, so realistically, unlocking blocks if there is DSP left over would be cool, but would likely not make anyone go "Wow, a 5th block?!  Forget the Stomp/Helix I'm going with Go!!!".  Go is way more limited... 


    Guess it's just frustrating knowing there's still DSP power available, and not being able to use it because someone decided that you should not be able to use it.  Like if Dell decided that you would only be able to use 60% of the CPU or memory of the computer it sold you.  I mean the CPU/memory can do it right?  Ah ok you don't want to 'cannibalize' the sales of your more expensive computers?  Or that you could only run 4 programs at one time.   Want more programs?  Buy our more expensive computer.  LOL

  10. 19 hours ago, wpostma said:

    If I had a Youtube Channel I think I'd do some tutorials, but I can't be arsed, to be honest,  the video would go something like: Learn to build from scratch,  read the whole manual,   learn about the global settings FIRST not after 2 years.      Learn to tear down and rebuild your signal chains.  Learn to work with your amp without pedals, and learn the quirks of your amp or FRFR as well as the quirks of the pod go.   


    There's already a bunch of them though, maybe not going about every global setting, but yeah for general usage, building your own patches, tips about effects and stuff, there's really a LOT of stuff out there.  You can spend days watching them all!



    I think it's interesting that some people are more into an all in one "workstation"  as the core, and many want to mix and match a dozen or more discrete boxes to build their floor boards.


    Some people still prefer turntables and vinyl records than modern flacs and digital devices!    LOL     I mean, sure, if you own a studio, have millions because you're a music star, etc., sure, spend the dough on amps and pedals.  But for everybody else...  Yeah, there's much more modern and practical solutions.  But like you said, different strokes.  But yeah at this point, to me, seems an absolutely no brainer at this point.  When most people can't tell apart real amps vs Go, and you get such crazy value over something like PGO, seems absolutely crazy to buy super expensive tube amps and ridiculously expensive pedals...  Like $500 for a reverb, distortion, etc. pedal?  Like dude... Come on...   Sure, not the same as the dozens in Go, but sound quality wise and price......

  11. For snapshot mode, you can set the up/down to either switch snapshots, switch preset or bank.


    -When up/down is set to preset, it goes to the next preset (5B -> 5C -> 5D) and as you switch preset, the default preset of the new patch is activated.

    -When set to bank, it shows you the 4 presets of your current bank, and hitting up/down a 2nd time shows you the next/previous bank, you select one, then it activates the preset and the default snapshot of the preset.

    -Next snapshot is well next snapshot.


    So for Bank, if you're in 4A, and hit up, you'll see 4A-4D, if you hit up a 2nd time, you'll see 5A-5D.   If you're in 4A and you hit down, you'll see 4A-4D, hit down a 2nd time, 3A-3D.  So looks like it works like you want.  :)

  12. See here! https://benvesco.com/store/helix-dsp-allocations/


    Kinda silly that this info didn't come from L6, and had to be painstakingly analyzed and generated by a user (Ben Vesco, thanks!!!!).


    Just noticed at the end:



    POD Go Amp Costs: All POD Go amp costs are the additional cost above the cheapest amp or preamp block.
    Pro Tip: If you do not want to use an Amp block in your preset, assign it to the Del Sol 300 preamp model and deactivate the block. This will maximize DSP power available for other processing.


  13. 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...





    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. 

    • Upvote 1
  14. 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.  :)

  15. 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.

  16. 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.

  17. 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.  :)

    • Like 1
  18. 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.

    • Like 3
    • Upvote 1
  19. 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:


    "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    ;)

  20. 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

  21. 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:



  • Create New...