similar to: A faster ogginfo

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

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:

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 ;-) I'm a totally newby working the first time with ogg vorbis. The problem I have is this: I ripped Musik CD's with the Program Exact Audio Copy (EAC) and used the the newest vorbis tools to kompress the files. But I have made a mistake. With EAC I can give oggenc some parameters with a commandline. So I do it for the titel of the tracks. The commandline looks like this: -q 6

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

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

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.

I'm trying to use libFLAC++ v1.1.2, to read Song information (like artist, trackname etc..). So.. I read metadata from file FLAC::Metadata::get_streaminfo("somefile.flac", infosik); and It's ok - no error, then I read vorbis info: FLAC::Metadata::VorbisComment vorbis_kom(infosik); int number_of_comments = vorbis_kom.get_num_comments(); and after that I have

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

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

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

I looked around on the web, but I found no guidance on this subject, so I'm guessing. Here is what I came up with. It appears to work on a limited sample of CDs. Can anyone comment on whether or not this is OK? My system is Mandrake 9.0. My Grip is 3.0.1 (as supplied with Mandrake 9.0) My flac is 1.1.0, built from the source tarball. Mandrake ships with 1.0.3, which does not appear to have

Hello. Read all about Extprograms, but have a question. Use case: Every day we have couple messages with attachment (from one sender, this is one-way communication). This attachment is uploads to ownCloud. By hand... need some automation. As I see, pipe cat execute scripts with text data USER/FROM/SUBJECT - and I think with variables it can be any text data, how about attachment? How I see

--- vorbiscomment/vorbiscomment.1 | 4 +--- 1 files changed, 1 insertions(+), 3 deletions(-) diff --git a/vorbiscomment/vorbiscomment.1 b/vorbiscomment/vorbiscomment.1 index 0108e78..2bceb83 100644 --- a/vorbiscomment/vorbiscomment.1 +++ b/vorbiscomment/vorbiscomment.1 @@ -39,13 +39,11 @@ Reads, modifies, and appends Ogg Vorbis audio file metadata tags. .IP "-a, --append" Append

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?

Hi, when I encode some files with the current CVS I get the following error with ogginfo: [...] New logical stream (#1, serial: 476aea05): type vorbis Warning: Vorbis stream 1 does not have headers correctly framed. Terminal header page contains additional packets or has non-zero granulepos Vorbis headers parsed for stream 1, information follows... Version: 0 Vendor: Xiph.Org libVorbis I 20020713

Thank you, ogginfo returned: ----- Note: Stream 1 has serial number 0, which is legal but may cause problems with some tools. New logical stream (#1, serial: 00000000): type vorbis Vorbis headers parsed for stream 1, information follows... Version: 0 Vendor: ffmpeg Channels: 1 Rate: 22050 Nominal bitrate: 35.333000 kb/s Upper bitrate not set Lower bitrate not set Vorbis stream 1: Total data

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