similar to: Why does this code not generate a valid opus file?

Jan, Here's a hacky patch to add a few commandline options for setting comment header fields in ffmpeg2theora. It's a bit big because I virtualized the global info struct in theorautils.c. In retrospect that probably wasn't necessary, but I think it's cleaner anyway. I didn't test it because I couldn't compile ffmpeg2theora, but modulo bugs it should support

Hi all, I'm actually learning how to use ogg, theora and vorbis. My idea is to create a small program running, that is able to concatenate ogg video+audio files. However I have some small questions. Here I will start with the first one: I read the following for seeking in ogg for a theora key-frame: ---- snipp (http://www.xiph.org/ogg/doc/ogg-multiplex.html) ---- [...]The third point

Hi. I am trying to understand how to package opus-encoded data in an ogg stream to make a standards-compilant ogg/opus file. Most things are clear, but there is one thing I simply do not understand. What I do understand is that Ogg is based on pages, that each come with a fairly sizeable header (>=27 bytes). Now, I encode with a fairly low bitrate, so my opus packages are <100 bytes long.

On Wed, Oct 14, 2015 at 4:18 AM, Daniel Armyr <daniel at armyr.se> wrote: > Hi. > I am trying to understand how to package opus-encoded data in an ogg stream to make a standards-compilant ogg/opus file. Most things are clear, but there is one thing I simply do not understand. > > What I do understand is that Ogg is based on pages, that each come with a fairly sizeable header

On Wed, Oct 14, 2015 at 9:11 AM, Daniel Armyr <daniel at armyr.se> wrote: > Thanks for a very quick and very good answer. Let me just double-check one thing: > >> To put multiple Ogg Opus packets in an Ogg page, all you need to do is >> start a new segment for each Ogg Opus packet. There can be up to 255 >> segments per page. For details, see the Ogg specification:

Thanks for a very quick and very good answer. Let me just double-check one thing: > To put multiple Ogg Opus packets in an Ogg page, all you need to do is > start a new segment for each Ogg Opus packet. There can be up to 255 > segments per page. For details, see the Ogg specification: > https://tools.ietf.org/html/rfc3533 So do I understand it correctly that a decoder will

Hi. I am trying to implement an ogg codec using libogg, and testing with a piece of encoded data you can see below. It consists of 4 pages, the first two being header data, the third containing two packets of data and the last containing one packet of data. I am confused at the results I get if I corrupt the third page (The first one of the two that contain data). If I corrupt the first page,