Displaying 3 results from an estimated 3 matches for "ms_warn".
Did you mean:
as_warn
2007 May 16
3
draft-ietf-avt-rtp-speex-01.txt
...more
complicated than it should be. Normally, the decode code should look like:
speex_bits_init(&bits);
speex_bits_read_from(&bits, packet, length);
while (1)
{
err = speex_decode_int(state, bits, out_buffer);
if (err != 0)
break;
play_audio(out_buffer);
}
if (err == -2)
ms_warning("there was an error decoding");
I see from your code that you use speex_bits_remaining(&bits) but I
can't really understand why. Could you explain?
Jean-Marc
2007 May 17
0
draft-ietf-avt-rtp-speex-01.txt
...ode code should look like:
>
> speex_bits_init(&bits);
> speex_bits_read_from(&bits, packet, length);
> while (1)
> {
> err = speex_decode_int(state, bits, out_buffer);
> if (err != 0)
> break;
> play_audio(out_buffer);
> }
> if (err == -2)
> ms_warning("there was an error decoding");
>
>
> I see from your code that you use speex_bits_remaining(&bits) but I
> can't really understand why. Could you explain?
I don't know......
I think that when I implemented this, that helped me to get out the loop.
It seems th...
2007 May 16
2
draft-ietf-avt-rtp-speex-01.txt
>> The main idea is that Speex supports many bit-rates, but for one reason
>> or another, some modes may be left out in implementations (e.g. for RAM
>> or network reasons). What we're saying here is that you should make an
>> effoft to at least support (and offer) the 8 kbps mode to maximise
>> compatibility.
>
> I understood this. But as you may know: the