Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[elderavelas]

MC does not play PCM using Yulong DA8 ASIO driver, however it plays DSD64 and DSD128.

MC shows this error message:

"(?) Something went wrong with playback.

Details:
Playback could not be started on the output 'ASIO' using the format "44,1KHz 16bit 2ch'.

This output format may not be supported by your hardware. You can use DSP Studio to change the output to a compatible format.
Also, make sure that your system has a valid sound playback device and that it is properly configured in playback options."

This happens with MC18 and MC19. Foobar2000 and Korg AudioGate can play using the same driver.

Sometimes I get to play PCM using ASIO, just after a MC update. I noticed this because I always try it after upgrading to a new version.
It plays normally the first time and keep playing if I do not hit the stop button. I can even change tracks but after stopping playing it will never play again.

Thanks.

[Matt]

Could you use Help > Logging to capture a log of playback failing?  Then mail it to logs (at) jriver [dot] com and include a link to this thread.

Thanks.

[elderavelas]

Hello Matt,

I've captured the log and emailed it to the address you indicated.

I also had the same problem in a different computer running Windows 8 and Windows 7 (dual boot).
The Windows 7 partition had a freshly installed MC.

If you need anything else to helping you to debbug this issue, let me know.


Thanks and regards,

Elder

[Matt]

I see this in the log:
0227402: 6032: Playback: CASIOPlugin::Open: kAsioSetIoFormat failed on format 0
0227402: 6032: Playback: CASIOPlugin::Open: Format not supported

