What would be a good portable Dac/Amp to use with my HD6xx and Sony Xperia 1 V cell phone?
I am new to this hobby. I purchased a HD6XX and plan to use it with my Sony Xperia 1 V cell phone, that has a 3.5mm jack. I was wondering if I needed a portable dac/amp or just a portable amp and if so what would one recommend? Any assistance one could provide, would be greatly appreciated. Kind regards, Haz
Mar 7, 2024
Aside from not putting out updated / supported drivers they do say " Supported OS: Windows 7, 8, Vista, XP; Mac OS X: iOS; Android with OTG " which has no mention of Windows 10. If you read the specs and do a little research you'll realize the best possible output with real HD files (24 bit and 192000 Hz and above) is to use USB so lets hope xDuoo gets with the times.
On a side note I did initially have an issue with the USB port having a short but Massdrop support took care of me for that without issue. It did take a month to get the replacement though but massdrop support was great.
Massdrop have you been in touch with xDuoo on this issue? Thanks.
The initial package (XMOS-USB-Drive-V3.0.0.exe) is absolutely broken, but it's just a self-extracting archive. I opened it in 7-zip and removed the driver itself (XMOS_EVAL_KITS_DriverSetup_v3.34.0.exe, as described in the accompanying documentation) and it installed fine, without error, and without having to disable signed driver enforcement. I'm listening to music right now through foobar2000 and the xDuoo X-5 on Windows 10 1703. This was from the package on the accompanying cd.
Can you guys give that approach a try and see if it works for you?
F.Y.I. Still no word from their support. I've sent multiple emails to them and haven't received a response.
<shrug>
I have no idea why it would work for me and not for others, but I'd be happy to provide any additional details if you can tell me what you want to see.
I'll also, just to duplicate my test, install it on my wife's machine. Will do that tonight after work and post back. I'm interested to figure out why it didn't complain on my main machine.
I verified that my machine (Windows 10 64-bit Home, 1703) has driver signature enforcement on (via registry). I uninstalled and reinstalled the driver, no complaints.
I did the same exercise on my wife's machine (Windows 10 32-bit Pro) which also has driver signature enforcement turned on (verified via registry). Hers was a Windows 7 machine upgraded to Windows 10. Same thing, installed, never complained about signature. Both machines, when looking at the driver in the device manager, show what appear to be valid signatures from "Thesycon Software Solutions" blah blah blah.
So, maybe my machines are both broken and the registry is being ignored for signature enforcement? <shrug>
Let me know if I can be of any help. Sucks so many people are having problems.
Guess I can try removing them from the machine completely by using the Windows way point feature. What is it called, the feature where Windows saves the current system files before an install. Then perhaps try installing differently. Plug in the XD-05 and when Windows prompts about needing a driver and using the I have the files option. It'd be doing the same thing as just installing first but perhaps the slightly different methodology might make a difference. I'll report back as soon as I try. It may be a few days, I'm not the healthiest person right now.
He found another driver package on the Japanese xduoo site that worked for him - might help you out.
To test it I found an older laptop that didn't have that feature in the BIOS and had Windows 10 (1703) installed (luckily I have access to a lot of laptops at work). I installed the xDuoo XD-05 drivers and it worked fine. Somehow that setting is stepping on the XD-05 drivers.
I'm not at the house right now, but will be later tonight. I'd be more than happy to check my BIOS just for the data point and report back. I'd really like to know definitively why some people have no problems while others are plagued.
So, I confirmed my machine has Secure Boot disabled (via powershell). I had no idea, and was kinda pissed. But, when researching how to even enable it on my machine (because there isn't an option in my BIOS that actually says "Secure Boot"), it looks like my particular mainboard has a problem with that feature. So, maybe I am just lucky all around that it was left off by the OEM.
If it were something easy to turn on and test, I would do it, but I fear corrupting my bios (as others report).
I have to say I'm very concerned and disappointed in Massdrop's silence on this. They are usually responsive and work to assure they are delivering a quality product but in this case... not so much.
Its as Limbo says. Xduoo is completely responsible whether the driver gets updated for Windows 10 or not. I'll argue that Windows 10 has been out long enough now that any product that wants to claim its "Windows" compatible must be compatible with Windows 10 and saying in either small or large print only up to Windows 8 just doesn't work.