similar to: Seeking in a saved stream; or, Why isn't that sucker valid?

>>I realize that I may have unintentionally been misleading you by leaving some information out. That error report from ogginfo keeps going, repeating the same 3 errors (as above) over and over again. It ends after a stream_truncated=true, not giving a final header_integrity=fail. (Perhaps because there's not another packet?) Then it reports a total playtime of 0. > >Yes,

>> Running ogginfo on the stream data gives: >> stream_integrity=fail >This line in the ogginfo output concerns me. It means that there are actually >damaged Ogg packets in the stream. How are you saving this stream to disk? This particular one was obtained with wget on OpenBSD. I've observed the same problem with files saved from Winamp. >I think there is a problem

After accidentally ogginfo-ing a WAV file, I'm wondering if there's any reason I shouldn't commit my fix that breaks out of the current file test if header integrity fails. Is there any case where the header integrity will fail but there is still any useful information to get out of the stream? I don't think so... -- Kenneth Arnold <ken@arnoldnet.net> - "Know

I have a CD ripped with RC2, ogginfo from 1.0 claims they are all "broken". ogg123 also goes a little wild with them. I'll experiment a little more, maybe play with xmms, etc. RC3's ogginfo do not see anything wrong with them... an example: ---------- ogginfo 1.0 New logical stream (#1, serial: 2aab0567): type vorbis Vorbis headers parsed for stream 1, information follows...

Just got around to compiling RC3 under beos and came across an anomaly when using managed bitrates. I haven't changed the code for the beos encoder but I now get double the bitrates so vorbis_encode_init(&vi,mediaFormat.u.raw_audio.channel_count,(long)mediaFormat.u.raw_audio.frame_rate , -1, 128000, -1); now gives me vorbis files that average around 325 - 350. Is this now the correct

I found I have ripped the same CD twice with different machines. Cannot remember when, why, or how, but anyway. I've been using jack, here is relevant output: first one: 01/|\enc/|\128/|\[coding @0.67× done,129kbit] 02/|\enc/|\128/|\[coding @0.69× done,124kbit] 03/|\enc/|\128/|\[coding @0.66× done,124kbit] <etc> econd one: 01/|\enc/|\128/|\[coding @5.50× done,116kbit]

Hi all, A while back (Feb 11) Stephen Commiskey sent mail to this list with the subject : "Seeking in a saved stream; or, Why isn't that sucker valid?". Stephen had some problems with streams he saved from the BBC that gave him all sorts of weird errors and resulted in his not being able to seek in his saved streams. I tried the same thing immediately (never saved an oggstream

Hi, I am using libvorbis-1.0.1 and I am trying to debug the example decoder (examples/decoder_example.c) using gdb. I have compiled the source tree for debug and can single step through the program. However i am facing the following problem (which I think is more of C than vorbis) 1. after single steppig I finally arrive at the function shown below (in file lib/info.c) static int

brtfs could be supported on Opensolaris, too. IMO it could even complement ZFS and spawn some concurrent development between both. ZFS is too high end and works very poorly with less than 2GB while brtfs reportedly works well with 128MB on ARM. Olga On Wed, Apr 14, 2010 at 5:31 PM, <Casper.Dik at sun.com> wrote: > > >>Just a completely different question...is there any plans

Some detailed feedback that looks useful. ----- Forwarded message from Michael Semon <wayfarer42@postmaster.co.uk> ----- Delivery-Date: Tue Jul 16 05:29:37 2002 X-Mailer: MIME-tools 5.41 (Entity 5.404) From: "Michael Semon" <wayfarer42@postmaster.co.uk> Subject: CVS: ogg123 rocks! vcut no so much so... To: feedback@vorbis.com Hi! Being impatient for RC4, I downloaded

With this patch, ogginfo will display bitrate information (upper/lower/nominal/average bitrate). It is patched against today's CVS code (main branch). I am also working on true VBR support in oggenc (the user can specify the minimum & maximum bitrate) and will send a patch when it's done. <HR NOSHADE> <UL> <LI>application/x-gzip attachment: ogginfo-diff.gz

While using ogginfo (command line util), I've noticed that there's info on "stream integrity" (it says stream integrity=pass). Does this mean that there are no errors in the bitstream (which can happen if the file is corrupted)? <p>Aleksandar <p><p><p>--- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage:

------- Forwarded Message From: Jesse Hammons <jessehammons@yahoo.com> Reply-To: jhammons@alumni.princeton.edu Subject: VBR encoding in ogglame? To: vorbis@xiph.org Cc: vorbis-dev@xiph.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Hello, I ran a little test where I encoded an audio file at a bunch of different data rates. The results are here:

------- Forwarded Message From: Jesse Hammons <jessehammons@yahoo.com> Reply-To: jhammons@alumni.princeton.edu Subject: VBR encoding in ogglame? To: vorbis@xiph.org Cc: vorbis-dev@xiph.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Hello, I ran a little test where I encoded an audio file at a bunch of different data rates. The results are here:

When I run ogginfo on a .ogg file I created with oggenc (RC3), it lists some things that I have questions about: 1. Ogginfo lists bitrate_average and bitrate_nominal. Now, bitrate_average (I assume) would mean the overall bitrate average for the entire file but what does bitrate_nominal mean? 2. How is the serial number created? Can I tell something specific about an .ogg file by looking at it?

Does anybody have any tips for combating site suckers - of the variety that use wget and other site downloaders; hit sites hard; ignore robots.txt; and even set User-agent to commonly used browser strings? I''m using Lighty and SCGI. Back with Apache, there were various modules that could limit total bandwidth, but I never found anything that worked well. thanks csn

I'm tentatively creating a Windows .dll file using the Vorbis tools demos as a base for it. I've taken oggenc and simply converted it into a .dll file, with some minor changes purely to pass parameters to it (the original uses the command line). I have it working as far as it goes, but there seems to be something going wrong deep inside that I don't understand. The line at fault

Hello everybody, I've put some functions/modifications into the Ogg Vorbis encoder source. (The new functions are in the first 500 lines of the oggenc.c, some definitions are in the oggenc.h) I hope, you can use it. Here is the full source (same source on 3 locations): http://www.geocities.com/mpxplay/oggenc.zip http://www.tar.hu/mpxplay/oggenc.zip http://www.extra.hu/galileog/oggenc.zip

Hi all, I've got a question on regarding how to find out the duration of an ogg vorbis file. Sorry if it should already be mentioned somewhere in the docs, but I couldn't find out how to do it the best way. So, I can read the [bitrate_nominal] field from the identification header (if it is set), find out the size of the audio data (by subtracting the size of the three headers from the

Hello all, I am currently doing a partial port of vorbisenc to java. Partial port being that I am just concerned with 44kHz and above stereo coupled modes. I have done the grunt work of converting the 44kHz static code and res book data structures to java classes and want to verify that my data of the Java app matches that of C app. I'm pretty tired so instead of babbling an explanation