|
|
Post by wilburthegoose on Aug 20, 2015 8:27:02 GMT -5
From Keith L on August 7: "We will, of course, make the official drivers available for download as soon as we receive them and confirm that they work correctly.
(We expect the Windows 10 drivers to be available early next week.)"
We're way past "early next week". When will the drivers be available?
|
|
KeithL
Administrator 
Posts: 10,261
|
Post by KeithL on Aug 20, 2015 9:03:28 GMT -5
UPDATE (8/20/2015) The Windows 10 DRIVERS ARE NOW AVAILABLE.
They have been tested and we haven't seen or heard of any problems.
(Note that you will have to disable driver signature enforcement in Windows 10 -
this is required in order to install many current drivers, and the procedure to do so is covered in the Install Instructions.)
|
|
KeithL
Administrator
Posts: 10,261
|
Post by KeithL on Aug 20, 2015 9:05:54 GMT -5
Sorry - the drivers have been available for about a week. (This was mentioned IN the thread, but I didn't make a separate "announcement post".) From Keith L on August 7: "We will, of course, make the official drivers available for download as soon as we receive them and confirm that they work correctly. (We expect the Windows 10 drivers to be available early next week.)" We're way past "early next week". When will the drivers be available? |
|
|
|
Post by ozohnoes on Aug 21, 2015 8:38:52 GMT -5
Just FYI Keith, Windows 10 Defender (Anti Virus) detects the zip as Malware. You need to disable Real Time protection to download the zip, then perform DSE, then run the installer. At this point, it will also complain about Malware detected but all will be fine.
It's working now, thanks!
Emotiva (and/or CMedia) should really look into driver signing when you get a chance.
|
|
|
|
Post by wilburthegoose on Aug 21, 2015 9:43:40 GMT -5
Yeah - driver signing is very important.
|
|
KeithL
Administrator
Posts: 10,261
|
Post by KeithL on Aug 21, 2015 11:04:01 GMT -5
Interesting.... I do know that Norton Internet Security flagged the installer. (but only based on some "reputation based heuristic" based on the fact that it was less than a week old and not many people had already installed it). I also know that Windows 10 Defender didn't have any trouble with RUNNING the installer file itself (at least as of last week). However, I never actually tried DOWNLOADING or extracting it through Windows 10. Honestly, driver signing is something that you have to pay for, but which provides little to no value, so about half of the world does it and the other half doesn't. (And, since a significant percentage of drivers are not signed, most people I know end up disabling DSE anyway.) Some security programs simply pop a red flag if you try to download ANY file or attachment that contains an executable. Thanks for the heads-up. (And I will include it in the FAQ.) Just FYI Keith, Windows 10 Defender (Anti Virus) detects the zip as Malware. You need to disable Real Time protection to download the zip, then perform DSE, then run the installer. At this point, it will also complain about Malware detected but all will be fine. It's working now, thanks! Emotiva (and/or CMedia) should really look into driver signing when you get a chance. |
|
|
|
Post by rygher3 on Sept 6, 2015 13:34:27 GMT -5
Any info on the XDA-1? I'm looking at upgrading and want to make sure that I won't lose the XDA-1 functionality.
|
|
|
|
Post by garbulky on Sept 6, 2015 14:36:57 GMT -5
xda1 should work no issues
|
|
|
|
Post by Mark P. on Sept 15, 2015 0:43:29 GMT -5
Using Windows 10 and DC-1 without a problem. Just make sure you have selected "USB Mode" > "USB 2.0" and then the CMEDIA will recognize you are connected. Took me a while to figure that out as the drivers kept asking for the device to be connected even though it was. Using Foobar2000 with WASPI and it is working great.
Emotiva DC-1
Windows 10
PreSonus Eris 5 speakers
PreSonus Tremblor T10 subwoofer
Emotiva Control Freak
|
|
|
|
Post by grampafuzzy on Sept 27, 2015 20:04:45 GMT -5
Have I missed a post, or are we still waiting for the official Windows 10 driver for the XCA-2?
|
|
|
|
Post by geebo on Sept 27, 2015 20:49:40 GMT -5
Have I missed a post, or are we still waiting for the official Windows 10 driver for the XCA-2? Maybe you meant XDA-2? If so, there on this page under Resources: emotiva.com/products/dacs/xda-2-gen2 |
|
|
|
Post by romotiva on Oct 28, 2015 15:41:46 GMT -5
Hi there, after installing FW 3.1 on my XMC-1, i had to reconfigure my Win 10 drivers on my PC running foobar2000. After installing the c-media win 10 driver 1.01a (turning the digit signing off) properly, there is no 'SPDIF Out (XMC-1)' device but only 'Speakers (XMC-1)' This doesn't give me a direct bitstream capapbility from my PC files to the XMC-1, any of you had the same ?
|
|
|
|
Post by romotiva on Oct 28, 2015 16:52:26 GMT -5
Hi there, after installing FW 3.1 on my XMC-1, i had to reconfigure my Win 10 drivers on my PC running foobar2000. After installing the c-media win 10 driver 1.01a (turning the digit signing off) properly, there is no 'SPDIF Out (XMC-1)' device but only 'Speakers (XMC-1)' This doesn't give me a direct bitstream capapbility from my PC files to the XMC-1, any of you had the same ? ok, solved it ! I had to completely turn off XMC-1 (switch off in the back). After 1 min I switched it on and Voila! the SPDIF output was there ! |
|
|
|
Post by Geriatric Sod on Nov 23, 2015 22:44:10 GMT -5
Can someone post a working link to these drivers? The XDA 2 page is giving a (403 - Forbidden) response and I can't seem to find a way to download the drivers anywhere!
Thanks
|
|
|
|
Post by frenchyfranky on Nov 24, 2015 11:43:40 GMT -5
Can someone post a working link to these drivers? The XDA 2 page is giving a (403 - Forbidden) response and I can't seem to find a way to download the drivers anywhere! Thanks The XDA-2 is discontinued, you can find the drivers download link on the XMC-1 page under resources tab. |
|
|
|
Post by frenchyfranky on Dec 27, 2015 11:47:33 GMT -5
It appears that over the time of using the not signed c-media driver 1.01a for Win 10 with JRiver, is creating some conflict errors in Windows 10 interface, a lot of error log have been sent to Microsoft. I'm waiting for a future Win 10 signed version of c-media driver because this one is working but not trouble free with Win 10.
|
|
KeithL
Administrator
Posts: 10,261
|
Post by KeithL on Dec 27, 2015 12:38:05 GMT -5
I'm sure Microsoft will eventually get their act together with Windows 10. (When Driver Signature Enforcement is OFF, then Windows should ignore whether a driver is signed or not; if it's still having problems with unsigned drivers, even when checking has supposedly been disabled, then that is clearly Microsoft's problem.) The whole purpose of driver signing is to prevent unknown drivers from being installed "unknowingly" - either automatically by Windows or carelessly by users. It does NOT protect you from drivers that were infected with a virus at the vendor's location before they were signed, or from poorly designed drivers that might crash your computer, nor in fact does it protect you from bogus drivers with "legitimate signatures"; all it does is to provide some level of protection that the driver you have really came from where you thought it did. (In other words, it's only real value is in providing some level of authentication for drivers that "magically appear" at your machine via automatic updates, or that you download from some mysterious location on the Internet.) Since many vendors don't see the value in signing their drivers, and not all users are careless, it seems to me that an obvious solution would be to be able to flag the drivers for individual devices as "controlled". And device whose drivers were flagged as "controlled" would ONLY allow the user to specifically install drivers when they decide to, would ignore the signature status of any drivers which are MANUALLY installed by the user, and totally disable automatic driver installation and update. This would allow you to override DSE for any driver which you download yourself from a trusted source, lock that driver from being updated without your permission, and prevent it from being disabled or damaged by any rogue update afterwards. (I don't at all like the idea that Windows will automatically install anything, especially since, in the past, there have been numerous issues not only with signed drivers that simply didn't work, but with updates issued by Microsoft, both of which have a far from perfect track record of being "safe" to use. I'd much rather download a driver I trust, from a site I trust, and install it myself - then be able to lock Windows from changing it without my permission. I would personally prefer if Windows simply asked my permission before installing ANY driver.) It appears that over the time of using the not signed c-media driver 1.01a for Win 10 with JRiver, is creating some conflict errors in Windows 10 interface, a lot of error log have been sent to Microsoft. I'm waiting for a future Win 10 signed version of c-media driver because this one is working but not trouble free with Win 10. |
|
|
|
Post by sgonz11 on Dec 30, 2015 18:49:31 GMT -5
can you provide a link to the win 10 drivers?
|
|
|
|
Post by cwmcobra on Dec 30, 2015 20:02:31 GMT -5
Go here and click on "Resources" and click on the Win 10 driver. |
|
|
|
Post by toliandar on Jan 18, 2016 3:44:01 GMT -5
When I got my DC-1 the drivers (including the Schiit driver) didn't work with Windows 8.1. It seems this has changed and it can even work in Windows 10 - I'm curious though is there any advantage in using the USB connection over Toslink optical?
|
|
