hunts desperately for bottle of mind-bleach
5 Likes
Itâs too late. The damage has been done and is permanent. Iâll never be the same again, listening to MQA.
2 Likes
Is that a comment on the lossy MQA mastering process�
1 Like
I really wish I could say yes, to deflect from the visuals of @miguelito in his very tight trunks 
2 Likes
Jeez! You havenât even seen my trunks!
2 Likes
I donât like the way this is un-foldingâŚ
7 Likes
More blurring please.
2 Likes
RuPaul season 1 vaseline filters on their way
2 Likes
it should be obvious that roon is not going to be able to ever unfold mqa anytime soon if at all. i am betting the latter.
What are you prepared to wager that Roon never unfolds MQA ? Eating of hat or baring of bum in public ?
Edit: I myself will wager unprotected viewing of a pic of Miguelito in his shorts (with reaction video) if it hasnât happened by 30 June.
4 Likes
at a certain point soon becomes never.
I canât wait Roon put up its nice âshortsâ by then. Patiently waitingâŚ
I love @miguelito ('s) posts on MQA, BUT I do not need an underwear modeling event popping up in the Roon browserâŚ
1 Like
Roon are not stupid. If MQA were not coming I think they would simply say so, deal with the fall out and carry on!
how many months have they been saying itâs right around the corner?
If I were Roon: introduction at the high end in Munchen?
Itâs a fair question, so I went searching:
The earliest reference I could find was January 16, 2017 just after Tidal introduced MQA Masters. In this interview where Rob Darling was quoted as saying:
âOnce we have code from MQA, it should be a matter of single digit days to get it integrated.â
I think it would be fair to call that an âoverly enthusiasticâ estimate.
In February 2017 Brian walked it back a bit here:
âYouâve been around here long enough to know we donât put time estimates on anything, but especially not things that involve other companies.
In terms of new features coming, MQA software decoding is our top priority. Itâs a top priority for MQA too. We want the same things you do, and we are well aware of the massive demand for this feature.
Weâll share more when thereâs more to share.â
In July 2017 Roon introduced MQA detection in Build 242. No news at that time about MQA unfolding.
Then a long silence until MQA announced that Roon was onboard at CES 2018. I understand that this marked the end of negotiations and entry into a commercial agreement. The technical development commenced after this.
In January 2018 Brian confirmed that Roon would do the first unfold when MQA support was released but didnât give any estimate as to time.
So you can pick either January 2017 or January 2018. Clearly negotiations took a lot longer than expected, but contracts have now been signed and implementation is under active development.
Like Henry, I believe that if for any reason they were not going to unfold MQA then they would simply tell us. What could be gained from sitting on such news ?
4 Likes
I checked a certain computer software player that implemented MQA - between their earliest public announcement (that I can find) and the actual release of the MQA decoding feature, it toke them 6 months. Usually a company should have started work on stuff before public announcement, so the actual time is very likely to be even longer.
Roon is considerably more sophisticated in functionality and architecture than the other software players, so it is an even larger challenge to get it done.
1 Like
Roon has to unfold MQA soon! It is the only way to stop the endless stream of MQA threadsâŚNo doubt they will be replaced by another endless stream of âMQA sounds good/bad/whatâs all the fuss aboutâ threads.
2 Likes
Isnât the delay all due to business decisions right now? MQA wants money from all users of Roon and Roon wants to give money for users that uses MQA (or something similar)?
I would guess DSP after first unfold could also be a somewhat sensitive issue for the MQA guys.