The .ady file is essentially a JSON data file. It stores all the FIR filters for every channel, among other settings. These filters are loaded and processed by the receiver exactly as they appear in the file. The real limitation comes from the total number of samples available in each filter impulse response.
For example, the basic EQ speaker filters only have 128 taps which is easy to verify directly from the .ady file. At a sampling rate of 48 kHz, the lowest frequency a 128-tap filter can meaningfully correct is:
48,000 Hz / 128 = 375 Hz.
That’s just fundamental DSP math.
The surprising part is that the units also include internal mechanisms capable of running FIR filters at lower internal sampling rates, such as 6 kHz, effectively giving the filter 8× more usable resolution. Because of this, my initial assumption was that the basic EQ was processing those 128-tap filters at 6 kH just like the subwoofer filters allowing correction up to 3 kHz, which is honestly fine for most EQ tasks. Evo was even designed that way initially as I was certain that should be the method (I do not have basic or XT to test it myself)
But this is where things got confusing.
Users with XT or basic EQ systems eventually measured the post-calibration responses and noticed that the filters weren’t behaving as expected. After a lot of testing, it turned out the filters were not being downsampled. They were being processed at the full 48 kHz, which cripples their low-frequency capability. That means:
• EQ (128 taps): correction limited to ~375 Hz
• XT (512 taps): correction limited to ~93 Hz
Given what the hardware is clearly capable of, it’s frustrating to see them being left like that. Whether it’s oversight or deliberate is beyond me. Having said that, it's possible (although highly unlikely) that about 10 XT users all measured their systems wrong multiple times or a firmware update might silently fix it at some point especially now that people are hearing about it. So, people with these units should keep testing IMO.
For example, the basic EQ speaker filters only have 128 taps which is easy to verify directly from the .ady file. At a sampling rate of 48 kHz, the lowest frequency a 128-tap filter can meaningfully correct is:
48,000 Hz / 128 = 375 Hz.
That’s just fundamental DSP math.
The surprising part is that the units also include internal mechanisms capable of running FIR filters at lower internal sampling rates, such as 6 kHz, effectively giving the filter 8× more usable resolution. Because of this, my initial assumption was that the basic EQ was processing those 128-tap filters at 6 kH just like the subwoofer filters allowing correction up to 3 kHz, which is honestly fine for most EQ tasks. Evo was even designed that way initially as I was certain that should be the method (I do not have basic or XT to test it myself)
But this is where things got confusing.
Users with XT or basic EQ systems eventually measured the post-calibration responses and noticed that the filters weren’t behaving as expected. After a lot of testing, it turned out the filters were not being downsampled. They were being processed at the full 48 kHz, which cripples their low-frequency capability. That means:
• EQ (128 taps): correction limited to ~375 Hz
• XT (512 taps): correction limited to ~93 Hz
Given what the hardware is clearly capable of, it’s frustrating to see them being left like that. Whether it’s oversight or deliberate is beyond me. Having said that, it's possible (although highly unlikely) that about 10 XT users all measured their systems wrong multiple times or a firmware update might silently fix it at some point especially now that people are hearing about it. So, people with these units should keep testing IMO.