#2 Missing bass below 20hz

[Neko Alosama]

I'm transitioning from using the ASH-Listening-Set to this project, so I've generated some HeSuVi BRIRs with KEMAR-N (PKU-IOA) since I used R32 ASH Listening Room KEMAR-N before. KEMAR-N (PKU-IOA) is surprisingly similar to KEMAR-L (MIT) for some reason, but the main issue I have is that I'm lacking infrasound compared to ASH Listening Room with both locations/sources. I'm unsure whether it's accurate for the KEMAR HATS to have such a dip, but it's probably not believable for less rumble to be heard/felt.

[Shanon Pearce]

I'm currently working on an update which will have the issue of reduced gain in sub bass fixed. I'm also aiming to have less roll off around the 20Hz region.

In regard to the similarities between KEMAR-N (PKU-IOA) and KEMAR-L (MIT), I'll verify that they have been named correctly as there is a chance the N and L could swapped. I also found that the front/back directions in the MMHR HRTFs were reversed which will be fixed in the next release.

[Neko Alosama]

I assume you're waiting for v2.2.1 or v2.3.0 to give me an update here, since it seems there are some bugs with the Acoustic Space parameter. Using "Outdoors" in the attached screenshot gives [INFO] Failed to export BRIRs, which should really be [WARN] or [ERROR]. I assume that that parameter is a replacement for the Target RT60 Reverberation Time (ms), and if it's just the same thing behind categories (like how the "Auditorium" setting gives me a HeSuVi BRIR of 1463.4 ms), I'd like to see the expected length in the UI. I also found the original parameter name in the "Project Samples".

List of Accoustic Spaces that I tested which cause a failed export:

• Concert Hall
• Hall
• Outdoors
  Seems to be long BRIRs which cause trouble.

[Shanon Pearce]

Thanks for bringing the failed export bug to my attention. I hadn't updated my hesuvi export function to support longer IR lengths which is preventing acoustic spaces with long reverb times to fail. It will be fixed in the next release.

The acoustic space parameter was intended to replace the target RT60 time parameter. The option to adjust RT60 time was removed from the GUI as it complicates things now that reverberation time varies across the different acoustic spaces. In the next release I will show the estimated RT60 time for each acoustic space in the GUI for reference.

The issue of reduced gain in low frequencies should be resolved in the current release however I'm looking into further improving the extension below 20Hz.

[Neko Alosama]

Should this ticket be closed now with the v2.3.0 release?

[Shanon Pearce]

Yes I will close the ticket now as the issue is resolved in the v2.3.0 release