Welcome Guest ( Log In | Register )

Opus inside OggPages, Decoding a live Opus internet stream
post Nov 14 2012, 06:15
Post #1

Group: Members
Posts: 12
Joined: 14-November 12
Member No.: 104501

I'm currently working on a Winamp input plugin to provide better native support for the Opus codec than the one that dshow could provide linking in the k-lite codec pack. Metadata and whatnot.

Anyways, I'm dynamically linking in the official opusfile-0.1-win32 libraries from the opus-codec site and I have been able to succesfully decode and get Winamp to play a local .opus file. However, I've not been so fortunate with online streams.

I am not familiar at all with any of the internals/packets/pages/whatevers of live streams. I can get my plugin to connect to a server, get the data it's outchucking, parse out the HTTP header, parse the seperate Ogg Pages, get the OpusHead, and get the OpusTags, but that's it. I tried sending, just the Ogg pages, a chain of Ogg pages, individual segments in the pages, to all of the in-memory functions of the libraries but they all either return error code -133 (OP_EBADHEADER), -137 (OP_EBADLINK), or -139 (OP_EBADTIMESTAMP).

I know nothing of "granules", whatever that means.

Can somebody tell me how to decode an Ogg Opus stream with those libraries or if it's not possible to?



This post has been edited by thinktink: Nov 14 2012, 06:19
Go to the top of the page
+Quote Post
Start new topic
post Nov 19 2012, 12:05
Post #2

Group: Developer
Posts: 693
Joined: 22-November 10
From: Japan
Member No.: 85902

Made a (quick & dirty) patch for opusfile, which opens http support on win32:
Attached File  winsock.patch.gz ( 5.11K ) Number of downloads: 131

This patch is built against the latest commit of the official git repository:
commit f2e27e4d1aa6e1b12b1af5bce166d1c3b10473dd
Author: Ralph Giles <giles@mozilla.com>
Date:   Wed Nov 14 11:05:32 2012 -0800
I used mingw-w64 toolchain on Linux.

Some tweak might be still needed to take care of OPENSSL_AppLink to get https support working.
In win32, user application of openssl is required to do
#include <openssl/applink.c>
or something, when openssl is compiled with OPENSSL_USE_APPLINK.
I don't know how it should be taken care of, from the library point of view (it must be done by user of libopusfile, since openssl always searches that function in executable module).
Go to the top of the page
+Quote Post

Posts in this topic

Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:


RSS Lo-Fi Version Time is now: 30th November 2015 - 12:51