Displaying 16 results from an estimated 16 matches for "in_short".
2005 Jun 27
1
VAD encoder sensitivity?
Hi,
When using the encoder function, speex_encode_int(st, in_short, &bits),
with VBR disabled and VAD enabled, the function always return a 1.
Also, when enabled DTX along with VAD enabled, most of the time the
function return a 1 even when it is silence.
Is there a way to change the sensitivity of the VAD by changing some
parameters in the source code,...
2010 Jul 25
0
notification: More than two wideband layers found. The stream is corrupted.
...}
else
{
inout_byte[2*i_loop] = RcvL2[i_loop];
inout_byte[2*i_loop+1] = RcvR2[i_loop];
}
}
byte2word(inout_byte, in_short, FRAME_SIZE);
speex_bits_reset(&bits);
returnVal = speex_encode_int(encoderState, (spx_int16_t
*) in_short, &bits);
nbChars = speex_bits_write(&bits, cbits,
sizeof(cbits)*BYTES_PER_CHAR) /BYTES_PER_CHAR;
s...
2017 Nov 24
3
[PATCH] Fix memory issue in Projection API
...rder to get the tests to work correctly. I will still submit a separate
patch for him for a few other concerns he had after this one clears.
Cheers,
Drew
On Thu, Nov 23, 2017 at 10:42 AM Jean-Marc Valin <jmvalin at jmvalin.ca> wrote:
> Actually, there's also something wrong with the in_short() function. For
> floating point (#else case), you shouldn't need shifting since you're
> already doing the scaling through a float multiply.
>
> Jean-Marc
>
> On 11/23/2017 01:39 PM, Drew Allen wrote:
> > got it. actually that patch i sent you has something...
2017 Dec 04
3
[PATCH] Fix memory issue in Projection API
...> > this one clears.
> >
> > Cheers,
> > Drew
> >
> > On Thu, Nov 23, 2017 at 10:42 AM Jean-Marc Valin <jmvalin at jmvalin.ca
> > <mailto:jmvalin at jmvalin.ca>> wrote:
> >
> > Actually, there's also something wrong with the in_short() function.
> For
> > floating point (#else case), you shouldn't need shifting since you're
> > already doing the scaling through a float multiply.
> >
> > Jean-Marc
> >
> > On 11/23/2017 01:39 PM, Drew Allen wrote:
> >...
2017 Nov 24
2
[PATCH] Fix memory issue in Projection API
...> > this one clears.
> >
> > Cheers,
> > Drew
> >
> > On Thu, Nov 23, 2017 at 10:42 AM Jean-Marc Valin <jmvalin at jmvalin.ca
> > <mailto:jmvalin at jmvalin.ca>> wrote:
> >
> > Actually, there's also something wrong with the in_short() function.
> For
> > floating point (#else case), you shouldn't need shifting since you're
> > already doing the scaling through a float multiply.
> >
> > Jean-Marc
> >
> > On 11/23/2017 01:39 PM, Drew Allen wrote:
> >...
2017 Nov 23
2
[PATCH] Fix memory issue in Projection API
got it. actually that patch i sent you has something wrong with the
mapping_matrix_multiply_short_out... let me fix that and will send you
another patch soon.
Cheers,
Drew
On Thu, Nov 23, 2017 at 10:34 AM Jean-Marc Valin <jmvalin at jmvalin.ca> wrote:
> On 11/23/2017 01:28 PM, Drew Allen wrote:
> > To your first point, I was only trying to copy how _multistream_'s c
> >
2017 Nov 23
0
[PATCH] Fix memory issue in Projection API
Actually, there's also something wrong with the in_short() function. For
floating point (#else case), you shouldn't need shifting since you're
already doing the scaling through a float multiply.
Jean-Marc
On 11/23/2017 01:39 PM, Drew Allen wrote:
> got it. actually that patch i sent you has something wrong with the
> mapping_matrix_multi...
2011 Apr 15
4
Can I use VBR option to change byte_per_packet dynamically ?
...ehaves,too, like Andrew Lentvorski. But I want to use VBR option.I want to ask a question about VBR in CELT codec.Can we use VBR option in CELT ??? "byte_per_packet" variable in code means constant bit rate, does not it ?In this code : bytes_per_packet is constant.len = celt_encode(enc, in_short, frame_size, data, bytes_per_packet);....."len" is equal "bte_per_packet" evey time.
celt_encoder_ctl(st, CELT_SET_VBR(1);celt_encoder_ctl(st, CELT_SET_VBR_CONSTRAINT(0);May I write two lines codes to active VBR ?Selami Tastan
-------------- next part --------------...
2017 Nov 24
0
[PATCH] Fix memory issue in Projection API
...him for a few other concerns he had after
> this one clears.
>
> Cheers,
> Drew
>
> On Thu, Nov 23, 2017 at 10:42 AM Jean-Marc Valin <jmvalin at jmvalin.ca
> <mailto:jmvalin at jmvalin.ca>> wrote:
>
> Actually, there's also something wrong with the in_short() function. For
> floating point (#else case), you shouldn't need shifting since you're
> already doing the scaling through a float multiply.
>
> Jean-Marc
>
> On 11/23/2017 01:39 PM, Drew Allen wrote:
> > got it. actually that patch i s...
2017 Nov 28
2
[PATCH] Fix memory issue in Projection API
...at 10:42 AM Jean-Marc Valin
> <jmvalin at jmvalin.ca <mailto:jmvalin at jmvalin.ca>
> > <mailto:jmvalin at jmvalin.ca <mailto:jmvalin at jmvalin.ca>>> wrote:
> >
> > Actually, there's also something wrong with the in_short()
> function. For
> > floating point (#else case), you shouldn't need shifting
> since you're
> > already doing the scaling through a float multiply.
> >
> > Jean-Marc
> >
>...
2017 Nov 27
0
[PATCH] Fix memory issue in Projection API
...> >
>> > Cheers,
>> > Drew
>> >
>> > On Thu, Nov 23, 2017 at 10:42 AM Jean-Marc Valin <jmvalin at jmvalin.ca
>> > <mailto:jmvalin at jmvalin.ca>> wrote:
>> >
>> > Actually, there's also something wrong with the in_short()
>> function. For
>> > floating point (#else case), you shouldn't need shifting since
>> you're
>> > already doing the scaling through a float multiply.
>> >
>> > Jean-Marc
>> >
>> > On 11/23/2017 01:...
2017 Dec 07
0
[PATCH] Fix memory issue in Projection API
...hu, Nov 23, 2017 at 10:42 AM Jean-Marc Valin
> <jmvalin at jmvalin.ca <mailto:jmvalin at jmvalin.ca>
> > <mailto:jmvalin at jmvalin.ca <mailto:jmvalin at jmvalin.ca>>> wrote:
> >
> > Actually, there's also something wrong with the in_short()
> function. For
> > floating point (#else case), you shouldn't need shifting since
> you're
> > already doing the scaling through a float multiply.
> >
> > Jean-Marc
> >
> > On 11/23/2017 01:...
2017 Nov 28
0
[PATCH] Fix memory issue in Projection API
...lin
> > <jmvalin at jmvalin.ca <mailto:jmvalin at jmvalin.ca>
> > > <mailto:jmvalin at jmvalin.ca <mailto:jmvalin at jmvalin.ca>>>
> wrote:
> > >
> > > Actually, there's also something wrong with the in_short()
> > function. For
> > > floating point (#else case), you shouldn't need shifting
> > since you're
> > > already doing the scaling through a float multiply.
> > >
> > > Jean-...
2017 Nov 28
3
[PATCH] Fix memory issue in Projection API
... > <mailto:jmvalin at jmvalin.ca <mailto:jmvalin at jmvalin.ca>
> <mailto:jmvalin at jmvalin.ca <mailto:jmvalin at jmvalin.ca>>>> wrote:
> > >
> > > Actually, there's also something wrong with the
> in_short()
> > function. For
> > > floating point (#else case), you shouldn't need shifting
> > since you're
> > > already doing the scaling through a float multiply.
> > >
> > ...
2017 Nov 29
0
Antw: Re: [PATCH] Fix memory issue in Projection API
...;mailto:jmvalin at jmvalin.ca <mailto:jmvalin at jmvalin.ca>
>> <mailto:jmvalin at jmvalin.ca <mailto:jmvalin at jmvalin.ca>>>> wrote:
>> > >
>> > > Actually, there's also something wrong with the
>> in_short()
>> > function. For
>> > > floating point (#else case), you shouldn't need shifting
>> > since you're
>> > > already doing the scaling through a float multiply.
>> > >...
2017 Nov 30
0
Antw: Re: [PATCH] Fix memory issue in Projection API
...o:jmvalin at jmvalin.ca>
> <mailto:jmvalin at jmvalin.ca <mailto:jmvalin at jmvalin.ca>>>>> wrote:
> >>> > >
> >>> > > Actually, there's also something wrong with the
> >>> in_short()
> >>> > function. For
> >>> > > floating point (#else case), you shouldn't
> need shifting
> >>> > since you're
> >>> > > already doing the scal...