similar to: libogg 1.3.0 ?

Hi there, I maintain the libvorbis, libogg and vorbis-tool package for Fink <http://finkproject.org/ >. Recently I had time to wonder about those again. In particular, since I was informed libsndfile self-tests fails with 1.2.0, but not with a version dubbed 1.2.1rc1 somebody sent me. Also trunk seems to contain security fixes. In https://trac.xiph.org/browser/trunk/vorbis/CHANGES

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:

Hi there, I just wanted to submit a patch for libao on http/::trac.xiph.org. The page tells me: "If you would like to report a bug or request a feature, please add a ticket." with a link. When I follow that link, it asks me for a username & password. Same for the "login" button, of course. However, I have not been able to figure our where and how I would go

[Sorry if this is a duplicate post. My original didn't appear to have gotten through.] I had previously installed libao, libogg, libvorbis, and vorbis-tools, as linked from the RC3 download page at vorbis.com -- I downloaded and installed the latest versions of these four libraries from the vorbis.com download page, at which point my pyogg/pyvorbis Python bindings broke. I reinstalled the

Hello I am new at this. I have compiled the libogg and libvorbis libraries and installed them on my MacOS X machine. The libao cannot be compiled yet since stuff is missing. But I only want to play round with encoding right now. So I also unpacked the vorbis tools distribution and am in oggenc. In oggenc I do a cc *.c -I. -L/usr/local/lib -logg -lvorbis -lvorbisenc I get unknown symbols

Hi, I have downloaded the following files libao-0.6.0.tar.gz libogg-1.0beta4.tar.gz libvorbis-1.0beta4.tar.gz vorbis-tools-1.0beta4.tar.gz as said from the download section. But I'm at a loss to what do after that. I don't have much experience/knowledge in compiling etc, but I still want to try out ogg. (I downloaded the source coz I have an OpenBSD machine, and there was no

Slackware 7.1/Linux 2.2.16 Downloaded latest tar gz's: libao, libogg, libvorbis Proceeded to ./configure | make | make install on each libao went fine libogg on the 'make' gives me all 'Nothing to be done' messages libvorbis on the './configure': checking for Ogg... no *** Could not run Ogg test program, checking why... *** The test program compiled, but did not

Form the vorbis.com homepage: "Ogg Vorbis does not compromise quality for freedom. Its stunning quality is coupled with aggressive features like fast bitrate scaling, surround channels, and fast sample-granularity seek and decode." This makes me wonder... -- What is "fast bitrate scaling"? -- I've never seen anything in the source supporting surround channels. -- I

I'm trying to clean up CVS, getting everything where it should be, because pretty soon we're going to have to build SDK's and whatnot, and I want that to be easy. We're basically going to have 3 libraries: 1) libogg 2) libvorbis 3) libvorbisfile I have separated libogg out from the rest of the code, cleaned it up, got it doing 'make dist' and rpms and imported this into

Hello, I am trying build vorbis-tools-1.1.1 in the framework of my tool (see signature). The essence of the tools is that it builds and install everything locally, and, of course, it uses the available mechanisms to specify search paths for both headers and libraries; the tool first builds dependencies abd then the target itself. So, for example, 'configure' for vorbis-tools-1.1.1 is

Here's an updated set of patches to fix some problems with the build process. These patches are relevant to the CVS head as of 30 Dec 2000. Overview: - Patch 1: Allowing the user to set CFLAGS/LDFLAGS before running configure in all four modules. All these patches do is essentially: cflags_save="$CFLAGS" ldflags_save="$LDFLAGS" # ... stuff to

I ran into a dependency problem while compiling the CVS snapshot which did not occur while compiling the beta 3 tarballs. For some missing resources, autogen.sh echoes very helpful messages (such as if automake is not present), but there was no indication that the kdelibs-devel package was required for ao (in order to get artsc.h into /usr/include - I'm sure it is possible to edit the

Any objections to sorting the list of projects on http://xiph.org/downloads/ alphabetically? This is the order that we have currently: libogg libvorbis vorbis-tools libtheora libspeex libflac libao libxspf vorbis-java I can do it if you let me. Sebastian

The beta4 rpms from the vorbis.com site do not install the link to libogg.so.0: lrwxrwxrwx 1 root root 15 Mar 16 18:24 libogg.so.0 -> libogg.so.0.1.0 -rwxr-xr-x 1 root root 16269 Feb 26 04:53 libogg.so.0.1.0 The source dist does it correctly: lrwxrwxrwx 1 root root 15 Feb 27 13:03 libogg.so -> libogg.so.0.1.0 lrwxrwxrwx 1 root root

Hi, I have compiled the Vorbis libraries and tools on Solaris 8 using Forte 6 update 2. I am now trying to run ogg123 but nothing happens: $ ogg123 -v Pateras.ogg Audio Device: Sun audio driver output Author: Christian Weisgerber <naddy@openbsd.org> Comments: Outputs to the sun audio system. I have also worked around bug #191 by defining HAVE_SQRTF:

Hi all. I found some references to a problem similar to mine in the archives, but none of the solutions posed there worked, so I'm left to ask again. I'm running Debian 2.2r5, libc6, and as far as I know all other necessary libraries for compilation. libao and libogg compile and install fine, but when I try run ./configure for libvorbis, it fails and says it can't find libogg.

All, I've released a new libogg today. Version 1.3.0 includes Greg Maxwell's ogg_stream_flush_fill() call, which does the same thing as ogg_stream_flush() but allows the caller to specify the page spill threshold if pages outside the usual 4k target are desirable. This is used by the new opus tools to better control latency. The codebase is otherwise the same at the 1.2 series. We

All, I've released a new libogg today. Version 1.3.0 includes Greg Maxwell's ogg_stream_flush_fill() call, which does the same thing as ogg_stream_flush() but allows the caller to specify the page spill threshold if pages outside the usual 4k target are desirable. This is used by the new opus tools to better control latency. The codebase is otherwise the same at the 1.2 series. We

All, I've released a new libogg today. Version 1.3.0 includes Greg Maxwell's ogg_stream_flush_fill() call, which does the same thing as ogg_stream_flush() but allows the caller to specify the page spill threshold if pages outside the usual 4k target are desirable. This is used by the new opus tools to better control latency. The codebase is otherwise the same at the 1.2 series. We

hi, i am trying to load vorbis tool on to my arm board EDB9302 , till now i have cross compiled libao, libogg, libvorbis, flac, speex and vorbis tool. when i run the command line arm-linux-ogg123 with some sample ogg format file on my arm board it gave *"Could not load default driver and no driver specified in config file : Exiting"* , please help me to over come this error.