Home
AudioAsylum Trader
Critic's Corner

Discuss a review. Provide constructive feedback. Talk to the industry.

For Sale Ads

FAQ / News / Events

 

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


Login to access features only available to registered Asylum Inmates.
    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

RE: Likely an ignorant comment by me.

Posted by Charles Hansen on June 6, 2017 at 12:57:55:

>> At this point I don't know how MQA works. Is it employed during the recording stage, mixing or mastering stage? Has zilch to do with any of that and is just employed in playback? <<

The short answer is that it applied at the mastering stage. The long answer is that MQA seems to have morphed over time, and as such is something of a moving target in attempting to understanding how it works. I believe that the original intent of MQA was to reduce the file size to allow easier streaming. Some time after MQA was announced, the goals were expanded to also improve the sound quality of existing files by performing digital filtering to "correct" for "errors" created by the A/D converter. Now it appears that they have expanded the goal even more by employing digital filtering to "correct" for the "errors" in the D/A converter also. Looking at those goals separately:

1) Regarding file size reduction, this success of MQA would seem to be dependent on the sample rate and bit depth of the original source file. The clearest case is when starting with a double-rate, 24-bit file (eg, 88/24 or 96/24) that the file size is reduced by ~30% because the bit depth is reduced to ~17 bits (one form of lossy compression). Quad-rate, 24-bit files have greater compression ratios because the audio data in the very top octave is compressed using lossy methods similar to MP3, which can achieve compression ratios of 10:1. In that case a quad-rate MQA-processed file will not be much larger than a double-rate MQA-processed file. While the resolution is still reduced to ~17 bits, this situation allows for the greatest file size reduction. It is unclear if there is any file size reduction for single-rate files. It appears that Redbook (44/16) files would actually increase in file size, while 44/24 and 48/24 files may again reduce the file size slightly due to the reduction in bit depth to ~17 bits.

2) Regarding improving the sound by way of using digital filters, this has been an area of interest for many decades. Both Wadia and Theta began producing D/A converters with custom digital filters in the late 1980s. Wadia specifically focused on improving the time-domain performance, just as MQA is currently claiming to do. Historically, the use of these types of digital filters that improve time-domain performance have been restricted to D/A converter manufacturers that possessed the resources to design and manufacture custom digital filters. When looked at from this standpoint, MQA is simply a third-party company offering to license the custom digital filter they have developed to any D/A manufacturer who wishes to use it.

One interesting note is Auralic. They originally had planned to support MQA but it turned out that the MQA requirements conflicted with features that Auralic were developing. Auralic has therefore implemented their own version of decoding MQA-encoded files. See link below for more information.

As always, strictly my own opinions and not necessarily those of my employer or stuffed animals.