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

[Dumdum]

I’ll be impressed when I can input a test signal and route it to any channel or combination of channels as I can with most dsps, that way I can measure phase with Smaart without disconnecting speakers as I have to now

 

[Andysu]

I’ll be impressed when I can input a test signal and route it to any channel or combination of channels as I can with most dsps, that way I can measure phase with Smaart without disconnecting speakers as I have to now

just use the multi stereo mode on the avr that sends same sound generated mono signal to all speakers , put a speaker switcher box on the system so can flip a switch to mute certain speakers for testing

 

[just1n]

just use the multi stereo mode on the avr that sends same sound generated mono signal to all speakers , put a speaker switcher box on the system so can flip a switch to mute certain speakers for testing

This is a clever suggestion.

 

[Andysu]

This is a clever suggestion.

denon X3800H has multi stereo mode i used it all time when 8500h was in use now serves for laserdisc and VHS video mode hdmi to stormaudio
use that and all need is a behringer DCX 2496 for ( common LCR ) 2nd DCX for subs and two sidewall surrounds that will be connected for multi sidewall surround array
use A input for left surround , B input for LFE.1/sw extension , C input for right surround , 3rd DCX for , get the idea ? and each DCX has mute switch so can mute channels and frequency sweep pink noise until blue in the face with it , all these rubbish avr on the market have no mute switches for individual channels and no LED meters to see what is going on but LED VU meters on the DCX are not all accurate to few dB , ( i know what your looking for to listening for ) just brought the wrong avr/s i know

you want to hear , indiana jones and the last crusade with pin point dialogue panning , i know , you really want to hear ( last crusade with five screen wide ) but the avr can't do five screen wide only few processors can or few simple cheap x2 Dolby SDU4 will achieve this with five matching speakers behind the projection screen and then you can hear those , wow , wow dialog pans better than when it was shown 70mm format 43 with just three screen even thou that sounded wow in THX , i know , i know this is what your looking for and it's all on ebay 2nd-hand cheap just waiting to be , " grab it by the 2nd hand "and put it together , with JBL Jedi Blaster Lightsabers why else did Tom , George select JBL ? its Jedi speakers , i know , i know this is what your been looking for

 

[emptygreat]

Can anyone point me to a tutorial that explains how to take the measurements (I understand with EVO onwards you do it with REW)

Also - can it be done on a Mac? I notice there is a .bat script that must be run to read the config out of the AVR. Presumably that is windows only. It'l be a pain in the ass if I have to lug down my (now unused) tower PC to put it next to the AVR.

Ta Muchly.

If I recall correctly, OCA has covered it on some of his videos on previous versions of his calibration tools, so I'd start looking there!

You will also find some of the settings you should use in REW on the Nexus Changelogs, though the sweeps you'll be able to use depend a lot on your system (windows or Mac + if you have height speakers or not).
From your comment, sounds like it's a Mac, so if you don't have height channels, you can do it with REWs own sweeps. Do keep in mind that sometimes when you connect the AVR to a mac through HDMI, you might have center / LFE channels incorrectly mapped (swapped), but I believe this can be remapped in rew.

I was about to test Neuron yesterday with my current Nexus measurements, though apparently the Mac version hasn't been released yet. I've read some users were able to run using Wine, though if you're not in a rush, it shouldn't be worth the trouble, as OCA has suggested that a Mac compatible version should come out in a couple of days.

There has been some teasing that the new tool that comes with Neuron might help the process of measuring, and apparently a new video on it should come out soon, so I'd also recommend waiting for it to come out (and hopefully Mac compatible by then).

 

[antcollinet]

If I recall correctly, OCA has covered it on some of his videos on previous versions of his calibration tools, so I'd start looking there!

You will also find some of the settings you should use in REW on the Nexus Changelogs, though the sweeps you'll be able to use depend a lot on your system (windows or Mac + if you have height speakers or not).
From your comment, sounds like it's a Mac, so if you don't have height channels, you can do it with REWs own sweeps. Do keep in mind that sometimes when you connect the AVR to a mac through HDMI, you might have center / LFE channels incorrectly mapped (swapped), but I believe this can be remapped in rew.

