My guess is they will make a determination, based on the demographics of MQA playback… I don’t claim to know how this would be determined… but I can tell you unequivocally, that I have zero (0) MQA files in my content library and I don’t subscribe to a streaming service… Am I in the minority? The argument for MQA processing is still being debated… Is there enough savvy users with MQA DAC’s that are compelled to focus on MQA encoded content…? This is my question… I understand the nature of time-domain artifacts on the perceived playback sound-quality… But these can be managed by proper configuration of a SDM like r8Brain without the need for a dedicated MQA processor in the DAC architecture… However, all of this is dependent on subjective biases in the final assessment.
![]()
Studio version 3.0.5: Problem still present …
We have not looked at it yet.
That surprises me. Why haven’t you looked at it yet? Wouldn’t that be the obvious first step in order solve an issue?
How much MQA content do you have…? I would prefer the team spend time and resources on performance aspects that will keep the Audirvāna audio-engine at the top in regard to sound-quality…
How many titles are mastered as 32-bit or 24-bit 352.8kHz and 384kHz MQA files? How many folks can perceive pre-ringing or the lack of pre-ringing in playback in any given PCM encoding?.. The fall-back argument for MQA is the reduced storage volume.
![]()
Not of your buissness how much content people have.
Your comments never solved any problem in any topic.You are like a bumper to kick out of forum any additional unnecessary work.
Bla, bla bla.
Your comment must be the last one at conversation to cover main subject of discssion.
Non of your buissness MQA so be quiet.
Listen to your DSDs and leave people problems alone.
We dont need your nonsense talk at this topic.
Go bother other people.
Thats what you do
It is a rhetorical question… ![]()
![]()
Audirvana
odtoesprnSf7c7 2000l4u3al2t3a19f1c0lafahi173i0 72u83M6t,8r8l ·
The development of the Audirvana Plus 3.0 application is complete.
But I’m waiting for a last update of the MQA Core Decoder library, providing some last minor bug fixes. They are willing to provide something perfect for the first integration in an audiophile player, knowing the audiophile community is quite demanding in terms of sound quality. Since it does not depend on me, I can’t promise any release date, but my understanding is that it is a matter of days.
See less
Because we have something cooking, I must test first ![]()
But we have now done the test and fixed the issue on our end.
Thank you !