Skip to main content

logWMSE is an audio quality metric with support for digital silence target. Useful for evaluating audio source separation systems, even when there are many audio tracks or stems.

Project description

logWMSE

This audio quality metric, logWMSE, tries to address a limitation of existing metrics: The lack of support for digital silence. Existing audio quality metrics, like VISQOL, CDPAM, SDR, SIR, SAR, ISR, STOI and SI-SDR are not well-behaved when the target is digital silence. Some also struggle when the reference audio gets perfectly reconstructed.

Installation

pip install git+https://github.com/nomonosound/log-wmse-audio-quality

Usage example

import numpy as np
from log_wmse_audio_quality import calculate_log_wmse

sample_rate = 44100
input_sound = np.random.uniform(low=-1.0, high=1.0, size=(sample_rate,)).astype(np.float32)
est_sound = input_sound * 0.1
target_sound = np.zeros((sample_rate,), dtype=np.float32)

log_wmse = calculate_log_wmse(input_sound, est_sound, target_sound, sample_rate)
print(log_wmse)  # Expected output: ~18.42

Motivation and more info

Here are some examples of use cases where the target (reference) is pure digital silence:

  • Music source separation: Imagine separating music into stems like "vocal", "drums", "bass", and "other". A song without bass would naturally have a silent target for the "bass" stem.
  • Speech denoising: If you have a recording with only noise, and no speech, the target should be digital silence.
  • Multichannel speaker separation When evaluating speaker separation in a windowed approach, periods when a speaker isn't speaking should be evaluated against silence.

Mean squared error (MSE) is well-defined for digital silence targets, but has several drawbacks:

  • The values are commonly ridiculously small, like between 1e-8 and 1e-3, which makes number formatting and sight-reading hard
  • It's not tailored specifically for audio
  • Lack of scale-invariance
  • Doesn't consider the frequency sensitivity of human hearing
  • It's not invariant to tiny errors that don't matter (because humans can't hear those errors anyway)
  • It's not logarithmic, like human hearing is

logWMSE attempts to solve all the problems mentioned above. It's essentially the log of a frequency-weighted MSE, with a few bells and whistles.

The frequency weighting is like this: frequency_weighting.png

The idea of weighting it by frequency is to make it pay less attention to frequencies that human hearing is less sensitive to. For example, an error at 3000 Hz sounds worse than an error (with the same amplitude) at 50 Hz.

This audio quality metric was made with high sample rates in mind, like 36000, 44100 and 48000 Hz. However, in theory it should also work for low sample rates, like 16000 Hz. The metric function performs an internal resampling to 44100 Hz to make the frequency weighting filter consistent across multiple input sample rates.

Unlike many audio quality metrics, logWMSE accepts a triple of audio inputs:

  • unprocessed audio (e.g. a raw, noisy recording)
  • processed audio (e.g. a denoised recording)
  • target audio (e.g. a clean reference without noise)

Relative audio quality metrics usually only input the two latter. However, logWMSE additionally needs the unprocessed audio, because it needs to be able to measure how well input audio was attenuated to the given target when the target is digital silence (all zeros). And it needs to do this in a "scale-invariant" way. The scale invariance in logWMSE is not exactly like SI-SDR, where the processed audio can have arbitrary scaling compared to the target and still get the same score. logWMSE requires the gain of the target to be consistent with the gain of the unprocessed sound. And the processed sound needs to be scaled similarly to the target for a good metric score. The scale invariance in logWMSE can be explained like this: if all three sounds are gained by an arbitrary amount (the same gain for all three), the metric score will stay the same. Internally, that property is implemented like this: the processed audio and the target audio are both gained by the factor that would be required to bring the filtered unprocessed audio to 0 dB RMS.

logWMSE is scaled to the same order of magnitude as common SDR values. For example, logWMSE=3 means poor quality, while logWMSE=30 means very good quality. In other words, higher is better.

calculate_log_wmse accepts 1D or 2D numpy arrays as input. In the latter case, the shape is expected to be (channels, samples). The dtype of the numpy arrays is expected to be float32.

Please note the following limitations:

  • The metric isn't invariant to arbitrary scaling, polarity inversion, or offsets in the estimated audio relative to the target.
  • Although it incorporates frequency filtering inspired by human auditory sensitivity, it doesn't fully model human auditory perception. For instance, it doesn't consider auditory masking.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

log-wmse-audio-quality-0.1.0.tar.gz (40.7 kB view details)

Uploaded Source

Built Distribution

log_wmse_audio_quality-0.1.0-py3-none-any.whl (35.5 kB view details)

Uploaded Python 3

File details

Details for the file log-wmse-audio-quality-0.1.0.tar.gz.

File metadata

File hashes

Hashes for log-wmse-audio-quality-0.1.0.tar.gz
Algorithm Hash digest
SHA256 c2773a8e27dd601a7c8a43114087c835a2faa08340a289275be9198006da882f
MD5 e1b74c940c7b884e15e6f49792293efc
BLAKE2b-256 26c39dbbcaaadf6dc7bf1be894ff57666b5f26ed413aaea75619ecedb2d0145e

See more details on using hashes here.

File details

Details for the file log_wmse_audio_quality-0.1.0-py3-none-any.whl.

File metadata

File hashes

Hashes for log_wmse_audio_quality-0.1.0-py3-none-any.whl
Algorithm Hash digest
SHA256 829a47e2b8be4327dded4402afd9595f6f0f87b7d04eb809885363fc1dd2a092
MD5 1672d3d33c8ab4c4a09b2c100de311d6
BLAKE2b-256 d782d4cd7b679854acd3841ab06ff23efdbdff2b52c23a4d0441142b1678fc9e

See more details on using hashes here.

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page