similar to: opusfiles 0.7 release

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

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

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

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

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

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:

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

You might want to take a look at the op_open_callbacks API: https://opus-codec.org/docs/opusfile_api-0.7/group__stream__open__close.html#ga5b81c0b685f3d3c9c7d7091e5536c759 libopusfile will only call your provided read() function as needed. If you don't implement the seeking functions, it will only read it in a linear order. On 04/06/2018 09:08 AM, Chris McGowan wrote: > I would like to

This is version 0.7 of the virtio-iommu specification. The diff from 0.6, included below, is fairly small and consists of the following changes: * Address comments from 0.6, rework bits of the implementation notes. * Change resv_mem parameters to be consistent with the rest of the spec. * Add the MMIO flag to MAP requests. At the moment it is used by mapped MSIs mostly for completeness, but

Just a report about compiler warnings generated when building opusfile from current git. Regards. # x86-Linux builds / gcc48 and clang-3.3 (no warnings) # x86-Linux builds / gcc34 src/opusfile.c: In function `op_calc_bitrate': src/opusfile.c:1777: warning: integer constant is too large for "long" type src/opusfile.c: In function `op_open2': src/opusfile.c:1131: warning:

I would like to decode an Opus file in chunks (e.g. 16K byte array). Is this possible with the Opusfile library or would I need to interface directly with libogg and libopus? It seems like the Opusfile decoder functions maintain an internal pointer/state for OggOpusFile during multiple calls to op_read(OggOpusFile *_op ...) and a complete byte array of the entire Opus file would be needed. Any

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

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

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

Hi, I was look on the website ( http://www.opus-codec.org/downloads/ ) for the latest version of opusfile and it currently says 0.9 is the latest version. However, there is a 0.10 version available at https://archive.mozilla.org/pub/opus/ and there is a Git tag for the 0.10 release ( https://git.xiph.org/?p=opusfile.git;a=tag;h=2979040b8e9086f6f452c1d567c588961bc8b5a8 ). Did you forget to

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

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 Xiph.org Team. We are using opusfile library <https://github.com/xiph/opusfile> for streaming *.opus* audio in our projects. But now we have a problem with building opusfile library for android with *ndk-build*. In particular, with arm64-v8a platform: Google removed <sys/timeb.h> from android. And now building opusfile with nkd-build crashes with error "fatal error:

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

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