grdGo33

The Pod Go is realistic enough so that it's pretty similar to real amps, so I would hunt down the real amps equivalent using this page and check out videos about tweaking the real amps. That's one of the thing I really loved with the Go, instead of just virtual amps, it gets you to learn about real gear, even some history about amps and iconic amps. There's also quite a few EQ vids also which might help you get rid of that nasal sound, but might that come from the Orange Baby or cab? Maybe using the EQ/tone controls on the the Orange Baby might help to make it sound more neutral, as possibly the amp + your cab have their own flavors. So, for that playing some music using the line-in of the go might help you figure out how to make it more neutral of a platform. If the EQ on amp does not do much, and there's still too much coloration, the Go has a global EQ, so you could set that up to 'counter' the amp/cab, and then you'd have a clean slate for all your patches! Plus, if you have to plug somewhere else, can just edit global EQ and all your patches will sound great. Then there's all the PGO pedals and effecsts to check out lol

probably the optical volume pedal, which is affected by light. Maybe modding or covering up in some way the bit under the pedal might help, you can do a search has been asked a couple of times. Or, if you're not using the volume pedal, disabling its block might be a solution also.

What do you mean by 'audio interface' and DAW? How is/was your Go connected to what? I'm using mine connected to PC via USB, and outputting the sound of the Go and PC to Go's headphone out to an amp and speakers, and it sounds as you would expect; normal, like any other DAC or whatnot. So either you somehow had an issue, or maybe the other audio interface has some sort of feature which alters the signal (ex; spatial or dynamic plugin). Go should sound transparent.

hehe yeah... Personally, I'm happy with the best IR in the world; does everything I want, and never feel compelled to go cab/mic route. Plus, as I mentioned, a great solution for the Go would be DIY dual cabs IR, by merging 2 different IR files. So, if that works as I think it should, could again be a great workaround/until we get the new cab system, if that's what you're waiting for. (From what I saw for IRs, they appear to be mono, so you couldn't have different left/right channels, but you could merge say 33% amp1 and 67% amp2, which could give interesting results, or could be horrible... Haven't tried it yet lol) If it's new cabs/effects, probably lots of stuff you can revisit, or check out vids about Go to get new inspiration! Already so much stuff in the Go, likely tons of stuff we've all overlooked!

1) ok so it's not just after you import the patch, even after restart stays messed up.. 2) yep, should tell you if the in-memory settings are same or different. If you test the #3 and #4 above, you should be able to pinpoint the issue; you might be able to find a pattern, get an idea of the cause.. Any response from support? 6) What you could also try is import the same patch multiple times. Not sure how it could happen, but if you had some sort of memory issue, which could randomly 'change' some settings, importing multiple times might result in somewhat random behaviour for each import... Or maybe it's the same, either would give us a clue. Really have no idea how Go works relating to memory; but if it's like a standard computer or computer program, memory works in blocks; ex; [1010100011011010100101100110] [1010100011011010100101100110] [1010100011011010100101100110] [1010100011011010100101100110] Paraphrasing, say the 3rd memory block is bad, and the 4th bit is stuck at 0 for instance, if it's like dynamic memory used for effects, it might have completely random effect, where it changes a '16' to a '4' for instance, which for one effect could a feedback parameter, or amp bass, etc., totally random. Could be that this corrupt memory space is used by import or for storing loaded patches, etc., so yeah if your PGO is acting up and acting erratically, could be some sort of hardware malfunction.. Programs tend to crash when such hardware issues arrive; a value will not fit an expected value and some unexpected behaviour will throw an error, but maybe Go is resilient, and just acts unpredictably rather than just crashing; which is good in an sense, at least it somehow still works rather than becoming an expensive paperweight... :\

