Displaying 2 results from an estimated 2 matches for "cur_signal_typ".
Did you mean:
cur_signal_type
2017 Jun 16
2
[EXTERNAL] Re: Submitting a patch that exposes VAD voiced/unvoiced signal type
Hi Peter,
Can you say a little bit more about what you're doing exactly with the
information you're exposing and how? unfortunately, I don't have a
concrete proposal in mind right now. That's in part because I don't
quite understand the use case, but also because it's really hard to
expose this kind of information in a way that both avoids breaking
application with new
2017 Jun 20
0
[EXTERNAL] Re: Submitting a patch that exposes VAD voiced/unvoiced signal type
...ng the opus_internal_flags data structure so that we can access the value assigned to prevSignalType. Here's a snippet of our code:
error = opus_encoder_get_internal_flags(vad->opus, &internalflags);
if (error != OPUS_OK)
{
return OPUSVAD_OPUS_ERROR;
}
cur_signal_type = internalflags.prevSignalType;
if ((vad->cur_state == STATE_NO_STATE) && (cur_signal_type == TYPE_UNVOICED || cur_signal_type == TYPE_VOICED) && (vad->prev_signal_type == TYPE_NO_VOICE_ACTIVITY)) {
...
Our library uses this information to apply end pointing on vo...