In Reply to: Hey JimiAustin: MQA Enabled ADCs posted by Isaak J. Garvey on October 30, 2016 at 22:49:49:
Isaak,
in one of the numerous MQA threads I posted that the biggest problem with MQA is that it is too clever for most to understand.
The real problem with MQA is that is, IMO, really two functions:
1. An end-to-end temporal response with minimal 'blurring', to use Bob Stuart's phrase.
2. An encoding scheme that reduces the file size/bit-rate to below that of conventional 'hi-res' files.
Maybe the implementation of the two functions are so intertwined that they are one thing. It certainly seems that all interviews and publicity treat it as one thing (maybe to its detriment?)
An ADC is still an ADC. The answer in the linked interview does not state there is anything special about the ADC function for MQA except 'low modulation noise', i.e. it should be a good ADC. So, in those terms, Jim was correct, your original question does not make sense.
What I think the talk of an MQA-enabled ADC is about is, at minimum, having a defined temporal response or, at maximum, building the encoding process into the ADC so that output data rate is already reduced and the metadata included for the decoder to know what reconstruction filter response to adopt to compliment the ADC without the need to add that during mastering.
Regards
13DoW
This post is made possible by the generous support of people like you and our sponsors:
Follow Ups
- RE: Hey JimiAustin: MQA Enabled ADCs - 13th Duke of Wymbourne 18:09:21 10/31/16 (4)
- RE: Hey JimiAustin: MQA Enabled ADCs - Jim Austin 15:40:10 11/01/16 (0)
- RE: MQA Enabled ADCs - John Atkinson 09:29:45 11/01/16 (2)
- RE: MQA Enabled ADCs - 13th Duke of Wymbourne 18:15:35 11/02/16 (0)
- RE: MQA Enabled ADCs - bjh 20:18:49 11/01/16 (0)