similar to: Proposal: enhance ogginfo to not verify whole stream

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

Hello Some time ago I posted a lil' patch to this list which adds milliseconds display of playlength to ogginfo. Some folks replied that it's plausible and this patch will be merged to the next version. Vorbistools-1.0.1 got out and the patch is not in it. Why? Anyway, here's this patch for vorbistools-1.0.1. I hope this time you will include it, because milliseconds support is

Good day all, I have a small collection of ogg files (5Gb) on my fileserver which I have mounted over NFS. My problem is that ogginfo takes too long to be used practically in programs like gqmpeg due to naturally wanting to do a full file check on each ogg file for valadity etc. My question/request is; is there a way to make ogginfo only look at the headers (ie, first K or two of data) and

Hello, I want to check my collection of hundreds of ogg files for potential problems. As far as I know, "ogginfo -v" is as comprehensive as it gets. However, using the "-v" option causes the output to be VERY VERY long when there are hundreds of files to check. I need a way to skim the output and only look at warnings and errors. In order to do that I need to know the complete

Hi, these are a few bits I found while working out why ogginfo was barfing on a stream (see previous oggz-comment patch). It fixes 32/64 bit %lld format bugs (vorbis and kate), adds a missing argument to a warning message, adds comments to what the return values of pageseek mean, and doesn't read more data if unneeded (this will lessen the memory used, but might mean worse performance, so the

Hello ! I'm using ogginfo quite often to generate a up to date list of all files I encoded so far. I noticed that it almost always reads the whole ogg file (to determine bitrate?) which is awfully slow if you have more than a gig of ogg. How can I speed up the process? Best regards, Sascha -- I get enough exercise just pushing my luck. --- >8 ---- List archives:

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

The ogginfo tool writes its errors to stdout instead of stderr. Shouldn't that change? (Warnings also go to stdout, but that's more of a gray area.) The other vorbis-tools don't have this problem, with the possible exception of vcut, which writes the usage message to stdout, another edge case.

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

Could someone please tell me what I'm doing wrong here? I have some oggs tagged using other applications and ogginfo doesn't give me any warnings when I use UTF-8 in them. I did the following: $ vorbiscomment --raw -a test.ogg -t "test=åäö" $ vorbiscomment --raw -l test.ogg test=åäö $ ogginfo -v test.ogg Processing file "test.ogg"... New logical stream (#1, serial:

Dear authors of Vorbis, currently, the manpages that come with vorbistools are written in the traditional man(7) markup language. I am proposing to rewrite them into the semantic markup of the mdoc(7) language. I am willing to do the work. Both the man(7) and mdoc(7) languages have been around for decades, and are supported by the prevalent formatters: groff(1) on most Linuxes and mandoc(1) on

>>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

I looked through the archives and I didn't really seem to find the answer to what my question. I used wget to get an audio stream from a site and now I would like to be able to split up the stream into the individual songs. The site is nice enough to encode the artist and track name in each new song. This info is displayed in Winamp when the song plays. Doing an xxd dump of the file I can

Hello Jean-Marc, As an example, I am using the output of opus encoder to store the file as the following format and read back the same during decode process, without having much overhead. (Thought it would be useful to put a picture rather than running text) [image: Inline image 2] Regards Amit On Thu, May 12, 2016 at 10:47 AM, Amit Ashara <ashara.amit at gmail.com> wrote: > Hello

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:

A new tab has been added to show ogg information including duration & bitrates, providing OggInfo.exe is available. Also, 1 or 2 minor bugs fixed. http://winvc.stationplaylist.com/WinVC.exe (183k) Cheers, Ross Levis <p><p>--- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message to

>>> Ralph Giles <giles at thaumas.net> schrieb am 21.12.2015 um 19:51 in Nachricht <CAEW_RkshUM55uwdvU6DsE17pLZki651Xvvu7d2Y6jObePXZwCQ at mail.gmail.com>: > On 21 December 2015 at 04:31, Ulrich Windl > <Ulrich.Windl at rz.uni-regensburg.de> wrote: > >> opusenc does not display the file name it processes. In Lunux when you use > some batch processing,

Hi All, For my new file (and thus mp3) server I've decided to switch completely to Ogg Vorbis. This means having to reencode ~30GB worth of 128Kb MP3's, but i figured that it would all be worth the effort. So I downloaded the sources for libogg, libvorbis and vorbis-tools and fired up my trusty old compiler. libogg and libvorbis built and installed like a charm. Not so for

Hello, with OpenSSH_2.3.0p1 running in HP-UX 11.00 I noticed that the "SD commands" (like "swcopy") produce the following error when being logged in via SSH: ERROR: RPC exception: "Who are you failed (dce / rpc)" 11/29/00 11:20:18 MET Ideas? Regards, Ulrich P.S. Not subscribed to the list