Sonicorbiter - Native DSD support

[pas]

Thank you, I appreciate the support.

 

Maybe. I'll look into it.

[pas]

Maybe. I'll look into it.

FYI - SMSL M8

XMOS xCORE USB Audio 2.0 at usb-ci_hdrc.1-1.1, high speed : USB Audio

 

Playback:

Status: Running

Interface = 1

Altset = 1

Packet Size = 392

Momentary freq = 352798 Hz (0x2c.1988)

Feedback Format = 16.16

Interface 1

Altset 1

Format: S32_LE

Channels: 2

Endpoint: 1 OUT (ASYNC)

Rates: 44100, 48000, 88200, 96000, 176400, 192000, 352800, 384000

Data packet interval: 125 us

Interface 1

Altset 2

Format: S24_3LE

Channels: 2

Endpoint: 1 OUT (ASYNC)

Rates: 44100, 48000, 88200, 96000, 176400, 192000, 352800, 384000

Data packet interval: 125 us

Interface 1

Altset 3

Format: SPECIAL DSD_U32_BE

Channels: 2

Endpoint: 1 OUT (ASYNC)

Rates: 44100, 48000, 88200, 96000, 176400, 192000, 352800, 384000

Data packet interval: 125 us

 

Capture:

Status: Stop

Interface 2

Altset 1

Format: S32_LE

Channels: 2

Endpoint: 2 IN (ASYNC)

Rates: 44100, 48000, 88200, 96000, 176400, 192000, 352800, 384000

Data packet interval: 125 usaccess: RW_INTERLEAVED

format: S32_LE

subformat: STD

channels: 2

rate: 352800 (352800/1)

period_size: 32768

buffer_size: 131072Simple mixer control 'Analogue 1',0

Capabilities: pvolume cvolume pswitch cswitch

Playback channels: Front Left - Front Right

Capture channels: Front Left - Front Right

Limits: Playback 0 - 127 Capture 0 - 127

Front Left: Playback 127 [100%] [0.00dB] [on] Capture 127 [100%] [0.00dB] [off]

Front Right: Playback 127 [100%] [0.00dB] [on] Capture 127 [100%] [0.00dB] [off]

Simple mixer control 'Analogue 1',1

Capabilities: pvolume pvolume-joined cvolume cvolume-joined pswitch pswitch-joined cswitch cswitch-joined

Playback channels: Mono

Capture channels: Mono

Limits: Playback 0 - 127 Capture 0 - 127

Mono: Playback 127 [100%] [0.00dB] [on] Capture 127 [100%] [0.00dB] [off]

[JohnDonaldson]

Jesus, any thoughts on whether this [PATCH] ALSA: usb-audio: Eliminate noise at the start of DSD playback. — ALSA Devel is the solution to popping in native DSD?

[vortecjr]

What device is that?

[vortecjr]

Jesus, any thoughts on whether this [PATCH] ALSA: usb-audio: Eliminate noise at the start of DSD playback. — ALSA Devel is the solution to popping in native DSD?

 

There are a lot of unknowns regarding it.

[pas]

I am not sure if you are referring to my post. I was just informing you that the SMSL M8 will play native DSD 128 through the microRendu, if you wanted to add it to your list. Thanks, Paul

[vortecjr]

I am not sure if you are referring to my post. I was just informing you that the SMSL M8 will play native DSD 128 through the microRendu, if you wanted to add it to your list. Thanks, Paul

 

I was and that looks like DoP:)

[pas]

I was and that looks like DoP:)

If I have the enable direct DSD support checked in the MPD/DLNA renderer settings, it will still play DoP?

[ted_b]

I am not sure if you are referring to my post. I was just informing you that the SMSL M8 will play native DSD 128 through the microRendu, if you wanted to add it to your list. Thanks, Paul

 

Pas, I think you are looking at this list incorrectly. This is a list of approved/coded dacs and DDCs that have the correct code in SonicORbiter's OS to allow the microRendu to identify them and allow native (not DoP) DSD to be played back. Lots of times this improves playback because although DoP is not a bad venhicle for DSD it often cannot allow the highest DSD rates through (since it relies on a supported PCM rate to carry it). So things like DSD512 are currently impossible for DoP to carry, and often even DSD256 is difficult under DoP.

 

But now that Jesus has your dac description and diagnosis, he can put a request into the Linux guys to support the dac. No promises. Also, let it be known that even if the device is approved, the process of adding the code to the SonicOrbiter stack is a bi-monthly thing at best, sometimes longer.

[pas]

Pas, I think you are looking at this list incorrectly. This is a list of approved/coded dacs and DDCs that have the correct code in SonicORbiter's OS to allow the microRendu to identify them and allow native (not DoP) DSD to be played back. Lots of times this improves playback because although DoP is not a bad venhicle for DSD it often cannot allow the highest DSD rates through (since it relies on a supported PCM rate to carry it). So things like DSD512 are currently impossible for DoP to carry, and often even DSD256 is difficult under DoP.

 

Ted - Thank you for the explanation. If capable, the diagnostics would contain the 2.8, 5.6, 11.2 and so on rates? The SMSL M8 displays DoP or DSD on the readout. Paul

[JohnDonaldson]

There are a lot of unknowns regarding it.

 

I am curious, what needs to happen with this patch to ALSA for microRendu to use it and where are we in this process?

[Confused]

I had reported elsewhere about an issue I have had trying to run native DSD via a microRendu to a Mutec MC3+USB. Post #1075 per the link below:

 

http://www.computeraudiophile.com/f6-dac-digital-analog-conversion/mutec-mc-3-a-17300/index43.html

 

