similar to: Patch for bitrate information in ogginfo

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

I hope that this is the appropriate venue for this question. If it's not, let me know and I'll take it elsewhere (perhaps vorbis-dev). Saved streams are great - it lets this norteamericano get his fill of BBC Radio 1's Essential Mix. Unfortunately, saved streams aren't seekable. Running ogginfo on the stream data gives: erial=1626603590 header_integrity=pass vendor=Xiphophorus

I hope that this is the appropriate venue for this question. If it's not, let me know and I'll take it elsewhere (perhaps vorbis-dev). Saved streams are great - it lets this norteamericano get his fill of BBC Radio 1's Essential Mix. Unfortunately, saved streams aren't seekable. Running ogginfo on the stream data gives: erial=1626603590 header_integrity=pass vendor=Xiphophorus

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

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

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]

ok, I'm aware that vo_open cant be used at the same time as other functions such as ogg_sync_wrote, ogg_sync_pageout, ogg_stream_pagein, ogg_stream_packetout and vorbis_synthesis_headerin. In order to get information from the bitstream i've been using this method because it's fast and doesn't require decoding of the stream. But, i can only retrieve the average bitrate of

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:

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

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.

If I understand correctly, Ogg Vorbis is a lossless format. But then why does it support bitrates? Ogg Vorbis does not delete any information. When I encode a 128 kbit MP3 file to 32 kbit OggVorbis, the resulting file has a bitrate of about 110 kbit. And when I encode it to 320 kbit, the file will be bigger, but the quality won't improve because of the quality of the original. So what purpose

Why ov_open_callbacks(fd_, &vf, NULL, 0, OV_CALLBACKS_NOCLOSE) takes so long to open OGG file? The OGG file has just 210 MB. It takes a lot of time open the file. I am working on OGG audio recorder and player. Thanks in advance! With kind regards, Pavel

Thanks to my provider, my old email alias (hongli@telekabel.nl) had been deleted. Now I can only use h.lai@chello.nl However, I'm subscribed to Vorbis's mailing lists using hongli@telekabel.nl Is there any way to change my subscription's address? <p><p>--- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe

Thanks to my provider, my old email alias (hongli@telekabel.nl) had been deleted. Now I can only use h.lai@chello.nl However, I'm subscribed to Vorbis's mailing lists using hongli@telekabel.nl Is there any way to change my subscription's address? <p><p>--- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe

>From dcd47a609f4489bb37ce33ea1ce975bb2b3ab160 Mon Sep 17 00:00:00 2001 From: Hongli Lai (Phusion) <hongli at phusion.nl> Date: Mon, 6 Jun 2011 13:36:57 +0200 Subject: [PATCH] Document the method for building the Unicorn gem. Signed-off-by: Hongli Lai (Phusion) <hongli at phusion.nl> --- HACKING | 11 +++++++++++ 1 files changed, 11 insertions(+), 0 deletions(-) diff --git