similar to: broken ogg file

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

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

Hello, I hope this is the right place to ask. I am having random lockups from the python bindings. My app has one or two threads running, the lockups only occure at one point, here is the code run as a thread def play(self): self.playing = TRUE self.output = [] self.lastplay = time.time() args = self.song_file, self.output retval =

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

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 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, I just noticed that ogginfo is not properly detecting Ogg FLAC files. To fix the issue I will need to know what is the correct magic for Ogg FLAC and how big are the packet bytes. Please advise. -Ivo

Here is a list of current open bugs in debian bts, some of these bugs are probably fixed but I do not know how to test for them properly (like UTF-8) and others may not be important enough to hold up 1.0. bugs.debian.org/(bug num) libao 130816 - WAV device doesn't print error when device is full 150220 - Doesn't open OSS devices with O_NONBLOCK all the time vorbis-tools 128521 -

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

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

Greetings. Possibly as the result of buggy tagging software, several hundred of my Ogg Vorbis files exhibit the following warning when examined by ogginfo: WARNING: Vorbis stream 1 does not have headers correctly framed. Terminal header page contains additional packets or has non-zero granulepos Nonetheless, most media players can play these files without any problem. A notable exception is

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

Hi everybody! I encountered a strange problem with ices-2.0.0. I use a icecast2/ices2 combo ti stream live audio and I use ices to record my stream. This worked well until last week. Since then the recording function produces somehow corrupt ogg-files. I cannot decode them to wav with oggdec, the program tells me "Only one logical bitstream currently supported". ogginfo prints out

Apologies if this is know. But I've spent most of today Googling for a way to get this working, and to me, something is wrong here. But it might well be me. Anyway... I've been trying to record direct from the soundcard into an ogg file. I came up with rawrec -t 10 | oggenc -r -Q -q 5 - > foo.ogg which partially works. ogg123 will play it, but ogginfo reports Warning: Hole in

I have several corrupted ogg files; I believe they were created several years ago with grip, and that the corruption is not disk corruption but just something wrong with the encoder at the time. I would rather not have to re-rip these discs. The error I see with ogginfo is Warning: Hole in data (18000 bytes) found at approximate offset 702086827724505088 bytes. Corrupted ogg. Warning: Hole

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

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:

dear list, i am trying to write a small program which reads an ogg file and writes it to another ogg file (and changes serial number, granulepos etc on the fly). reading the ogg file is ok (ogg_sync_pageout, ogg_stream_pagein, ogg_stream_packetout). but writing the file doesn't work - the granulepos and page structures don't match with the original file. here's what i am doing.

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

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