Audyssey Manual Calibration “OCA’s REW + Audyssey Awesomeness”

[Chromatischism]

I tend to get really good results with Audyssey. All I have to do is the sub distance tweak, counter the surround level increases, then adjust sub levels while going through various content I use for testing. Other than that, my results are predictable as I strictly control my room arrangement. But to make life better I would just like improvement in 2 areas:

1. Reduce the high-frequency increase from Dynamic EQ by about 50%, but keep the bass adjustments intact as the levels really are perfect
2. (optionally) cancel the surround speaker level adjustment from Dynamic EQ. I level this out myself in a few minutes with Dolby's white noise speaker test post-cal but automation is always nice!

Some toggle options would be really powerful, if it's possible to modify the .ady files in this way. If not, I'll live

 

[middlemarch]

Have any of the Mac users tried the EVO script yet? In Safari, at the .ady file upload phase, my script (version 1.3) saves the Target file but not the zip file with the measurements. I've pinged OCA but he's not familiar with the Mac. For the time being it does work using Edge in my Win11 VM. Mr. OCA suggested going to Facebook but I don't have an account there and would prefer not to. I've had no success searching on the AVS forum.

Anyone had success?

 

[Hyacin]

Have any of the Mac users tried the EVO script yet? In Safari, at the .ady file upload phase, my script (version 1.3) saves the Target file but not the zip file with the measurements. I've pinged OCA but he's not familiar with the Mac. For the time being it does work using Edge in my Win11 VM. Mr. OCA suggested going to Facebook but I don't have an account there and would prefer not to. I've had no success searching on the AVS forum.

Anyone had success?

I've not done it on Mac, but I've had the same issue on Windows - Firefox will absolutely not let me do the "site is trying to send you multiple files" that you see in the video at that step. My solution on Windows is to use Chrome instead. I'd think the same might work for you on Mac?

 

[middlemarch]

Good suggestion as to Chrome, used that on my Mac and it does the zip file correctly.

I then loaded all the files into REW and hit "optimize". Using either Chrome or Safari it goes to a certain point and everything just stops. Following from the log file:

1:16:43 PM [IMPORTANT!] 'Standard bass' mode with 1 subwoofer(s) detected.
1:16:43 PM [INFORMATION] Transposing measurements from <8> different microphone positions to the primary listening location (1st mic position)...
1:16:43 PM [INFORMATION] This will take a while but ensure 'direct sound' is prioritized with every measurement impulse.
1:16:43 PM [INFORMATION] Computing optimal spatial averaging configuration for speaker #1...
1:16:51 PM [INFORMATION] Computing optimal spatial averaging configuration for speaker #2...
1:16:59 PM [INFORMATION] Computing optimal spatial averaging configuration for speaker #3...
1:17:07 PM [INFORMATION] Computing optimal spatial averaging configuration for speaker #4...
1:17:15 PM [INFORMATION] Computing optimal spatial averaging configuration for speaker #5...
1:17:22 PM [INFORMATION] Computing optimal spatial averaging configuration for speaker #6...
1:17:30 PM [INFORMATION] Computing optimal spatial averaging configuration for speaker #7...
1:17:38 PM [INFORMATION] Computing optimal spatial averaging configuration for speaker #8...
1:17:46 PM [INFORMATION] Computing optimal spatial averaging configuration for speaker #9...
1:17:54 PM [INFORMATION] Computing optimal spatial averaging configuration for speaker #10...
1:18:02 PM [INFORMATION] Computing optimal spatial averaging configuration for speaker #11...
1:18:10 PM [INFORMATION] Computing optimal spatial averaging configuration for speaker #12...
1:18:18 PM [INFORMATION] Computing optimal spatial averaging configuration for speaker #13...
1:18:25 PM [INFORMATION] Computing optimal spatial averaging configuration for speaker #14...

I'm at a loss, so I guess will have to give it up for a while.
I'm using REW v5.40 Beta 31, the latest

