similar to: Oggenc - strange display output

...even worse, it *appears* to work, and produces crap files. When specifying a -b <foo> option for a batch encode, -b <foo> is only obeyed for the first file. All subsequent files encode with the equivalent of -b 0 (despite the chatty text output claiming otherwise) resulting in overly low bitrates that sound like shit. I don't know if this affects -q as well, but it a safe

I'm trying to clean up CVS, getting everything where it should be, because pretty soon we're going to have to build SDK's and whatnot, and I want that to be easy. We're basically going to have 3 libraries: 1) libogg 2) libvorbis 3) libvorbisfile I have separated libogg out from the rest of the code, cleaned it up, got it doing 'make dist' and rpms and imported this into

Does anybody successfully use oggenc from vorbis-tools-1.0beta4 on an alpha (BSD, Linux, Tru64)? My very first attempts to encode an ogg file promptly made oggenc dump core on me. (FreeBSD/alpha) -- Christian "naddy" Weisgerber naddy@mips.inka.de --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To

Hey All, I just wrote a nifty gem and wanted to share(its one of my first). Wondering if anyone would be so kind as to tell me what they think and/or code review it. MailJack - its like LoJack but for the links in your emails. The problem this solves is the ability to track click throughs in emails. https://github.com/synth/mail_jack Basically, you specify what mailers you want to track

Hello list, I've been having a tough time adding windows resource support to my ogg vorbise decoder, although I think I am close. Basically when I call ov_open_callbacks(), it doesn't ever return and repeatedly calls my seek_func. I'm hoping it is something obvious, but I can't see why my seek_func is being called endlessly. If the file is seekable, I should return 0, right? If

First of all, keep the replies on the mailing list. Are you subscribed to the mailing list? On Aug 24 09:44:56, nguyenquocthao00 at gmail.com wrote: > The file ogg is the same, I know that. So oggenc must have produced exactly the same audio. So it must be specific to the "live" playing. > And the problem is not from curl, > curl is only an example to replicate my problem.

Reported-by: Thomas K?ller Bug: https://bugzilla.redhat.com/1185558 --- oggenc/oggenc.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/oggenc/oggenc.c b/oggenc/oggenc.c index ea105b2..323dedb 100644 --- a/oggenc/oggenc.c +++ b/oggenc/oggenc.c @@ -239,7 +239,7 @@ int main(int argc, char **argv) if(opt.rawmode) { - input_format raw_format = {NULL,

Attached is the manual page for OggEnc. Please proofread it and commit to CVS. Also remember to edit Makefile.in to install the man page to the appropriate location. Thanks. --- Stan Seibert .\" Process this file with .\" groff -man -Tascii oggenc.1 .\" .TH oggenc 1 "August 13, 2000" "" "Vorbis Tools" .SH NAME oggenc \- encode audio into

Hi, I think this should also go on the llvm-dev mailing list... On Sat, Jul 13, 2013 at 11:18 PM, Star Tan <tanmx_star at yeah.net> wrote: > > At 2013-07-14 02:30:07,"Tobias Grosser" <tobias at grosser.es> wrote: >>On 07/13/2013 10:13 AM, Star Tan wrote: >>> Hi Tobias, >> >>Hi Star, >> >>thanks for the update. I copied the polly

Hi, I recently noticed that a relativly short wav file loses the last second (truncated perhaps) when I ran it through oggenc. Originally the wav was 25 seconds, the ogg is 24 seconds. This happens at various quality levels, and I saved several copys of the file on a webserver at http://array26.rockefeller.edu/www/ogg/ If anyone wants to confirm my observations. The command lines were:

Hi, I am trying to encode a 2.1gig .wav file using oggenc with the following error message: andrew@ilium:~/Desktop$ oggenc -q 6 merge.wav -o test.ogg ERROR: Cannot open input file "merge.wav": File too large I have compiled oggenc from source: andrew@ilium:~/Desktop$ oggenc -version OggEnc v1.0.2 I am hoping that this not a limitation of oggenc, rather that I have done something a

