Hi-Rez Highway

New high resolution SACD releases, players and technology.

Use this form to submit comments directly to the Asylum moderators for this forum. We're particularly interested in truly outstanding posts that might be added to our FAQs.
You may also use this form to provide feedback or to call attention to messages that may be in violation of our content rules.

You must login to use this feature.

Inmate Login

By default, logging in will set a session cookie that disappears when you close your browser. Clicking on the 'Remember my Moniker & Password' below will cause a permanent 'Login Cookie' to be set.

Moniker/Username: The Name that you picked or by default, your email. Forgot Moniker?	Examples "Rapper", "Bob W", "joe@aol.com".
Password:	Forgot Password?
	Remember my Moniker & Password ( What's this?)

If you don't have an Asylum Account, you can create one by clicking Here.

Our privacy policy can be reviewed by clicking Here.

Inmate Comments

From:
Your Email:
Subject:

Message Comments

Original Message

Decoding MQA in the TIDAL player....

Posted by Ivan303 on July 14, 2017 at 06:47:04:
uses significantly more CPU time than playing 16/44.1 tracks. Obviously my MacBook Air with the slowest CPU available at the time (mid 2011) is going to have a larger percentage of CPU time used to decode MQA in TIDAL than my recently purchased maxed out i7 iMac.

But still, it's using at least 3 time the resources to stream MQA and decode it in the player that it is to just stream 16/44.1, or so it would seem. Enough to make the fan come on. But that happens when I streaming a YouTube video and have a dozen Firefox tabs open anyway.