Skip to content

OMASA not BE between 5ms and 20ms rendering

Basic info

Bug description

OMASA is not BE between 5ms and 20 ms rendering and rendering to non binaural and stereo. The causes are a wrong offset into the separate object transport channels for the unified memory case and delaying the object signals with non-matching td data due to not copying enough samples into the intermediate object buffer in the non-20ms cases.

Ways to reproduce

Disable the limiter by adding

#define DISABLE_LIMITER

to options.h

Run a discrete object OMASA bit rate for both 5ms and 20 ms and compare the output, e.g.:

.\runIvasCodec.py -C OMASA -p your_site_config.json -U10 -o fr5 -D="-fr 5" -x "b384"
.\runIvasCodec.py -C OMASA -p your_site_config.json -U10 -o fr20 -D="-fr 20" -x "b384"
.\batch_comp_audio.py -d .\fr5\dec\ .\fr20\dec\