We did some testing on an old P4 with XP and also an Atom-based system.
The P4 worked great with the Transit.
The Atom has some hardware problem with the Transit where the output would switch to noise using ASIO if the video card does anything. (happens with multiple ASIO playback programs, so not a JRiver issue)
I would disable any DSPs (including resampling) and makes rue the 'Latency' tab on your Transit is set to the max during playback. If you still get hiccups, you may just be out of luck with ASIO and that hardware.
Sorry Matt, my findings don't concur. While I do have an Atom, it seems the problem is with MC.
I just tested playback of a local 192kHz file in Foobar with no hiccups using Lynx ASIO or WASAPI, while min/max MC (in tiles mode at 1920x1080).
Then I switch to playback of MC for the same file, and I can make playback hiccup every time on minimize.
I tested seeking to the end of 20 files in Foobar using their WASAPI 2.2.1 output plugin with no issues or hiccups. MC resulted in LOUD white noise, or out of sync playback when left to crossfade into another song.
I have both Foobar and MC set to 1000ms buffer, with MC set to 6 seconds playback and no memory playback. I have also tried the hardware sync feature at 1/4 and 1/2 second which just makes things worse. Tried various WASAPI settings but 24bit playback is needed for Lynx WASAPI playback so that's all I can use.
I can't see how this is an ATOM issue if Foobar works 100% with the same files and sound hardware.