search for: opusfile_api

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: <http://lists.xiph.org/pipermail/opus/attachments/20200812/2936dd3c/attachment.html>

...opusurl depends on opusfile and openssl. The library is functional, but there are likely issues we didn't find in our own testing. Please give feedback in #opus on irc.freenode.net or at opus at xiph.org. Programming documentation is available in tree and online at https://opus-codec.org/docs/opusfile_api-0.7/index.html or https://opus-codec.org/docs/opusfile_api-0.7.pdf SHA-256 checksums 9e2bed13bc729058591a0f1cab2505e8cfd8e7ac460bf10a78bcc3b125e7c301 opusfile-0.7.tar.gz 346967d7989bb83b05949483b76bd0f69a12c59bd8b4457e864902b52bb0ac34 opusfile-0.7.zip c4c4c57b6b4bc9780a08c1e6300cc35846671bee61d84...

...im'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 http://opus-codec.org/docs/opusfile_api-0.5/ Changes since the last release: - Report HTTP (ICY) headers to client - New tag comparison and copy functions - New application decoding callback API for advanced clients - New dither disable function for advanced clients - constify API - Avoid clipping downmixing from a fixed-point de...

Hello. When trying to access a url with op_test_url, ther is that error message: error: op_test_file: -129 What is error -129 (and how to know meaning of int messages) ? Thanks. Fre;D -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.xiph.org/pipermail/opus/attachments/20170123/be547250/attachment.html>

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

Hi, Dear alls I had encounted a problem in using opus-tool-0.2-opus-1.3(download from www.opus-codec.org, Win64 binaries: opus-tools-0.2-win64.zip). First, I use opusenc to generate a opus file which input is a 9-channels wav file. The opusenc can work. Then, I use opusdec to transform the generated opus file to wav file, but opusdec can't work. I received the error message: failed to open

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