similar to: getting playback length from ogg vorbis file

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

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

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

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

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

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

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

Good day. I don't know if anyone cares, but I just noticed the new vorbis 1.1.0 isn't showing itself to be 1.1.0 in the created streams. The previous releases did: $ find -name "*.ogg" -print0 | xargs -0 ogginfo | grep ^Vendor | sort | uniq Vendor: Xiph.Org libVorbis I 20020717 (1.0) Vendor: Xiph.Org libVorbis I 20030909 (1.0.1) Vendor: Xiph.Org libVorbis I 20040629 That

Hi, I have some *.ogg file got by streamripper which seems to be broken. # ogginfo file.ogg Processing file "file.ogg"... New logical stream (#1, serial: 20236f01): type vorbis Vorbis headers parsed for stream 1, information follows... Version: 0 Vendor: Xiph.Org libVorbis I 20050304 Channels: 2 Rate: 48000 Nominal bitrate: 224,000000 kb/s Upper bitrate not set Lower bitrate not set

Hi, I have a broken ogg file. ogginfo reports the playback length as 1:14 Both xmms and ogg123 report the length correctly at 5:19. So I re ripped the wav and re-encoded the file, same thing. I am uploading the ogg at the moment (it might take an hour) if anyone wants to have a look. http://www.zoism.org/ogg/broke.ogg I dont know if it will help, but I really cant upload wav, a my modem

2009/6/26 Adam Rosi-Kessel <adam at rosi-kessel.org>: > Can I fix the checksum with a hex editor? I just realized that the hogg tools will fix the CRC issues (by design accident: hogg ignores the CRC on reading but sets it correctly on writing). "hogg rip" rewrites the pages (fixing the CRC), and "hogg reconstruct" also rewrites the I've uploaded the outputs of

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

hi yorn and all, thank you oggvideo tools for windows. it is great... i can live with the command line for now myself but i will need to make some art students work with oggvideotools and they may not be happy with that:D anyway your video tutorial is also good (but it also crashed my firefox 3.5 beta 4 for two times on windows and i have reported that to mozilla), i would love to help for that

Can I fix the checksum with a hex editor? Sent from my iPhone On Jun 25, 2009, at 3:23 PM, Monty Montgomery <monty at xiph.org> wrote: > Confirmed--- the checksum on the second page (the comment page where > the album art was added) is incorrect. Vorbis players are not allowed > to decode any stream in which one of the setup headers is corrupt, and > a bad checksum counts as

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

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

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

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