getmusicbee.com
Support => Bug Reports => Topic started by: HeavyFede on January 02, 2020, 03:43:50 PM
-
Hi, first of all I want to thank the developer to provide a so usefull and well made FREE software, said that I noticed the following issues:
1) The <bit depth> and <sample rate> tags stopped to work for my .dsf files (DSD), more precisely bit depth is completely missing while sample rate is 88.2 kHz while it should be 2.8 MHz, but the stangest thing is that for older albums the info is correct (1 bit / 2.8 MHz) while for newly added albums is wrong (missing / 88.2 kHz) so now in the library I have a mix of the two.
As another proof of the strange behaviour if I remove an album and then re-add it gets wrong attributes.
2) The HDCD doesn't work, I noticed that when I enable it and then playback an album there is no information showed in the footer so I don't know if it is working or not. Moreover if I exit the program and reopen the EQ panel HDCD.dll has no tick, each time I close the program it loses the selection.
Here some screenshots:
(https://i.imgur.com/URfnc1a.jpg)
(https://i.imgur.com/UoHNzYr.jpg)
The current version of MusicBee I'm using is 3.3.7261 Portable
I thank you in advance for any usefull answer.
-
Does anything change after you try Tools->Advanced->Rescan All Files?
-
Hi sveakul, thank you for your answer, I followed your suggestion and now all DSD are 88.2 kHz (should be 2.8 MHz) and bit depth missing (should be 1 bit), I really can't figure out what happened and why all DSD files show wrong properties.
-
I have the same problem of HDCD plugin that is not working anymore since Windows 10 has been updated to the latest version 20H2. I don't know exactly the issue but the other laptop with Windows 10 1909 still working well. I have seen this plugin hasn't been updated since a long time. Hope this can be fixed soon.
-
Hello
I am a very new user of this player, everything works fine except for DSD files,
I am using a Topping E30 DAC on a win 10 PC (latest version) with the suggested Topping drivers already installed.
When I try to configure the player I select OUTPUT ASIO and then can choose between foo_dsd, and Topping DAC. Despite all the possible combination, the only way the get music of a DSD 64 or 128 file is to set PCM output, on the contrary i hear a hiss or a kind of white noise with a display showing details like the screenshot below.
Am I wrong on any setup?
Thanks in advance for your help
[img(https://i.imgur.com/LSLTYfe.png)[/img]
-
I'm having the same problem with DSF files. Ever since version 3.3 (on Windows 10).
I can confirm that version 3.2.6902 (running on a different computer - Windows 7) marks the files correctly as 1 bit with the right sample rate.
Reading up a bit on the inner workings, I've also tried swapping all the BASS dlls (from 3.2 to my latest 3.3), but that didn't make a difference. 3.3 (latest build) with the DLLs from 3.2 still marks the DSF files wrongly (no bit depth and the wrong sample rate - 88.2khz).
-
I'm no expert on DSD/DSF, but just to rule out a few things why don't you try updating to MusicBee 3.4 from here https://getmusicbee.com/forum/index.php?topic=32142.msg187516#new (https://getmusicbee.com/forum/index.php?topic=32142.msg187516#new) and giving it another shot. If that doesn't work, keep 3.4, but try updating bass.dll to the one here www.un4seen.com/stuff/bass.zip (http://www.un4seen.com/stuff/bass.zip) (back up the original first), and be sure you are using bassdsd.dll version 2.4.1.2. If still a no-go, I would suspect a Windows 10 version issue as reported by djony above.
-
I installed 3.3.7491 on Windows 7, replacing the 3.2 version. That one then produces the same problem with the dsf files. Wrong sample rate, no bit depth mentioned, where version 3.2 imported them correctly.
Version 3.3 / 3.4 on Windows 10. Same problem.
It's not bugging me that much that I'm gonna try 3.2 on Windows 10. ;D
I think Windows 7 proves the point already. It seems somehow related to the MusicBee version, not to Windows 10.
The BASS dll version for all my experiments was 2.4.1.2.
(note that there's two issues in this thread... I'm not talking about the HDCD plugin - I don't use that one - but about the properties of a .dsf not being displayed correctly, which is the first point of topic starter)
-
The BASS dll version for all my experiments was 2.4.1.2.
]You mean that was version of bassdsd.dll, right? Did you try replacing bass.dll with version 2.4.15.29 from the link I gave you? Just to complete the BASS experiment--then I'm all out of things to try, maybe Steven can help on why the DSF files show the wrong bit and sample rate. BTW what kind of audio device are you using and how is your output set?
Edit: I downloaded a test DSF here http://samplerateconverter.com/free-files/samples/dsf/sweep-176400hz-0-22050hz-20s-D128-5.6mhz.zip (http://samplerateconverter.com/free-files/samples/dsf/sweep-176400hz-0-22050hz-20s-D128-5.6mhz.zip) ; while it plays fine can confirm that in the file properties the sample rate is erroneously shown as 88.2kHz (should be 5.6mHz) and bit depth does not show--all as reported by HeavyFede and ememMusic. My MusicBee is 3.4.7724, Windows 10 v. 2004, current versions of all bass dll's. The newest AIMP player shows the bit depth (1) and sample rate correctly; both players tested using wasapi-exclusive output. AIMP uses its own non-BASS dsd plugin.
-
In case it helps Steven: I copied my existing up-to-date portable install and made a test folder unchanged in content except for the fact that MusicBee.exe 3.4.7724 was replaced with MusicBee.exe 3.2.6902. Looking at the sample DSF file linked to in my last post, Edit/Properties then indeed showed the bit depth (1), and the sample rate as HALF the actual 5.6mHz (??). So the issue lies somewhere (.."along the infinite corridors of time"--any Time Tunnel fans out there??) within the MusicBee.exe file, as postulated by ememMusic.
-
If you right click/ send to/ rescan file then it should show the correct source file sample rate. It intentionally doesnt show the 1bit info
https://getmusicbee.com/patches/MusicBee34_Patched.zip
unzip and replace the existing musicbee application files
-
If you right click/ send to/ rescan file then it should show the correct source file sample rate. It intentionally doesnt show the 1bit info
https://getmusicbee.com/patches/MusicBee34_Patched.zip
unzip and replace the existing musicbee application files
Hey Steven,
That worked.
It does show the 1-bit info, like it used to, in the Type field, if you click on the properties of one track (not the whole album). Right click on track -> Edit -> Properties. Behind the "DSF audio file" it says '1-bit' (which was lacking in 3.3). And the sample rate is correct.
As far as I'm concerned this is now fixed to what it was originally in 3.2.
Thanks.
-
If you right click/ send to/ rescan file then it should show the correct source file sample rate. It intentionally doesnt show the 1bit info
https://getmusicbee.com/patches/MusicBee34_Patched.zip
unzip and replace the existing musicbee application files
Thanks Steven this fixed it for the sample DSF I mentioned as well, even showing the 1bit info. And unlike with the 3.2.6902 test I did sample rate is now the full 5.6mHz instead of 2.8mHz. Done and done!
(https://i.imgur.com/L5cbv2M.png)
-
Hello
I am a very new user of this player, everything works fine except for DSD files,
I am using a Topping E30 DAC on a win 10 PC (latest version) with the suggested Topping drivers already installed.
When I try to configure the player I select OUTPUT ASIO and then can choose between foo_dsd, and Topping DAC. Despite all the possible combination, the only way the get music of a DSD 64 or 128 file is to set PCM output, on the contrary i hear a hiss or a kind of white noise with a display showing details like the screenshot below.
Am I wrong on any setup?
Thanks in advance for your help
[img(https://i.imgur.com/LSLTYfe.png)[/img]
Hey Jogas,
I have the Gustard A22, which is sort of similar to the Topping. For playback I mostly use Foobar, which does a good job with .dsf files.
So today I tried MusicBee for the first time for .dsf files and I have the same problem as you have. I think the difference is that Foobar uses an additional decoder (SACD input). Without it (with just ASIO and the USB drivers) it's also impossible in Foobar. I do get some results in MusicBee, but it's either full PCM conversion or a pretty ugly DOP, which seems to confuse the DAC quite a bit. I think the DSD stream needs some additional care by a specialized decoder.
So my idea is that until someone writes a SACD or DSF plugin, this is not going to work in MusicBee.
-
Hey Jogas,
I have the Gustard A22, which is sort of similar to the Topping. For playback I mostly use Foobar, which does a good job with .dsf files.
So today I tried MusicBee for the first time for .dsf files and I have the same problem as you have. I think the difference is that Foobar uses an additional decoder (SACD input). Without it (with just ASIO and the USB drivers) it's also impossible in Foobar. I do get some results in MusicBee, but it's either full PCM conversion or a pretty ugly DOP, which seems to confuse the DAC quite a bit. I think the DSD stream needs some additional care by a specialized decoder.
So my idea is that until someone writes a SACD or DSF plugin, this is not going to work in MusicBee.
While this is obviously a YMMV situation depending on hardware, etc. some people are getting good results using DOP via ASIO in MusicBee with DSD64 and DSD128 files (https://getmusicbee.com/forum/index.php?topic=34298.msg187960#msg187960 (https://getmusicbee.com/forum/index.php?topic=34298.msg187960#msg187960)). Check the referenced thread for info on file versions used, etc.
-
While this is obviously a YMMV situation depending on hardware, etc. some people are getting good results using DOP via ASIO in MusicBee with DSD64 and DSD128 files (https://getmusicbee.com/forum/index.php?topic=34298.msg187960#msg187960 (https://getmusicbee.com/forum/index.php?topic=34298.msg187960#msg187960)). Check the referenced thread for info on file versions used, etc.
Yes, thanks, I've got DOP working now. That turned out to be a network issue, where the file simply came in too slow.
However, I have to make sure the volume control is set to 100%. I guess it should be actually disabled, since DSD streams can't handle software volume (I think). As soon as I lower the volume in MusicBee, the file drops back to PCM 176khz with no output (might be a tip for some of the people in that other thread - MusicBee version 3.4).
But this is good enough for me. I just wish it would stream a bit easier. I'm not sure why, but Foobar seems to have less problems with my rather slow network. Priority settings maybe. I'll see if buffering helps.
-
I appreciate MusicBee . Nice software . like it more than Audirvana , JRiver or Roon.
But same problem here : Musicbee is not able to play native DSD files.
Config.: MusicBee (latest) > Win10 > RME Asio > RME Adi 2 DAC (native DSD setting) : Extreme loud hiss > 100 dB ! :o
This is really dangerous , because the incoming hiss can easily destroy your tweeters .
You have to immediately switch to PCM conversion.
There is the option for no conversion to PCM in RME Asio driver . Naturally you have no access to volume and other controls.
But phantastic sound quality as well. .
Tried Audirvana ,Foobar (with plug ins) and JRiver , and all have no problem with native DSD.
Would be so nice , if MB would add this feature as well.
Regards from Germany
M.
-
I appreciate MusicBee . Nice software . like it more than Audirvana , JRiver or Roon.
But same problem here : Musicbee is not able to play native DSD files.
Config.: MusicBee (latest) > Win10 > RME Asio > RME Adi 2 DAC (native DSD setting) : Extreme loud hiss > 100 dB ! :o
This is really dangerous , because the incoming hiss can easily destroy your tweeters .
You have to immediately switch to PCM conversion.
There is the option for no conversion to PCM in RME Asio driver . Naturally you have no access to volume and other controls.
But phantastic sound quality as well. .
Tried Audirvana ,Foobar (with plug ins) and JRiver , and all have no problem with native DSD.
Would be so nice , if MB would add this feature as well.
Regards from Germany
M.
Hey mine,
I had the same problems, but DSD over PCM (DOP) does work. That's essentially the same as native. If you have that option in your ASIO settings? Indeed, direct DSD just gives a bunch of loud white noise (I think we're hearing the bit stream in stead of the music that's hiding in the stream).
Then make sure the volume is set to 100% (I also turned off any fading options / replay gain options etc.). If the volume slider is not at 100% there's no output and the DAC will show 176kHz (with no sound). At least in my setup. But at 100% it switches to native DSD. Even if the stream is masked as a PCM container. The DAC shows the right info.
-
As ememMusic said, there is the working option for using DOP, or "Stream DSD data as PCM", which is not the same as "Convert to PCM".
"The original idea for DoP was invented by dCS in 2011. It involves taking groups of 16 adjacent 1-bit samples from a DSD stream and packing them into the lower 16 bits of a 24/176.4 data stream. Data from the other channel of the stereo pair is packed the same way. A specific marker code in the top 8 bits identifies the data stream as DoP, rather than PCM. The resulting DoP stream can be transmitted through existing 24/192-capable USB, AES, Dual AES or SPDIF interfaces to a DoP-compatible DAC, which reassembles the original stereo DSD data stream COMPLETELY UNCHANGED. If something goes wrong and the data stream is decoded as PCM, the output will be low-level noise with faint music in the back ground, so it fails safely. This can happen if the computer erases the marker code by applying a volume adjustment."
Source: https://www.dcsltd.co.uk/support/what-is-dop-dsd-over-pcm/ (https://www.dcsltd.co.uk/support/what-is-dop-dsd-over-pcm/)
-
Great info.
There is something else I am curious about.
As I reported earlier, using ASIO and setting DOP for it in general plays fine. Only the spectrum analyser and the VU meter doesn't work, and DSD256 files won't play for me.
When I switch to Wasapi exclusive, DSD256 also plays, and both the spectrum and VU meters work.
I believe I read somewhere that Wasapi exclusive will also perform bit-perfect DSD playback, on the condition that the DAC can use (and the player is set to) event mode.
Do you know more about this?
edit:
What I also wonder about: I just read somebody explaining things on another forum:
Quote: "As far as I am concerned the only "disadvantage" for DoP is that it requires high rate PCM capability for those who want to be able to playback high rate DSD files: DSD64 requires a 176.4 PCM package, DSD 128 requires a 352.8 PCM package, and DSD256 requires a 705.6 PCM package. Not a lot of DACs can do 705.6 PCM, so DSD256 delivery is generally limited to Native DSD streams."
The specs of my DAC mention 384kHz as the maximum rate it can handle for PCM. So it shouldn't be able to process DSD256.
That would explain why DSD256 won't play.
When using Wasapi exclusive event mode it seems to play it fine without any issue whatsoever.
That probably means that in Wasapi exclusive I have an actual DSD stream playing?
If so, why use ASIO (or DOP) to begin with?
-
There is the option for no conversion to PCM in RME Asio driver.
If your dac can work in event mode, could you try what happens when you use Wasapi exclusive with event mode checked?
-
edit:
What I also wonder about: I just read somebody explaining things on another forum:
Quote: "As far as I am concerned the only "disadvantage" for DoP is that it requires high rate PCM capability for those who want to be able to playback high rate DSD files: DSD64 requires a 176.4 PCM package, DSD 128 requires a 352.8 PCM package, and DSD256 requires a 705.6 PCM package. Not a lot of DACs can do 705.6 PCM, so DSD256 delivery is generally limited to Native DSD streams."
I believe that's correct. If I play DSD64 (DoP) my DAC briefly shows receiving PCM 176kHz and then it switches to DSD. If I play DSD128 it shows 352kHz before switching over to DSD. I don't have DSD256 files, and I don't know the exact specs of my DAC, but I assume it would double again in PCM.
I don't have WASAPI event mode. Just 'shared' or 'exclusive'. And the DAC driver then plays DSD at PCM 44.1kHz. So for me that's not an option.
-
I don't have WASAPI event mode. Just 'shared' or 'exclusive'. And the DAC driver then plays DSD at PCM 44.1kHz. So for me that's not an option.
It should be an option:
(https://i.imgur.com/0JJ7VWx.png)
But your DAC must also support event (a.k.a. asynchronous, a.k.a. pull) mode to benefit from it.
-
The specs of my DAC mention 384kHz as the maximum rate it can handle for PCM. So it shouldn't be able to process DSD256.
That would explain why DSD256 won't play.
When using Wasapi exclusive event mode it seems to play it fine without any issue whatsoever.
That probably means that in Wasapi exclusive I have an actual DSD stream playing?
If so, why use ASIO (or DOP) to begin with?
Hiccup it's my understanding from Steven's past posts that the only way MB can use DOP is via the ASIO interface. Any DSF files played via Wasapi-Exclusive are automatically converted to "regular" PCM at a sample rate of 88.2kHz. My own non-DAC setup will play a 5.6mHz DSF using Wasapi-Exclusive, which HAS to be a straight non-DOP PCM conversion, so that would seem to confirm this--although maybe a DAC with the specs could take it pre-conversion??
So my own conclusion is that MusicBee will play ANY DSF file (as long as bassdsd.dll is up to date), but using PCM conversion to a much lower sample rate. In order to get "real" DSF out to a DAC, MusicBee must use ASIO only, and from your testing in DOP as opposed to raw DSD.
DSD256 won't play for you via ASIO/DOP due to the spec limits of your DAC. It will play for you via Wasapi-Exclusive because in that case MusicBee is just converting it to a regular PCM stream by default, and not using DOP.
I'm more than open to any corrections to my conclusions (educated guesses based on reported experiences) if Steven or a MusicBee DSD user cares to check in here (PLEASE do!!).
Whoops I see there's been two more posts but let me submit this as the sum total of "what I know/think I know now."
-
@Sveakul,
Do you have any idea why using ASIO with the setting 'Stream raw DSD data' for me produces nothing but noise?
Are there testimonies of MB users that are successfully using this mode?
edit:
Maybe it's because I'm on Windows 10 1809. When I originally installed it it didn't have USB2 audio drivers.
At a later moment I made some effort to add/install them, but I can't be sure that was a success.
But I am not sure if that is relevant either t.b.h.
I did install drivers from the manufacturer of my DAC.
When somebody reads all this in the next century he is going to have pity on us.
And respect for the troubles we went through ;-)
edit 2:
Adding some specifications that I found on the USB receiver of my DAC.
Not because I am personally concerned about being able to play DSD (I don't see—or hear—any benefits in DSD at all), but maybe it's useful for others that are trying to make sense of all this and are interested in getting things to work as expected.
"DESCRIPTIONThe combo384 is an USB audio device adapter for OEM applications.USB PCM audio data (2 Channels ) accepted in input are converted in an I2S stream or DSD native stream. The PCM sample rates supported are 44.1 Khz, 48 Khz, 88,2 Khz, 96 Khz, 176,4 Khz, 192 Khz, 352,8 Khz, 384 Khz.The DSD over USB format is detected when PCM sample with an alternate sequence of 32 FA05 token in the MSB part is received. The DSD managed frequencies are 2.822 Mhz, 3.072 Mhz, 5.644 Mhz, 6.144 Mhz. With ASIO Driver http://www.amanero.com/asio it's possible to play native DSD extending the range to DSD256 and DSD512."
-
I don't have WASAPI event mode. Just 'shared' or 'exclusive'. And the DAC driver then plays DSD at PCM 44.1kHz. So for me that's not an option.
It should be an option:
(https://i.imgur.com/0JJ7VWx.png)
But your DAC must also support event (a.k.a. asynchronous, a.k.a. pull) mode to benefit from it.
Ah yes, now I see the option. Well, it works, but as sveakul writes, it seems to convert to PCM 88.2kHz (as reported by my DAC). So for true DSD that's not the way I suppose.
But to be honest, I also don't understand why the direct DSD stream doesn't work, if all the other options do. I suspect the DAC needs some kind of header info or something - being tricked into the idea it's an SACD? I have Foobar set up to play straight DSD (no DoP) and that one still shows me briefly the PCM 176kHz on the DAC when playing DSD64. So either it's doing DoP behind my back (despite the settings) or native DSD also needs some extra info for the DAC.
Edit: if I play DSD64 as RAW DSD the DAC does report it correctly. It's just not turned into music. And additionally, despite the continuous white noise, the file is not progressing in MusicBee... it stops in the first second... (the noise does not)...
-
"DESCRIPTIONThe combo384 is an USB audio device adapter for OEM applications.USB PCM audio data (2 Channels ) accepted in input are converted in an I2S stream or DSD native stream. The PCM sample rates supported are 44.1 Khz, 48 Khz, 88,2 Khz, 96 Khz, 176,4 Khz, 192 Khz, 352,8 Khz, 384 Khz.The DSD over USB format is detected when PCM sample with an alternate sequence of 32 FA05 token in the MSB part is received. The DSD managed frequencies are 2.822 Mhz, 3.072 Mhz, 5.644 Mhz, 6.144 Mhz. With ASIO Driver http://www.amanero.com/asio it's possible to play native DSD extending the range to DSD256 and DSD512."
That sounds a bit like I suggested in my previous post: the DAC needs an announcement it's about to be loaded up with DSD. And that announcement needs to be in some kind of PCM form. So the direct stream won't work if the header is lacking. Might also explain why I see PCM for a second or so when I play native DSD through Foobar.
Well... just a hypothesis.
-
@Sveakul,
Do you have any idea why using ASIO with the setting 'Stream raw DSD data' for me produces nothing but noise?
Are there testimonies of MB users that are successfully using this mode?
I have a feeling it may indeed depend on having specific types of USB drivers designed for raw DSD. It also could be a limitation of the current bassdsd.dll--Steven had indicated he worked specifically with Ian Luck the Un4seen developer in getting bassdsd.dll to work with ASIO in handling DSD for MusicBee. In one post he stated, "Also its not clear to me that the BASS library is able to accurately auto-detect when the ASIO device does support decoding native DSD data." I've found several people in the old thread confirming that DOP works fine (as it does for you), but only one poster (MagSirius) that claims success with raw DSD (https://getmusicbee.com/forum/index.php?topic=4863.msg163672#msg163672 (https://getmusicbee.com/forum/index.php?topic=4863.msg163672#msg163672)).
I guess we should be glad that it DOES work with DOP--an actual DSD solution using PCM as a wrapper instead of a PCM conversion. Like you, I have no real personal use for DSD in the first place due to the file sizes and the fact that my ears won't tell the difference with Wasapi-Exclusive PCM. But, I think it's INTERESTING, and if the raw DSD option can be made to work, then why not try, depending on how Steven feels on the work vs. results ratio. A statement made in another time/place/situation was, "It is unsatisfactory to have it lying on the beach and not know what it is." That's why I'm interested in a positive result--it's unsatisfactory to have a raw-DSD option choice, and not know how to make it work.
-
Okay, I've got it working native in MusicBee.
No more PCM switching on the DAC and the noise turns into music.
But it's rather a strange setup and it seems a bit unstable. So not sure if this method is advised. I think DoP is fine.
I've installed DSDTranscoder... https://sourceforge.net/projects/sacddecoder/files/dsd_transcoder/ - since it turns out I was indeed playing DoP in Foobar. That's why the DAC feedback was similar to MusicBee.
Then select DSD-Transcoder as Sound Device in MusicBee. Click configure and again configure. In the DSD-Trancoder window select your USB DAC driver. Then turn the two columns to DSD for everything (click on the items and you can change them).
Then in the ASIO window select DoP (no, that raw stream still doesn't work).
Probably why it's unstable. I suspect I now have two conversions going on. From DSD to DoP back to DSD. But confirmed by the music and the DAC audio driver: it's now native DSD being played. And I don't see any PCM switching on the DAC.
I'll stick to DoP :-)
-
Probably why it's unstable. I suspect I now have two conversions going on. From DSD to DoP back to DSD. But confirmed by the music and the DAC audio driver: it's now native DSD being played. And I don't see any PCM switching on the DAC.
I'll stick to DoP :-)
Thanks for sharing those results! I agree with your conclusion though. Other readers, remember that with DoP you DO end up with native DSD being played, not a PCM conversion, as the DAC is reassembling the native DSD from the DoP stream.
-
Probably why it's unstable. I suspect I now have two conversions going on. From DSD to DoP back to DSD. But confirmed by the music and the DAC audio driver: it's now native DSD being played. And I don't see any PCM switching on the DAC.
I'll stick to DoP :-)
Thanks for sharing those results! I agree with your conclusion though. Other readers, remember that with DoP you DO end up with native DSD being played, not a PCM conversion, as the DAC is reassembling the native DSD from the DoP stream.
Yes, I think my solution is all a bit too much. Especially since it makes no difference if it's native or DoP. I'm now just loading up my computer with useless multiple conversions.
But this might work for Hiccup and his DSD256 files. If that 700+ PCM isn't accepted, the native stream might. DSDTranscoder can be set so that only DSD256 will play as native DSD, even if all the other DSD types are passed through as DoP.
DSDTranscoder is also open source (I think). Perhaps interesting to the developer(s) of MusicBee to see what happens within it and what that raw stream exiting DSDTranscoder actually looks like. It might shed some light on the 'why' for many DACs that raw option turns into noise.
-
Nice findings , guys
Another one from the beginning :
https://dsd-guide.com/dop-open-standard
DoP works flawlessly with Musicbee > USB and my RME DAC (RME Asio Driver)
128FS > 352.8kHz. Even
256FS > 705.6K is supported .
Wonder why some features are activated with DoP (not with native DSD) - Spectrumanalyzer works, Volume works. Loudness works.. There must be some internal conversion :o ?
-
Nice findings , guys
Another one from the beginning :
https://dsd-guide.com/dop-open-standard
DoP works flawlessly with Musicbee > USB and my RME DAC (RME Asio Driver)
128FS > 352.8kHz. Even
256FS > 705.6K is supported .
Wonder why some features are activated with DoP (not with native DSD) - Spectrumanalyzer works, Volume works. Loudness works.. There must be some internal conversion :o ?
That's interesting. For me it doesn't. Well, not the volume. For me the volume slider in MB has to be at 100%, else the DAC drops back to showing the PCM kHz with no sound. Maybe your DAC knows how to internally handle volume changes encoded in the PCM container? Not sure if that's possible with DoP. But looking at the RME, I think you should then also see the DB indicator drop (or go up) on the DAC LCD?
-
Sorry I made a mistake . In the various hidden (there are so many !) RME menues , (if you are in USB mode) ,you have to activate :
DSD detection : on
DSD direct line : on
DSD Filter : on (50kHz orb 150 kHz).
And now the spectrum analyzer and level meter turns into blue colour (it still works !) but now the other functions (Volume a.o. ) are disabled. So it works with DoP as it is supposed to do.
Nice side effect . With the RME- ADi 2 pro : via USB the SPDIF inputs can even record not only PCM but also DSD.
Remains : DoP works in the settings controlpanel , DSD direct is extremely dangerous , the hiss can destroy your speakers. Maybe Steve can have a look on it.
Sorry for my english (not my native language)
Best
mine (with regards from Germany) Donation done.
-
Sorry I made a mistake . In the various hidden (there are so many !) RME menues , (if you are in USB mode) ,you have to aktivate
DSD detection : on
DSD direct line : on
DSD Filter : on (50kHz orb 150 kHz).
And now the spectrum analyzer and level meter turns into blue colour (it still works !) but now the other functions (Volume a.o. ) are disabled. So it works with DoP as it is supposed to do.
Nice side effect . With the RME- ADi 2 pro : via USB the SPDIF inputs can even record not only PCM but also DSD.
Remains : DoP works in the settings controlpanel , DSD direct is extremely dangerous , the hiss can destroy your speakers. Maybe Steve can have a look on it.
Sorry for my english (not my native language)
Best
mine (with regards from Germany) Donation done.
Does DoP also turn to silence if you slide the volume away from 100%?
Additionally be careful. When I use DoP and I put the volume slider at 98%, the music turn into the same hiss as the raw stream. Only if I slide it lower, the DAC turns into silence, showing the PCM kHz. So in my setup the volume changes have some weird effects on DoP. Volume should be disconnected internally. You still want to be able to set it if your next file in a playlist is PCM, but it shouldn't bother DoP. In Foobar you can still slide it, but it's being ignored. EQ, DSPs, fading options etc. might all be a problem.
Another observation with DoP: if I turn on any of the visualizers, the music starts to speed up.
In the raw stream mode, the file doesn't progress at all. It just gets stuck in the first second, despite the noise being continuous. So I wonder if it's some kind of timing problem.
-
[
Does DoP also turn to silence if you slide the volume away from 100%?
Additionally be careful. When I use DoP and I put the volume slider at 98%, the music turn into the same hiss as the raw stream. Only if I slide it lower, the DAC turns into silence, showing the PCM kHz. So in my setup the volume changes have some weird effects on DoP.
Another observation with DoP: if I turn on any of the visualizers, the music starts to speed up.
In the raw stream mode, the file doesn't progress at all. It just gets stuck in the first second, despite the noise being continuous. So I wonder if it's some kind of timing problem.
No , no such observation . Only the spectrum analyizer turns into blue , and all control elements are locked.
Found this @ RME :
"If you solely refer "DSD Native" as UAC Alternative Setting 3 such as many other USB audio interface chips (such as XMOS) support, it's NOT supporting that. It does not behave the same as many other DACs (such as XMOS based products) do.
It does support "ASIO native DSD", but it's just using the RME ASIO driver to convert native DSD to DOP on your computer first, and then send the DOP signal to the unit via USB. The conversion is seamless so you don't need to care about it in Windows. For any other operating systems you can't set your music player to output "native DSD" to the unit."
Best
mine
-
Does DoP also turn to silence if you slide the volume away from 100%?
According to the developers of DoP, by design "If something goes wrong and the data stream is decoded as PCM, the output will be low-level noise with faint music in the back ground, so it fails safely. This can happen if the computer erases the marker code by applying a volume adjustment.." But as your own experiment shows, that must be in some specific-but-undefined environment in terms of hardware and drivers.