[opus] How to identify packets to input to opus_decode()

Matthew Chung matthewchung74 at gmail.com
Tue Apr 30 12:54:46 PDT 2013


Hi HK,

i don't believe you need open ssl for the embedded system.  at least for
ios, i was able to compile and run the opusfile examples

https://github.com/captainchung/opusfileIosExample

which links to vorbis and ogg but does not link to open ssl.


On Tue, Apr 30, 2013 at 11:03 AM, hk at woohing <hk at woohing.net> wrote:

> Hi Ralph,
>
> Thanks for your prompt reply. For OpenSSL, is it needed for embedded
> system? And where to download it?
>
> 從我的 iPhone 傳送
>
> Ralph Giles <giles at thaumas.net> 於 2013年5月1日 1:09 寫道:
>
> > On 13-04-30 5:45 AM, HK Wong wrote:
> >
> >> So each libopus packet begins by a TOC byte as stated in RFC6716? And
> >> the no. of bytes of each packet usually denoted by the segment table
> >> entries in the ogg layer? If the TOC byte is also needed to feed into
> >> libopus?
> >
> > Yes. The TOC byte is part of the Opus data packet and must be fed to the
> > libopus decoder.
> >
> >> And for libopusfile, it needs to run with libopus and also libogg?
> >
> > opusfile needs libopus, libogg, and openssl.
> >
> >> is this (http://downloads.xiph.org/releases/ogg/libogg-1.3.0.zip) the
> >> download link for libogg?
> >
> > Yes, that's the latest release.
> >
> > -r
>



-- 
Regards,
Matthew
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.xiph.org/pipermail/opus/attachments/20130430/ac74aca1/attachment.htm 


More information about the opus mailing list