Displaying 2 results from an estimated 2 matches for "curr_read".
Did you mean:
chr_read
2015 Feb 23
1
[PATCH] opus_demo: remove unused but set values
...t bandwidth=OPUS_AUTO;
const char *bandwidth_string;
int lost = 0, lost_prev = 1;
int toggle = 0;
opus_uint32 enc_final_range[2];
opus_uint32 dec_final_range;
int encode_only=0, decode_only=0;
- int max_frame_size = 960*6;
+ int max_frame_size = 48000*2;
int curr_read=0;
int sweep_bps = 0;
int random_framesize=0, newsize=0, delayed_celt=0;
@@ -336,15 +336,12 @@ int main(int argc, char *argv[])
/* defaults: */
use_vbr = 1;
- bandwidth = OPUS_AUTO;
max_payload_bytes = MAX_PACKET;
complexity = 10;
use_inbandfec = 0;
forc...
2013 Oct 06
1
Encoder off by one
If you encode with
int iByteSizeEncoded = opus_encode(m_enc, m_ShortsInput,
(1920/sizeof(short)), m_EncodedBytes, (960*6));
... the byte size is 120.
I thought that an odd value like 359 has to be a fault on my side.
I thought it would be a multiple of something.
So 359 is really correct???
Thank you for clearing this up.
Am 06.10.2013 16:50, schrieb Jean-Marc Valin:
> Why