I think the driver probably rejects setting the format to PCM.  I would call this a driver bug (they should return not implemented if they don't honor this call).

It would be good to bring this to the attention of the driver maker.

We might be able to work around it on our side as well.  I'll have to look at the code.

[elderavelas]

It may be a driver bug, indeed. I wonder why other players have no problems with it?
Does MC perform more checks than other players to assure that the DAC can handle the audio format to be played?

[elderavelas]

I got to play some PCM files through Yulong ASIO output. I was playing with the "device settings...".
Changing something there make the trick. Is is not always the same changes that work. I change something then try. If the file does not play, I try changing something else until I get to play. I sent a new log with MC playing PCM files using the ASIO output until the problems happen again.

Thanks and regards.

[elderavelas]

I found out that going to "device settings..." and trying to open the driver control panel (the drive does not have it) makes MC playing PCM on the ASIO output.
Again, stopping or playing DSD causes the problem on the next PCM playback.

[Matt]

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.

[elderavelas]

Hello Matt,

MC plays PCM using ASIO output with no problems in my notebook.
I've emailed you the logs.

It is curious. The notebook is fine, two different desktops have the same problem.

I will email Yulong to report this problem.

Thanks,

Elder

[elderavelas]

Hi Matt,

I reported this issue to Yulong. He just recommended using WASAPI. He said that WASAPI is better than ASIO for Windows 7 and above.
It looks like they will not do anything to fix their driver.
I appreciate your good will in trying to resolve this problem but I believe there is nothing else you can do if the issue is in the driver.
Thanks.

[Amleth]

I reported this issue to Yulong. He just recommended using WASAPI. He said that WASAPI is better than ASIO for Windows 7 and above.
It looks like they will not do anything to fix their driver.
I appreciate your good will in trying to resolve this problem but I believe there is nothing else you can do if the issue is in the driver.
Thanks.

Just found this thread, and I'm having exactly the same issues with my Yulong DA8 and new JRiver license. Thanks to your observation that attempting to open the Yulong ASIO driver control panel in JRiver that somehow magically makes it work, I'm now able to get it to play ASIO PCM when I want to without the random arcane rituals of changing every setting in reach back and forth repeatedly until it works, which is a big improvement on sacrificing a rooster or two, but still not really ideal.

But still, based on that observation, it strikes me that there IS something that can be done on the JRiver end, especially since they seem willing to help, while apparently Yulong don't care whether their customers can actually use their products, as long as they've bought them. (And despite the DA8 costing about 30 times what JRiver does, too...)

If trying to open the (non-existant) driver panel somehow clears whatever is making the driver refuse to set PCM mode, in a situation where JRiver wants to play PCM but the Yulong driver responded to kAsioGetIoFormat with kASIODSDFormat, indicating it will fail if a change to PCM is attempted before trying to open the panel, can't JRiver send the call that attempts to launch the dialog (and also clear said dialog), then play? Basically, have the software do the dance we're doing manually through the UI every time we want to get PCM working again after playing native DSD content?

(Also, it might be a good idea to add the word "JRiver" to the forum spellcheck custom dictionary so it stops underlining it as a mistake when typing posts?)

[elderavelas]

Just found this thread, and I'm having exactly the same issues with my Yulong DA8 and new JRiver license. Thanks to your observation that attempting to open the Yulong ASIO driver control panel in JRiver that somehow magically makes it work, I'm now able to get it to play ASIO PCM when I want to without the random arcane rituals of changing every setting in reach back and forth repeatedly until it works, which is a big improvement on sacrificing a rooster or two, but still not really ideal.

But still, based on that observation, it strikes me that there IS something that can be done on the JRiver end, especially since they seem willing to help, while apparently Yulong don't care whether their customers can actually use their products, as long as they've bought them. (And despite the DA8 costing about 30 times what JRiver does, too...)

If trying to open the (non-existant) driver panel somehow clears whatever is making the driver refuse to set PCM mode, in a situation where JRiver wants to play PCM but the Yulong driver responded to kAsioGetIoFormat with kASIODSDFormat, indicating it will fail if a change to PCM is attempted before trying to open the panel, can't JRiver send the call that attempts to launch the dialog (and also clear said dialog), then play? Basically, have the software do the dance we're doing manually through the UI every time we want to get PCM working again after playing native DSD content?

(Also, it might be a good idea to add the word "JRiver" to the forum spellcheck custom dictionary so it stops underlining it as a mistake when typing posts?)

The fact that other players seem to have no problems playing through Youlong ASIO driver puzzles me. May be other players do not take so many precautions as JRiver does to be sure that the DAC will replay the audio stream correctly.

There is something else. With my notebook JRiver MC can play using the DA8's ASIO driver. Maybe this is due to the slower processor.

Anyway, it looks like the DA8's ASIO driver is not well implemented. When we get it playing, switching from DSD to PCM causes some pops. Also switching from DSD DoP to native ASIO DSD causes a high pitch tone on the left channel. I have to top and start playing again to stop it.

Using WASAPI seems to be better. I noticed no improvement using ASIO and WASAPI replay is flawless.
Using ASIO is only required when playing DSD 256 and 512. I tried these two using the foobar ASIO proxy's upsampling feature. The result was not good. There were some noises and distortions. My DA8 has a fault in the DSD switch (according with Yulong) causing some noises while playing DSD on hot days when the DAC gets hotter (no matter what driver is being used). I was advised to return it for replacement. May be the pops and the high pitch tone that I mentioned before are related to this fault, however they only happens with ASIO. I'll try again when it is back.

[Amleth]

Yulong told a distributor that they'd look into it, but it sounded pretty vague. See "Discussion" from page 3 onwards:
https://www.massdrop.com/buy/yulong-sabre?s=Yulong

Let's see if anything comes from it. <crosses fingers>

It's a pretty darn annoying issue. It doesn't prevent you using the product, but it does make you continuously jump through hoops just to do so. :c

[Matt]

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

[Esprit]

I've received this mail after I've sent the link of this discussion to Yulong:

"Thank you, please try new driver 1.057 and asio updated available:
 
http://yulongaudio.com/Files/others/JR%20iver%20New%20asio.zip
 
the setup is a full one, it installs automatically 32bit or 64bit version and ASIO support too.
It can require to remove from the control panel a previous Asio installed.
I think it can solve the problem depicted on the forum.
Merry Christmas"

[elderavelas]

I've received this mail after I've sent the link of this discussion to Yulong:

"Thank you, please try new driver 1.057 and asio updated available:
 
http://yulongaudio.com/Files/others/JR%20iver%20New%20asio.zip
 
the setup is a full one, it installs automatically 32bit or 64bit version and ASIO support too.
It can require to remove from the control panel a previous Asio installed.
I think it can solve the problem depicted on the forum.
Merry Christmas"

I installed this new ASIO driver and now PCM works fine.

Esprit, thank you for the help.

Matt, if you want me to provide a log with the new driver, just let me know.

Happy Holidays!

Cheers.