Jul 16, 2019 at 9:13 AM
- Feb 6, 2015
- Reaction score
- Feb 6, 2015
I will try explain what happened for me.I have encountered this issue quite some times and contacted Chord. The response was that the fpga can sometimes be confused if you switch inputs or turn off and on your pc, so the easiest way is to just unplug the usb or whatever you are connecting it with and plug it back in.
When it first happened I rebooted the Qutest and it was OK. The it happened very quickly again. I tried Qutest reboots and was thinking I had been sold a faulty Qutest. However I figured try another device on the USB input. I have a Sony DAP, and I an connect it to my Hugo 2, via an OTG cable. I connected it to the Qutest and the Qutest was immediately fine. Going back to PC there was still no sound. This sort of assured me that the Qutest was fine, probably.
On my PC in Sound control panel, I noticed something a bit odd. Since I have two DACS on my desktop, I can often see two Chord entries in the Sound panel. For the entry that runs my TT2, it's just Digital Output - Chord Async etc. The entry for the Qutest or Hugo 2 or Mojo, says Digital Output - 5 Chord Async. (The second entry started of as 2 Chord Async, but then not known why jumped to 5.)
However those entries got swapped over somehow. That seemed to be the problem. Whether it was or not, I don't know. Clicking make one or the other default, for a while didn't fix the Qutest issue. After a couple of 'Default resets' and a couple of reboots, I had the Qutest back.
I think the PC gets confused by having two Chord products, when one get unplugged. Like the TT2 entry in Sound Control Panel, is always there, whether the TT2 is on or off. The TT2 is only ever in stand-by or on, if it is plugged in. It talks to the PC even when in stand-by.
I'd like to think that it's what you say, though, that Chord said. However unplugging the USB and plugging it back in, didn't work.