Displaying 3 results from an estimated 3 matches for "cur_max".
Did you mean:
curr_max
2014 Jun 04
4
opus_multistream_encode_float not working in libopus 1.1
On Wed, Jun 4, 2014 at 4:31 PM, Timothy B. Terriberry <tterribe at xiph.org> wrote:
> Alpha Thinktink wrote:
>> max_data_bytes=-11
>
> That value is passed in by you. I also don't think passing such a value
> would have worked in earlier releases. It indicates the size of the
> buffer you are passing to the encoder to receive the encoded output.
Actually, I'm
2014 Jun 05
0
opus_multistream_encode_float not working in libopus 1.1
...set to -1000 to
indicate Auto bitrate. I imagine Max bitrate (-1) has a slightly
similar effect.
then in the same c file
line 846
curr_max = max_data_bytes - tot_size;
curr_max becomes -2 as tot_size was 0.
then line 848
curr_max -= IMAX(0,4*(st->layout.nb_streams-s-1)-1);
cur_max becomes -13 as nb_streams was 4 and s was 0.
then line 849
curr_max = IMIN(curr_max,MS_FRAME_TMP);
which left curr_max at -13
The result at line 853 is opus_encode_native is called with parameters
so thusly:
(encoder state pointer, buf pointer, frame_size=960, tmp_data pointer,
curr_max...
2014 Jun 21
1
opus_multistream_encode_float not working in libopus 1.1
...1) has a slightly
> similar effect.
>
> then in the same c file
> line 846
> curr_max = max_data_bytes - tot_size;
>
> curr_max becomes -2 as tot_size was 0.
>
> then line 848
>
> curr_max -= IMAX(0,4*(st->layout.nb_streams-s-1)-1);
>
> cur_max becomes -13 as nb_streams was 4 and s was 0.
>
> then line 849
>
> curr_max = IMIN(curr_max,MS_FRAME_TMP);
>
> which left curr_max at -13
>
> The result at line 853 is opus_encode_native is called with parameters
> so thusly:
> (encoder state pointer, buf p...