similar to: vorbis-tools release

I'm pleased to announce the release of libvorbis and vorbis-tools 1.1.1. These releases include some bug and documentation fixes, but no new encoder modes. However, oggenc from this release now properly supports the new CBR engine introduced in libvorbis 1.1.0 but the 1.1.1 release of both libraries is required for things to work properly. Not that there was never a 1.1.0 release of

I'm pleased to announce the release of libvorbis and vorbis-tools 1.1.1. These releases include some bug and documentation fixes, but no new encoder modes. However, oggenc from this release now properly supports the new CBR engine introduced in libvorbis 1.1.0 but the 1.1.1 release of both libraries is required for things to work properly. Not that there was never a 1.1.0 release of

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

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

I just moved a bunch of shared code (like 4 copies of getopt) into a share directory within vorbis-tools. I also moved the UTF-8 code from oggenc into the vorbis-tools/share directory as well so that it could be used by all of the tools, since they all need to handle UTF-8 comments correctly. Header files for the shared code are stored in vorbis-tools/include. I have already fixed vorbiscomment

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

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

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

ping On Jun 23 09:05:38, hans at stare.cz wrote: > Dear authors of vorbis-tools, > > the manpages are currently writen using the man(7) markup language. > Would there be any interest in having them rewritten to mdoc(7)? > > The mdoc(7) language allows for _semantic_ markup, expressing > things like "this is an optional argument", as opposed to the physical >

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

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?

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,

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

Again, Hi All, Thanks for your replies. I probably should've mentioned that I'm not subscribed to the list but I found your answers on the archives. I just wanted to go on record and mention that I do in fact have all the original CD's and that by re-encoding I meant repeating the entire process of ripping the original CD's (with cdparanoia (of course ;)) and then encoding them

Hi, Regarding to my previous question, I think I have found out from oggenc source code that the correct way to initialize encoding is: vorbis_encode_init_vbr (or vorbis_encode_setup_managed for cbr etc.) vorbis_encode_ctl (to turn off or use avg bitrate management) vorbis_encode_setup_init By this way, there is no problem with encoded stream. However, there is no documentation of the three

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

2009/4/2 Ian Malone <ibmalone at gmail.com>: > If no-one is keen then I'll take the vorbiscomment and ogginfo > patches. ?They are lower priority than actually updating the wiki, but > I might be able to do that this evening. > Adding a -s option to ogginfo and vorbiscomment to hide METADATA_BLOCK_PICTURE contents git://github.com/imalone/imalone_vorbis-tools.git

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