similar to: opusfile 0.10 announcement?

opusfile version 0.9 is availble. Thanks to everyone who contributed! The opusfile and opusurl libraries provide a high-level API for decoding and seeking within .opus files on disk or over http(s). opusfile depends on libopus and libogg. opusurl depends on opusfile and openssl. Binaries for macOS will be available through homebrew soon. Changes since the v0.8 release: - Fix an invalid free

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 opusfile version 0.6 I'm pleased to annouce the latest development release of the opusfile playback library. Changes since the v0.5 release: - Fix bugs with comment handling - Fix build for BSD - Fix bugs handling invalid and non-opus streams Some of these bugs kept basic functionality of the APIs from working at all, so we recommend all

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm pleased to announce the release of version 0.5 of Tim's opusfile library for decoding and seeking inside .opus files and remote streams over http(s). This release includes some new API calls and fixes a number of mostly minor bugs from the previous release. Programming documentation for this release is available from

A new opusfile source release is available. The opusfile and opusurl libraries provide a high-level API for decoding and seeking within .opus files on disk or over http(s). opusfile depends on libopus and libogg. opusurl depends on opusfile and openssl. Changes since the v0.7 release: - Add support for OpenSSL 1.1.x. - Fix issues with tag parsing introduced in v0.7. - Fix skip logic for

I'm pleased to announce the release of opusfile v0.7. The opusfile and opusurl libraries provide a high-level API for decoding and seeking within .opus files on disk or over http(s). Changes since the v0.6 release: - Add API to access and preserve binary metadata. - Add support for R128_ALBUM_GAIN metadata tag. - Better seeking with continued packets and multiplexed streams. - Portability

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm pleased to announce the availability of opusfile v0.4. The opusfile and opusurl libraries provide a high-level API for decoding and seeking within .opus files on disk or over http(s). * https://ftp.mozilla.org/pub/mozilla.org/opus/opusfile-0.4.tar.gz * https://ftp.mozilla.org/pub/mozilla.org/opus/opusfile-0.4.zip *

We've made a new release of Tim's opusfile library. Like libvorbisfile for Vorbis files, libopusfile provides a high-level API for decoding and seeking within .opus files. Changes since the previous release: - Accept valid SSL certificates. - Various build and packaging fixes. The library is functional, but there are likely issues we didn't find in our own testing. Please give

This is the initial release of libopusfile. Like libvorbisfile for Vorbis files, libopusfile provides a high-level API for decoding and seeking within .opus files. It includes: - Support for all files with at least one Opus stream (including multichannel files or Ogg files where Opus is muxed with something else). - Full support, including seeking, for chained files. - A simple stereo

I'm pleased to announce the release of opusfile 0.12 The opusfile library provides seeking, decode, and playback of Opus streams in the Ogg container (.opus files) including over http(s) on posix and windows systems. opusfile depends on libopus and libogg. The included opusurl library for http(s) access depends on opusfile and openssl. Changes since the v0.11 release: - Fix stack overflow

Dear Opus community, I'm trying to build opusfile as a shared (.dll) library on Windows 10 using Visual Studio 2017. I know there are prebuilt libraries, but those are depending on a whole bunch of other libraries and x86 (32 bit) only. Whenever I try to build opusfile, it generates opusfile.dll, which is basically empty (no functions), which makes it unuseable. This is most likely because

The Opusfile docs do not seem to be showing after clicking links from the landing page Landing (works): https://opus-codec.org/docs/opusfile_api-0.12/index.html Subpage (blank content): https://opus-codec.org/docs/opusfile_api-0.12/group__stream__open__close.html -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi, please find attached two patches for opusfile: 1. Fix invalid pkg-config files on MinGW. 2. (trivial) Add some files to .gitignore. Two other random things I noticed: - The API reference for libopusfile linked from http://opus-codec.org/docs/ is for version 0.1. - The pkg-config files say "Description: Opus playback library". Well, the library doesn't do playback, does it?

>>> Jean-Marc Valin <jmvalin at jmvalin.ca> schrieb am 16.09.2017 um 08:12 in Nachricht <29959506-9f3b-2ad1-fc02-2aea7c53c084 at jmvalin.ca>: > Actually, you're supposed to add /usr/include/opus to your include path. > That's why the includes don't have the "opus/" prefix. Hi! But that's uncommon: You also don't put /usr/include/sys into

Actually, you're supposed to add /usr/include/opus to your include path. That's why the includes don't have the "opus/" prefix. Cheers, Jean-Marc On 31/08/17 05:20 AM, Alexander Panchenko wrote: > Hi all! > When compiling the program using opusfile the > > #include <opus/opusfile.h> > > generates error that > > # include

I've developed the unofficial Opus codec support plugin for Winamp and I have been able to keep the libopusfile libraries inside a folder inside the application's install path - "%PROGRAMFILES%\WinampNarf\opusfile" - and all seemed to be fine and dandy. However, if I try to load the new libopusurl-0.dll from the same folder as I have always done as with the other libraries, I

Hi all! When compiling the program using opusfile the #include <opus/opusfile.h> generates error that # include <opus_multistream.h> is not found. Actually it should be included as # include <opus/opus_multistream.h> just like the ogg.h in the previous line. A small patch attached. -- Best regards, Alexander -------------- next part -------------- A non-text attachment

Hi, Would you be interested in a patch to add CMake support to Opusfile? Opus already seems to have it, but I had to roll my own for Opusfile. I've attached a patch if you're interested, I've been using for a while now and it does what I need, it may not be exhaustive enough for wider distribution though. Hope it helps, Simon -------------- next part -------------- An HTML attachment

[this time compeled the mail]. The autogen.sh of opusfile doesn't work for me: Updating build configuration files for opusfile, please wait.... configure.ac:8: installing `./install-sh' configure.ac:8: installing `./missing' Makefile.am:10: Libtool library used but `LIBTOOL' is undefined Makefile.am:10: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL'

alpha thinktink wrote: > On Sun, Aug 25, 2013 at 8:53 PM, Timothy B. Terriberry > <tterribe at xiph.org <mailto:tterribe at xiph.org>> wrote: > > alpha thinktink wrote: > > You've got "_host" instead of "_user" in the definition for the macro > > for "OP_HTTP_PROXY_USER" > > Yeah, already fixed in >

I don't know. Derf? -r -------- Original Message -------- Subject: Re: [opus] opusfile 0.4 release Date: Sat, 24 Aug 2013 14:20:35 -0700 From: alpha thinktink With my old streaming thread I am able to retrieve a unicode file from a web server by converting the resource name to UTF-8 MBCS then uri encoding it before sending it to the server with "GET /[resourcename]