similar to: [PATCH] ogginfo: various

Hi, I'm using ogginfo a lot to get the comments section on the terminal. However ogginfo always verifies (reads) the whole stream to print some more information. I'd like to see an additional option that does just print the comments efficiently. For a player connected via USB 1, that would clearly make a difference. (I have a Perl script that renames files based on the comments, and I

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, I spent a while working out why ogginfo reported holes in one of my streams - turns out oggz-comment writes bad data into the stream, and oggz-validate doesn't see it (should it ?), oggz-dump displays correct data, etc. Eventually, some combination of xxd and comparing byte offsets led me to it... two hours later... -------------- next part -------------- A non-text attachment was

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.

hi, trying to join audio and video tracks that have been itself composed from several ogg files with oggCat, i get a file that does not work. that happens both with oggz-merge and oggJoin. the files produces by oggCat look ok according to ogginfo / oggz-info / oggz-validate, they also play fine in all players. anyone got an idea what could cause that problem? i can put up some sample file if

On 5/26/08, ogg.k.ogg.k at googlemail.com <ogg.k.ogg.k at googlemail.com> wrote: >> char[8]: 'kate\0\0\0\0' | kate > > This is incorrect, should be: > > char[9]: '\x80kate\0\0\0\0' | kate The last one is how it's listed on ogginfo code, but the first one (char[8]) is how it's described in the wiki page. I thought the

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

While testing the new vcut, some of the early results had badly framed headers. I actually didn't notice it at first, because I was testing with oggz-validate, but ogginfo does identify the problem: "WARNING: Vorbis stream X does not have headers correctly framed. Terminal header page contains additional packets or has non-zero granulepos" Conrad (or someone else) may want to

On Thu, Feb 16, 2006 at 03:25:07PM +0000, Ian Malone wrote: > (You really don't want to know this I'm sure) > I gave this a go this morning on the samples from > <http://wiki.xiph.org/index.php/Metadata>, which > are there mainly for the purpose of breaking things. > They don't validate (which neither surprises nor upsets > me), but I downloaded the oggz source

Hello I need to extract playback length from ogg vorbis file, with 1/100th second precision. The ogginfo program tells the playback length to 1 second precision. Why not to change ogginfo? I suppose many automatic tools need precision higher than 1 second. If you don't want to modify this ogginfo behaviour, please tell me how to get this playback length with high precision. Thank you very

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

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

hi guys, first of all, i'd like to ask if there any crossplatform software/service ( gui is also better, an online application like firefogg is great, or at least a command line tools for any platform) to combine theora videos, other than oggcat... i am doing some art projects that people should be able to remix featured theora videos and i find oggcat very usefull in theory but not in

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

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?