Print

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

[kr4]

This is a long recurring problem.  Sometimes when reconfiguring an output zone or adding a new one, I get an error message at playback of a DSD file saying that the device does not support DoP.  This happens even though (1) I never elect DoP and (2) the device is fully capable of Native DSD processing.
Somehow, this is resolved with some machinations that seem not to ever say anything about DoP.

[thecrow]

My guesses would be:

If the device is connected directly to the MC computer, Tools>Options>Audio>Audio Device>Device Settings>DSD Bitstream in DoP format

Or if you are sending via DLNA, Tools>Options>Media Network>Add or Configure DLNA Server>"Select the server">Advanced>UNTICK Bitsteam DSD

The last one seems counter intuitive but the tick box only applies to DoP format  not native DSD

[JimH]

Also possible the device is capable of DSD but not DSD 2x, 4x, etc.

[kr4]

If the device is connected directly to the MC computer, Tools>Options>Audio>Audio Device>Device Settings>DSD Bitstream in DoP format
Or if you are sending via DLNA, Tools>Options>Media Network>Add or Configure DLNA Server>"Select the server">Advanced>UNTICK Bitsteam DSD

Neither of those options appear.

Also possible the device is capable of DSD but not DSD 2x, 4x, etc.

I am sending DSD64 and the device is capable of DSD128.  Nonetheless, I do not wish to use nor have I done anything to select DoP.

[DJLegba]

Isn't it sufficient to set Bitstreaming to Yes (DSD)?

[kr4]

Isn't it sufficient to set Bitstreaming to Yes (DSD)?

I thought it would be.  If I do not set Bitstreaming to Yes (DSD), I get PCM.  If I do, I get the DoP error message.

[DJLegba]

I thought it would be.  If I do not set Bitstreaming to Yes (DSD), I get PCM.  If I do, I get the DoP error message.

When I experimented with that Listening Test feature MC sent some very compressed mp3 files to my DAC, which didn't like them. So MC asked if it should adjust the output format and I agreed. It proceeded to change EVERYTHING to 44,100 Hz and that stopped DSD from working. I reset all the output formats and then never tried the Listening Test again. Maybe something you've played has caused MC to reset the output format for high sample rates.

[kr4]

Maybe something you've played has caused MC to reset the output format for high sample rates.

I have a policy of not ever allowing MC to change settings by itself.  One loses awareness and control.

[JimH]

I have a policy of not ever allowing MC to change settings by itself.  One loses awareness and control.

Personally, I don't trust computers.

[kr4]

Personally, I don't trust computers.

I don't trust my government but I do have to deal with it.

[kr4]

Aha!  I think this may be the issue (from another thread):

On Windows if you're using WASAPI for audio output, it's limited to DoP only. As mentioned before, native DSD on Windows requires an ASIO driver provided by your DAC's manufacturer and set as the audio output in MC's audio options.

I am using an Arvus H2-4D Renderer via HDMI with WASAPI (there is no provided ASIO driver).  Will try ASIO4ALL or equivalent.  Other suggestions welcome.

[dtc]

Native DSD is actually sent as 32 bits packed into a PCM stream.  As I understand it, neither WASAPI nor HDMI support that particular format. ASIO drivers have been designed to handle that unusual format.

ASIO4ALL is just a wrapper for kernal streaming so it probably does not support native DSD either.

[kr4]

Native DSD is actually sent as 32 bits packed into a PCM stream.  As I understand it, neither WASAPI nor HDMI support that particular format. ASIO drivers have been designed to handle that unusual format.

Then how does an SACD player do it over HDMI?

[dtc]

Then how does an SACD player do it over HDMI?

SACD players actually send the native bit rate as per the HDMI spec. Windows does not do that. The HDMI interfaces on PCs are provided by video companies who never saw fit to implement those sample rates even though they are in the HDMI spec. So, a workaround for companies who want to support DSD audio was to pack the DSD into a 32 bit format and modify the easily available ASIO driver to support that format.  If the video companies would support the native bit rates, then ASIO would not be needed, but there is no motivation for video companies to support a format that is audio only.

[kr4]

Thanks for the explanation.  Saves me a lot of effort.

[eve]

Aha!  I think this may be the issue (from another thread):I am using an Arvus H2-4D Renderer via HDMI with WASAPI (there is no provided ASIO driver).  Will try ASIO4ALL or equivalent.  Other suggestions welcome.

Damn. Very nice.
How do you like the Arvus Kal?