Click to view our Accessibility Statement or contact us with accessibility-related questions
Anonymouse
216
Dec 15, 2013
I picked up one of these in the last drop. I'd like to point out that there's an issue with the Yulong ASIO driver and JRiver Media Centre that makes playback a hassle (it keeps ceasing to work until you burrow into the options and open and shut the ASIO driver's control panel). Apparently the Yulong driver under some circumstances isn't responding correctly to some of the format support checks JRiver does, and playback fails as a result. Despite the fact that the Yulong driver doesn't actually _have_ a control panel, clicking the button in JRiver that attempts to open one does some strange digital voodoo that restores functionality, at least until it decides to fail again, which it does most of the time you manually stop or skip any track. :/
Yulong do not seem very interested in fixing it, either, by which I mean they basically told another customer affected by the issue to just deal with it:
http://yabb.jriver.com/interact/index.php?topic=84743.msg586223#msg586223
Their suggestion to use WASAPI instead is kind of a big "fuck you", too, as ASIO is the only option that will let you play both PCM and DSD content natively from a library without having to manually change options every time you want to switch between the formats, or converting one on the fly to the other and making it no-longer bit-perfect. If I was going to transcode my SACDs into PCM as I listen, I wouldn't have bought a US$1300 DAC. I bought this one, because it's supposed to support ASIO and let me pump out anything I want in native format. If your whole library is PCM, you can use WASAPI and not miss out on anything, but if you want to use this to play back both, you might want to drop Yulong a line and ask them why they think playback constantly stopping working is acceptable behaviour for a supposedly high end Hi-Fi component...
https://www.facebook.com/pages/Yulong-Audio/326982077398065
nelson
5275
Dec 15, 2013
AnonymouseInteresting, I will forward the entire thread to Yulong himself. Hopefully that will help escalate the problem so they will allocate proportionally more resources into this.
Feel free to forward me any additional supplementary information at nelson.wu@massdrop.com.
nelson
5275
Dec 18, 2013
AnonymouseHey @Anonymouse
Talked to Yulong yesterday, and he suggests to try the new driver for DA8 and see if the problem persists. In the meantime, he's going to have their engineers look into the problem described in the thread. Hopefully we can find a solution to resolve this problem.
DanielC
2
Dec 18, 2013
nelsonAny chance of opening this massdrop for the remaining 2 days that were originally scheduled?
Anonymouse
216
Dec 19, 2013
nelsonThe driver I'm using I downloaded on October 29th. I just checked and there's no notice of any updated driver (or any version number at all, really), just the same download link I saw almost two months ago. I downloaded it again anyway, on the off-chance it had been changed without notification, but the file I downloaded was the same size and same MD5 hash as the one I already have. I'm using the "latest" and only driver available. :c
nelson
5275
Dec 19, 2013
AnonymouseI got it.
I'll be sure to let Yulong know about this. They also want me to let you know that they are on it :)
I'll update here if I get any news from Yulong.
Anonymouse
216
Dec 21, 2013
nelsonOne of the JRiver developers has offered to assist Yulong with sorting out the issue, if Yulong want to contact them at "matt at jriver dot com":
http://yabb.jriver.com/interact/index.php?topic=84743.msg579111#msg579111 "I can't see how to work around this cleanly.
We only set the format if the device returns success from kAsioGetIoFormat and the format it returns doesn't match the format we're trying to play.
In this case, it must return kASIODSDFormat and we're trying to play kASIOPCMFormat.
When we call kAsioSetIoFormat with kASIOPCMFormat, it seems to fail.
Could you write to Yulong? Send them a link to this thread, and feel free to share my contact information (matt at jriver [dot] com) -- we'll do whatever we can to help.
Thanks."
Although I should note that it was directly after this that the other user with the same issue did in fact email Yulong as requested, but only got the WASAPI advice as a result; no statement that they'd look into it, or even acknowledgement that it was a problem. :c
Just recently the same dev restated his offer to work with Yulong to resolve this, and linked back to the above post. I guess Yulong don't wany any help? :\
http://yabb.jriver.com/interact/index.php?topic=84743.msg589005#msg589005 "I haven't heard anything from Yulong.
Like I said above, I'm happy to help if they ask: http://yabb.jriver.com/interact/index.php?topic=84743.msg579111#msg579111"
PRODUCTS YOU MAY LIKE
Trending Posts in Audiophile