Thanks to some input from Roon's Brian Luczkiewicz, this issue is now clear, the reason it does not work is a lack of a Linux patch for native DSD being available for the Mutec MCS+USB.

OK, the issue is clear, but is this ever likely to be resolved? In fact, I am not totally clear if this is an mR issue to solve, something for Mutec to look at, or one maybe for the 'Linux community'

[vortecjr]

FYI - SMSL M8

XMOS xCORE USB Audio 2.0 at usb-ci_hdrc.1-1.1, high speed : USB Audio

 

I need some more information. In App / DAC Diagnostics I need the information next to "DAC description". Please post it here.

[vortecjr]

I had reported elsewhere about an issue I have had trying to run native DSD via a microRendu to a Mutec MC3+USB. Post #1075 per the link below:

 

http://www.computeraudiophile.com/f6-dac-digital-analog-conversion/mutec-mc-3-a-17300/index43.html

 

Thanks to some input from Roon's Brian Luczkiewicz, this issue is now clear, the reason it does not work is a lack of a Linux patch for native DSD being available for the Mutec MCS+USB.

OK, the issue is clear, but is this ever likely to be resolved? In fact, I am not totally clear if this is an mR issue to solve, something for Mutec to look at, or one maybe for the 'Linux community'

 

Post the information from App / DAC Diagnostics.

[Confused]

Post the information from App / DAC Diagnostics.

As follows, with 'native DSD' selected, then when successfully running DoP128:

 

[vortecjr]

As follows, with 'native DSD' selected, then when successfully running DoP128:

 

That looks good...Ill get this going. It's going to be a while though. You need too select DoP for now and not native.

[pas]

I need some more information. In App / DAC Diagnostics I need the information next to "DAC description". Please post it here.

DAC description: xCORE USB Audio 2.0 20b1:000a

[pas]

Maybe. I'll look into it.

Jesus, Here is the DAC description for the Sound Magic Serenade Pro. Once again, thanks for the support. Paul

DAC description: Serenade DSD 22e1:ca01

[vortecjr]

DAC description: xCORE USB Audio 2.0 20b1:000a

 

Is this the SMSL M8?

[pas]

Is this the SMSL M8?

 

Yes it is. Thanks

[artyom_k]

Hello,

first of all, thank you for your microRendu, its sound is great in my system!

Now I`d like to find out if Cary Audio dac 200ts is support native DSD through microRendu

 

(playback DSD64)

 

DAC description: xCORE USB Audio 2.0 20b1:000a

Diagnostic information for this DAC

XMOS xCORE USB Audio 2.0 at usb-ci_hdrc.1-1.1, high speed : USB Audio

 

Playback:

Status: Running

Interface = 1

Altset = 3

Packet Size = 118

Momentary freq = 88197 Hz (0xb.0650)

Feedback Format = 16.16

Interface 1

Altset 1

Format: S32_LE

Channels: 2

Endpoint: 1 OUT (ASYNC)

Rates: 44100, 48000, 88200, 96000, 176400, 192000, 352800, 384000

Data packet interval: 125 us

Interface 1

Altset 2

Format: S16_LE

Channels: 2

Endpoint: 1 OUT (ASYNC)

Rates: 44100, 48000, 88200, 96000, 176400, 192000, 352800, 384000

Data packet interval: 125 us

Interface 1

Altset 3

Format: SPECIAL DSD_U32_BE

Channels: 2

Endpoint: 1 OUT (ASYNC)

Rates: 44100, 48000, 88200, 96000, 176400, 192000, 352800, 384000

Data packet interval: 125 us

 

 

 

access: RW_INTERLEAVED

format: DSD_U32_BE

subformat: STD

channels: 2

rate: 88200 (88200/1)

period_size: 11025

buffer_size: 44100

 

 

 

Simple mixer control 'iAP Interface',0

Capabilities: pvolume pswitch

Playback channels: Front Left - Front Right

Limits: Playback 0 - 127

Mono:

Front Left: Playback 127 [100%] [0.00dB] [on]

Front Right: Playback 127 [100%] [0.00dB] [on]

Simple mixer control 'iAP Interface',1

Capabilities: pvolume pvolume-joined pswitch pswitch-joined

Playback channels: Mono

Limits: Playback 0 - 127

Mono: Playback 127 [100%] [0.00dB] [on]

[vortecjr]

Hello,

first of all, thank you for your microRendu, its sound is great in my system!

Now I`d like to find out if Cary Audio dac 200ts is support native DSD through microRendu

 

That looks like native DSD. The reason it works is because they are using USB IDs that are supported by another device.

[Confused]

That looks good...Ill get this going. It's going to be a while though. You need too select DoP for now and not native.

This was regarding the Linux patch issue for native DSD from mR to Mutec. Is it possible to get a very approximate idea of how long this might take. To be clear, I am not pushing for this to be prioritised and make no claim it is at all urgent. It's just I have no idea of the possible order of magnitude of difficulty here? That is are we potentially looking at days, weeks, a few months? Any ideas?

[vortecjr]

This was regarding the Linux patch issue for native DSD from mR to Mutec. Is it possible to get a very approximate idea of how long this might take. To be clear, I am not pushing for this to be prioritised and make no claim it is at all urgent. It's just I have no idea of the possible order of magnitude of difficulty here? That is are we potentially looking at days, weeks, a few months? Any ideas?

 

There is no set schedule for this and it just depends on everything that is going on behind the scenes.

[Confused]

There is no set schedule for this and it just depends on everything that is going on behind the scenes.

 

Yes, that is perfectly understandable, I was certainly not expecting any kind of schedule update. The thing is, I have absolutely no idea if this is something that might take weeks, months, years or whatever. I simply have no feel for this kind of stuff!