Hi, has the Denon distance bug been fixed in the latest MultEQ App?
Sorry about my long response, can't help it..
From what I gathered, based on at least one post on AVSF (it was a long ago so it might have been another forum) in which the poster included a response from D+M)Denon/Marantz did not seem to consider that an issue, but quite a few AVSF members were convinced that it was, I debated one or two of them but gave up after realizing there's no way to change their mind, when they just believed some smaller errors in distances would result in terms of audible performance issues.
My main reason of agreeing with D+M is that a) if they really thought it was a real issue, they would have fixed it in a heart beat in one of the many FW updates, instead of taking their time, b) no one knows for sure why D+M's MultEQ Editor app developer would be so silly to have the app/mic measured delays, then convert delays to distance, then send file to the AVR, then the AVR converts distance back to delays, why wouldn't they just let the app send the data in delays (seconds) so the AVR's DSP doesn't need to do another conversion? Those avsf believers just assume that's how it's done, ie. convert time delay to distance and the back to distance. But even if that is true, why they believe the 300 m/s vs 343 m/s speed of sound used would make the kind of audible difference they claimed to be so audible, even night and day kind of difference some claimed? To me, it's again the powerful Placebo effect at play. There is a c), that is, room correction systems, regardless of whether Audy, DL, AARC, even Trinnov are going to be that accurate anyway when they have to deal with so many factors, 14% error in time delays used in calculating the filters are going to be very minor, relative to many other factors such as how the user takes his measurements (mic positions, room acoustic, speakers, subwoofers characteristics, accuracy of mic, temperature of the room, (its effects on speed of sound lol..), etc.
b) is the important point that believers never bother confirming how it's done. If the app send the data without converting time to distance, then the speed error used obviously doesn't matter and in that case D+M's distance display is simply their preference since day one, like others, for whatever reasons. I wish they all just display delays in seconds instead of distance. The choice of distance is the reason we keep seeing people complaining about Audyssey and other RC's not accurate when they checked their distances with a measuring tape, and then other forum members would tell them not to worry, RC systems actually measure time delays, no physical distances bla bla bla...
Regardless, if you are a believer in that too, and want to be sure, just contact Denon or Marantz, or both and if you insist on getting an answer, you will get it though you might have to ask them to get the official answer from the level two agents. It is better to ask both Denon and Marantz, because in that case you would likely reach two customer service reps hence double your chance of getting the correct answer.