vorbis-tools/oggenc/utf8.c:164 has a //-style comment; it should be /* ... */ so that non-gcc compilers won't barf (e.g., solaris Forte 6.1 cc). Patch included, if you're really lazy. :-) {+} Jeff Squyres {+} squyres@cse.nd.edu {+} Perpetual Obsessive Notre Dame Student Craving Utter Madness {+} "I came to ND for 4 years and ended up staying for a decade" Index: oggenc/utf8.c

---------- > Van: ORK <korsmo@solungen.hm.no> > Aan: vorbis@xiph.org > Onderwerp: [vorbis] OggEnc help file > Datum: maandag 3 september 2001 18:21 > > Somebody asked how to use OggEnc a while ago. > > OggEnc v0.8 (libvorbis rc2) > (c) 2001 Michael Smith <msmith@labyrinth.net.au) > > Usage: oggenc [options] input.wav [...] LOL! --- >8 ---- List

On Aug 22 09:38:17, u.windl at ukr.de wrote: > I wonder: What happens if you disable cURL's (default) buffering? With curl -N, I see the same behaviour. That's curl 8.1.2. What about you? I still can't see the original problem. Jan > -----Original Message----- > From: Vorbis <vorbis-bounces at xiph.org> On Behalf Of Jan Stary > Sent: Tuesday, August 22, 2023

... in order to prevent a division by zero (CVE-2014-9638) and integer overflow (CVE-2014-9639). Bug: https://trac.xiph.org/ticket/2136 Bug: https://trac.xiph.org/ticket/2137 --- oggenc/audio.c | 19 +++++++++++++++++-- 1 file changed, 17 insertions(+), 2 deletions(-) diff --git a/oggenc/audio.c b/oggenc/audio.c index 477da8c..1167f1b 100644 --- a/oggenc/audio.c +++ b/oggenc/audio.c @@ -13,6

Hello! I would like to send some bugs and bugfix(es): 1. There is an encoding bug in the beta 3 (downloaded exe from the vorbis.com) and in the latest CVS (jan. 10.) too (compiled with MSVC 6.0): If the file contains some non-audible noise at the begin or at the end, the encoder/decoder makes some large clips in the output file, if the bitrate is 350kbit/s . If I use 256kbit/s or

Hi all, I've got a strange problem. I was just encoding a new CD I bought a couple of days ago (Muse - Hullabaloo Soundtrack) when I ran into a strange bug. After ripping track 8, CD 1 with cdparanoia under OpenBSD/alpha, I wanted to encode it with oggenc (latest version from the OpenBSD-current ports tree, (`oggenc -v` says 'OggEnc v1.0 (libvorbis 1.0)')). Here's the output :

Hi, I just came across some behaviour in oggenc that I didn't expect and wondered if this was intentional or not. I was wanting to encode a Cd which has more than one artist, but several tracks per artist. The command I entered took the form of: oggenc -n "%n - %a - %t.ogg" -a artist1 -N 1 -t title1 -N 2 -t title2 -N 3 -t title3 -a artist2 -N 4 -t title4 -N 5 -t title5 -a

Could someone please search and replace the msvc projectfile for oggenc: "c:\src" -> "..\.." I tried to make a patchfile but I dont know if I got it right... /Erik <HR NOSHADE> <UL> <LI>TEXT/PLAIN attachment: oggenc.dsp.diff </UL> -------------- next part -------------- A non-text attachment was scrubbed... Name: oggenc.dsp.diff Type:

Fix the crash of oggenc when parsing a WAV file including zero or a negative number of channels. Fixes for both CVE-2014-9638 and CVE-2014-9639 --- oggenc/audio.c | 6 ++++++ 1 file changed, 6 insertions(+) --- a/oggenc/audio.c +++ b/oggenc/audio.c @@ -455,6 +455,12 @@ int wav_open(FILE *in, oe_enc_opt *opt, format.align = READ_U16_LE(buf+12); format.samplesize =