grdGo33

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

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

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

Simplest and most practical and logical would be between your guitar and the PGO; guitar -> volume pedal -> PGO -> etc.

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.

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...? :\

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.

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!

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.

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

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?

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

First, 'nd', that's not even like, a real word... Second, WE ALREADY HAS SHIMMER OMGOMG!!!1111oneoneoneone Ahem. It is called "Plateau" reverb. :p It be a shimmer! :D

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.

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.

Is there such a setting? I was unable to find it also if there is and I'm also getting quite low volume output for DAW (Audacity)

Why would they not be happy with the results? It's 100% how the PGO is intended to be used. The only drawback would be that you're not taking advantage of the PGO's reverbs, which are likely 'better' than your reverb pedals, as for instance the Ganimede, Plateau, Glitz, etc., reverbs are somewhat comparable to Strymon big sky ($479), blue sky (#299), $399 eventide h9 and others very expensive pedals. So if you have some of those pedals, by all means use them lol but for us poor chaps who went for the Go for its affordability, most of us won't have those kinds of pedals. But yeah if you're using just a Spring or Plate reverb or whatever, absolutely nothing wrong with using outboard reverb pedals, other than it won't be outputted to USB, etc. Or even then, use the FX Loop, add the loop at the end of your chain, and you can get your reverb pedal out to USB! I have some cheap Nano reverb with spring/room/well reverbs but haven't touched it since getting the Go. I'm just having too much fun with the Go's reverbs. :D They all seem to have a sort of particular niche of what they like or don't like... Still experimenting and trying to wrap my head around them, but having fun in the process! And yeah, unless you're using live, you can always just create more patches. I've found that when you're using heavy reverbs, your 'tone' becomes less important as the reverb takes more place in the soundscape; so any small tweak to your original tone is much less audible, so I guess there's like two cases; one where the reverb is the main focus; then the other effects becomes less important and the higher cost reverbs are necessary, or, when the reverb is more of a 'add-on' to an existing tone; then you don't need the big reverbs and can use less expensive reverbs without too much cost to your overall tone, since the reverb will have a more minor effect on the tone. https://www.youtube.com/watch?v=Eob_t8Rg_ao

Did you try: Also did you try with another guitar? Unlikely to be the issue but who knows.. I've used the L6 Litigator on a couple of patches with different distortions and don't remember any issue with it and distortion pedals. But as I had mentioned, if you tried with the default patch and had the same issue, the default amp isn't the Litigator, so it seems your issue occurs on more than 1 amp, and with all distortions? Another test you can do, try to set your amp and cab to 'off'. It'll sound like horsepoo, but you can test whether the distortion pedal's level affects the signal; whether it'll increase or lower the volume. If it behaves normally, then try with just the amp, then with just the cab. Maybe it has something to do with combinations of something. That's why I mentioned unplugging everything; KISS: keep it as simple stupid as possible (with as few parameters / unknowns / factors) to debug your issue.

Are you going through the FX Loop? Really strange... I'd start with a new default patch, no IR, just the base setting. Then try different distortions, they should get your overall volume much louder. Do you get the same result? If so, I'd try unplugging everything and try with headphones. Reboot the Go if it still occurs.

Ah ok yeah I think I remember seeing a Helix vid where the DSP was displayed in terms of % in the patch edit software, but I've never used the Helix. But in essence, they use the same 'dynamic' DSP ; each block has a cost in DSP % and you can't go over that %. The main difference seems to be more limitative rather than functional: The PGO is like baby mode, PGO just hides the % and only give 4 dynamic blocks. And the Helix is like grown up mode; here's the numbers, here's the key to use it however you want, have fun. PGO is much simpler right? Don't want to strain those big brained PGO users with big numbers lol

Really? Didn't it always had 4 'dynamic' blocks where if you use too much DSP some of the effects will be greyed out due to high DSP usage? Or am I misunderstanding the 'dynamic' terminology? If you're talking about the # of blocks, I think the stomp got an increase in # of blocks, probably as was discussed in this forum for the Go: "if there's enough DSP left, why not just give us extra blocks to use it!". I think the PGO always had 4 blocks with the 'if' then greyed out and can't select x...

Is there some USB output volume setting or something? I'm thinking now that not being loud might be normal... Here's a shot of the first 4 presets when hitting a couple of power chords, are yours much louder? It's not going through the FX Loop at all. I am using a USB extension though, 4 meters total, but I think the audio signal should be digital so shouldn't make any difference... Or could there be a driver issue? Reading hte manual, it references "Line 6 Pod Go ASIO driver" but I don't see it in the downloads section... https://line6.com/software/index.html In audacity I've tried both MME and Windows Direct Sound, even WASAPI, same result. (sorry this shouldn't be underlined, when I edit it's not but when saved it becomes underlined... forum bug...) Looper pedal is this https://www.ammoon.com/p-i1995.html

The Space one was really cool, otherwise, I scrolled through them when first getting the unit, and never really went back to them.

It's not a question of 'blocks', it's a question of processing speed. Some effects are nearly free (ex; EQ uses like 0.5% CPU or whatever) vs some effects will cost 50% of the Pod Go's DSP, because they require a lot of processing. That's why sometimes you can't even use the 4 blocks if you chose an expensive amp or effects. What you could ask for though is dynamic # of blocks. So that if you're using low cost effects, that you could use as many as you have the processing power left.