DSP = Digital Signal Processing, in this case it just represents a % of the available PGO resources / CPU capabilities. The FX Loop, according to https://benvesco.com/store/helix-dsp-allocations/ has a cost, but unless you use a custom patch which has removed the default effects, it's always there, so it makes zero difference if you plug in external effects or not. The way the Go works is that it L6 has computed the cost in terms of performance, has reserved that % so that the PGO CPU for instance has always enough CPU/memory speed so that it never slows down because there are too many effects and not enough CPU. So, if empty go is 100%, when you add an amp, you subtract 20% because it will take around 20% of the CPU to work, so you have 80% left, etc., so you can never slow down or overload PGO, as it will prevent you from adding anything which would do so.

Nope, not possible, you'd likely need to hack its firmware or something.

@rarellano why the sad face? lol One thing which L6 should, or could do, is just release a patch for the new effects, such as the above amp & reverbs, and just add the new cab engine in a later patch, if they're having trouble doing so... Not sure what type of job adding existing amps/reverbs to Go vs Helix, but since they've done a few now, should be straightforward? The last 1.4 patch was released July 2022, 9 months ago? That's a while ago.. But to be frank, I'm still discovering lots of stuff with the Go, so it's not like as if the update and new stuff are that important... I mean, ex; 'discovered' the Jazz Rivet 120, which sounds pretty fn incredible clean, not sure why I had discarded it earlier, likely because I hate 99% of Jazz out there... Probably does not beat my favourite Archtype Clean, but pretty awesome alternative, I need to spend more time with Fender amps, but yeah, fantastic alternative... And then when you add compressors and everything, whcih there's a ton of, you can get so many tones, switch the cabs/mics, or IRs, and again, infinite number of tones... So it's not like I, or anybody, needs more cabs/amps; already an infinity of sounds in there. Bit the same with effects; Ariadratic (sp?) delay + plate reverb = some sort of fancy Ganymede/Glitch like delay, so if for some reason you're itching for new reverbs, you can kinda make your own, mix & match, or even just reconfiguring existing delays you can get a LOT of variety... But yeah few hours of guitar per week, and it's a toy / hobby for me, plus most of the time now is just playing rather than tweaking, which can be somewhat of a pain..

Didn't want to create a new thread but there's a new Helix patch out; so might be interesting for the new goodies we will get in the future

Weird, sounds like an issue with importation; if two things are the same then they cannot be different. 1) If you restart Go after import does it change anything? 2) If you export both identical patches and compare them using winmerge or other file comparison program, any difference? 3) Could also be related to snapshot; again; either bug in importation or settings. You could try clearing all snapshot settings and comparing, see if it makes a difference. 4) Could try to change all settings; ex; volume from 4.3 to 4.2, drive 5.4 to 5.3, etc., just to see if when manually changing a setting you can hear a difference. If there's a big jump after changing a setting, you know something was screwy in that setting. 5) Finally, as a last resort I would try this, it's a long shot, but to be sure... Or maybe export, reset then re-install latest firmware..

Yeah the sound from the samples will largely come from the guitar, the amp, cab&mic or IR. The distortion characteristics of the distortion pedal should be audible, but it'll definitely alter/interact with the amp's distortion; The pedal will push the amp and the amp's distortion characteristics is a large part of what you'll hear... There are some clues about the pedal settings as they are visible, so again if you've managed to somehow match the clean tone, then when you introduce the distortion pedal, you will likely have to tweak as vox mentioned the amp volumes so that they sort of hit that sweet spot for pedal just hitting the amp hard enough so that the amp distorts with the tone you're hearing. But yeah, in order of importance, greater effect on sound imho; 1) it all starts with the guit, it's got this sort of glassy tone which isn't that close to les paul, which sounds more 'dead' (as if you lowered the tone knob), really hard to make a les paul sound like a strat. So if your source signal is very different... 2) Mic huge difference of type, so ... as I said you'll have to experiment; finding correct type at least, as that has a drastic effect on sound. 3) cab / amp. The cab has its own sound which skews the FR, but amp has bass/mids/treble, so can somehow tune stuff a bit.. Unless distortion characteristics are drastically different, distortion is distortion, so amp doesn't matter that much.. 4) distortion pedal; as mentioned if it's more like an OD / boost, has minor effect on distortion characteristics & tone; subtle differences.

