Spike caused by BASOP encoder in OMASA LTV input
# Basic info <!--- Add commit SHA used to reproduce --> - Float reference: - Encoder (float): db364042fba738d5d0f9823c047e75edea62bae7 - Decoder (float): db364042fba738d5d0f9823c047e75edea62bae7 - Fixed point: - Encoder (fixed): f14583620e84f03d718223da0ea4be6cc7c77c61 - Decoder (fixed): f14583620e84f03d718223da0ea4be6cc7c77c61 # Bug description There seems to be a clipping or similar saturation spike in OMASA caused by BASOP encoder. See the figure below. This is with BASOP encoder to float decoder but same spike is there for full BASOP path. ![Screenshot_2025-06-25_at_15.19.04](/uploads/4877f12d48783f805435d04863f84faa/Screenshot_2025-06-25_at_15.19.04.png) # Ways to reproduce <!-- Commandline or script --> ```bash IVAS_cod -ism_masa 3 2 ltv48_OMASA_3ISM_2TC_ISM1.csv ltv48_OMASA_3ISM_2TC_ISM2.csv ltv48_OMASA_3ISM_2TC_ISM3.csv ltv48_OMASA_3ISM_2TC.met -max_band fb 32000 48 ltv48_OMASA_3ISM_2TC.wav test_0103.bs IVAS_dec BINAURAL 48 test_0103.bs 0103_ltv48_OMASA_3ISM_2TC.wav_32k_48-48___BINAURAL.wav ``` <!--- Below are labels that will be added but are not shown in description. This is a template to help fill them. Add further information to the first row and remove and add labels as necessary. -->
issue