Documentation
Documentation
Documentation
Documentation
Documentation
Documentation
It looks like I broke backwards compatibility when I was updating the metadata for the acoustic spaces. Im preparing a new release which will have additional acoustic spaces. Atrium was renamed to atrium A in the new list which means the original value is no longer in the list so it threw an error. Ive also added some validation in the code so this kind of error won't happen in future. A short term fix is to replace the metadata file with the previous version which Ive attached. It goes in this folder:...
Also the log.log doesn't really say anything. 2025-06-04 07:49:10 - root - INFO - Started 2025-06-04 07:49:10 - pyi_splash - INFO - A connection to the splash screen was successfully established. 2025-06-04 07:49:10 - root - INFO - Splash screen closed. 2025-06-04 07:49:10 - root - INFO - Started ASH Toolset - Version: 3.2.0
''Attritum' is not in list' Unhandled exception in script
Documentation
Documentation
Documentation
Documentation
Documentation
Documentation
Documentation
Documentation
Documentation
Documentation
I will adjust the colours in the next release to ensure each tab has a consistent colour theme. The apply/process buttons & bars will be updated
Two different primary colors, one is greener than the other
Documentation
Documentation
Documentation
Documentation
Missing bass below 20hz
Yes I will close the ticket now as the issue is resolved in the v2.3.0 release
Should this ticket be closed now with the v2.3.0 release?
Should this ticket be closed now?
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...
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 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...
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...
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...
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...
Documentation
Documentation
Documentation
Documentation
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.
Missing bass below 20hz
Documentation
Documentation