I ran these files on Cascade along with Aurender N30 , the ones with the arrow did not pass .
Hi ASIO,
Just a guess, because the test seems to be failing around 192kHz.
Are you using the SPDIF or AES/EBU input? That technology is limited to at best 192kHz, depending on the length of the cable. Also, the MSB SPDIF modules are limited to 192kHz.
I think Aurender will down-sample anything it sends out on SPDIF if the sample-rate is too high (I’m not sure at what rate it thinks is too high). Any down-sampled signal will fail the MSB bit-perfect test.
Typically USB can handle rates higher than 192kHz.
Dan
2 Likes
Thanks
The ones that fail are also very theoretic examples. 16bit, 192kHz, don’t think you ever run into that as source material. Same for the higher examples.
24/352.8 is DXD and this a very common format for new, high resolution music. The Pyramix workstation will record in that format natively, and it is used to edit DSD256 files (during mastering).
Per Dan’s message, I would check/change your connection to the Cascade.
Separately, if you own a Cascade, it would be nuts to do any DSP with the Aurender. Just sayin’ : )
R
1 Like
Yes, DXD is great in studios and post production. But let me see how many of the 10.000 albums that are on my NAS here are in that format. Obviously the answer is 0.
So given that most of is will use this DAC to listen what is commercially available, it’s a theoretically exercise. For the performance of the DAC it is more important what it can do with 16/44.1 than with 24/352.8.
Fair point @jvdijk, but that isn’t the point of the post.
Here we have a bit perfect test fail at higher resolution.
I am curious @ASIO : were you able to try a different connection and get “passes” for the failed HD resolutions?
If not, this would be issue important enough to escalate to MSB management
R
24_384
16_192,352,384 failed with pro usb also
I would think if MSB included these files in the test tones they should pass
-
- Works at rates up to 24/768kHz and 8xDSD
This is what is advertised? Pls explain why these fail
My N30 supports 32/768 on USB
Hi everyone. I’m investigating this issue because I’m working on a new firmware update now. Regarding the failing test, if it occasionally fails, it’s not a cause for concern. If you play the file a few times and it reports good once, you should be fine. I suspect that the bit-perfect test is passing, but it’s happening so rapidly that it’s not being accurately reported. When you say it fails, does it happen every time, or is it just some instances? When it doesn’t work do you hear a little burst of noise or is it silent before “check your display now.”?
Silent and happens every time
I can confirm that this is a reporting bug. I’m working on fixing it now. The playback is bit perfect, it’s just not displaying it. It should be fixed in the next firmware release.
1 Like