That might be a problem, given Les Pauls tend to sound quite dark, and his humbucker on his super super strat does not appear to sound very close to your typical les paul... He says JTM45, into a 65 HW cabinet?? https://helixhelp.com/models/ For the cab; could it be similar to this? https://www.sweetwater.com/store/detail/1960AHW--marshall-1960ahw-120-watt-4x12-inch-handwired-angled-extension-cabinet "4x12" Cabinet with Celestion G12H-30 Speakers" Doesn't seem to be an exact match, but maybe this? Half the equation is the mic, but I'm not sure which mic he was using.... So that might take some trial and error, I'd really start to match the clean tone, you can play the same chords he do and record it via the Pod Go looper, then you should be able to work on the mics to try to replicate what sounds similar... :\ But yeah, it all starts with the guitar, and imho the clean tone has a bit of a peculiar sound; it's quite clean sounding, doesn't sound like your average neck humbucker, quite detailed, very balanced sound yet with sparkly high end, quite sweet sounding imho. So yeah definitely not your average neck humbucker sound. If your LP sounds quite different, might be a challenge to replicate... Thinking, his PU maybe sounds like some type of Fishman? Ok yeah 'house' pickups... https://www.andersonguitarworks.com/pickups-22

Nothing has changed. If anyone is interested writing a program for it, go for it! Could be fun learning experience for someone, could turn out to be a useful app for some. But. Topic was discussed about like 8 months ago, so apparently very little user interest... How many people 1) own Pod Go and 2) what % of them would be interested in the app? And again, realistically, what % of Helix patches would be convertible to Pod Go? I would question the pertinence of the app given the complexity and limitations of Go.. Btw, we're really talking weeks of full time work here for a decent tool, so basically paying for a meal or a coffee, or I don't know what is 'nominal' in terms of $$$ exactly, would be a tiny amount compared to the work. Well yeah as I stated I was impressed by the leg work... Reverse engineering code or format is hard work. But L6 could simply release the info... But even if it did release its doc for the 2 formats, you'd still have tons of issues to solve... Like again DSP, a user went to the trouble to calculate the costs, it's available, could be used, but integrating it in a user friendly way would be a real challenge. But even if you solved it, still the # of blocks, lack of dual path, missing effects, etc., Is it really worth the effort? The Pod Go isn't getting any younger. I would have no use for such an app, would a lot of people? I think there already exists other tools which do so much better; doesn't BOSS or something have a sort of tone clone where it'll listen to a song and just 100% replicate the tone? There's already a visualizer for Helix patches.. But yeah, think the issue would be that the usefulness of the tool would be very limited, given that likely most Helix patches simply won't fit or won't make any sens on the Pod Go... But, maybe I'm wrong! :)

There's plenty of free IRs out there, so I would start off with that rather than buying anything. Search for IR in this forum, I created a thread where there are I think nearly 100 free patches to try. Also, upcoming Go patch might contain re-vamped Cabs, so, unless you need IR packs right now, could wait, or just use free patches in the meanwhile.

How many though? It would take a lot of people paying 'nominal' (5? 10? 20? 50? 100?) fees to pay for the dev hours for such a project. The other big problem would be working around the PGO limitations, not sure what would be the value of such converter in most cases; unless the majority of Helix patches are small and simple enough so that the Go can support them; meaning; DSP, single path, existing effects, etc., the value of partially importing a patch might be marginal, as some patches might not entirely work, or work at all, without all the blocks... And yeah, you would need to factor DSP limitations, blocks, etc. So there would have to surely be some user input; ex; - 2 paths detected, choose path to use [ ] cab1 -> effect 1 -> effect2 -> effect 3 [x] cab2 -> effect 4 -> effect 5 Too many blocks for Go, choose 4 effects to keep - Distortion1 - Distortion2 - Reverb1 - Reverb2 - Chorus1 - Chorus2 - Delay1 Too much DSP for Go, choose 1 effect to remove - Distortion1 - Reverb1 - Chorus1 - Delay1 ... So yeah, maybe you'd want to have some built-in alternative effects/presets to mitigate the non-existing PGO effects... Anyway, really not sure there would be enough PGO users to either fund or develop the feature..

