Hi-Res Audio for Android based DAPs
(PCM 32-bit, <= 768k)
New HiBy R6 is suggested to support 768k.
In fact, when I first installed and used Neutron in my New Hiby R6, I could oversampling and set Frequency to 768k.
However, don't know why, maybe update to another version of Neutron, then now I could only set to the Frequency to 384000.
And even though I want to find 768k, i could no longer find it.
Besides, New Hiby R6 supports MQA, but does Neutron supports MQA?
New HiBy R6 - 768k Frequency and MQA enquiry
Re: New HiBy R6 - 768k Frequency and MQA enquiry
See here - it would seem that Neutron can decode MQA ( into PCM and then play it ). But perhaps you want to transfer the MQA unchanged to the DAC, as is sometimes possible with DSD ? I don't think that Neutron supports this.
Re: New HiBy R6 - 768k Frequency and MQA enquiry
Feel free to contact neutronmp@gmail.com to analyze this.
Re: New HiBy R6 - 768k Frequency and MQA enquiry
Neutron identifies presence of 'MQAEncode v1.1 (and so on)' found in file's 'encoder' tag data, and then sets output sample rate to the value under file's 'originalsamplerate' tag data.
Yeah, this would interfere with DACs expecting untouched MQA bit stream. Up to Dmitry to know how it affects devices with built-in MQA support.
Yeah, this would interfere with DACs expecting untouched MQA bit stream. Up to Dmitry to know how it affects devices with built-in MQA support.
Re: New HiBy R6 - 768k Frequency and MQA enquiry
Sorry.
I forgot to update all interested (if any) regarding my enquiry.
Regarding the issue of limited to 386k only but not 768k,
Dmitry was so helpful and had spent about a week to work for my enquiry.
Dev version was given to me to resolve the problem.
According to what Dmitry did have mentioned, NR6s is using their private audio API.
Although Neutron also supports Hiby's private audio API, some adjustments were needed.
So, if any user of NR6 do encounter the same problem with me that could not use
oversampling up to 768k, please contact neutronmp@gmail.com, or otherwise,
wait until the next update.
I forgot to update all interested (if any) regarding my enquiry.
Regarding the issue of limited to 386k only but not 768k,
Dmitry was so helpful and had spent about a week to work for my enquiry.
Dev version was given to me to resolve the problem.
According to what Dmitry did have mentioned, NR6s is using their private audio API.
Although Neutron also supports Hiby's private audio API, some adjustments were needed.
So, if any user of NR6 do encounter the same problem with me that could not use
oversampling up to 768k, please contact neutronmp@gmail.com, or otherwise,
wait until the next update.
Who is online
Users browsing this forum: No registered users and 21 guests