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. 

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.