@FractalAudio Please don’t leave axe fx II in this broken state
This has been mentioned a few times in this thread, and in the other threads on this subject.I don't know if anyone else figured this out, but I realized for me it's only happening when I'm also using the axe fx as an audio interface. So what I'm doing now is every time I use the Axe Edit, I stop using the axe fx as an interface, and I've had zero communication problems. This obviously is not a fix, but at least you won't have to restart the axe fx every 2 minutes.
I don't know if anyone else figured this out, but I realized for me it's only happening when I'm also using the axe fx as an audio interface. So what I'm doing now is every time I use the Axe Edit, I stop using the axe fx as an interface, and I've had zero communication problems. This obviously is not a fix, but at least you won't have to restart the axe fx every 2 minutes.
Then remember the 10,000 other threads where Fractal exhibited superb customer support.Remember this thread the next time someone says Fractal has good customer support.
Appreciate it Cliff. I will be able to find out pretty quickly if it worked.We have not been able to reproduce the problem here. However while working on the Axe-Fx III (fixing the crash on the Underwater preset) I found a bug that also affects the Axe-Fx II. This bug is a string copy bug that causes a write into a wrong area of memory. This could explain the problem if the write is overwriting an area of memory that services the USB. I'm not saying this will fix it but it's the only bug I've been able to find.
I'll be releasing an update shortly.