theREALdotnet
Major Contributor
- Joined
- Mar 11, 2022
- Messages
- 1,710
- Likes
- 3,014
What is the reason for that?
See here, section 16 “Minimum Phase”. That explains it much better than I could.
What is the reason for that?
By "curtain" you mean the EQ'd frequencies, correct?@Acerun - I've noticed when curtaining with MQX, the corrected region can be raised in relation to the rest of the speaker range.
Open MQX and reconnect, then shift the range of the correction to see how it's affecting the volume level, try checking or unchecking "Disable Auto-Leveling" to see if that improves anything if there is a problem, or see if you can't find a curtain point that better maintains the volume balance.
This for me was an issue and partly because of it I ended up sticking with manual correction through MQX only.
By "curtain" you mean the EQ'd frequencies, correct?
I have found in the past, in my room, that I if I use tilt or a bass boost, I run into trouble if I include the subwoofer for that boost in MultiEQX. I "think" my subs are so good + room effects that I simply don't need the boost there and adding it seems to add bloat. I am playing with that now to try to tame things and find the right crossover and room response. Unclicking the Sub button for the extra EQ, but keeping the LRCS.Yes, EQ'd frequency range.
Btw, I always disable auto leveling, and add headroom. Looking more carefully at some of my previous measurements there may have been a little bit of user error so I am back and retest. Quick and dirty is looking like 60 may be the best cut over. That was where I crossed my m126be's as well.Yes, EQ'd frequency range.
Btw, I always disable auto leveling, and add headroom. Looking more carefully at some of my previous measurements there may have been a little bit of user error so I am back and retest. Quick and dirty is looking like 60 may be the best cut over. That was where I crossed my m126be's as well.

Not summed with the distance from MLP to speaker. They do a basic calculation of what the third length of that triangle (the point sound hits ceiling to the MLP) would be given the assumption of the typical upfiring speaker's baffle angle per Dolby, then use that distance plus the distance to ceiling as the expected arrival time.Would anyone be able to clarify Atmos enabled speaker distance settings for me.
In the Denon menu you can set distances for individual speakers, but in the case of Atmos enabled speakers there is an additional setting for distance to ceiling. Am I right in assuming this distance is then summed with the physical distance for appropriate delay?
View attachment 381039
You would expect Audyssey to also to capture the reflection and do its calculations based on that?Not summed with the distance from MLP to speaker. They do a basic calculation of what the third length of that triangle (the point sound hits ceiling to the MLP) would be given the assumption of the typical upfiring speaker's baffle angle per Dolby, then use that distance plus the distance to ceiling as the expected arrival time.
Whether they get it right is questionable. It's definitely closer than the first round of Atmos receivers that just assumed 9 foot ceilings and the customary "seated ear level" as a makeshift average, but I would still recommend tweaking that parameter with demo material on a loop to listen for which setting snaps the imaging into place... or better yet, using the Speaker Pairs tests on the Spatial Audio Calibration Toolkit to isolate each upfirer and its corresponding ear-level speaker so you can nail the delays. Upfirers can actually work pretty well if you get them lined up right, but most auto-cal doesn't quite get there.
No, capturing reflections seperately from the steady state room "curve" is tricky... that's where more sophisticated methods including DLBC and DLART come in.You would expect Audyssey to also to capture the reflection and do its calculations based on that?
To be fair, Audyssey is outdated where Atmos is concerned, in a lot of ways. Doesn't compensate for the differences in grazing incidence to the mic with heights, even in a general way. Throws off Atmos imaging when you use DEQ because of how they alter surround/height levels (which they have no supporting data for as far as heights because their research was done pre-Atmos). They basically shoe-horned makeshift solutions into their existing product. There are things you can do on your own to account for these things, but if you're expecting Audyssey to actually do anything other than iterate on what they already have out there, keep holding your breath.You would expect Audyssey to also to capture the reflection and do its calculations based on that?
indeed I had to manually change the atmos levels quite a bit to make it sound reasonably ok.To be fair, Audyssey is outdated where Atmos is concerned, in a lot of ways. Doesn't compensate for the differences in grazing incidence to the mic with heights, even in a general way. Throws off Atmos imaging when you use DEQ because of how they alter surround/height levels (which they have no supporting data for as far as heights because their research was done pre-Atmos). They basically shoe-horned makeshift solutions into their existing product. There are things you can do on your own to account for these things, but if you're expecting Audyssey to actually do anything other than iterate on what they already have out there, keep holding your breath.
If you're using upfirers, make sure MultEQ-X is putting the Dolby curve on those so that it doesn't undo any in-speaker frequency shaping. As far as Dirac, I have no hands-on experience with it.indeed I had to manually change the atmos levels quite a bit to make it sound reasonably ok.
The AV10 can also do Dirac, would it do better with the atmos channels?
To be fair, Audy does many things right, and many things wrong. It is up to you to figure out the balance. DEQ is not feature you have to use, it is clearly optional.To be fair, Audyssey is outdated where Atmos is concerned, in a lot of ways. Doesn't compensate for the differences in grazing incidence to the mic with heights, even in a general way. Throws off Atmos imaging when you use DEQ because of how they alter surround/height levels (which they have no supporting data for as far as heights because their research was done pre-Atmos). They basically shoe-horned makeshift solutions into their existing product. There are things you can do on your own to account for these things, but if you're expecting Audyssey to actually do anything other than iterate on what they already have out there, keep holding your breath.
This should not be the case.I'm finding that the settings that I need for 2.2 music and for home theater are completely different. (I watched The matrix last night with my music settings and was appalled).
Something is not right, likely settings and Audyssey related. Even my near bottom of the line x1800h can do an excellent job in 2.1 up to 7.1, as good as my main system. The 8500 is a flagship model, should be abe to do a much better job. Does it do better with Audyssy off?The only things that solve for this are two configuration files, but shockingly they can't even hold a candle through the way that movie used to blow through my chest. With all the highs and all the lows.