REW seems to stop doing the first excess phase calculation? not sure what's going on

 

[middlemarch]

Just re-did the whole shootin' match from within my Win11 VM and it ran successfully to conclusion with not even any warnings. Now to see how it sounds! Took 336 seconds under emulation for 14 speakers and eight positions.

Looks like the Mac version still needs some more polish, looking forward to playing with this natively, but in the meantime I'll take it.

 

[Kayshot]

After reading some posts from people stating Audyssey One yielded more clarity than Evo, I decided to give it a shot.

Audyssey One's results came out with much higher clarity. Not just the high-end frequencies, but the dynamic range. Snare's can really hit now, vocals can jump out whereas EVO had everything pulled back. The imaging even seems wider now, though that could just be a result of the mids/highs being able to breathe better.

Where EVO takes the cake is bass response (with a caveat). EVO boosted my subs to a whopping +3.5dB! Bringing it down does not bring the mids/highs back to life.
A1 only set it to -4.5dB, which sounds great when bumped up to -2dB.

So why do I say EVO does better with bass? Well, the response I'm getting seems to be flatter and more consistent. Just too damn loud. Not sure if that's what's sucking the life out of the mids/highs, but I have a hunch it's related.

The clarity and dynamic range that A1 gives me far outweigh the more consistent bass response I get with EVO 1.3, so I will stick with A1 1.3 for now.
I'm keen to follow the updates to EVO though, as it does look like they are working out bugs currently.

Note: I used MiniDSP 2x4 HD to align level match and align my subs. I first tried EVO with a house curve, then EQ'd to flat, then eventually got the best results by only level-matching and aligning with MiniDSP (zero EQ done). I let EVO handle the EQ. Same route was taken for A1.

 

[ooheadsoo]

My HTPC is an older PC machine which also stopped computing at some point, so I switched to my newer computer, which was able to calculate things to completion. Whoa, what a change to the bass! I actually think there is now too much sub-bass content and am on the verge of turning the subs down. But this is a much more pleasant problem than what I had with native Audyssey calibration!

 

[antcollinet]

Have any of the Mac users tried the EVO script yet? In Safari, at the .ady file upload phase, my script (version 1.3) saves the Target file but not the zip file with the measurements. I've pinged OCA but he's not familiar with the Mac. For the time being it does work using Edge in my Win11 VM. Mr. OCA suggested going to Facebook but I don't have an account there and would prefer not to. I've had no success searching on the AVS forum.

Anyone had success?

Same problem with Safari. I used Brave.

 

[middlemarch]

Which I think has Chrome underpinnings, which also worked (as far as the zip file) for me.

Having said that, following the success with the win11 version of things, I compared the standard Evo version to my 500Hz limited Audyssey version. The Evo version is very forward and bass shy. To the point of being unpleasant and "shouty" on my system. The standard Audy version also has issues, but currently preferred. Will have to try some other house curves. Clearly this is no silver bullet for me, the adventure continues...

 

[EasyC]

I've ran A1 and Evo on a M1 MacStudio in Arc - also a chrome based browser - without any problems.
Evo sounds best to me, although I had to take the subwoofers 1-2dB down with evo. Best sound overall though, and all provide better results than standard Audyssey with my system. I've done the measurements in directional bass mode, which measures my 2 subs independently. Evo then switches that to standard mode. I previously used the Harman curve, with evo I used the curve OCA provided.

Sometimes the script doesn't run well if REW hasn't got enough RAM allocated to it. I use 1.5Gb, but I've seen reports of 4 to 8Gb. You can set that when installing REW, but beware to use the right version beta: Evo uses beta 30, A1 uses beta 21.

(edit: spelling - not my native language)

 

[antcollinet]

Which I think has Chrome underpinnings, which also worked (as far as the zip file) for me.

