|
|
Post by mysterymachine on Jun 18, 2014 11:17:49 GMT -5
Hello,
I seem to have issues with the XDA-2 USB drivers. Previously I had it plugged into my USB hub and I had the problem that if the PC went to sleep when it woke back up the XDA-2 would not function over USB. This is not an uncommon problem with some USB devices and hubs and sleep.
I finally got tired of rebooting after sleep and bought a longer cable so I could connect directly to the PC - which now I have a new problem. Everything works fine after initial boot, but if I turn off the XDA (standby) and turn it back on my PC pops up this message briefly:
"The device can perform faster please connect to a hi-speed USB 2.0 port"
And then the XDA-2 will work but it will not support anything above 48khz until I reboot the PC. All the USB ports on my PC are either hi-speed 2.0 or 3.0. I have tried both the 2.0 and the 3.0 ports. Other devices are fine and do not pop up this message about "can perform faster" (unless I plug a USB 3.0 device into a 2.0 port).
Any ideas?
Edit update: Windows 7, 64-bit
|
|
|
|
Post by garbulky on Jun 18, 2014 11:25:52 GMT -5
What happens if you turn it off and on from standby after sleep?
|
|
|
|
Post by mysterymachine on Jun 18, 2014 11:48:01 GMT -5
What happens if you turn it off and on from standby after sleep? What do you mean? The sleep issue was "fixed" when I changed from using a hub to connecting directly to the PC (but then this other issue popped up). When it was connected to the hub doing standby or even unplugging and plugging back in had no change. It would never show back up on the PC. Side note: Where have the XDA-2 drivers gone? I don't see them anymore (I still have them saved from Christmas when I got the XDA-2 and I hadn't heard of any updates but I couldn't find the links now). |
|
|
|
Post by garbulky on Jun 18, 2014 11:50:38 GMT -5
What happens if you turn it off and on from standby after sleep? What do you mean? The sleep issue was "fixed" when I changed from using a hub to connecting directly to the PC (but then this other issue popped up). When it was connected to the hub doing standby or even unplugging and plugging back in had no change. It would never show back up on the PC. Side note: Where have the XDA-2 drivers gone? I don't see them anymore (I still have them saved from Christmas when I got the XDA-2 and I hadn't heard of any updates but I couldn't find the links now). Right so the new issue is that it's being detected as USB 1. What happens if when you get the message you turn it off (standby) and turn it on again. |
|
|
|
Post by dac0964 on Jun 18, 2014 19:34:39 GMT -5
What happens if you turn it off and on from standby after sleep? What do you mean? The sleep issue was "fixed" when I changed from using a hub to connecting directly to the PC (but then this other issue popped up). When it was connected to the hub doing standby or even unplugging and plugging back in had no change. It would never show back up on the PC. Side note: Where have the XDA-2 drivers gone? I don't see them anymore (I still have them saved from Christmas when I got the XDA-2 and I hadn't heard of any updates but I couldn't find the links now). Yeah you're right the links aren't there anymore. Anyway, since you have it saved and it hasn't changed since, try re-installing the driver. |
|
|
|
Post by mysterymachine on Jun 19, 2014 13:04:14 GMT -5
Tried reinstalling the driver... No change.
Any time I use standby it reverts to no higher than 48khz, but I just found if I reach behind the XDA2 and pull out the USB and plug back in then it detects just fine as USB 2.0 with full 192. So its very weird something with the standby does not work correctly with my USB. I will try on my laptop some day when I get a chance.
I wonder if a better design would have been if in standby all the USB chips still work so the PC never sees it as unplugged. For now I will just leave it on 24/7 unless someone here on the forum thinks thats a bad idea?
Sent from my Moto X via Tapatalk
|
|
mrhoss
Seeker Of Truth
Posts: 8 
|
Post by mrhoss on Jun 19, 2014 19:20:17 GMT -5
DEAD ON MAN!!! I joined this forum SOLELY for this problem. This is what I recently sent to Emotiva. I currently have windows 8 64 and using the Emotiva XDA-2 in usb mode exclusively. If the xda-2 is not powered up before windows boots up I can only pick 44.1khz and 48khz. When the xda2 is powered up before the computer is I can pick from over 20 sample rates ranging from 44.1k to 192khz. If I turn on the computer without the XDA-2 being turned on first it shows up under audio controllers as "2 - USB2 High-speed true Audio" with a sample rate from 44.1 to 48k khz If I turn on the XDA2 first then the computer it shows up under audio controllers as "3 - USB2 High-speed true Audio" with a sample rate of 44.1 to 192khz  When the XDA-2 is working perfectly and I put it to sleep and take it out of sleep mode it will default to only letting me use 44.1khz and 48khz.  When the XDA2 is working perfect as "3 - USB2 High-speed true Audio" and I check the driver details it gives me an error of "No driver files are required or have been loaded for this device"  When the XDA2 is not working ideally as "2 - USB2 High-speed true Audio" with the 44.1k to 48khz range and I look at the driver details it shows me 2 files installed within the system32 folder. I've tried installing the drivers using the .exe file. I've also tried manually installing each driver, windows 8, windows 7, windows vista and windows xp using device manager. They either don't work because they haven't been signed by Microsoft or give me the 44.1 to 48khz range issue.  Another issue I had was drivers not being signed. I had to boot up windows 8 special so it would allow me to install non-signed drivers.  |
|
mz
Seeker Of Truth
Posts: 6
|
Post by mz on Jun 20, 2014 15:07:10 GMT -5
I had the same issue and Emotiva was unable to help. I thought it was mainly related to MAC hardware, but it seems to be more widespread. My "final" workaroud is not to use usb input directly but through usb-to-optical converter, available on ebay for ~$40 Take a look at 2 of my posts here: emotivalounge.proboards.com/post/614462/threadTrying different workarounds and fighting this issue lead me to believe that its a hardware problem (usb handshake), that needs to be reproduced and investigated by Emotiva. Still waiting for them to at least acknowledge the issue. |
|
KeithL
Administrator 
Posts: 10,271
|
Post by KeithL on Jun 20, 2014 16:53:22 GMT -5
We do know what the problem is, and we can sometimes replicate it.....
However the issue lies with the computer (and how it handles USB connections)... and not with the DAC or the drivers.
Unfortunately, since this will vary depending on the individual version of Windows you have, and your specific computer hardware, we can't provide a solution that will work for everyone. The way USB "works" is that your computer "knows" when a USB device is plugged in, and when a connected USB device is turned On. (The computer can tell when a device is plugged in, even if it is turned Off, which is why unplugging the cable sometimes produces a different response than simply turning the attached device Off and On again.) This status is detected by the computer's internal USB hub and hardware, and reported to Windows. When Windows detects that a USB device has become active, it loads the appropriate driver into memory (NOT to be confused with installing the driver onto the computer). It then "asks" the device about its capabilities - which, if the device is a DAC, is where the DAC tells Windows the list of sample rates it supports. (This is all pretty much the same for a Mac.)
If this communication fails, or if Windows fails to properly interpret the reply it gets, it uses default settings - which, for a USB DAC in Windows, is to support only 44k and 48k.
So, if your DAC connects, and plays properly at 44k and 48k, but fails to list other sample rates as supported, this tells you TWO things:
1) The drivers are indeed loading; because the computer won't be able to communicate with the XDA-2 or a DC-1 at all without the drivers. So, if it's playing, then the drivers are installed, and are loading.
2) Either the negotiations where the computer finds out what sample rates the DAC supports have failed to occur, or they somehow got corrupted, or the computer has either lost the information or failed to handle it properly.
When this process works correctly, Windows "knows" that the XDA-2 supports up to 192k - and everything works like it should. When you see Windows indicating that the XDA-2 only supports 44k and 48k, that means that the process did NOT work properly (44k and 48k is the "default" that you get when the correct information isn't available.). As far as we've been able to determine, the XDA-2 ALWAYS responds with the correct information when asked, and it is the computer that either isn't asking, isn't receiving the reply, or isn't handling the information correctly.
Now, there are several ways in which this process can "go wrong":
1) If the USB connection is less than perfect, then the information may become garbled. This can happen if the USB cable itself is flaky, or if your USB port is flaky, or even if the cable is simply too long, or if you're connecting through a hub. (It could also happen if there's something wrong with the DAC - but that is rather uncommon.) If this is the case, then changing USB ports, or changing USB cables (or eliminating an external USB hub), will usually solve it. Often, in situations where the initial connection comes up wrong, but everything is fine if you unplug and then reconnect the USB cable, this will also solve the problem.
2) Some computers (especially Apples) seem to have a problem when they go into hibernation. When a computer wakes up from hibernation, it should either continue to use the settings it had when it went into hibernation, or it should re-scan the current USB devices connected and get new information. For whatever reason, many Macs, and a few PCs, fail to do either. Even though they were working correctly before hibernating, they wake up with the default settings (44k and 48k only). There are quite a few things that could cause this to occur - and all of them constitute a fault in the hardware or software in the computer. They can also be prohibitively complicated to diagnose, and may not even be subject to repair. In these situations, the best solution is to set the computer to do full shutdown (disable hibernation).
3) In some cases, the process only works if you power up the various devices in a certain order (usually XDA-2 first, followed by the computer). As with hibernation issues, this is a matter of how the computer handles the USB connection and communication sequence - and not anything to do with the DAC itself. Unplugging and reconnecting the DAC "fixes" it because, when you do this, if forces the computer to repeat the connection process and renegotiate the parameters. (Presumably, because the DAC was already connected when the computer was powered on, the computer "forgot" to do the initial communication with the DAC.) Again, this is an issue with the computer's hardware or software, and may be difficult to track down or fix, so the best solution is simply to turn everything on in the sequence that reliably works correctly.
NOTE: It is VERY unlikely that reinstalling the driver would affect or eliminate these issues. However, since removing and installing drivers may cause Windows to reinstall or reconfigure other options, it is POSSIBLE that doing so may affect other areas of behavior - including this one.
NOW......
None of this has anything to do with the drivers. If the DAC is working perfectly at 44k and 48k, then the drivers are loading, and are working correctly.
The "Unsigned Driver" error message is another issue entirely.
The drivers we use were written by C-Media (who manufactures the USB interface chip we use), and were never signed "correctly" according to Microsoft standard. In the past, Windows would sometimes offer an error message about this when you installed the drivers but, if so, there was also an option to "ignore the error and install drivers". Apparently, some recent security update in Windows has changed this - and now some users get an error message - with no option to override it.
There is a solution (provided by Microsoft) - to disable "driver checking".
-------------------------
This is a common issue with Windows machines...specifically for software/hardware drivers that are improperly signed.
Here's a workaround provided by Microsoft:
In the Startup Menu, under Advanced Startup Options (including safe mode)
Find the option that says "Disable Driver Signature Enforcement" and check it (it should be the second up from the bottom).
This will disable driver signature checking for all drivers.
This is just one of a large number of "security precautions" in Windows but, after doing this, you should be extra-careful to only install programs that you trust.
--------------------------
|
|
mrhoss
Seeker Of Truth
Posts: 8
|
Post by mrhoss on Jun 20, 2014 20:11:27 GMT -5
I've tried using the XDA2 with Windows 8, windows 7 and windows xp. I've also tried using 7 different USB cables on 3 different computers. So 21 possible combos and they all yield the same result. If the XDA2 is not turned on you get 48k max sample. If you put it to sleep the same issue. What I don't get is I have 4 other USB dac/amp and they don't have this issue. They work flawless on all 3 computers with any of the usb cables. If you search google you see numerous other people having problems with usb and xda 2. The ONLY reason I use the xda2 over the 4 usb dac/amps I own is because it has dual XLR out that I need to rid my rokit 8's of distortion. When the XDA2 is working well I noticed an option under "playback devices". Not sure what this midi thing is   |
|
mrhoss
Seeker Of Truth
Posts: 8
|
Post by mrhoss on Jun 24, 2014 11:01:13 GMT -5
This might be the issue. I'm not gonna mess with firmware stuff until I know 100% its right. The XDA2 has the C-Media CM6631 chip. The C-Media CM6631A chip is the only variation that supports 32/192. So I'm assuming that is the right chip. Upon looking online I came across the bottom link. An updater to the CM6631A. hifiduino.wordpress.com/2013/10/11/c-media-cm6631a-firmware-tool/The first thing the page mentions is this "While testing a CM6631A interface, I discovered that for 44.1K/48K sample rate material, the bitclock was running at 128FS" This is completely out of my realm of knowledge but it appears that the firmware may not be configured properly ? |
|
bene
Minor Hero
Posts: 18
|
Post by bene on Jun 26, 2014 11:05:09 GMT -5
|
|
|
|
Post by dac0964 on Jun 27, 2014 14:23:17 GMT -5
2) Some computers (especially Apples) seem to have a problem when they go into hibernation. When a computer wakes up from hibernation, it should either continue to use the settings it had when it went into hibernation, or it should re-scan the current USB devices connected and get new information. For whatever reason, many Macs, and a few PCs, fail to do either. Even though they were working correctly before hibernating, they wake up with the default settings (44k and 48k only). There are quite a few things that could cause this to occur - and all of them constitute a fault in the hardware or software in the computer. They can also be prohibitively complicated to diagnose, and may not even be subject to repair. In these situations, the best solution is to set the computer to do full shutdown (disable hibernation). This is very true... I recently changed to Macbook Pro/Audirvana from Windows/JRiver cause I thought Apple would give me less of a problem since there is no need to install the USB driver. This doesn't happen always but when it does I found the only solution for it to work is by shutting down the DC-1 again then turn it back on and reboot the MacBook. Most of the time they just work!  |
|
|
|
Post by GreenKiwi on Jun 28, 2014 21:31:12 GMT -5
2) Some computers (especially Apples) seem to have a problem when they go into hibernation. When a computer wakes up from hibernation, it should either continue to use the settings it had when it went into hibernation, or it should re-scan the current USB devices connected and get new information. For whatever reason, many Macs, and a few PCs, fail to do either. Even though they were working correctly before hibernating, they wake up with the default settings (44k and 48k only). There are quite a few things that could cause this to occur - and all of them constitute a fault in the hardware or software in the computer. They can also be prohibitively complicated to diagnose, and may not even be subject to repair. In these situations, the best solution is to set the computer to do full shutdown (disable hibernation). This is very true... I recently changed to Macbook Pro/Audirvana from Windows/JRiver cause I thought Apple would give me less of a problem since there is no need to install the USB driver. This doesn't happen always but when it does I found the only solution for it to work is by shutting down the DC-1 again then turn it back on and reboot the MacBook. Most of the time they just work! Wow that's a bummer. I've never had a problem with the dc-1 and the macs. |
|
|
|
Post by dac0964 on Jul 1, 2014 16:06:48 GMT -5
This is very true... I recently changed to Macbook Pro/Audirvana from Windows/JRiver cause I thought Apple would give me less of a problem since there is no need to install the USB driver. This doesn't happen always but when it does I found the only solution for it to work is by shutting down the DC-1 again then turn it back on and reboot the MacBook. Most of the time they just work! Wow that's a bummer. I've never had a problem with the dc-1 and the macs. I know... but like I said it doesn't happen always. I probably experienced it twice since I bought the Mac mid-June. Hopefully it's just an initial glitch and never happen again. |
|
scramble45
Seeker Of Truth
Rice is what tastes real good for real, you know?
Posts: 1
|
Post by scramble45 on Jan 12, 2015 20:18:22 GMT -5
Hello, I got tired of constantly having to unplug my XDA2 from the back. This is honestly a pretty silly problem that with the right people could be solved. Anyway here is my ghetto attempt at coming up with a way to save me from having to wear-out my USB port. Hope this helps someone and I will leave it here. goo.gl/t6HACuI only tested this on x64 systems but it may work on x86 I cant remember if I compiled the binary for both. This is not digitally signed either so you may need to unblock the application in the file properties. No modifications are made to your system short of extracting and running the program in your temporary directory. What the application does. Well its quite simple... This application waits for the stupid message that complains about "This device can preform faster.. blah blah blah.." Then it disables upon your request the XDA composite device in device manager. It then waits a set time and then re-enables it. This works well if you are like me and put the XDA into standby when you goto sleep and then come back and are haunted with these problems. You simply run the app select option 1 and wait patiently, after 25 seconds or so you should be good to resume playing music at the original bit you specified in windows. I provide no warranty, and will post the script to this ghetto program if someone wants it. - This serves my purposes but I really wish emotiva would talk to someone at cmedia or just fix this silly glitch. It would seem if you decrease the amount of time that the usb component stays in device manager upon power off and then increase the amount of time it takes for it to show back up after the emotiva has fully loaded we wouldnt see this problem. Enough ranting. - I truly enjoyed wasting hours of my time on this. |
|
jt01
Seeker Of Truth
Posts: 2
|
Post by jt01 on Jan 27, 2015 0:38:26 GMT -5
The link for the USB fix in the message from scramble45 above has been disabled - how about fixing or replacing it? Thank you.
As of 2/1/2015, the link appears to be back - thanks to all involved.
|
|
