JRIVER and WINDOWS 8.1 x64Since a few people seem to be having trouble with jRiver 20 and WASAPI ....
I just tried this on my test machine here.
This is a Dell Optiplex 3010 (desktop) running a 64 bit copy of Windows 8.1 (which was updated online from the original Windows 8.0 OEM version that came with the machine).
Driver Signature Enforcement has previously been disabled (using the instructions included with the driver).
I started the machine from full off (full boot, not hibernation) without holding down any keys.
The drivers appear to have loaded correctly (there were no errors).
Under Device Manager, the XMC-1 is identified as "XMC-1".
On the tab under Driver Properties it says "C-MEDIA" - which is the interface chip we use (if you see MicroSoft there, then the WRONG driver is loaded).
I have jRiver v 20.0.10 installed (which is relatively recent).
jRiver shows the XMC-1 as "SPDIF OUT (3-XMC-1) WASAPI (note that the number before "XMC-1" will vary depending on what other devices you have loaded).
I have Bit Depth set to AUTO.
I think everything else is set more or less to the defaults, and with the new drivers, it doesn't matter if you "Disable Event Mode" under WASAPI or not....
When I play a 24/192 file (from one of the new HDTracks Grateful Dead remasters) it shows on the XMC-1 as "A:USB PCM2.0 192kHz 24bits"
It shows the same when I play it through FooBar2000 on the same computer.
-------------------------
Since I can't replicate any problem here, all I can do is make some suggestions......
* For those of you who have older XMC-1's whose USB firmware you've updated.... once the USB firmware update has been successfully applied, it is VERY permanent.
It won't disappear, or mysteriously return to the older version; unless you re-run the installer, and physically install a different version, you can think of it like new hardware.
Likewise, I have never seen a situation where, after confirming that the correct version was present on the USB interface chip, it later turned out not to be.
(I mention this specifically because being able to work at 24/96 but not 24/192 is a typical symptom of NOT having the USB firmware update.)
* The C-Media interface chip we use is relatively popular, so it is not unlikely that Windows might find and install the WRONG driver is allowed to search for drivers or do an automatic driver update.
(However, Windows should NOT be doing this unless you tell it to).
If this happens, installing the correct driver (ours) will fix it.
* On most 64 bit versions of Windows 8.0 and 8.1 (and even some few 64 bit copies of Windows 7) you MUST have Driver Signature Enforcement turned off to install the driver
and it must remain off. If it gets turned back on, the driver will disappear or become disabled. If this happens, you will have to reinstall the driver.
(When Driver Signature Enforcement is turned on, it will physically remove parts of the driver, so simply turning it back off again will NOT put the driver back.)
The method I provided in the driver instructions for disabling Driver Signature Enforcement should work for all computers and SHOULD be permanent (it worked on every computer I tried it with)....
HOWEVER, there are multiple methods for doing this, and reports suggest that not all methods work for all computers and version subsets of Windows.
*NOTE that you won't see the drivers in Device Manager (or your application) unless the XMC-1 is connected and turned On (you don't have to have that input selected). This also means that, if you have a bad cable, or a too long cable, or a flaky USB port, the drivers won't load and won't be visible.
If you look in Device Manager and see Microsoft drivers, it almost certainly means that our drivers have been damaged and will need to be reinstalled.
* To reinstall the drivers, you should run the driver installer, let it REMOVE the drivers if it says they're still there, reboot the computer, then reinstall the drivers.
It doesn't matter if the computer tries to automatically install other drivers and fails - or even if it succeeds.
Unfortunately, some individual computers and Windows installations may act other than the normal default behavior for Windows.
For example, Driver Signature Enforcement is ENABLED in some Asus 64 bit WINDOWS 7 laptops, even though it normally is not enabled for Windows 7/64.
It is also possible that certain "automatic driver checkers" may delete our driver and replace it with the wrong one.
Incidentally, the information you see listed for drivers and devices in the "output device selection" screens of many programs comes from a variety of places.
This is why you sometimes see things like the XMC-1 being identified as "S/PDIF device" (the C-Media chip is actually reporting that it is configured to use ITS S/PDIF output).
In general, since both the S/PDIF interface, and the normal implementations of USB audio, pad 16 bit audio data to 16 bits, the XMC-1 should ALWAYS show USB audio as 24 bits.
(Even 16 bit audio will normally be padded by the USB interface to 24 bits. If the XMC-1 shows 16 bits for a USB audio source, this is another indication that there's something weird going on with the drivers or your settings.)
If you are also using HDMI I don't really see the point in using the USB interface.
Just make sure you go through the windows speaker wizard and set all speaker sizes to LARGE to avoid the built in windows LFE channel xover and also to make sure it's set to the right channel count on your speakers and that it's set to send all of the sample rates the HDMI output is capable of.
I would be bold enough to even suggest the HDMI input from an HTPC is superior to the USB interface in every metric.
