Displaying 20 results from an estimated 200 matches similar to: "opus file trimming/clipping"
2015 Nov 05
3
Opusfile seeking bug
Hi,
I seem to have found a bug with seeking in opusfile in some situations, though this might be better directed to the ogg list. I?ve included a short description below and a test case C program that describes it more detail (comments) and reproduces the issue when used with a file which contains packets that have been split over a page boundary (less common than I thought). The test program is
2017 Nov 20
0
[PATCH 1/2] op_pcm_seek: fix int64 overflow
check for overflow with a negative diff
---
src/opusfile.c | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/src/opusfile.c b/src/opusfile.c
index 72f1272..df326af 100644
--- a/src/opusfile.c
+++ b/src/opusfile.c
@@ -2605,7 +2605,11 @@ int op_pcm_seek(OggOpusFile *_of,ogg_int64_t _pcm_offset){
would be better just to do a full seek.*/
2017 Dec 07
0
[PATCH 0/2] libopusfile int64 overflows
James Zern wrote:
> On Tue, Nov 28, 2017 at 3:22 PM, James Zern <jzern at google.com> wrote:
>> On Mon, Nov 20, 2017 at 1:07 PM, James Zern <jzern at google.com> wrote:
>>> Just an attempt to avoid overflows with an explicit check, I don't know if
>>> there's a better way to identify corrupt input here.
>>>
>>> James Zern (2):
2017 Nov 20
7
[PATCH 0/2] libopusfile int64 overflows
Just an attempt to avoid overflows with an explicit check, I don't know if
there's a better way to identify corrupt input here.
James Zern (2):
op_pcm_seek: fix int64 overflow
op_fetch_and_process_page: fix int64 overflow
src/opusfile.c | 11 +++++++++--
1 file changed, 9 insertions(+), 2 deletions(-)
--
2.15.0.448.gf294e3d99a-goog
2002 Mar 18
2
[PATCH] make vorbis work with KDE 3.0
Hello,
the appended Patch makes vorbis work on KDE 3.0.(again)
A seek on a closed stream segfault vorbis, unfortunately
this situation happens in the KDE Multimedia player
very frequently (threads), thus vorbis does not work with KDE 3.0.
The bug is that the goto seek_error calls in ov_pcm_seek_page
do not set the return value in the error case.
Monty, can you apply this?
The bug was
2017 Dec 07
2
[PATCH 0/2] libopusfile int64 overflows
On Tue, Nov 28, 2017 at 3:22 PM, James Zern <jzern at google.com> wrote:
> On Mon, Nov 20, 2017 at 1:07 PM, James Zern <jzern at google.com> wrote:
>> Just an attempt to avoid overflows with an explicit check, I don't know if
>> there's a better way to identify corrupt input here.
>>
>> James Zern (2):
>> op_pcm_seek: fix int64 overflow
2016 Nov 14
1
Help with Opus Streaming
On 2016-11-14 6:09 AM, Deepak K wrote:
> I am using Http Progressive download technique to download the opus
> audio in chunks. So I am not sure if the Opusfile seek API will work in
> this case. Please correct me if I am wrong.
If you don't want to use opusfile's http client implementation
(libopusurl) you can still use its seeking implementation. Just provide
the
2017 Nov 28
0
[PATCH 0/2] libopusfile int64 overflows
On Mon, Nov 20, 2017 at 1:07 PM, James Zern <jzern at google.com> wrote:
> Just an attempt to avoid overflows with an explicit check, I don't know if
> there's a better way to identify corrupt input here.
>
> James Zern (2):
> op_pcm_seek: fix int64 overflow
> op_fetch_and_process_page: fix int64 overflow
>
> src/opusfile.c | 11 +++++++++--
> 1 file
2017 Dec 07
1
[PATCH 0/2] libopusfile int64 overflows
On Thu, Dec 7, 2017 at 12:18 PM, Timothy B. Terriberry
<tterribe at xiph.org> wrote:
> [...]
>
> Sorry, I can't reply to the original patches because I didn't actually get
> that e-mail due to local trouble with my mail server. I could pull the
> patches from the list archive, however. Thanks for the reports.
>
Thanks for recovering them and having a look. I
2013 May 13
0
DSPs which are suitable for porting OPUS
Dear Christian van Bijleveld,
You can use any of the below DSPs of Texas Instruments
1. TMS320C674x - This supports floating point implementation of opus
2. TMS320C66x - This supports both floating and fixed point implementations
3. TMS320C64x - This supports only fixed point implementation
Regards,
Mahantesh
On Mon, May 13, 2013 at 10:12 PM, <opus-request at xiph.org> wrote:
>
2013 Jul 17
0
opusfile, compiler warnings
Just a report about compiler warnings generated when building opusfile
from current git. Regards.
# x86-Linux builds / gcc48 and clang-3.3
(no warnings)
# x86-Linux builds / gcc34
src/opusfile.c: In function `op_calc_bitrate':
src/opusfile.c:1777: warning: integer constant is too large for "long" type
src/opusfile.c: In function `op_open2':
src/opusfile.c:1131: warning:
2001 Mar 01
2
ov_time_seek to 0s fails... AGAIN
Hello everybody, I sent something about this before, but this bug is still
there, so...
If you call
ov_time_seek(vf, 0);
it will fail, returning OV_EFAULT (from ov_pcm_seek_page). I think this must
be a bug, because seeking to 0 seconds *should* be OK.
Another thing, when ov_time_seek fails with OV_EFAULT, you cannot continue
playing
(because of the goto seek_error). This is not clear from
2005 Sep 18
1
trimmed mean in R seems to round the trimming fraction
subject: trimmed mean in R seems to round the trimming fraction
to r-help at stat.math.ethz.ch.
Consider the following example of 10 numbers. 10% trimmed mean is correct
but you can see that the result is the same for many trimming fractions
till 0.20!
For example 13% trimmed mean should use interpolation of second and
eighth ordered observation. R does not seem to do this.
The correct 13%
2005 Jun 27
0
A short netiquette request: trimming irrelevant material
Hi folks,
I''ve noticed in recent times on the list that we seem to be getting a
low signal-to-noise ratio with a lot of posts (particularly those
where people include their configuration).
Once you have posted the appropriate information once, there is no
need to keep quoting it unless it is central to the discussion.
Trimming irrelevant material makes it easy for people who have been
2020 Mar 28
0
[klibc:update-dash] dash: expand: Fix skipping of command substitution when trimming in evalvar
Commit-ID: 603b0dd1f1e08e9184661251513d281c89a42fac
Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=603b0dd1f1e08e9184661251513d281c89a42fac
Author: Herbert Xu <herbert at gondor.apana.org.au>
AuthorDate: Mon, 28 May 2018 17:09:48 +0800
Committer: Ben Hutchings <ben at decadent.org.uk>
CommitDate: Sat, 28 Mar 2020 21:42:55 +0000
[klibc] dash: expand: Fix
2018 Sep 05
0
Re: Tests and trimming vfat
On Wed, Sep 05, 2018 at 04:37:05PM +0100, Richard W.M. Jones wrote:
>
> Here's a fun one:
>
> + guestfish -N test-virt-sparsify-in-place-fstrim-unsupported.img=fs:vfat exit
> + virt-sparsify --in-place test-virt-sparsify-in-place-fstrim-unsupported.img
> + tee test-virt-sparsify-in-place-fstrim-unsupported.log
> [ 2.4] Trimming /dev/sda1
> [ 7.5] Sparsify in-place
2018 Sep 05
0
Re: Tests and trimming vfat
On Wed, Sep 05, 2018 at 04:45:51PM +0100, Richard W.M. Jones wrote:
> On Wed, Sep 05, 2018 at 04:41:01PM +0100, Daniel P. Berrangé wrote:
> > On Wed, Sep 05, 2018 at 04:37:05PM +0100, Richard W.M. Jones wrote:
> > >
> > > Here's a fun one:
> > >
> > > + guestfish -N test-virt-sparsify-in-place-fstrim-unsupported.img=fs:vfat exit
> > > +
2018 Sep 05
1
Re: Tests and trimming vfat
On Wed, Sep 05, 2018 at 04:53:03PM +0100, Daniel P. Berrangé wrote:
> On Wed, Sep 05, 2018 at 04:45:51PM +0100, Richard W.M. Jones wrote:
> > On Wed, Sep 05, 2018 at 04:41:01PM +0100, Daniel P. Berrangé wrote:
> > > On Wed, Sep 05, 2018 at 04:37:05PM +0100, Richard W.M. Jones wrote:
> > > >
> > > > Here's a fun one:
> > > >
> > >
2005 Nov 24
1
trimming CentOS - flash disk
Hi,
I am switching a few specific servers with CentOS 4.2 and I'd like to
use in some a flash disk (CF card).
Unfortunately the minimum size of a centos install seems to be around
600 Mb (at least that's what I got) and 1 Gb card are still expensive
and, IMHO too big if all you want is a gateway/iptables machine or a
NFS server.
There are other OSes and even distros that have a smaller
2011 Feb 01
1
automated mailbox trimming?
Hello all,
If this is answered in the wiki, I apologize. Please point me to it
and I'll be on my way ...
This may be more of a MailDir-generic question, except that as I
understand it there's some wiggle room in the naming of the message
files.
I've just switched from an mbox-based mail system to Dovecot with
MailDir. With mbox, I used logrotate to keep some of my mailboxes
(spam,