Having said that, following the success with the win11 version of things, I compared the standard Evo version to my 500Hz limited Audyssey version. The Evo version is very forward and bass shy. To the point of being unpleasant and "shouty" on my system. The standard Audy version also has issues, but currently preferred. Will have to try some other house curves. Clearly this is no silver bullet for me, the adventure continues...

I found the same until I used a Harmon target. Perfect now.

 

[middlemarch]

(edit: spelling - not my native language)

Ik kan ook en beetje Hollands verstaan, was in Friesland geboren... (edit: spelling as well, but it's been over 60 years...)

But question: You've been succesfull running Evo on your M1 Studio. When I try (M1 Pro MBPro), I get the hang I show in Post 284. I'm using Evo 1.3 and REW 5.40 beta 31. Using Chrome, but same behavior in Safari. What versions are you using? or is there another trick I haven't run across yet?

 

[EasyC]

Ik kan ook en beetje Hollands verstaan, was in Friesland geboren... (edit: spelling as well, but it's been over 60 years...)

But question: You've been succesfull running Evo on your M1 Studio. When I try (M1 Pro MBPro), I get the hang I show in Post 284. I'm using Evo 1.3 and REW 5.40 beta 31. Using Chrome, but same behavior in Safari. What versions are you using? or is there another trick I haven't run across yet?

Niet slecht voor 60 jaar geleden

But about your question: I think it's very important to use the exact REW beta version - so beta 30 with EVO 1.1. The MB Pro should be able to run it. My Mac does it effortlessly. For my system I need 72 measurements (5.2.2) to import into REW. Maybe you've got many more? That's the only two differences I can think of.
OCA is still working on it btw, he's on 1.3 now and 1.4 has been announced. It's evolving as we speak...

 

[middlemarch]

But about your question: I think it's very important to use the exact REW beta version - so beta 30 with EVO 1.1. The MB Pro should be able to run it. My Mac does it effortlessly. For my system I need 72 measurements (5.2.2) to import into REW. Maybe you've got many more? That's the only two differences I can think of.

I think you're right, just haven't hit the right combination yet. Runs OK in Parallels for now. I've been playing and running multiple configurations. Noticed I get different results on different runs. Been following the action on AVS Forums (just not very scientific and disciplined over there, but very enthusiastic). Many suggest the first REW run has issues. So I've done the second run thing, which has totally different results from the first run, including telling me to invert the polarity of my "sub" (actually 4 subs showing as one via MiniDSP 2x4HD).

So I'm left with which is correct? Are any correct? What does "correct" even mean? So my next step is to measure the different versions via REW and compare reality that way, and of course listening. First version I listened to was a DEQ0 version, which I did not like at all.

I'm looking forward to the next version of both the script and REW. It's clear this is an evolving work-in-progress. Maybe I'll back off a bit and wait for this thing to settle out a bit. It is kind of fun, though. Reminds me of when I was working, doing a lot of software debugging. Serko and John M are doing pretty amazing work in my opinion.

En bedankt, hoor! Most of my cousins still live in Nederland, including Amsterdam. Don't know if you've heard of Joke Tjalsma, she's one of them. An actress. So I do occasionally get a chance to keep up the language somewhat. Hard though, most Dutch folks anymore speak better English than many Americans.

 

[OCA]

I think you're right, just haven't hit the right combination yet. Runs OK in Parallels for now. I've been playing and running multiple configurations. Noticed I get different results on different runs. Been following the action on AVS Forums (just not very scientific and disciplined over there, but very enthusiastic). Many suggest the first REW run has issues. So I've done the second run thing, which has totally different results from the first run, including telling me to invert the polarity of my "sub" (actually 4 subs showing as one via MiniDSP 2x4HD).

So I'm left with which is correct? Are any correct? What does "correct" even mean? So my next step is to measure the different versions via REW and compare reality that way, and of course listening. First version I listened to was a DEQ0 version, which I did not like at all.

I'm looking forward to the next version of both the script and REW. It's clear this is an evolving work-in-progress. Maybe I'll back off a bit and wait for this thing to settle out a bit. It is kind of fun, though. Reminds me of when I was working, doing a lot of software debugging. Serko and John M are doing pretty amazing work in my opinion.

En bedankt, hoor! Most of my cousins still live in Nederland, including Amsterdam. Don't know if you've heard of Joke Tjalsma, she's one of them. An actress. So I do occasionally get a chance to keep up the language somewhat. Hard though, most Dutch folks anymore speak better English than many Americans.

If you get 0ms result in either of the impulse or phase alignment steps, it's probably a bugged result. There were issues with alignment tool APIs, script itself and additional issues from user set ups including and not limited to OneDrive and adblockers. Majority are all fixed now for v1.4, awaiting next REW beta release.

 

[middlemarch]

Majority are all fixed now for v1.4, awaiting next REW beta release.

Thanks Serko, looking forward to trying them out. It must be maddening to be in the middle of developing something like this with all the different platforms and variables at play. Just remember, none of this is life or death for those of us on the receiving end of your good work. Please keep it up, it's well appreciated, a case of the journey being as much fun as the final result. At least it is for me. Listening to one of your non DEQ versions at the moment and enjoying it very much.

All the best.

 

[Peupeut]

Hello @OCA !!

Thanks a lot for the updates of One Evo, everything is great now!! No more Subs leveling issue, the result is absolutely amazing! I am playing a lot with it!
I have run it with 3 different target curves: the "OCA" one, the "Harmann" one, the "Toole" one (even if we are not supposed to use this name anymore ...). For my room and my system, I found the Toole one the more pleasant, so I kept this one.

I have also played with your script and tried a "Full Range" correction. I agree with all the comments you made, it sounds much less impressive, it narrows everything!

...however....

... I have a problem: I have built my system incrementally, and the first system I used was before reading ASR. It is because I was disappointed by the sound that I came to this forum. Today I am using remaining parts of this system for my 4 surrounds speakers: 4 Bowers & Wilkins ML1 Mark2 speakers. I kept them because they have a ratio dimensions/form factors/power/distortion that is practical for me, these are installed into the bookshelfs behind the sofa. However, I am totally aware these are "hoe" speakers with over brillance. And I have noticed that specifically for those 4 speakers, the full range correction have improved the percieved sound, not destroyed it.

I am not in position anymore to buy 4 new additional speakers. So my question is:

From the same original .ady file, if I run 2 "Evo1" scripts, the first with correction up to 225Hz as you have built it and the second one "Full Range"up to 20,000Hz, can I import the 4 surrounds filters from the Full Range into the classical 225Hz corrected .ady file?

Can I use the old script "CorrectThem.html" that you made last year for that? Will it destroy all the good parameters Evo1 is producing?

(my intent was to copy the 225Hz filters for Fronts, center, atmos and subs and the Full Range filters for surrounds, in a same folder and then to run CorrectThem on the "225Hz" XXXXXX_A1_evolved.ady )

 

[OCA]

It's easier and would sound better if you could tame the brigthness by adjusting their toe in angles but if you really have to filter them, you can optimize twice one with 225Hz and the next with extended range. Then open jsononline editor, put two ady files them side by side and copy/paste/replace the extended range filters you need to the required speakers - customTargetCurvePoints with 1532 items in them.

 

[Peupeut]

Oh yes!! I forget I had the json editor solution!!! Thanks a lot!!!

And a Super Thanks for your Youtube channel

 

[PHD]

Hi

Does the 255Hz limit in v1.4 only apply to the A1 script optimization or does the script also defeat the original Audyssey optimization beyond 255Hz?

Can I use A1 for 20Hz to 255Hz optimization and then use MultiEQ app for the remaining freq gange? I do notice an improvement up to 500Hz with the Audyssey app.

Thanks