similar to: libogg HOWTO

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 I'm pleased to announce the release of libogg 1.3.2. The 'libogg' library is Xiph.Org's reference implementation of the Ogg media container. This release fixes an issue which could cause oggpack_write to fail. There are no other substantial changes. Upgrading is recommended for all users. *

Hi, today I learned that libogg 1.3.0 had been released in August 2011. Curiously, there seems to have been no announcement mail here, and it is not being mentioned on <http://www.xiph.org/press/> either. Is that on purpose? Is there some other channel I could subscribe to in order to learn about updates? Freecode.com doesn't have up-to-date info either (though I just submitted a 1.3.0

Xiph.Org is pleased to announce a release cacndidate of libogg 1.1.4. This release candidate will have a trial period of two weeks followed by full release. The only changes between now and the full release date will be fixes to any regressions we may have missed in the release testing process. This is intended to be a fully stable release and the hope is the 'rc' moniker is a formality.

Any time code is stuck in a loop calling ogg_sync_pageseek() or ogg_sync_pageout(), you'll see most of the time sunk into checksum calculation. It's the only thing in libogg that _can_ take much time. This is not likely a libogg bug, but a bug in the code calling libogg in a tight loop. Looking at the file listed in the bug, there's a page discontinuity at the very beginning; after

Xiph.Org is pleased to announce a full release of libogg 1.2.0. Changes in the new libogg release include: - A new default flushing behavior that reduces overhead for moderate and high bitrate streams, such as video - Documentation updates - Various build fixes intended to keep the autofoo and Windows build mechanisms up to date - Build fixes for additional compilers This release is ABI

Am 03.12.2013 23:49, schrieb Monty Montgomery: > Any time code is stuck in a loop calling ogg_sync_pageseek() or > ogg_sync_pageout(), you'll see most of the time sunk into checksum > calculation. It's the only thing in libogg that _can_ take much time. > This is not likely a libogg bug, but a bug in the code calling libogg > in a tight loop. > > Looking at the file

Xiph.Org is pleased to announce a full release of libogg 1.2.1 and libvorbis 1.3.2. This is not a coordinated release, it was merely convenient to do a release cycle for both at the same time. Changes and fixes in the new libogg release include: * Various build updates (see SVN) * Add ogg_stream_pageout_fill() to API to allow applications greater explicit flexibility in page sizing. *

Folks, the packets I want to place in an ogg stream are concatenations of two hunks of memory. Rather than memcopy() them into one then pass them to libogg, I patched framing.c to accept iovecs. The unified diff is 80 lines, minus the OS-specific stuff for defining struct ogg_iovec_t - pretty trivial. Is there any interest in it? Or is libogg frozen while all efforts are concentrated on

Hello, ogg-dev team. I'm Takeo Arai. I am investigating the license of Open Sorce Software. [Question] Which license is applied to "debian rules"? The "debian rules" was detected in the Debian folder that is contained in the Libogg ?BSD 3-clause License? component. - Download: libogg-1.1.3.tar.gz < http://downloads.xiph.org/releases/ogg/ > Is this "debian

Xiph.Org is pleased to announce a full release of libogg 1.2.2. This is a spot release that contains only build and documentation fixes. Changes and fixes in the new libogg release include: * Build fix (types correction) for Mac OS X * Update win32 project files to Visual Studio 2008 * ogg_stream_pageout_fill documentation fix This release contains no library code changes, only a type

Hi all, I am curious, when do you plan to release new libogg? The current release is unusable on Mac because the u_int32_t problem. So I have to build against the trunk. If you are not ready with other features, why not release a small point release just to fix such an contained and small issue. Miki. -------------- next part -------------- An HTML attachment was scrubbed... URL:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hello devs, since this bug affect gstreamer and vlc, i assume it is libogg regression. Please take a look at this bug report: https://bugzilla.gnome.org/show_bug.cgi?id=719615 - -- Regards, Oleksij -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.14 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Alexey.Petruchik has submitted a cmake build file for libogg. https://github.com/xiph/ogg/pull/6 I'm curious how many people here would find this useful, particularly Visual Studio users. I don't object in principle, but I'm wary of adding yet another build description which would need to be maintained. -r -----BEGIN PGP

Yes please. CMake support is somehow mandatory for any C/C++ project nowadays. Death to autotools! But that's just my ignorance speaking :-) I have also commented on that pull request. Cheers, Cristian. On Wed, May 27, 2015 at 2:07 AM, Ralph Giles <giles at thaumas.net> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > Alexey.Petruchik has submitted a cmake

Mandi! Rowland Penny via samba In chel di` si favelave... [Sorry for that late post... i was very busy on other things!] > The howto also doesn't tell you that, on a DC, the 'unixHomeDirectory' > and 'loginShell' attributes are ignored. Once you have 'getent' > working, you will find that all your users have their Unix home > directories set to

Hi all, I've got a problem building libogg 1.1 on Solaris 8. I'm using the sunfreeware.com gcc and glib packages, and have been able to build other library packages (libpng, etc) without any problems. I haven't seen anybody else have this problem, so I figured I'd ask. Here's what I get, running make after a successful ./configure: /bin/bash ../libtool --mode=link

Everyone, When it rains it poors. This is to announce the release of libogg version 1.1.2. This is a bugfix release to address a problem with large packet assembly after seek. Vorbis is unlikely to trigger the bug, but it is an issue for FLAC and Theora. Thanks to Josh Coalson for finding this one, and Monty for fixing it so quickly. Source archives are available from our new download site:

Everyone, When it rains it poors. This is to announce the release of libogg version 1.1.2. This is a bugfix release to address a problem with large packet assembly after seek. Vorbis is unlikely to trigger the bug, but it is an issue for FLAC and Theora. Thanks to Josh Coalson for finding this one, and Monty for fixing it so quickly. Source archives are available from our new download site:

Everyone, When it rains it poors. This is to announce the release of libogg version 1.1.2. This is a bugfix release to address a problem with large packet assembly after seek. Vorbis is unlikely to trigger the bug, but it is an issue for FLAC and Theora. Thanks to Josh Coalson for finding this one, and Monty for fixing it so quickly. Source archives are available from our new download site:

I'm pleased to announce the release of new versions of our Ogg and Vorbis reference implementation libraries. These are bug fix releases, with no new features. Particularly important is a fix for a pointer aliasing bug triggered by the new gcc 4.x optimizer. Because of this we strongly recommend that all gcc-based users upgrade, i.e. those on GNU/Linux and MacOS X, for example. The new