Sample rate of Bluesound Node 2i analog in
BeantwortetIt has been stated several times on this forum by Bluesound staff, that the analog in on all Bluesound products is internally converted to 24/96 PCM. However, my DAC only indicates 44.1kHz when I pass through the analog in to the coax out. Could someone from Bluesound clarify why we are not getting 96kHz output from the analog in? Is there the possibility of a software update to unlock that functionality?
Many thanks,
-
Offizieller Kommentar
There is no settings on this - please select Help, Send Support Request so the Support Crew may take a closer look. Please also include the make and model of your third party DAC.
-
I’m not sure what to do. I opened a support ticket, but the response I received doesn’t help with my question and the agent has stopped responding to my follow-up questions:
Hello h@nnes.io,
Thank you for contacting the Bluesound Support Crew.
If you are using Coaxial or Optical output from BluOS Player, the output is 24-bit/96KHz audio. To get 24-bit/192KHz audio, you must use the analog RCA outputs of BluOS Players to have the internal DAC of BluOS Player to process both the rendering stages and output fully unfolded MQA file.
If your external DAC is showing 44Khz there would be something wrong on the input used in the DAC. I would recommend double checking with the DAC manufacturer. There is no additional setting that needs to be adjusted on the Node.
Vishnu
The Bluesound Support CrewThis answer is both beside the point because MQA has nothing to do with the analog input and also incorrect, because the coax out is perfectly capable of outputting a 192kHz signal without the need for MQA. The agent then blames the problem on me and suggests I have misconfigured my DAC (RME ADI-2 FS) in some unspecified way, but this can’t be the case because the DAC plays hi-res files from the Node’s coax out to 192kHz without problems. Consistently, the analog in only outputs 44.1kHz though.
I would really appreciate if someone could have a more serious look at this issue and attempt to reproduce the problem.
1 -
Same here, was this ever addressed?
0
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
3 Kommentare