Skip to content

SQAT v1.1

Latest
Latest
Compare
Choose a tag to compare
@ggrecow ggrecow released this 29 Jan 13:05
· 58 commits to main since this release
v1.1
c47dac3
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.

Additional features (and modifications necessary for that)

  • Loudness_ISO532_1: the third octave band calculation used in this code was re-coded into an standalone function and placed in the sound_level_meter folder. The name of the function is Do_OB13_ISO532_1.m. This allows for its flexible use on other codes, including for the calculation of 1/3 octave band spectra using the sound_level_meter itself. This change does not have any effect on the results provided by the Loudness_ISO532_1 code released in SQAT v1.0.

  • sound_level_meter: with the addition of the Do_OB13_ISO532_1.m function, it is now possible to perform spectral analysis using the sound_level_meter in 1/3 octave bands. An example of usage is included under examples/sound_level_meter/ex_Do_OB13_ISO532_1.m.

  • EPNL_FAR_Part36.m - an implementation of the Effective Perceived Noise Level (EPNL) metri is now available under the psychoacoustic_metrics folder. An example code (including a ex sound file), as well as validation codes of this implementation are provided. All necessary files can be automatically added into the matlab search path using the startup_SQAT.m script.

Fixed issues

  • sound_level_meter: implementation of the B-weighting is now fixed. A code named sound_level_meter/test_Gen_weighting.m is now available. This code allows for a quick visual verification of the weighting functions generated by the Gen_weighting_filters function.

  • Tonality_Aures1985: an issue on the bandwidth calculation method was reported and corrected. Because the tones' bandwidth has an relevant influence on the final result, this has lead to a small change on the results. In comparison to the original version of the code, the results leads now to slightly smaller values. Thus, the value of the calibration constant had to be incresed to compensate for that. The change of the calibration value was based on the reference signal. Additionaly, this new version of the code was tested using the code available on the validation folder (a very small difference between old vs. new versions were observed). Nevertheless, this modification might have a relevant influence on your results, and the recalculation of tonality values using this updated version is highly recommended.

Assets 2
Loading