adauria

OP here. I ended up sending it back to Line6. I believe they wanted to look at my unit so they could determine if the issue was something related to hardware, software, or what. They ended up doing the repair under warranty for me. I didn't get a lot of details on what they did or found, but when I asked they said they swapped the entire display with the knobs. So, maybe hardware? Maybe software impacted the hardware? In any case, they made right by me and I'm grateful I've got it working again. I did have the same issue you had on knob 4 - 2 values alternating back and forth. So, weird for sure.

I worked for a major AV vendor for 4 years... these days I'm all about MS Defender as well. Built and works as well as any of them. If you are just using the system for recording/playing and not surfing the net or checking email, you could temporarily disable your AV while doing that - might help if you are have AV related latency issues.

Thanks. It can't hurt to reach out to support, I suppose! Much appreciated.

DSP is a limited resource in any modeling unit. There's a quantity of it, and each effect in the chain (including amps and cabs) all require some to varying degrees. When you start using most of it up, some of the more DSP-intensive effects become unavailable. Since there are differences in how much each block uses, though, you can sometimes substitute an "expensive" (high DSP) block with a similar effect and get some available DSP power back for other things. Your pitch and filter blocks use a lot of DSP, IIRC. I'd start there. Someone over on the Helix forum here has posted a public spreadsheet on how much DSP each of the Helix effects and amps use, and I'm sure it will give you a good idea of the relative DSP required by the same blocks on the Pod Go. Also keep in mind that a big part of the price difference between a Helix and a Pod Go (or the smaller HX units) is the amount of DSP power, with the Helix rack/floor/LT being the most in a Line 6 hardware unit, and you can even go beyond those limitations with Helix Native software on your computer.

One would think/hope, but who knows... No where near a service center, unfortunately.

Less than a month ago (11/18) from Sweetwater, who I assume does a pretty good turnover of inventory. -Andrew

Some of this exists, or can be worked around. My (very uninformed) thoughts here: 1) You can set any parameter to a snapshot or pedal. I go from clean to dirty on some amps, e.g. a plexi, by having a pedal assigned to the drive, channel volume, and master volume parameters (I will probably add some amp tone stack changes in there too). On my Helix I am able to switch between 2 actual amps, but this isn't a Helix. 2) I'd definitely like 8 snapshots per patch. You can do this with a Helix (my main gigging modeler). Might be possible for developers to do this with a Pod Go but I'd bet there are technical limitations you'd have to trade off (e.g. less presets or something), plus market differentiation with their other products. 6) Why can't you save effects presets in Pod Go Edit? You can use "User Defaults" for your preferred parameter settings or "Favorites" for this purpose, if I understand you correctly. 7) You can also return any parameter to a default in PG Edit (I think it's ctrl-click in Windows, e.g. or something like that). If you want to return an entire effect or amp to default just change the thing then change it back. Hope that helps!

I was not aware of this and it was the nature of my question above. Do you know if it's possible (other than testing with a buffer, since I don't trust my ears entirely) if this has been fixed in a given unit? I just got mine a month ago from Sweetwater, but if there's an easy test or serial number cutoff, etc. I'd love to know. I mean, I can and should test with a buffered pedal, but regardless of the unit's status I fully expect that it will sound brighter just due to the nature of buffer. Brighter or louder may sound better in direct comparisons but might not really be fair or a good way to compare. I'm really just curious if my unit would improve with a "fix" or not give nthat it seems to be new production. Thank you!

I actually also have a Helix LT and have had the same problem there (don't use it barefoot was the lesson I learned) because it has touch capacitance sensitive footswitches. The Pod Go does not have that same capability. I just tried it anyway and it doesn't work the same as with the Helix / HX devices, so that's a no go as well. Thanks for the suggestion, though!

Actually, doesn't seem to work. Here's what I did: - press pedal until light is on, amp goes to min value (clean) settings - moved sliders to match dirty settings - saved patch with amp set to max / dirty settings and light lit - clicked pedal a few times, and it reverted to light on as clean I even tried adjusting the values and max indicators (on top of slides) before re-saving with the same result. Am I missing a step here that worked for you?

Ah, thank you @dickiesymth! I'll give that a shot

OK, I attempted another downgrade, this time doing a factory reset (hold FS9/10) after the downgrade. Same result, no joy. One thing that is strange, though, is that on 3.5 turning that knob in either direction will alternate 2 adjacent values (e.g 39/40) and go no further, but in 3.15 and the UI test the number the parameter controls doesn't budget at all. So, still odd behavior, but another clue. At this point I'll take it to the shop in a couple of weeks once I can get over that that part of the state. Maybe I'll get lucky and hear more about it or find that it's software, but unless that happens we'll have to see what they say at the authorized service center.

Did you open a ticket? I'm trying to understand if you are one of the additional cases with the LT that the support rep told me about, or if you are another case altogether. Also, if you downgrade, try the factory reset procedure (power on with pedals 9/10 depressed) after the downgrade. I'll post the results of my downgrade / reset procedure here as well.

OP here... I don't think it's that crazy that it's an update related issue since the update specifically contained a change to the behavior of these knobs. Like most bugs (if this is a bug), it would only impact a limited number of users based, e.g., on configuration settings, hardware revision differences, etc. I've been working in the software business since 1996, so I have seen my share of weird software bugs. Not mention the sample size might be pretty small - Active Helix users, LT model, upgraded to 3.5, and whatever other conditions might cause this behavior, again IF it's a bug. I'm not married to that concept, but if has happened to 3 of us now (exact some knob on the LT) upon the point of upgrading to 3.5, the odds of coincidence go down - not impossible yet, but reduced. @datacommando @theElevators I'm glad you have no issues with the upgrade and your Helix. There's no need to mock investigating the possibility of this being a bug in light of the logic above. Another factor is that the closest authorized service center is 150 miles from me, and I'm out of warranty, so investigating fully before paying to investigate the hardware route makes a lot of sense, no? Support initially thought maybe they were seeing something here since there were a couple of other reports of similar issues. They had me do (another) UI mode test, and then said, oh well... take it for service. That's my plan, but in the mean time I'll keep watching this thread since we now have 3 independent reports of this. @HonestOpinionI did test the rollback, but I didn't factory reset AGAIN after the downgrade. I plan to try that test after I play at church this Sunday and bring the unit home again. If it works, you can be sure I'll report it here. I'll also let this forum know what the result of taking it in for authorized service is, if I have to go that route.

So I've got a couple of amp parameters assigned max/min values to a footswitch. I had it such that the dirty settings of the amp are the max value settings, and originally corresponded with the footswitch light being on. The clean settings were min values and light off. I made some adjustments in Pod Go Edit, and it switching things such that dirty still matched max and clean still matched min, but the light state is reversed. I'd like to go back to light on = dirty instead of light on = clean. Is there any way to do this without removing the assignments and recreating them?