Jump to content

grdGo33

Members
  • Posts

    381
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by grdGo33

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

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

  3. 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.  ;)

    • Upvote 1
  4. 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!

     

     

  5. 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?

  6. 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!

  7. 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*!

  8. 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/

  9. 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...)

  10. 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)

    • Like 1
    • Thanks 1
  11. 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)

     

     

  12. 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!!! 

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

  14. Using the effects loop or any additional pedals?  Go's signal is maybe too loud and causes one of your other pedals to clip.  Try lowering the volume of your amp in Go (ex; amp levels from 10 to 5 see if it clips less).

    • Thanks 1
  15. You would probably have to decompile the PGO software as well as the Helix software, and then make your own custom firmware update with your updated code containing the Helix freeze effect.  It will involve some work though...  

     

    Or...  I haven't opened up the PGO, but maybe there would be space.  So by drilling some extra holes in the chassis and running a couple of wires here and there, you might be able to fit the circuit off an harmonix freeze inside the PGO chassis.  You would also have to run power and a switch, witch would involve more drilling, but yeah, getting a freeze effect in the PGO might also work.  Saves the DSP from the freeze effect also.

     

    Other than that...  I don't see any other way...  :(

    • Downvote 1
  16.  

    21 hours ago, rosskoss said:

    I'm asking if it'd be possible to enable oversampling even if at the cost of just having Amp + Reverb.

     

    Yeah dynamic blocks is something which comes up often; kinda like a dynamic feature request; get the very high DSP effects from helix, at the cost of blocks... But I don't think that'll be happenin...

     

    The Jason test is up btw, if anyone wants to hear with and without oversampling.   I think I could hear a very very slight difference, but as I mentioned, it could very have well been placebo; really nothing to lose any sleep over.   That will not be the difference whether your album/show flops or whether it's a success...!  LOL    (IMHO; very very minor difference..)

     

    Here's the link to comparison:  https://www.youtube.com/watch?v=F0qmP3-4cYM

     

  17. Two small things I'm curious about;

    1) Has anyone noticed a bug where the footswitches stop working and and don't change when you switch patches?  It happened twice for me, and both times was with the new Glitch Delay...

     

    2) Just curious on your thoughts about using Go as an audio interface and leaving it on for 12+ hours a day?  I switched it to work station and now also use it for that PC's sound; so I've been using it all day, and have tended to leave it running even afterwards just to use with guitar setup; but then it's 90% just sitting there idle...   Thoughts?

     

    My thoughts; I think the Go is pretty much a computer; so using it almost full time shouldn't really be an issue.  And with computers, I even remember reading that powering it on causes even more wear and tear than simply leaving it running; ex; running for 6h is better than turning it on and off 3 times for 3h usage...

     

     

  18. Ha...  Just look at it that way:  A bunch of Pros have been raving and using the $1,699.99 Helix for years now, and it always sounded great.  The $450 Go has the exact same effects quality.  And the quality of the amps/effects/etc., is already at a level where it's pretty darn tough to tell which is the emulated sound vs which is the sound of a real amp.  Jason Sadite for instance has more than a couple of comparisons; try to see if you can tell the real deal vs emulated:

     

     

    Now, they added a new oversampling which will improve the $1,699.99 HelixWill this make a marginal or substantial difference?  Given the fact that already, the Helix/Go are near indistinguishable from the real thing, I doubt that it would make a substantial difference. 

     

    Of course, you'll see a lot of people who will claim that it makes a huge difference, but it's mostly going to be placebo.  Same type of thing where some people will claim to prefer real amps over emulation, yet under blind conditions, will very often fail or really struggle to identify which is emulated vs real.   So IMHO, even with good studio monitors & in a recording setting, you would struggle to hear the difference.  That would be my guess.  That if you just walked in a room, a track was playing, that 50% of the time you would guess correctly if the oversampling was on or off.  You would really have to A/B both clips, multiple times, to hear the difference, IF you were able to hear it, which you might not be...   And then, chances are that it would be placebo; and again, under blind conditions, you would fail to identify whether the effect was on or off.  Such is the nature of subtle audio differences & human brain/hearing.

     

    Anyway, Jason above is supposed to do a blind test for the oversampling feature, it will be interesting to see how much of a difference it'll make.  For me:  Go is more than enough.  If you are at the point where you need oversampling & absolute sound quality; TWF are you doing with a Go?  LOL  Buy a Helix or real amp!  At one point, expecting Go to absolutely equal the Helix is a bit silly!

    • Like 2
  19. Where did you hear that we're not getting the oversampling feature?   About 6 months ago, Helix 3.0 came out, then a few weeks back, we got the lower DSP amps/effects from 3.0.  Now Helix 3.1 has just been released, it's very possible that in 6 months we'll get a patch which include this new 3.1 feature.

    • Upvote 1
  20. 2 hours ago, silverhead said:

    I believe Line 6 has imposed the 4-block restriction (rather than 5 or 6) for a reason.

     

    I think it's way more for marketing & not cannibalizing their higher end product sales.  I really don't think it's to 'help' the users at all (lol) I really do believe that it's to put an arbitrary limit on their cheaper product.   It would be sooo simple to display a % value for each block, and allow the users to add as many effects as long as they don't get over 100%.

     

    I mean come on, are you saying that guitar players are so dumb they wouldn't be able to understand that each block takes a particular % and that they can't go over 100%?  LOL  That's pretty damn insulting and I think you owe an apology to all guitarists!  :p 

     

    But seriously, even now, it's even less intuitive to use, because if they give no % for each effects block, you have no clue which block uses how much, which actually makes it even HARDER to build a patch; because after adding 3 effects; you're like;  "WFT can't I add this effect?!?  Why can I add this and this, but not that and that?!" then they have to go online to find a page that gives the actual % of each effects block...  Something that could and should have been done in the unit.  Hell, they already do know the % of each, since they won't allow you to go over 100%, just write the %, and add an extra block if there's still room for an extra effects block!

     

    I don't think it would hurt the Stomp & others that much.  Fact that you can't do dual amps/cabs, have less inputs and outputs, etc., Go would still be very limited vs the others.

  21. @voxman55 yeah :)

     

    Also, if you want to get 'close' to headphone sound; maybe consider a FRFR speaker (lots of threads here) or Studio Monitors.  Then your headphone sound would be closer to what you would hear from either.  But again, the FRFR, headphones and studio monitors will also impart their own sound, so depending on how different they sound from one another, you'll again not get perfection.  Same for getting your your patches sounding good via Studio Monitors, then outputting through a PA at a gig or whatever...  EQ will help a lot like vox mentioned.

     

    I'm pretty sure the FRFR/studio monitors are 'better' vs a guitar cab to use with the Go..  As per this thread; using a Guitar Cab is kinda redundant and skews the emulated recorded with a cab + mic of the Go!  (Not that you can't get great results with a cab; but then you have to keep in mind that either you're stacking cabs and/or really using your own cab instead of the Go's vast cab/IR emulation; which does give you more options than your 1 real guitar amp.)

  22. On 3/30/2021 at 7:11 PM, voxman55 said:

    So, here's a common fallacy - 'I've got a real cab so I need to turn the cab model off' - right? Well, no - it's all down to personal taste and there are no absolute rights & wrongs.

     

    Well essentially, let's say you have a Go patch:  (guitar) -> OD -> amp -> cab -> mic -> delay -> reverb -> studio monitors -> room (final sound you hear), that is what 'qualifies' as a 'normal' chain.

     

    If you go:  (guitar) -> OD -> amp -> cab -> mic -> delay -> reverb -> 2nd cab -> room    or    (guitar) -> OD -> amp -> cab -> mic -> delay -> reverb -> 2nd cab -> 2nd mic -> speakers -> room    well that would not qualify as a 'normal' chain...   Sure, "it's all down to personal taste", but nobody in the real world would run that kind of setup.  So if you want to get closer to what you would be getting in real life were you not using emulation, you should bypass the Go's cab and microphone, because you already have a cab which will add its own cab sound, and don't need a microphone because your real cab is already outputting the sound in your room.

     

    Like nobody in the world world would run a Marshall Amp through Marshall 4x12, record it with a microphone, and then take that sound, and run it through a 2nd guitar 4x12 cab, and use this 2nd guitar cab sound for the room/recording...  Well at least I've never heard of it being done by anybody!  LOL

     

    The other thing is that the Microphone of the cab sim of the Go, does a LOT of things to the 'sound'... It doesn't just mess with the FR, it really does alter the 'fundamentals'...  And I mean, that change pre-cab, is just not natural for a cab...

     

    Ex:  Say you have a Marshall amp + cab in your room, and your amp blew up, and you replace your amp with a Go.  You'd run the Go's Marshall Amp sim without PGO cab+mic.  And that is what would sound closest.  The Go's amp+mic would just add distortion (differences vs normal amp).  Sure, maybe you would prefer this sound; but the typical way of doing it would just be no Go cab+mic.  Otherwise, you're getting emulated Microphone distortion, emulated cab distortion plus your own real cab distortion on top of it...

     

    The fallacy here, if there is one here, is going from headphone to your guitar amp and expecting it to sound anywhere near the same.  If that was your goal; then you could try to find the closest sounding cab in the Go to your real cab, find the most transparent PGO mic, then use that for headphones, and disable mic+cab of Go when using your own cab.  It' will never be the same, but that could be what gets you closest from one to the other.  Realistically; if you want to use your cab, you'll need to tweak your patches for your cab, and likely have a completely different set of patches for the headphones; as you'll never be able to 'match' of make 1 patch sound 'perfect' on both your guitar cab and headphones.

     

     

  23. 10 hours ago, rarellano said:

    So, an IR it's just another kind of equalization. I got it. 

    Not exactly...  IR = Impulse Response, and indeed, it does 'capture' FR (Frequency Response), but it does a LOT more more...   It will also capture 'everything' around it.  Ex:   If you had an amp and played the sound "tikilliki" through it, and it sounded like "tekesseke" because it it has a bad woofer; well, if you generated an IR, the IR would make it sound like if it was played through the amp.  Basically; it captures "the system"; it captures how a cab + a mic makes the sounds sound when you're playing 'through' them.

     

    The simplest way to visualize the concept, imagine a recording studio, where they have a Marshall Cab setup with a microphone at 2 inches at 3 degrees; well, if you plugged an amp on the cab and recorded the sound recorded by the microphone, it would record the way the cab + mic sound.  Well, that's exactly the IR.  In theory, if you played the sound through the cab + mic and recorded the mic output, you would get the exact same sound by recording the amp signal and running it through the IR.

     

    https://en.wikipedia.org/wiki/Impulse_response

    • Thanks 1
×
×
  • Create New...