Denon Marantz speaker distance bug (fixed in 2023 avr-x800 models) - instructions to address in older AVRs

[pat bateman]

Why wouldn't Denon just push a firmware update to fix this?

 

[FooBarFoo]

Would be nice, right? Maybe it's hard coded in a rom?

Maybe they are hoping that fixing it moving forward will drive "upgrade" sales, lol.

 

[Mackspower]

For those interested . . . here is the original quote direct from the motherland:

"This measurement sound speed is set to 300 m/s instead of 343m/s due to CPU power and calculation time. For the MultiEQ-X App, a multiplier is used that reduces conversion errors depending on PC performance, so distances close to expected values are calculated. The error in speaker distance you pointed out has a low impact on the audio delay, so this is the current specification.
We apologize for the inconvenience, but please use the MultiEQ-X App if you wish to obtain accurate speaker distance by Auto Setup."

 

[FooBarFoo]

For those interested . . . here is the original quote direct from the motherland:

"This measurement sound speed is set to 300 m/s instead of 343m/s due to CPU power and calculation time. For the MultiEQ-X App, a multiplier is used that reduces conversion errors depending on PC performance, so distances close to expected values are calculated. The error in speaker distance you pointed out has a low impact on the audio delay, so this is the current specification.
We apologize for the inconvenience, but please use the MultiEQ-X App if you wish to obtain accurate speaker distance by Auto Setup."

Translation:

"We messed up, we got caught, so let's blame technology limitations to make it seem intentional. (The amount of cpu needed to calculate speaker distance based on 300m/s vs 343m/s should be VERY similar if not exactly the same.).

Thankfully, due to the massive breakthroughs in modern cpu processing power, our new air cooled quantum computers in the x800 series systems can correct for this.

In the meantime, please pay $200 to fix our mistake.