Over the regular cabs I guess? "Thousands of impulses were captured with Sound Design's all new IR capture system and consolidated into 20 guitar cabs and 4 bass cabs.". Sounds like yeah they're 'selling' IRs as configurable 'cabs'; as in; you're basically end up using an IR when using the cabs... Guess it's good for people who were using the current cabs... But I'm guessing that if you're already using IRs, you won't gain much by going 'new' IR cab, maybe tweakability vs simple IRs. What would be really interesting is if they brought the dual cabs to the Go, but I'm guessing this takes advantage of the Helix dual paths, unless, they were built in the new IR cab system, but yeah I don't think so, as that would exponentially increase the number of required IRs... So yeah I guess the only way to get dual cabs in Go would be using IRs, as it very likely won't be included in Go? I've really not seen many dual IRs packs/downloads... But maybe they wouldn't be too difficult to generate via Audacity or the such? If IRs are simple .wavs, generating a dual cab IR would simply be adding the two waves together and then halving amplitude? You'd basically get the average of both IRs. If you wanted, you could also mix 60/40 or 70/30 % for left/right channels, which might give interesting stereo results. Am I misunderstanding the concept of IRs or wouldn't this be incredibly interesting for Pod Go users?

Meh... Seems a bit bland... Really like a more subtle / low CPU option; like something you'd put on a patch where you don't really want to hear a reverb but do want a reverb so it doesn't sound dry... In my experience, the fancy reverbs eat the DSP, but looking at the DSP usage, even the cheaper ones are 13.19%, so yeah even these are a bit expensive, if it's much cheaper than that.. Might unlock other previously impossible combinations.. But looking at Helix %, it's 13.33%, so compared to those same reverbs, they're showing 6.55% for Helix, so basically, it won't be cheaper, it'll be twice the cost of most reverbs, but being dynamic reverb, it'll probably have better quality. So it's really not a cheap option... Well not cheap as per saving DSP for reverbs, but cheap as per a a cheap 'dynamic' reverb... So yeah, I'm back to "Meh"...

Ha.. As a reminder, what were the big 3.5 upcoming changes again? Dual cabs? Were these likely go to in the go? https://line6.com/support/page/kb/effects-controllers/helix/helix-350-release-notes-r1003/ Some new Moon Amp, couple effects, I'd be mostly interested in "Dynamic Ambience (Mono, Stereo), Line 6 Original ambience reverb. At less extreme settings can be used to "open up" the sound of your amp without applying a notable reverb effect. Also utilizes less DSP than other Dynamic reverbs." In the meanwhile, does anybody know of good dual cab IRs? Think I've read about'em, but haven't really gotten a set of them, if they exist... Might be a good compromise in the meanwhile, if the dual cabs ever get released to Go..! Thanks for the info!

Both Pod Go and PGEdit up to date? Does the issue occur only when you edit the patches directly on Pod Go or just pod go edit? If you plug in headphones do you have the same issue? Lastly, "only a reverb pedal, or delay pedal became the controller for volume". Is it a particular reverb and a particular delay that controls the volume? What happens if you change them for a different reverb or delay? What if you create a new patch? Depending on your answers to the above, seems like a corrupted PGO, would contact Line6.. :\

try contacting line6 support, this is a user forum that line6 doesn't at least officially monitor.

