Displaying 5 results from an estimated 5 matches for "ideao".
Did you mean:
idea
2013 Oct 26
2
libopus API question - 120ms encoding
Hi Jean-Marc,
A simpler question. How does opus_encode() generate packets of 20ms (SILK-only or Hybrid)? Concatenating two 10ms frames or doing it straight with just one 20ms frame?
2013 Apr 11
0
No subject
...t to 1.
Regards,
Chris
-----Original Message-----
From: opus-bounces at xiph.org [mailto:opus-bounces at xiph.org] On Behalf Of Jea=
n-Marc Valin
Sent: Friday, October 25, 2013 7:19 AM
To: O'Connor, Kevin; opus at xiph.org
Subject: Re: [opus] libopus API question - 120ms encoding
The general ideao of opus_encode() is indeed to encode a single frame.
However, there is an exception for 40 and 60 ms because only one mode
(SILK-only) has this frame size. The original code would automatically forc=
e SILK-only mode on 40 and 60 ms, but that was suboptimal for mode switchin=
g. This why opus_encod...
2013 Oct 24
1
libopus API question - 120ms encoding
The libopus encoder's opus_encode() method is documented as "Encodes an Opus frame". Does that mean that it always produces a single Opus frame (i.e. the number of frames in the TOC byte will always be 0)? It's not clear from the documentation, but the fact that it cannot produce a 120ms Opus packet makes me wonder if that was the intention and any multi-frame Opus packets must
2013 Oct 26
0
libopus API question - 120ms encoding
...-----Original Message----- From: opus-bounces at xiph.org
> [mailto:opus-bounces at xiph.org] On Behalf Of Jean-Marc Valin Sent:
> Friday, October 25, 2013 7:19 AM To: O'Connor, Kevin; opus at xiph.org
> Subject: Re: [opus] libopus API question - 120ms encoding
>
> The general ideao of opus_encode() is indeed to encode a single
> frame. However, there is an exception for 40 and 60 ms because only
> one mode (SILK-only) has this frame size. The original code would
> automatically force SILK-only mode on 40 and 60 ms, but that was
> suboptimal for mode switching. Thi...
2013 Oct 30
1
libopus API question - 120ms encoding
...-----Original Message----- From: opus-bounces at xiph.org
> [mailto:opus-bounces at xiph.org] On Behalf Of Jean-Marc Valin Sent:
> Friday, October 25, 2013 7:19 AM To: O'Connor, Kevin; opus at xiph.org
> Subject: Re: [opus] libopus API question - 120ms encoding
>
> The general ideao of opus_encode() is indeed to encode a single frame.
> However, there is an exception for 40 and 60 ms because only one mode
> (SILK-only) has this frame size. The original code would automatically
> force SILK-only mode on 40 and 60 ms, but that was suboptimal for mode
> switching....