
grdGo33
Members-
Posts
484 -
Joined
-
Last visited
-
Days Won
1
Everything posted by grdGo33
-
Which preset did you want to purchase? There's plenty of free presets, so unless you really want one of the paid ones, I'd start exploring what's available on the free side! Especially since purchasing presets is giving you issues... There's also a lot of guides on how to build presets out there, so might want to try these out also instead!
-
The L6 litigator was said to be quite similar to a Dumble: So not really familiar with the artist tones you're looking for, but I'm pretty sure the Litigator is what you want! (always tone varies with guitar and all) https://www.youtube.com/watch?v=0e-HZN-cuz4
-
Yeah for sure... Also again being realistic; you should never purchase anything expecting to get updates or new functionalities... Go already does a lot, but yeah since it shares the exact same features as the helix (code/emulation), it would seem normal that new helix dev also gets pushed down to go, when possible... But it would not be worth it to upgrade to Helix though, they would be nice to have, but I wouldn't pay $1000+ for those new effects to switch up to one of the Helix products. For the Poly sustain, EHX Freeze does the sustain thing, but listening to DG's gilmour above and the poly sustain from the L6 video, it almost seems like there is some sort of modulation with DG & L6, anyway, maybe it's just the chords or guitar making the difference...
-
So this PGO volume thing is somewhat annoying... Has there ever been some official guide or best practices for setting up the PGO's different volume settings? I'm using an external looper in the FX Loop at the end of my chain. If the output is too loud, the pedal clips. So to combat this, I've setup the FX Loop out to be -6dB and in to be +6dB (max), and I make sure that the rest of my chain is not so loud as to make the pedal clip. Everything works well that way. One issue though with that, when using Audacity to record, it's really not very loud ... As in, it should be much louder, I think... There doesn't seem to be a way to increase that volume software or windows, so I'd have to do it post recording, which may or may not be the optimal way to record... So yeah... Any advice or best practice guide to follow? It sucks that the FX Loop causes pedals to clip, you'd think there would be some sort of pedal level signal normalization in PGO for the FXLoop... And because of FXLoop Send supports -60dB but the return only go up to +6dB, means you can reduce the signal by a lot, but you can't bring it back to normal volume afterwards... Thanks!
-
It's quite a bit of a let down if the Pod Go isn't going to get new newer effects. I bought the Go largely because 4 blocks seemed enough and it had pretty much every amp/effect of the Helix. But... It's not, but, it's a little bit like a bait and switch; as in; sure, it has most of the Helix effects, but if they're going to add more and more effects which will never get supported by the Go... :\ The gap is just going to get bigger and bigger. Like missing out on let's say 3-4 amps/effects is one thing. But then it kinda sucks when this becomes a dozen, with some of the more interesting effects being out.. I would have loved to get the poly sustain, but looking at its 53/69 mono/stereo DSP usage, yeah, seems like that's out... 21 Poly Sustain Line 6 Original delay hx 53.33% 69.47% na 4.2 Poly Pitch Line 6 Original pitch/synth hx 53.33% 60.65% na 4.4 Poly Wham Line 6 Original pitch/synth hx 53.33% 60.65% na 4.8 12-String Line 6 Original pitch/synth hx 50.67% 57.62% na 20.5 Poly Detune Line 6 Original modulation hx 48.00% 52.90% 10.21% 4.6 Poly Capo Line 6 Original pitch/synth hx 48.00% 54.59% na Legendary drive should be good, since it's just a tad bit above the double tank: 17.5 Legendary Drive Carvin VLD1 Legacy Drive (high gain channel) distortion hx 21.33% 41.33% na 6 tone sovereign Analogman King of Tone V4 distortion hx 20.00% 38.00% na 5 double tank Line 6 Original reverb hx 18.33% 19.00% 30.62% (nevermind I think the Legendary drive was one of the original effects not included in the Go...) If we go with DSP, We should be getting the Diesel amp and princess: 27 brit plexi jump Marshall® Super Lead 100 (jumped) amp-guitar 27.24% 41.23% 25.52% 40.83% 43.8 Das Benzin Lead Diezel VH4 (lead channel) amp-guitar 24.67% 40.00% #VALUE! #VALUE! 24.6 brit trem jump Marshall® Plexi Tremolo 50 (jumped) amp-guitar 24.80% 39.20% 23.82% 40.8 6.5 US Princess Fender® Princeton Reverb amp-guitar 20.00% 33.33% #VALUE! #VALUE! Glitch delay and shuffling looper should be good: 22 Glitch Delay Line 6 Original delay hx 6.67% 9.33% na 3 Shuffling Looper Line 6 Original looper hx 13.33% 26.67% na But yeah, really too bad for the sustain... I'm surprised it's really so expensive as an effect... Shouldn't it be like a delay? Just take 1s of sound, average it start/end and just loop... Anyway, not sure it works like below; the L6 demo had the sustain used with the switches rather than the wah/volume pedal. And yeah to state the obvious... Not even entirely sure we'll or when we'll get any of this new helix stuff... Or has there been any announcement yet?
-
3) I think the best place to adjust the volume is the amp's channel volume. You can do it on the cab, but depending where your FX Loop and other effects might sit, I think you're probably better to just set it there, rather to have a maxed out amp running a hot signal, which could screw up a pedal in your FX Loop or whatnot sitting between amp & cab. Also seems a bit more intuitive than cab... So yeah both would work, but I'd rather never touch cab volume, and just managing volume with amp. That way, it's always one place to check/adjust the volume.
-
Good times... Pretty amazing you got a unit which was dead on arrival. Where did you purchase it from? I'm guessing someone bought the Go, tried to update its firmware, it bricked the unit, then the customer returned it, and the shop just sold it to you as if it was a brand new unit. It's either that, or Line6 has ZERO QA and they're shipping 'dead' units lol which I doubt...
-
Nice! Yeah lots of good amps to chose from lol I really like the Archetype (PRS Archon), Placater Dirty (Friedman BE-100), Revv and Derailed Ingrid for lead/dirty tones. The IRs keep things simple cab side.
-
I think you just have a volume issue. From your clip: 0:00 to 0:15 sounded perfect, albeit not extremely loud, and must have been a dark sounding amp/mic combo 0:15 to 0:30 likely cab off, much louder, brighter 0:45 likely with a cab + mic, sounds fine to me 1:13 That sounds like an horrendous transistor clipped signal. Likely your PGO or software are clipping the signal because it's just too loud. That is NOT the sound you want lol So yeah strangely you seem to prefer the last sound segment, what monitors are you using? If you equalized the volume of cab on/off (your clips without the cab are MUCH louder) you'll very likely prefer your clips with cabs. But yeah if you just turn off the cab, you'll likely get a huge volume boost, and generally people like what sounds louder, so maybe that's why it sounds better to you... But I think you just want more gain. Keep it simple. Start a new patch, just change the amp and cab to these: L6 Badong amp + 4x12 Uber 30 What do you think? If it's not loud enough, increase the amp's Channel volume up. Or Master, if you want more gain/drive. Don't add any distortion pedal yet. And actually, try the different L6 amps, even with their default settings they're all pretty good for high gain. Try with cabs; Uber, the 4x12 XXL, Cali, defaults also not bad. Lead 80 112. But yeah, IMHO, you 100% should be using the cabs for studio monitors. Just increase the volume or gain if you want more. Description of what the L6s are: And here's a link for the IRs, with 3 links/packages, you'll have more than 50 IRs, so it's actually a much simpler to switch between 'cabs' than wrapping your head around the PGO's cab+mic+distance!
-
You can also post an mp3 sound clip, if your go is connected by USB it's pretty straightforward using Audacity or the such. Also, you can use the PGO looper to loop a short clip, and then change the settings with PGEdit; that way you don't have to fiddle with both the software and guitar. You can also try IRs, I made a thread about them not so long ago, should be on page 1 of this forum; just search for 'IR', the 'best' IR from it is quite good; very well balanced, should not sound muffled..
-
Think that's just the nature of cabs. Without a cab, your signal is basically 'clean', all that the cab does is take the signal, and alter it so that it sounds like it's coming from a real guitar cab; and since they aren't perfect, they all just skew/distort/muffle the sound. My experience is that with no cab, it sounds horrible through studio monitors; as it really doesn't sound like the typical electric guitar sound that we're used to ... But if you're using high gain, it might be what you're looking for; just pure gain sound. Also; while your studio monitors aren't guitar cabs, they have the same effect; the 'perfect' signal gets altered when converted from an electric current to sound waves, so your speakers (also called transducers; convert electric signal to sound) will add a sound of their own; which is what the L6 cabs do. They'll distort/change the signal. The better the speakers, the more accurate; or in the case of L6 cabs, the more they'll sound like if you did not have a L6 PGO cab on. But the worse the monitors, the more they'll add their own sound to what you're hearing, and that might actually end up being the exact same thing as having a L6 cab on. To the point where if you have L6 PGO cab on + your low performing 'cabs', you're getting a double dose of cabs, which will sound bad. Did you try with clean also?
-
Check what changes in your settings when you plug or unplug the go. So go in your sound settings, check every setting of every tab of your device, and compare with go on/off. Something must change, otherwise it would sound the same. Also check in your running programs if you have a program which alters your sound, dolby something maybe... Check if some programs are launched/killed when you plug or unplug. You can also kill programs using the task manager, don't worry at worse you restart your computer and they'll start back again.
-
did you check your pc sound settings? https://www.isunshare.com/windows-10/3-ways-to-open-sounds-settings-in-windows-10.html
-
What? Likely bug then. using voxman's link, some amps cost 40%, and modulation or other effects can be as high as 30%, even some distortions are almost 20%, dynamics 15%, so it's still possible to run out without reverb and delay. Or not being able to choose a more expensive amp if you're using expensive effects. Plus it's not on/off, it's just whether it's in the block in the chain or not.
-
https://www.myofficetricks.com/how-to-change-default-output-device-on-windows-10/ something like that. Or, so say you're using Winamp or whatever, you choose pod go as your output device in your software's settings. and like I said; https://www.audioswit.ch/er https://www.audioswit.ch/download/latest
-
The point of that option is that FX loop doesn't have to be on :) I'd check computer side, you likely don't have any sound from the computer, also, if your PGo is connected via USB, I think you can play music directly to PGO through USB, that would probably be a better setup. Software like 'Audio Switcher' also allows you to quickly switch sound between different devices.
-
Think I remember reading that the L6 powered cab was quite expensive... Also in some comparisons, think it didn't fare so well vs competition (ex; real cabs or whatnot). A lot of people seem to like the $200 headrush FRFR cab, just make sure you<re using balanced cables. But if you're using studio monitors, not sure how much of an upgrade that would be... https://line6.com/support/topic/56640-vastly-different-sound-frfr-vs-headphones/ What are you currently using as studio monitors?
-
It's too bad they didn't include everything, even if the cost was that you could only run 1 effect at a time, and only with certain amps...
-
PGEdit manual page 9. And yeah, could have been much clearer in the manual also. And that's the thing; some of the GUI/features are so idiosyncratic, even with the manual understanding some of the 'logic' behind some features is near impossible... (only made harder by the fact there is often simply no logic...!) The issue is a little bit like political correctness. If nobody ever says anything because they are afraid of criticizing a product, telling the truth, being called names, etc., you end up in current clown world where nothing makes sense, because since nobody ever corrected anyone and they just went with the PC narrative and with what was the polite opinion, reality & issues don't come to light, and things don't get any better, they just get worse and worse. Take Helix; not sure how many of the the faults of the PGo are inherited from Helix, but if more people had complained about what is wrong with the unit, maybe the PGo & PGEdit wouldn't have as many faults as they do now. Plus, maybe they'll be patched or improved.
-
Well that's an entirely different discussion, but I'm glad to have it. If you need to read the manual because the software is so unintuitive or so badly designed, I do believe a rant at L6 is fully deserved. In this case, when you select amps, distortions, cabs, effects, etc., you're always provided a list to scroll through. But not in the case of IRs, as I said, with IR, it shows you a totally wrong value: "1024 - Sample IR", which DOES NOT EXIST, and then, as if you had selected this non-existent IR, you can scroll through this IR settings to choose different IRs? That's absolutely absurd design. I don't care if it says so in the manual, it's inconsistent and borderline moronic. And the fact that you need to read the manual to be able to select a different IR just highlights this absurdity of the design. Exactly like when you asked how you could import multiple IRs. Didn't you read the manual? You were so proud two seconds ago about having read it... haha! ;) :p If you knew how to add 1 IR, shouldn't it have been obvious and easy to add more than one at a time? It's the same type of bulllollipop you have to deal constantly with the unit. You try to do something the obvious way it should be done, and it doesn't work, and you have to read the manual to find out how to do it with the idiosyncratic badly designed software/GUI. As I said in another thread, might be the best unit at $450, sound-wise it's great, features are great, etc., but damn, even if it might be the 'best' of the pedal gear at usability, it's still poor... It's a little bit like going to some remote village, going to their best strip club and not seeing single hot stripper... Then asking what's going on; being told that of the 5 villages of the region, these are the best looking strippers and best strip club... Well that's L6 PGo for me... I don't understand how so many find it acceptable, and I can't understand how L6 can release a product with design/software of this quality... But anyway, I'm being slightly hyperbolic. Like the IR selection 'logic', I'd give 5/10, just blow passing grade... It works, it's usable once someone taught you how to use it or you read the manual, it's just not using common sense nor consistent with the rest of the system... It's like bad intern worthy design... It's not really acceptable work... Sure it works, but as Biden would say.... C'mon man!
-
Yeah to be clear, if you're going to use PGo superficially or just use its simple features, it's simple. But the issue arises when you're trying to use the more advanced options; - Configuring snapshots - Configuring "Quick Controller Assignments" - Trying to figure out why the FX Loops clips the signal or why does your looper through FX loop continues playing even if you turn off the FX Loop. Or just different annoyances: - Why doesn't Go use grids, instead of having to scroll through lists of 100 amps, 60 cabs, 50 effects, etc. - If you've assigned to a foot switch multiple values, why can't you control the on/off state from PG Edit - As I said, being unable to set a mic & distance and simply switching cabs (changes the mic & distance if you change cabs) - etc., But again. With simpler units, say you want 'the brown sound', you select the brown amp and voila. With Go, some amps have 20 settings. The Bias of the tubes, the BiasX of the tubes, the hum, ripple, sag ... ! Master + channel volume, because the Master influences the amp's distortion behavior. Do you really need all those values? Or Is choosing 1 amp, having a drive settings is good enough, if the amp/drive sounds great? Same thing for Cabs + mics + distance... Is that a plus for you, or would simply selecting an IR or "Marshall Cab 1" would be good enough? Do you really need all this added 'Helix' complexity? Of course, you don't have to use it all. But if you don't use it, maybe other units are better... It's a super powerful, but complex unit. Do you really need 50 cabs, 100 amps, 8 different tremolos (each with different settings), 8 flangers, 8 chorusses, etc.? Again, each with their own different settings, sounds, etc... It all adds to complexity. Sure, you can choose a chorus and use it, and it's simple. But if you buy the complex PGo, and there's 8 choruses, do you want to know how they all sound, how they work, etc.? Because if so... That's a lot more complex than another unit with less stuff & less settings for each... So sure, it's easy to use superficially, but if you really want to use the unit for its features, and understand everything, it's a lot more complex than other units. A LOT more. Base usability isn't bad per se. I guess it's pretty good to just set some blocks & change some values. But advanced features become tedious & could have been made much better... But they're still usable. It's a bit like old sh!t computer systems; where you can become proficient using idiosyncratic & counter intuitive systems. If you know how it works, maybe once you're used to it it's not so bad. But it could have been a lot more optimal, intuitive, etc.
-
I think you didn't understand my point. The microphone arguably does a bigger difference than the cab, same for distance. The cab in itself is maybe 20% of the sound. If you use the same Mic & distance on two different cabs, it will very likely sound closer than if you use two different microphones at different distances with the same cab. So if you want to compare CABs, you need to use the same mic and the same distance. So that means you have to ALSO choose the same mic and same distance. And both mic & distance are 'lost' if you switch cab. So you DO need to select them manually, every time. Otherwise, you're comparing apples and oranges; totally useless comparison. Not really true for the "since day 1". As I remember, I was quite positive at the start, started a bunch of threads about amps, cabs, effects, etc., but the more I used the unit the more I encountered issues and annoyances and the more my opinion of PGEdit & PGo itself changed. Plus, even if I was the only one to complain (lol), that would not mean that the complaints are invalid. It's like gastronomy, because McDonalds fanboys do not complain about the quality of the food, it does not mean that the food is of great quality and flawless, and that the complaints of 1 guy would be invalid. In my case, having a background as a software engineer, I can hopefully pickup on a few things the average guitar player doesn't pick up on, when it concerns GUIs & software. Now that's crap. I followed 100% the instructions, and it crapped out on me. Bricked my unit. Happened to many others also: There's likely others, but firmware issues have been recurrent, and I 100% guarantee you it's not user error.
-
You could also try Audacity or some other recording software to really pinpoint the issue to being cubase, or if it's general (driver) or whatnot. Also what drivers are you using? ASIO is what is suggested for low latency playback, anyway, I'm definitely not the expert here... But yeah if you get the same issue using the same driver, well, likely driver issue, if in Audacity using the same driver it works flawlessly, then the issue is likely cubase or cubase + driver... At least it would help you in your search to correct the issue.