Thanks Tim,

Yes, it sounds like a potentiometer issue.

However, it did not display any similar problem prior to the update.  Even when editing, never had it jump or behave in any manner that suggested dirty pots, or bad pots.

I'm wondering if a good lubricating contact cleaner (like De-Oxit D5) would resolve this, if it is in fact a problematic pot.  I've been a fan of that stuff for years.  It has salvaged what appeared to be bad gear many times for me.

I notice a lot of people suggesting moving pots back and forth and parking them, which is actually good advice.

But I never hear about doing anything more than that.  If there is corrosion building up inside the pot, moving it back and forth only temporarily fixes it.  Contact cleaner (with lubricant) is a much better long term fix.

Corrosion WILL happen in any pot.

But the other problem is the real issue.

One thing I noticed is that when the solid black bar appears on the top line (where Tone1 name normally is) the Tone2 light turns off.

I can't say if this only happens in Tone2.  I'm not sure about that.  But I did notice that when I'm using Tone2, and this problem occurs, the Tone2 light always turns off.

It does seem to happen only when I toggle one of the individual effects on or off.  That is the event that triggers the problem and symptoms.

It's very frustrating.

First off, thanks to Line6Hugo for jumping in.  I apologize for venting, but obviously I'm just a bit frustrated. 

I think you're right Hugo.  I read it somewhere here before too.  But I've searched and searched and can't find it again.

I found it originally when I was looking for other information, but now I can't seem to find it.

Exact recipe is not possible, but I can tell you that it usually goes like this summary:

• I'm working on Tone2 in any given patch, toggling effects on/off and adjusting parameters.
  
• Saving the patch when I get a sound I like.

I repeat this many, many iterations.  That way I can easily undo any change I don't like by switching to another preset then coming back, because I've saved the most recent changes I did like.

• Problem happens while I'm adjusting parameter settings or toggling effects on and off.
• After the problem begins, any adjustments I make (except Master Volume) do not alter the sound at all.
  

More detailed explanation:

I usually start with a basic clean sound.  Amp and cab model only.  I will double tap one the effects footswitches (like Stomp for this example) to turn it on and bring up the page with the parameters which I can adjust.

After tweaking parameters I will toggle it back and forth between the clean sound to see if there is a good balance.

Then I might leave Stomp on and do the same with Delay or Mod (or .....).  Once I get it (delay for this example) dialed in I will toggle it off and compare with the Stomp.  Then toggle off Stomp and toggle on Delay to compare.  I like these transitions to be smooth and not jump up in level or volume.

After doing this for a while, that is when the problem occurs.  Just to be clear, I don't do this once, or twice, or ten times.  It is many, many iterations.  Perhaps hundreds or thousands of times in a matter of twenty minutes.  Probably most users don't do this, therefore have not had the problem.  Or they use Gear Box or Pod Farm to do their patch editing.

The basic things going on prior to the problem is a lot of toggling on and off of effects, a lot of tweaking parameters, a lot of saving the patch.

Sometimes I'm going back and forth between Tone1 and Tone2 and/or other presets.  But always a lot of tweaking parameters and saving the patch.  Not using GearBox or PodFarm.  And the problem happens while I'm adjusting something, or toggling something on/off.

Problem seems to happen only when I'm on Tone2, but that could just be coincidence.

Perhaps most important is that I did not seem to have this problem before I updated the firmware.

I can't reproduce it every time with step by step procedure, but usually within 20 minutes of intense editing and experimentation it happens.

I'll try the "recipe" from the other thread and see if I can repeat it on my unit.

I believe they are one in the same, not just the symptom.

Some kind of buffer overflow or something.  I don't know.

I'll see if I can produce some kind of recipe for the exact problem, though I'd prefer a recipe on how to fix it. 

My question has not been answered yet.

The most recent posts indicated that there was more work to do in order to determine if this is the same as the other similar problem.

A previous post was referred to, and it had a bug logged in May 2009.  However, it Line6Hugo stated that my "recipe" to recreate the problem was not exactly the same as in the other user's previous thread, and therefore my exact problem is not going to be addressed.

So that doesn't sound like my question was answered.  Sounds like I might just be stuck with a defect.

True, you haven't heard from me for a few days.  If I had been aware that I need to keep posting every few days to keep this alive, I would have done so.

I haven't had additional information to add to this thread, as I've already provided exhaustive details.  So closing this all of a sudden without asking if I'm still needing help doesn't seem very helpful.

Maybe this thread and/or a sticky or document with an explanation of the symptom and it already being logged as a bug to be addressed in future releases, would be appropriate.

Just closing this thread doesn't help much.  The other posts regarding this problem were logged as bugs and haven't been addressed yet, and I was unable to search this forum to find anything regarding this symptom.

It seems like it would be beneficial to Line 6 users to be able to quickly and easily find some answers to this problem, even if the answer is simply that it's a known problem and has been logged and might be fixed in a future update.

Line6Hugo,

I can reproduce this problem exactly as described.  I'm confused why I need to be able to reproduce the problem in another manner also.  If I could get my hands on another Pod X3 Live unit with the same firmware and updates, I suspect I could recreate the problem on that as well.

I thought about making a video of it to document it.  So anyone could try to replicate the problem.  Then I realized that you already have a similar bug logged, and that problem hasn't been addressed yet.  Soon it will have been a bug that has been logged for a year, with no fix in sight.

So I don't see what good it will do to spend more time documenting this problem.  Even if I can show you exactly how to recreate the problem on your equipment, I have no reason to believe that the problem is going to be worked on.  This model and firmware have a flaw, and if I upgrade to the next firmware I have to realize that I may be trading this problem for another problem, which is what happened to me with this latest update.

Of course this is not what anyone expects out of their gear when they spend their hard earned money.  But reading through these forums it's pretty clear to see that stability and consistent functionality aren't to be expected with the more advanced Line 6 gear.  It's probably much more reasonable to expect some kind of problem and either live with it or find some kind of workaround.

My question has not in fact been answered, but since it doesn't seem that there is an answer, nor any reasonable expectation of an answer, I can understand wanting to close this thread.  Perhaps marking it as "unanswered" would be more helpful to me and other Line 6 users, as it is misleading to claim that it's been answered.

Unless "answered" means that Line 6 doesn't have an answer.  Or Line 6 has no plans to address this problem (since you are saying it's different than the other problem and are unable to replicate the exact problem I've reported).  Obviously I have a problem with calling it "answered" as that seems to imply that it's been resolved, or that a resolution is pending.

I understand that there are statistics to keep, and having unanswered questions doesn't look good, so please proceed as however you are required to do by your employer.  You are just doing your job after all.