That's where I wound up. I can tell you (based on extended use) that the O2 I have (assembled by JDSLabs) is rock solid. Ordering it pre-assembled gets you the benefit of a warranty. My interaction with the ODAC was also very positive, but briefer. There are copious measurements available of both over at the designers blog (nwavguy), along with measurements of other affordably priced DACs. I'm not a fan of the front cables either, but the device is the size of a paperback book, so it's easy to conceal (I just turn it around).
The issue for me is that ReplayGain doesn't work well enough that I can leave volume alone 100% of the time (I think R128 analysis might) and I was unable to convince Matt to either allow ReplayGain/R128 to process videos, or at least provide an option that levels the volume between Stereo and 5.1/7.1 downmixing. (the more channels you have, the quieter the downmix needs to be)
So I would need to have the O2 within reach - and the ODAC input is on the rear of the unit anyway, so you can't just turn it around to hide the cables.
This is actually my biggest issue with using a DAC. With an AVR, it uses HDMI CEC so that I can control everything through my TV remote as I do now, and HDMI supports automatic lip-sync correction to adjust for delays. But an AVR is a huge unit, and the headphone outputs suck.
With an external DAC that is connected to the PC, I lose the ability to control volume via the TV remote (
unless they add support for libCEC) and I lose the automatic lip-sync correction. (and I was unable to convince Matt to add the option to adjust the delay depending on whether a video is being played fullscreen or windowed - as my TV has a variable delay)
I occasionally get cursor skipping with wireless mice when my mouse battery is dying or there's something physically obstructing the wireless pathway. I've never had mouse skipping with a wired USB mouse, and the wireless mouse skipping is so infrequent that it's never come up when I happened to be listening to headphones.
It's not a wireless issue - only the Logitech mouse is wireless, and it's linked to CPU usage rather than range/signal/battery life.
I do think it must either be Windows, or coincidentally an issue with all the mice I have used across multiple computers. (I can't rule it out)
I don't really do much that maxes out the CPU load (when I can still see a mouse cursor) on my current PC though (I've never observed the CPU load get much above 50% except during a fault condition, although it may get higher than that when it's hard to have a look at, i.e. during video games), so maybe my mice would skip under those circs, and it just hasn't come up yet.
The main thing that was causing it to happen for me was when Media Center was analyzing multichannel DSD files, or multiple DSD files at once. (with auto-import, it seems to do one at a time, manually analyzing I do four at once)
It also happens when using
sacd_extract to convert DST compressed DFF files to DSF. (if I didn't realize the disc used DST compression)