Audyssey One - Nexus (Automated hi-res Denon/Marantz calibration with REW/Umik-1/2)

[anphex]

Any idea why Neuron 3.1 goes completely wrong here? I wanted to try real measurements made with measurement mic and REW, using timing reference, naming, sorting, but I always run into this problem. Doesn't happen when I use Audyssey extracted measurements.

Here is the .mdat file: https://anphex.one/index.php/s/wifcjK5NH73CLNk

 

[OCA]

If you are using the latest REW Beta (78) some important API endpoints have changed syntax and will cause errors with Neuron which I no longer update. You should use Acoustica with the latest REW.

 

[anphex]

If you are using the latest REW Beta (78) some important API endpoints have changed syntax and will cause errors with Neuron which I no longer update. You should use Acoustica with the latest REW.

The very same thing happens n Acoustica with Beta 78 with the same measurements. It happens once the first "A times B" appears.

 

[OCA]

The very same thing happens n Acoustica with Beta 78 with the same measurements. It happens once the first "A times B" appears.


View attachment 448439

Something is wrong with your setup, maybe measurement naming since this is the first stage before saving pre-processed mdat but not something that happens to anyone else.

 

[anphex]

@OCA Hmm it's weird, REW seems to enter an unstable behaviour after the first sw250Hzfix is being applied. The measurement, in my case index 44, is created and looks valid but starting from this point REW isn't really usable anymore and has trouble displaying any graphs. Doesn't happen with the Audyssey AVR measurements. The rendering of graphs completely breaks too.

Edit: I just used acoustica with the prior Audyssey odd.wtf measurements and there it doesn't set the speakers to "Small" nor does it enable "LFE + Main". Intended behaviour or quirk again? Oh well, I just set it manuallto "small" and crossovers where okay and it sounds fine!



(index):3521 POST http://localhost:4735/measurements/44/command 400 (Bad Request)

	fetchWithRetry	@	(index):3521
	fetchWithRetry	@	(index):3544
	await in fetchWithRetry
	postNext	@	(index):3565
	fixSubs4REW	@	(index):2794
	await in fixSubs4REW
	main	@	(index):1371
	setTimeout
	progress2	@	(index):1328
	checkRewMeasurements	@	(index):1328

Dunno what breaks here, but it seem some operation inside REW is going horribly wrong.

 

[OCA]

If this is Acoustica, my guess is that "trim Ir to windows" command is failing which indicates something fundamentally wrong with your measurement structure, as no user has reported this issue and hundreds are running the same script daily. Graphs are blocked by the script during optimization and will not get unblocked on uncaught errors. This is what is happening with REW after the error. I’d need your .mdat and .avr files and details of your platform/browser to identify your mistake, but I simply can’t help debug errors additionally on this platform due to time constraints. Check the app and you can find where to report such issues and get support.

 

[middlemarch]

@OCA, you old devil! I'd been under the assumption you were probably in your thirties given your energy level, but come to find out you're 55 years young today! Makes your work output even more amazing! Happy Birthday! And happy to report I'm running Acoustica V5 with my own tweaked Target Curve. I added a slope UP from 1.5K to 10K to help compensate for my old fart hearing loss, and it's working pretty good! I just spent four hours listening to my Mark Knopfler station on Pandora using mostly the Auro3D upmixer and it was Glorious! Very happy! Again, Happy B'day to you, sir!

 

[anphex]

Hi @OCA,

I have a quick question regarding my subwoofer distance after calibrating.

Problem Description:After calibration, my subwoofer is displayed with a distance of 9.99m in the Distances menu. If I open this menu after uploading the calibration data to my AVR (Denon AVR-X2800H), the AVR immediately flags this value as invalid. Consequently, I'm now avoiding opening that menu after uploading the calibration.

My Question/Suspicion:Does this maximum value of 9.99m indicate that my subwoofer's internal signal processing (delay) is very long, and even with the hack tool, Audyssey has reached the maximum possible delay time it can set?

Edit: I forced the lowest crossover search to 60 Hz and now the distance is 9,29m and it sounds just perfect. So it actually IS an incredibly slow processing of the soundbar.

Background on My Setup:I'm using a "repurposed" soundbar (more accurately, a rather large soundbase) as a subwoofer because it goes down to 30 Hz at -3dB. The sound is fine, and all settings from version 5 of Acoustica were uploaded cleanly to my AVR-X2800H.


Additional Consideration:I'm currently unsure whether I should continue using the soundbar as a subwoofer or remove it. My main speakers (KEF R3), located in the same room (bedroom), measure down to a pretty clean 40 Hz due to wall reinforcement. Would it perhaps be more ideal to forgo the soundbar as a subwoofer, or does it still offer advantages despite the 9.99m distance reading?

Thanks in advance for your assessment and help!

 

[OCA]

Hi @OCA,

I have a quick question regarding my subwoofer distance after calibrating.

Problem Description:After calibration, my subwoofer is displayed with a distance of 9.99m in the Distances menu. If I open this menu after uploading the calibration data to my AVR (Denon AVR-X2800H), the AVR immediately flags this value as invalid. Consequently, I'm now avoiding opening that menu after uploading the calibration.

My Question/Suspicion:Does this maximum value of 9.99m indicate that my subwoofer's internal signal processing (delay) is very long, and even with the hack tool, Audyssey has reached the maximum possible delay time it can set?

Edit: I forced the lowest crossover search to 60 Hz and now the distance is 9,29m and it sounds just perfect. So it actually IS an incredibly slow processing of the soundbar.

Background on My Setup:I'm using a "repurposed" soundbar (more accurately, a rather large soundbase) as a subwoofer because it goes down to 30 Hz at -3dB. The sound is fine, and all settings from version 5 of Acoustica were uploaded cleanly to my AVR-X2800H.


Additional Consideration:I'm currently unsure whether I should continue using the soundbar as a subwoofer or remove it. My main speakers (KEF R3), located in the same room (bedroom), measure down to a pretty clean 40 Hz due to wall reinforcement. Would it perhaps be more ideal to forgo the soundbar as a subwoofer, or does it still offer advantages despite the 9.99m distance reading?

Thanks in advance for your assessment and help!

Subwoofer distances are inherently longer than their actual physical distances due to large drivers and active filters in them but Acoustica adjusts sub distance to compensate for dips in speaker responses and will often add up further delays. Generally ,the longer the sub distance, the tighter bass you will end up with.

 

[anphex]

Subwoofer distances are inherently longer than their actual physical distances due to large drivers and active filters in them but Acoustica adjusts sub distance to compensate for dips in speaker responses and will often add up further delays. Generally ,the longer the sub distance, the tighter bass you will end up with.

Thank you! My question was wether 9,99m is the actual peak value you can use with Audyssey and that my sub at 40 Hz might have needed more delay offsert than Audyssey/Acoustica could provide. A warning in the logs in that case would be nice so the user get's an alert when something goes off the given parameters and the calibration is reaching extreme values.


Edit: Another, maybe silly, quetsion: I made the manual REW measurements which caused crashes in the optimization (a few posts above) like this: I didn't use the dolby sweep but used internal REW 256k Sweeps with acoustic timing reference. Was that the culprit?