Jump to content

grdGo33

Members
  • Content Count

    262
  • Joined

  • Last visited

  • Days Won

    1

grdGo33 last won the day on August 19 2020

grdGo33 had the most liked content!

Community Reputation

33 Neutral

About grdGo33

  • Rank
    Iknowathingortwo

Recent Profile Visitors

423 profile views
  1. Welcome! :D You might also want to read this thread!
  2. 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!
  3. 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.
  4. grdGo33

    Looper fixed block

    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. 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.
  6. Cuuuuute! 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: 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 ;)
  7. Hahaha! I'll believe it when they fix it! :D
  8. 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:
  9. grdGo33

    Bye pod go

    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.
  10. 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.
  11. 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. ;)
  12. 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.
  13. Was there ever any confirmation that this is a software and not a hardware issue?
  14. 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!
×
×
  • Create New...