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

grdGo33

Members
  • Posts

    444
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by grdGo33

  1. Quote

    I've seen things that say its an immense improvement, and others that say its comparable.

    Yes.

     

    Quote

    Are the effects, amps, cabs, and mics on the Pod Go $500 better than the Katana? 

    It highly depends.  Ex; is $500 a lot of money or not a lot of money for you?  What does your current sound sounds like?  What do you like/dislike about it?  What are you trying to improve?  Do you for instance think that your BK 'marshall' sound doesn't sound right or something?

     

    I'd say the most important question is; how much do you like to tweak?  If you want to spend endless time experimenting and tweaking your sound, I think you'll get more out of the Go than the Katana; from what I remember seeing about the Kat; it's more a plug and play device.  The Go is more like an endless puzzle; where you'll plug in your guitar to play, and end up lost tweaking and testing different amps, reverbs, delays, etc.  So how much do you want to get lost in effects or tweaking? 

     

    I think the performance should be comparable; you'll be able to get good/great sounds from both.  Think the Go does more out of the box (you can download extra Katana effects, but can only use a few at a time from what I recall), and the latest fancy reverbs like Glitz, Ganimede, etc., likely will not have a Boss equivalent.  The amount of compressors, delays, amps, cabs, mics, etc., also way higher on GO.  So if that's what you're after, likely won't be disappointed.

     

    I've heard enough people rave about the Katana to be fairly confident that you can get very good, usable sounds out of it.  So if you have good lead, rhythm, etc., sounds dialed in with teh BK, and you make equivalent effects in PGO, I doubt most would be able to tell which is which in a blind test.  They'll likely sound quite similar, and probably not have one sound 'better' than the other; just a bit different.  I think you should be able to reproduce BK sounds in PGO with some work, but probably get lots more flexibility, 'tweakyness (tweaking the sound exactly like you want)' and options with Go. 

     

    But, imho, main 2 things:  1) how much do you want more?, 2) are you more of a plug and play or a tweaker? 

    • Upvote 1
  2. Yeah I'm using mine in the FX loop also.  The only drawbacks are:

    1) if one of your patches has the loop on and the pedal is not plugged in, you get no sound, which can be confusing given that the Go crashes the same way

    2) there are volume issues.  If the volume is too loud to the looper, causes my 2 looper pedals to clip and it just sounds like lollipop.  So the patches are all configured with relative low volume, which means that it's not very loud through USB for recording.

  3. The grgr.de IRs seem pretty cool, they even have some IRs with built-in reverbs, so I`m not sure how they compare to the L6PGO spring reverb for instance, but could be useful if the sound of the IR works out for you and you are running low on PGO resources or just want an additional block! (Using IR as reverb = saves 1 block!) 

     

    [edit: although...  It might just be the reverb without an amp, so might not really be useful with Go with typical usage...]

  4. Also, did you have all effect blocks disabled (just keeping amp + cab) and check out the different amp settings such as hum, bias, drive, etc.?  I mean, if you're going to compare the sound of ex; your PRS through a clean fender amp, but in Go have a ton of effects & different amp and different amp settings, you're a bit comparing apples and oranges!

     

    But yeah the Go has some issues with volume...  I've setup my patches one way, and turns out that it's not quite loud enough when recording through USB/DAW, but that was having the amp channels volume at around 4.  Some downloaded patches have the amp channel volume at 10...  So I just wish there was some sort of guide as to how to set your volumes within the Go...   It's a can of worms with lots potential issues.  (made a thread about it once, but I don't remember it providing it a clear answer)

  5. Just to be sure, did you record with a mic the sound of the studio monitors?  If not, if just recorded through DAW and Go, then has little to do with the studio monitors...

     

    Also I couldn't hear any crackling.  Are you talking about a sort of 'wobble' in the sound?  To me it sounds almost like a tremolo or like you have some sort of phase issue.  I can also hear some background noise, like some hiss in the background, is that what you're referring to?

     

    Also, either the issue is with the Go, with the speakers, or just with a special combination of both... If it's from the Go, you'd likely get the same issue with headphones or through USB.  Are you?  If it's the speakers, well, should do the same with just music.  Does it also occur on both speakers or just one of them?  All patches, or just that one patch?  If when you're getting the issue, you edit your patch to remove some of the effects, does it have any effect on the crackle?  If you switch patch, does the issue go away and come back 5m later?  If you turn the Go on and off the issues goes away and come back 5m later?

  6. Issue is that with the monitors you do want to use the cab block of the Go, but since your 4x12 is a cab, in theory you wouldn't want to have your cab block turned on in the Go.

     

    There's an option so that one of the outputs of the go not output the cab and everything afterwards, but then if you have ex; a reverb after your cab, you would not hear the reverb which kinda sucks.  Soo... You would have to arrange your patches so that the cab is always the last block of your chain, then you could have two outputs; one to the Mackie's outputting hte full chain, and the other to the 4x12. 

     

    But, then you'd have both playing at the same time, to only have 1 playing at a time and being able to switch quickly between both ...  No idea besides turning on/off the monitors and the cab! (cab via footswich or some other way..).  Don't think you can do 'everything' easily via Go.  Maybe if you had a stereo A/B switcher pedal you could output go to switch pedal and then connect A/B to mackie and cab, allowing you to switch via footswitch!

     

    something like this;

    https://www.amazon.ca/dp/B001WAKOJE/ref=as_li_ss_tl?keywords=Lehle+Little+Dual+Amp+Switcher&ie=UTF8&sr=8-1&linkCode=gs2&linkId=e7e5cc077fb6eaeabd7b8053357569be&tag=sonoboom0e-20

     

    https://www.loopipedals.com.au/product/stereo-splitter-ab-pedal/

     

    But I'm not 100% sure how the Go would handle the Stereo for Monitors vs Amp which takes a mono signal... You might just get left or right output for cab?  Or, there's likely an adapter to go from stereo to mono; yep;  "1-4-in-stereo-female-to-1-4-in-mono-male-adapter" that should work lol

     

    Or, just KISS, output both signals, turn on/off your monitors and amp via their power switch lol

  7. 3 hours ago, cruisinon2 said:

    Yes, you'll have to spend a few bucks

     

    Maybe?  Well you may have to if you are looking for a very specific thing, but there are soo many free IRs out there...  This site has quite a few mixes:   https://soundwoofer.com/ImpulseMix/Index

     

    But I don't know, guess it depends on your skill level and level of how much of a sound engineering guru you are, as if you're a super pro of mixing mics and cabs, well yeah, going with the more budget and limited Go was likely not the best choice!   is still a fine choice if you just purchase an IR pack for $50 or whatever which contain all the dual cab IRs you want!  

     

    But yeah for Go,  I really doubt we'll get dual cabs/mics in a software update!  But who knows...

  8. I think it's effectively for what are newer and generally more DSP intensive effects, vs legacy (paler) which are effects coming from older Line6 products and generally less expensive...  But that might not be it, since for instance Spring reverb is super expensive DSP-wise, but it's very possible that still the Spring reverb comes from an older L6 product...

    • Thanks 1
  9. On 1/14/2021 at 6:01 PM, engine-III said:

    the tones i managed to get out of both running thru the hd400 were MORE than adequate which made me think the GO would make them that much better. but...

     

    On 1/13/2021 at 1:50 PM, engine-III said:

    yes, i did. but, respectfully,  that response seems a bit too commonplace and isn’t really a solution. i understand that it’s not a simple  “plug and play” type of deal - it just seems to me that after 20 years the level of complexity to get even one attractive tone to start with out of 30+ banks of presets is starting to outweigh the benefits of the newer models. in the past it seemed that having so many “artist presets” was the draw towards modeling amps/pedals - having a good, usable starting point and patches that actually showed how they could be used. most of what i hear with the GO seems redundant. i feel like it’s unnecessary to have so many when things like the snapshot mode and blocks mean you can turn things on and off to essentially get the next patch in the list. again, personally i feel like quantity over quality and the added hassle of having to buy things like IR’s is taking over the usability of the products, especially when simple/useful things like having enough effects blocks or dual amps are being thrown out. i understand there will always be a sacrifice between product versions and that business is business, but IMO it’s just not worth it with this one.

     

    There are tons of free IRs, and when you use them instead of the bothersome [amp + mic + distance], the Go's usability gets a lot higher, as it's a PITA to experiment with amps/mic/distance.  And as the majority of tone is from the amp, you're really doing yourself a huge favor by using IRs imho.  But if you don't mind the PGO's amp+mic+dist thing, you likely won't be missing much in terms of tone.  

     

    But reading YT comments, you're not the only one who seems to love his HD400/500.  Not entirely sure how it compares sound-wise, but I'd think the Go would sound better as it's the latest emulation gen (helix tone).  Getting there might be a challenge though, so having years of tuning your hd400 tone vs jumping in Go and trying to reproduce/improve your hd400 tones might not be super easy...  

     

    And yeah IMHO the presets aren't a huge help and could have been better.  But how they sound depends on your playing and  your guitar, so again you can't really compare to the sounds you've dialed in your hd400; which are already tailored to your taste, playing, guitar, etc.

     

     

  10. 12 hours ago, Predictable said:

    but why do you think it's the same problem in a brand new device?

     

    Well it's an issue for 100% of the 3 people posting here; with almost brand new devices.  Mine did it from day 1.  So really not from wear and tear; imho it's just tradeoff or flaw of the design...  

     

    PS said all my mouses scroll wheels had the issue, but my current mouse seems to not have the issue...  So likely a component quality issue...?  :\

  11. 20 hours ago, catalyn86catalyn said:

    How u connect your Pod Go with Katana? I have the same amp 100 mkii..do u use the amp or preamp on Pod Go? Thx

     

    check out the 4 cable method in the manual.  Or, you can connect go direct to effect loop and bypass the Katana's effects and go straight to cab.  You might want to try with and without cab, see if one works better than the other.

  12. I really doubt it's software as 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,63,43,23,03,00   grrrr!

     

  13. Yeah it's annoying.  Mine does the same on both knobs, about 10% of inputs are randomly lost, both directions.  Think it's a common issue with that sort of hardware, never had a mouse (mainly logitech) that was able to capture 100% of mouse scrolls.

  14. Went back to them a few days ago, maybe the first dozen ones.  The thing is that, IMHO, the cabs really take over the sound.  So 90% of what I'm hearing with the default patches are "Ah that's a 4x12 Marshall, that's a 4x12 Mesa, etc.", and there's really not so many sort of 'incredible' tones; they're kinda generic/bland;  Anyway, I didn't find much super inspiring or amazing sounding patches there, but that also depends on your guitar, play style, etc.

     

    Rewatching this;   https://www.youtube.com/watch?v=5V6-nCYt88A    There seems to be a couple of patches which seem interesting (5D, 7B, 9B, 18A), so I think that going through the presets, and copying the presets which seem to have potential to your user preset and then tweaking them might have more value than trying to use presets as they are.

     

    Or... Maybe just using IRs instead of the stock cabs which all too often seem to take over the entire patch sound...  I really wish the stock patches were 'better'... I don't know, guess it's hard to setup good patches...  Other L6 devices seem to have too many 'silly' unusable patches, this has more usable patches, but doesn't really seem to highlight the incredible capabilities of the PGO...  Maybe it's not super realistic, but would have been awesome if you went patch by patch and went: "wow!  That's awesome!  How did they do that?!"   That happened once for me, with the space patch lol   

     

    Maybe the PGO's presets could have been a highlight of the different distortions and effects; like with snapshots; 4 snapshots to highlight the sound of a distortion pedal, with an amp, with a reverb, etc., so you could go preset 1, snapshot 1, then go: "oh I didn't know that reverb could do that!  Oh!  That's how this distortion should be used!  Etc.!"

  15. Your question isn't very clear.  Or just doesn't make any sense to me... If you're sending a dry/clean signal through USB and then applying distortion via software (not PGO) how is it the PGO's issue that " there's not much gain"   lol  

     

    Maybe this is related?

     

  16. Yeah, you can do it through the softare PGEdit via unassigning the stomp button in the stomp button interface, can also do it on go, but you have to go to action or something ...  It's done in a quite unintuitive way which I don't exactly recall.

     

    Quote

    image.png.410891dfabc11ed3f6ea45201c349faa.png

     

    A simpler way is to assign another pedal to the same stomp button and choose 'replace' while saving (don't merge!), your old stomp button will become blank, then you just re-assign the same block to another button and effectively have erased your loop stomp button.

  17. It's strange that they just didn't add an input volume on the input node...  Also too bad that you can't set the volume pedal to go over 100%.

     

    You can also place the EQ at the start of your chain and boost the signal from your 'free' always on EQ block.  Amps also typically have EQ settings so you can still get some EQ'ing with your amp, but yeah nothing could stop you using snapshots or that function where you attach values to buttons and have a button to do +10dB bass, +10dB mids, etc., and use EQ as a free boost.

  18. 17 hours ago, agiarretta said:

    Ah alright so the Pod will change the sound of the amp even when cab and head modulation is bypassed?

     

    The cab simulation of the PGO simulates the sound through a guitar cabinet, it's intended to be used with recording software or through studio monitors, headphones, etc.  But if you're using the PGO output to a guitar cab, you're already using a cab, so don't need to simulate a 2nd cab.  If you're simulating a cab and play through a guitar cab, it's as if you had, for example: 

     

    Guitar -> Marshall amp -> Marshall 4x12 cab -> recorded via microphone -> Mesa Boogie 4x12 cab.

     

    So yeah, that would affect your tone!   ;)

     

    If you have a regular stereo system, just regular amp, speakers, etc., to listen to music, you might want to try plugging your Go through that.   Already you'd benefit from Stereo effects, and you might get a better sound than through your guitar amp & cab.  It's quite a bit more flexible that way, you're getting to 'really' use the Go's cabs or IRs.

×
×
  • Create New...