Print

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

[Maltsters]

I notice that when I try to play a DoP 2.8MHz 2ch track on MC 23.0.84 64-bit, the playback fails and it reports the track as being 352.8KHz 64-bit instead. Switching to the 32-bit MC 23.0.84, the track plays fine and is recognised as DoP 2.8Mhz. Any idea if this will be fixed soon, or do I need to switch back to 32-bit version?

By the way, switching between 32 and 64-bit to bug report is killing the number of installs I am allowed!

[ferday]

You don't have to uninstall them, you can run both versions while testing

[Hendrik]

What kind of file are you playing? dsf? dff?

[Maltsters]

Its a .dff, Blue Coast Collection, The Dog Song - DSDIFF.dff. Plays fine in 32 bit version.

I didnt realise I could have both version installed, the 64 bit instructions said the 32 bit should be uninstalled.

If I can have both on the same machine, that would make it a lot easier!

Kind regards

Ian

[JimH]

Could be a driver problem.  You need a 64 bit version of the driver (if any) for the 64 bit version of JRiver.

[Awesome Donkey]

Are you using ASIO or WASAPI? What's your DAC?

[Maltsters]

Thanks JimH for the thought. I did wonder that and so put the 64-bit version on another machine and went through most of its drivers (including direct sound) which appears to be a native windows 64 bit driver. I always get the same message on any installation of 64 bit JRiver (now tried 3) with any driver and never get it on any 32 bit version (have tried 2 installations) and even switch to drivers that I know wont support the stream to see if the error message changes. In each case if the 32 bit version cannot play on the driver, it still correctly identifies the source material.

JRiver 64 bit is stating that it is trying to play it as 352.8kHz 64-bit 2 ch which is completely the wrong format for DoP (DSD 2.8 Mhz bit stream).

I also note, in case it is relevant, that I have tried playing high res upto 176 kHz 24 bit on JRiver 64 and that works fine (as does 44.1/16) with the drivers installed. For music I tend to use a dCS Vivaldi DAC using the dCS WASAPI driver but as mentioned above, I have tried other setups.

I have pinged a query to dCS regarding their drivers being 32 or 64 bit. I will let you know of the outcome when I get it.

Kind regards

Ian

[RD James]

You need to either set rules for 352.8kHz audio in DSP Studio's Output Format section, or enable bitstreaming if you have a DSD-capable DAC in Options > Audio > Settings > Bitstreaming
 
I would recommend selecting a format that your DAC will accept in DSP Studio, since bitstreaming does not allow any DSP to be applied - including things like Volume Leveling - but some people prefer to use bitstreaming.

[dtc]

2.8 MHz DSD should convert to 176 KHz DoP, not 352 KHz DoP.  Seeing a 352 KHz error message for a 2.8 MHz DoP is very strange. Can you confirm that on the 32 bit MC, the DoP is 176 KHz. You can see that in Audio Path. 

Make sure that there is no output conversion for 176 KHz in Output format or other changes being made in DSP Studio. Any DSP changes will wreck the DoP formating. Bitstreaming should be set to on for DSD.

[Maltsters]

Many thanks for your suggestions which got me there in the end!

My fault entirely, when installed the x64 version and restored the library, I think I installed it from my other JRiver machine which does not have a DSD compatible DAC connected and so Bitstreaming was not set!

I have updated this setting on the x64 version and it plays fine now. I checked the previous x86 version and bitstreaming was of course set! My take away is to be clearer on what i call the library backups!

dtc: It was definitely reporting the 352 kHz error on both 32 and 64 bit versions and there were no output conversions set either.

Thanks again for your support!

Kind regards

Ian

[dtc]

Glad it is working.

If the track is 2.8 MHz, then the DoP should be 176 KHz. If the DoP is actually 352Kh, then the file is probably 5.6 Mhz.

[RD James]

If the track is 2.8 MHz, then the DoP should be 176 KHz. If the DoP is actually 352Kh, then the file is probably 5.6 Mhz.

JRiver decodes DSD to 352.8kHz PCM.

[kr4]

JRiver decodes DSD to 352.8kHz PCM.

But DOP does not DSD-PCM conversion.

[dtc]

JRiver decodes DSD to 352.8kHz PCM.

When converting DSD to PCM MC converts to 1/8th of the original sample rate. 1xDSD (2.8MHz) converts to 352 KHz, 2x goes to 705 KHz, etc.

DoP does not convert to PCM, it simply uses the PCM file format.  It packs the 0s and 1s in 16 of the 24 bits of a sample and then those are unpacked back to DSD by the DAC. The DoP format is 1/16th of the original sample rate, corresponding to the 16 bits. So, 1xDSD goes to 176 KHz DoP, 2xDSD goes to 352 KHz and so on.

For a 2.8 MHz DSD, a DoP representation is 176 KHz and a conversion to PCM by MC is 352 KHz.
 
If the DoP is 352 KHz, then the original must be 2xDSD (5.6 MHz).

Audio path will display what MC is doing - either packing into DoP or converting to PCM - and display the final sample rate.


For reference, DoP uses the 8 most significant bits of a 24 bit sample as a special code to identify that the is a DoP format, and it uses the other 16 bits for the 0s and 1s of the DSD file. The DAC sees the 8 MSBs and knows it is  DoP and unpacks the other 16 bits into a DSD stream.  The 8 MSBs were chosen to produce a low level white noise, in case the DAC does not recognizes the DoP marker. This avoids overly loud sound if the DAC does not recognize the DoP signal.