This. IMHO, not the right unit if you wanted simplicity. Looking at the L6 products doesn't seem like any would really fit, think Zoom and others have simpler units, but likely not the strength of the Go. Maybe something like Boss GT-1 Guitar Multi-effects Pedal would have been simpler, albeit, definitely drawbacks such as sound quality, probably no downloadable patches, etc. Go Strengths: - Quality of effects: Fantastic emulation of amps, reverb effects, all kinds of pedals, etc. - Flexibility & tweakability: Probably lot better than most cheaper / other FX pedals. - Price, features, color screen, etc. Weakness: - Complexity; lots of effects with TONS of parameters, really hard to know what param does what - Cab/mic system; better to get "the best IR in the world"; fantastic alternative to cab/mic IMHO, YMMV - Limited blocks Another alternative could have been something like one of those 'portable' amps; Positive Grid, Yamaha THR, etc., but they don't really do what the Go does. And not same form factor. In the end, hte Go is a great unit, IMHO, but it's not 'simple'. It's simple enough as per it's easy enough to learn the basics, but if you're a sort of tweaker that can get overwhelmed by options, you can dive really really deep... But in the end, it's worth the effort. As you can really get incredible results from it. So you likely 'overbought'; you bought something 'too good' for a beginner player, but you bought something which has incredible potential and will likely get years and years of use, where the product will be limited by the user, not vice versa.

Not really sorry, might eventually try something but as I said sounds fine to me, ex; https://youtu.be/Hnco7JtYK7k?t=1020 But yeah, correct me if I'm wrong, but initially now so some are fine, some are noticeable others horrendous. Maybe someone else can chime in, but I think it's safe to accept that for instance, colordrive is horrible when used with a clean amp used on the edge of breakup. But that may very well not be its intended purpose. So it may not be a reasonable expectation that all drives are usable for that particular usage... Rereading z3albw1rr's comment, he explains many aspects of distortions and such. The clip above about the Heir Apparent, personally, love it, and don't hear any issue really. Will it work with 100% settings and 100% amps and sound perfect with all guitars & all? Maybe not... Can you find use cases where it can sound bad? I'm guessing sure, you're saying it's 'noticeably' 'bad' ... Maybe it's just not the right OD/distortion for your intended purpose? The Valve Driver is "obviously brittle"; it's the #3 in the previous clip; https://youtu.be/Hnco7JtYK7k?t=750 Sounds fine to me...? (maybe not 100% Go vs Helix, but should be very close..) Scream808 is #2 https://youtu.be/Hnco7JtYK7k?t=522 So yeah maybe you're more looking for particular 'great' drives for as you say; edge of breakup? Rather then all od pedals 'having issues' because they don't work as you would expect for this particular case? not saying there's no issue... Or that you're not correct in your 'quest' to get to the bottom of it! Just that... The issue seems a bit like a 'special case' ... Reminds me of the old: “The patient says, "Doctor, it hurts when I do this." The doctor says, "Then don't do that!”

yep, same problem but Silverhead's seems like a good solution/compromise!

I played a little bit with the Colordrive (Based on: Colorsound® Overdriver), and like you describe it's a 'funky' overdrive/fuzz/whatever, weird sort of tremolo effect, distorts weird, when volume goes down there's like a sort of 'wall' where volume drops significantly, some weird clipping sound as per your clip. Really seems to be like the odd one out as it doesn't behave like a normal boost/overdrive. If it's not the real pedal, maybe that L6 model is just funky. Honestly, not something that I think is usable with a clean amp, but looking at the original colorsound overdriver, every clip I've found have had the amp's drive so that the tone is not clean. So maybe it's just not made to match with a clean amp. Or maybe like I said L6 model just plain sucks... So it looks like you found maybe THE worst overdrive in the Pod Go. ;) I kid I kid, maybe others are worse, I don't know, I just tend to use the ones that sound good to my ears! Like the Minotaur (Klon), Heir Apparent (Analogman Prince of Tone), deranged master for heavy stuff, etc. There's quite a few great ones in there! Do you have issues with the 'good' overdrives / distortion too ? Which 'good' overdrive sounds 'bad'? [edit] For your patch just putting the kinky drive before the colordrive improves things drastically, your scenario is basically the worst, putting it after the colordrive makes its 'defects' sound worse!