chriskun

I'm with Mark on this, i've owned a x3 bean for 8 years, and this problem has always been there. I've never seen someone from line 6 even acknowledge it. Every thread i tried creating back in the days was just ignored. The only fix that works and is not placebo is running xp 32bit, which is kinda sad cause it probably means it's just a driver bug in the 64bit version... And yes in case you're wondering, problem's still here with windows 10.