I was about to test Neuron yesterday with my current Nexus measurements, though apparently the Mac version hasn't been released yet. I've read some users were able to run using Wine, though if you're not in a rush, it shouldn't be worth the trouble, as OCA has suggested that a Mac compatible version should come out in a couple of days.

There has been some teasing that the new tool that comes with Neuron might help the process of measuring, and apparently a new video on it should come out soon, so I'd also recommend waiting for it to come out (and hopefully Mac compatible by then).

Thanks for the info.

 

[Dumdum]

just use the multi stereo mode on the avr that sends same sound generated mono signal to all speakers , put a speaker switcher box on the system so can flip a switch to mute certain speakers for testing

That’s the same difference just with switches instead of unplugging a banana plug or seven

Manufacturers should make a solo menu so you can do it with a remote, it’s a given in all aftermarket dsps, why not put it into the AVR software, it’s a dsp after all at its heart

 

[Mike Lima]

If you have only have the MultiEQ version of Audyssey and do not have XT or XT32. A1 Evo Neuron will not work on your AVR.

 

[Flatlander]

I'm getting this message when importing an .ady file to the app – both from my phone and from Google Drive:

"The specified file is not located in the device's local storage or is not a proper curve file".

Does anyone know a solution to this?

 

[aarons915]

Some time ago I suggested a solution that would make it possible, to trick Audyssey even further, and make it correct a faked speaker response AND be able to switch between the Reference curve selection with the HF rollof and the Flat curve, without the rolloff.

Today I found a little time and it seems it is possible:

View attachment 405197


