view libtwamr/vad.h @ 581:e2d5cad04cbf

libgsmhr1 RxFE: store CN R0+LPC separately from speech In the original GSM 06.06 code the ECU for speech mode is entirely separate from the CN generator, maintaining separate state. (The main intertie between them is the speech vs CN state variable, distinguishing between speech and CN BFIs, in addition to the CN-specific function of distinguishing between initial and update SIDs.) In the present RxFE implementation I initially thought that we could use the same saved_frame buffer for both ECU and CN, overwriting just the first 4 params (R0 and LPC) when a valid SID comes in. However, I now realize it was a bad idea: the original code has a corner case (long sequence of speech-mode BFIs to put the ECU in state 6, then SID and CN-mode BFIs, then a good speech frame) that would be broken by that buffer reuse approach. We could eliminate this corner case by resetting the ECU state when passing through a CN insertion period, but doing so would needlessly increase the behavioral diffs between GSM 06.06 and our version. Solution: use a separate CN-specific buffer for CN R0+LPC parameters, and match the behavior of GSM 06.06 code in this regard.
author Mychaela Falconia <falcon@freecalypso.org>
date Thu, 13 Feb 2025 10:02:45 +0000
parents 028ed5114e52
children
line wrap: on
line source

/*
 * In the original 3GPP code, the selection between VAD1 and VAD2 is made
 * only at compile time.  In libtwamr we support run-time selection between
 * these two VAD algorithms for tinkering and investigation work; this
 * header file implements the logic that fits this run-time selection
 * into the existing code structure from 3GPP.
 */

#ifndef	vad_h
#define	vad_h

#include "typedef.h"
#include "vad1.h"
#include "vad2.h"

typedef struct {
	Flag	use_vad2;
	union {
		vadState1	v1;
		vadState2	v2;
	} u;
} vadState;

void vad_reset(vadState *st, Flag use_vad2);

#endif	/* include guard */