similar to: Complete list of possible ogginfo warning and error messages

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

One liner to add 1.1 rc1 to list of recognized files. Cheers, -------------- next part -------------- A non-text attachment was scrubbed... Name: ogginfopatch Type: application/octet-stream Size: 375 bytes Desc: not available Url : http://lists.xiph.org/pipermail/vorbis-dev/attachments/20040708/7c8c0952/ogginfopatch.obj

Coming out of a long (but definately needed) silence for a moment: A few things for vorbis-tools, since I no longer have CVS access (I think I just misplaced that key): 1. Before anything, put oggchain out of its misery. Please. It's a pile of junk that should have never been committed. Any smidgen of usefulness from it belongs in ogginfo anyway (and it's already there). 2. ./autogen.sh

Andrew Williams <andrew.s.williams@adelaide.edu.au> has tipped me off that vorbis-tools uses a format specifier "%Ld" in vcut/vcut.c and ogginfo/ogginfo2.c. This is plain wrong. The L modifier only applies to floating point. The modifier corresponding to "long long" is ll, e.g. "%lld". -- Christian "naddy" Weisgerber

Hiya: Since 1.0.1 is going to include minor tuning fixes that have an effect on audio quality in certain circumstances, I think the vendor tag should be updated according to the attached (and quite trivial) patch. (I chose 20030902 because that's the date of Monty's commits that included the tuning fixes.) -Carsten <p> Index: lib/info.c

Hello. Attached are some patches that some Debian users of vorbis-tools have sent to our BTS over the years (numbers refer to Debian bugs). It'd be nice to see them integrated. They apply cleanly to SVN as of today. The largefile_support one is a bit bigger than just the configure.ac since the submitter adviced that config.h got included in all C source files before the standard includes,

Hello. Attached are some patches that some Debian users of vorbis-tools have sent to our BTS over the years (numbers refer to Debian bugs). It'd be nice to see them integrated. They apply cleanly to SVN as of today. The largefile_support one is a bit bigger than just the configure.ac since the submitter adviced that config.h got included in all C source files before the standard includes,

Beni Cherniavksy (cben@techunix.technion.ac.il) wrote : [ big snip ] > Here are the dates as far as I know: > > > 20000508 (beta1/2) > 20001031 (beta3) > 20010225 (beta4) > 20010615 (RC1) > 20010813 (RC2) > 20010816 (gtune 1) (RC2 - Garf tuned v1) > 20011014 (GTune 2) (RC2 - Garf tuned v2) > 20011217 (RC3 - oggenc, oggdrop) > 20011231 (RC3 -

This patch cleans up the vorbis-tools Makefile.am files so they work with both automake 1.4 and 1.6. Some changes to configure.in were also needed in order to get things to work (and to fix some ac 2.50 issues). Please remove config.h from cvs as it is a generated file and empty anyway. automake 1.6 isn't really incompatable with 1.4, it's just more picky about you sticking to the rules:

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

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

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

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

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

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:

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.

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

Hi! I'm using the opus-tools package from the current Debian (it says it is 0.1.2). The output of opusinfo is strange: $ opusinfo demo01.opus Processing file "demo01.opus"... New logical stream (#1, serial: 0000456a): type opus Encoded with libopus 1.0.1-rc3 User comments section follows... ENCODER=opusenc from opus-tools 0.1.5 Opus stream 1: Pre-skip: 356 Playback

The download of the above still shows an id of: "Xiph.Org libVorbis I 20040629". Shouldn't this have been updated to: "Xiph.Org libVorbis I 20040920"? John

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?