I had to send my POD X3 Live back to Line 6 for a second time because the USB audio drop-out bug had not been fixed by their first attempt. Especially recording, but also playback, will eventually lose the connection to the computer and cause it to lock up whenever it tries to reacquire the X3 Live, resulting in crashing of music software and later an inability to shut down as the system tries to find an audio device that no longer exists (even though it is still plugged in). Sound familiar?
Well, I got it back today. And look what I was told on the paperwork:
tried recording with Ableton Live application and had no issues, recorded and played back fine. Soak tested as a sound card without any issues. Would suggest that customer reinstall Pod X3 Live drivers and recording application.
What, am I imagining that this issue occurs on two separate computers, one of which HAS just had the drivers newly installed for the first time ever, and with various different recording applications running various different I/O protocols, controls that I already specifically put in place because I’m not a total idiot and know to test things properly before reporting them? I have no idea how stringent your ‘soak test’ is, but it apparently is not good enough. And neither is your reply here.
Yes, I have performed a factory reset and re-flashed the firmware, too, before anyone throws yet another platitude at me. As expected, these did nothing. What next? ‘Try buying a new USB hub’? Anything to shift the blame onto me, I guess.
This is simply not good enough. I was told on the phone that I might be given a new motherboard. If you were so confident that there’s no problem with my current one, why not just shut me up by giving me a new one anyway? It’s not like you’re doing anything else with the surplus of boards you presumably have.
The POD X3 Live is a fantastic device on paper. A shame, then, that it doesn’t work in reality as it claims to on paper.
And it’s even more of a shame that you apparently can’t be bothered investigating this properly, instead trying to secure plausible deniability of guilt by defaulting to the old method of questioning the other elements of my setup and, by extension, blaming me for the problem.