What you see here, is (ratbuddyssey for quick check if the injected data is working as intended) a EQed perfect speaker response injected into ADY!
The peak you see as speaker measurement, is a (fully deliberately set EQ (58 Hz, +12 dB, q 10, mimicking a measured room mode) applied to a perfect speaker response.

If loaded into MultEQ Audyssey will be interpreting this fake measured speaker response as a real response and will apply it's correction torwards removing the peak.

Intended benefits:

1. USER defines what Audyssey will correct (but not with the custom target curve, but with faked speaker measurements):
Only the filters the user wants, REW will apply. Everything else remains untouched as perfect speaker.
For example: if you only want to correct to 300 Hz, you only apply the EQs you want in REW to 300 Hz (in the example above a 58 Hz room mode was simulated and is all that Audyssey will see).

2. No longer unuseable FLAT curve. It should be possible to switch between FLAT correction (for music without hf rolloff) and Reference, with the hf rolloff.

3. You additionally even have the custom target curve available for the Reference-curve-mode, for further adjustments.

4. You are free to apply any EQ curves with/without house curve as you wish as fake speaker response in REW.


If there is interest I could post the detailed step by step procedure.

This is exactly what I'm trying to do with Audyssey, I've been using Equalizer APO so I'm not up to date on all these different ways of modifying Audyssey files but I'm not sure why more people aren't interested in this method considering you can use a Umik for higher res measurements in the bass and anechoic measurements above the transition frequency, a much better way of EQing.

Does Audyssey do a good job at flattening these PEQ peaks? I would love a quick write up when you have time. All I want Audyssey to do is take my flat response line with the PEQ filters I already have and am happy with (as peaks instead of cuts obviously) then filter them flat, essentially giving me the same result as manual PEQ filters, hopefully this can be done without the high frequency drop off as well.

 

[TheZebraKilledDarwin]

This is exactly what I'm trying to do with Audyssey, I've been using Equalizer APO so I'm not up to date on all these different ways of modifying Audyssey files but I'm not sure why more people aren't interested in this method considering you can use a Umik for higher res measurements in the bass and anechoic measurements above the transition frequency, a much better way of EQing.

I don't get it either.

Does Audyssey do a good job at flattening these PEQ peaks?

I checked the results with pink noise steady state measurements with Voxengo Span and there was no difference between the pink noise corrected with Kirchhoff-EQ and the Audyssey 'flat' correction.

But you must be aware, that the maximum correction for a fake speaker measurement (ADY: 'responseData') is 12 dB. If you need more than 12 dB, then the Reference mode with a customTargetCurve can be used to apply up to additional 12 dB; but then you have the hf-rolloff, which you probably want to compensate for with the custom target curve.

I would love a quick write up when you have time. All I want Audyssey to do is take my flat response line with the PEQ filters I already have and am happy with (as peaks instead of cuts obviously) then filter them flat, essentially giving me the same result as manual PEQ filters, hopefully this can be done without the high frequency drop off as well.

That would take some time.
But if your setup does not have too many different speaker EQ-curves, I would apply it to your ADY-file for you. About how many EQ-curves and speakers are we talking?

 

[aarons915]

I don't get it either.

I checked the results with pink noise steady state measurements with Voxengo Span and there was no difference between the pink noise corrected with Kirchhoff-EQ and the Audyssey 'flat' correction.

But you must be aware, that the maximum correction for a fake speaker measurement (ADY: 'responseData') is 12 dB. If you need more than 12 dB, then the Reference mode with a customTargetCurve can be used to apply up to additional 12 dB; but then you have the hf-rolloff, which you probably want to compensate for with the custom target curve.



That would take some time.
But if your setup does not have too many different speaker EQ-curves, I would apply it to your ADY-file for you. About how many EQ-curves and speakers are we talking?

12db is my largest single cut so that should be fine. Basically my EQ is identical for my Left, center and right channels, then I have a Surround EQ and my subwoofer, so really just 3 unique EQs. I do high pass my mains at 120 and low pass my sub at 90 but not sure that's possible in Audyssey

 

[TheZebraKilledDarwin]

12db is my largest single cut so that should be fine. Basically my EQ is identical for my Left, center and right channels, then I have a Surround EQ and my subwoofer, so really just 3 unique EQs.

Ok, that is no problem.

I do high pass my mains at 120 and low pass my sub at 90 but not sure that's possible in Audyssey

Yes, that could be a problem.
I have not tested, how Audyssey would handle a lowpassed sub responseData, if the f drops "too low early". Does it try to boost, before it gives up?

No time to test it, but I could make an ADY with a 90 Hz lowpassed fake sub responseData and you measure and check the result.

Why do you have the gap?

Have you tried the LFE-parameter in the bass settings on the AVR? I am not sure, but I think it works on the whole bass-managed signal, so maybe it works by setting the LFE lower.
Another option could be, that you use the lp on the sub.

 

[aarons915]

Ok, that is no problem.



Yes, that could be a problem.
I have not tested, how Audyssey would handle a lowpassed sub responseData, if the f drops "too low early". Does it try to boost, before it gives up?

No time to test it, but I could make an ADY with a 90 Hz lowpassed fake sub responseData and you measure and check the result.

Why do you have the gap?

Have you tried the LFE-parameter in the bass settings on the AVR? I am not sure, but I think it works on the whole bass-managed signal, so maybe it works by setting the LFE lower.
Another option could be, that you use the lp on the sub.

The high pass on most receivers is 2nd order while the low pass is 4th order so it's really just getting the proper blend, a 120Hz 2nd order high pass will be down 6 db at 90Hz, the same as the 90Hz 4th order low pass on the sub.

 

[aarons915]

Alright so I tried this method in the video but a little different, I made a flat line at 0db to use as my correction file, basically duplicating my parametric EQs I use in Equalizer APO with the peace addon for windows. This way you can basically manually EQ the response without allowing Audyssey to boost any frequencies or over correct the response.

After putting in my PEQ filters on the flat line, I exported the text files for each speaker and followed the rest of the procedure to make the response data show perfect. After uploading back to the app the before showed a flat line so I think it worked ok but every graph shows a weird rise in the last octave for some reason, I wasn't able to get rid of the high frequency roll off. It seems the Flat setting did nothing at all, my Reference setting EQ'd the subs really well but did almost nothing to my mains, I'm thinking this is because my receiver uses MultEQ and there just aren't enough control points available. @OCA I thought I heard you say in one of your videos that it doesn't matter with version of Audyssey you have but is that what you meant? If MultEQ only has a few dozen control points and my file was almost 500, it would explain why it didn't do much. It looks like it just used very low Q broad filters to try to compensate but didn't do a good job based on the pics below.

 

[scottinwales]

I'm getting this message when importing an .ady file to the app – both from my phone and from Google Drive:

"The specified file is not located in the device's local storage or is not a proper curve file".

Does anyone know a solution to this?

Did you find a solution to this? I'm in the same position. Thanks

 

[Bucking]

You could try another app version and see if that fixes it.

But I would look into A1 Neuron if I were you. No app required.