similar to: Indexing Ogg files for faster seeking

Hi everybody, I've updated OggIndex to now output Skeleton 4.0 tracks. The differences between Skeleton 3.x and Skeleton 4.0 with OggIndex is: * The fisbone packet now includes a "Radix" field. * The fisbone packet now includes two new compulsory message headers; "Role" and "Name". * The fishead packet no longer includes "start time"

On 06/10/2010 09:25 PM, Chris Pearce wrote: > I looked at Benjamin's proposal, it does indeed produce much better > compression. However I decided not to use it because I felt it was too > complex. For the record, the Skeleton 4.0, as implemented by OggIndex, currently requires a multi-round iteration to produce. The encoder produces the index, then shifts the file content

On 10 May 2010 23:20, Chris Pearce <chris at pearce.org.nz> wrote: > The granulepos radix was something that Conrad and Ralph were talking about > at FOMS2010. I don't know how it's supposed to be used, or why we need it. > It was supposed to be needed for Dirac? Maybe Ralph or Conrad can remember? > If not, we should remove it. There's no point in adding a poorly

On 31 May 2010 20:51, Chris Pearce <chris at pearce.org.nz> wrote: > Ok, thanks Silvia. I'll keep working on OggIndex/Skeleton 4.0 without > the new granulepos fields, and if they're ready in time I'll include > them, otherwise they can wait until Skeleton 4.x. I was waiting for Monty so summarize his ideas too, but from the irc discussion, it sounds like the extra

On 06/10/2010 08:16 PM, Chris Pearce wrote: > I have no plans to change the 'index' packet format further. I have proposed an alternative formulation of the index packet at http://github.com/bemasc/OggIndex/blob/master/Proposed-modified-spec.txt That repository also contains a working implementation of the alternative formulation. I have reviewed the details with Chris extensively.

On Tue, Jun 1, 2010 at 12:56 PM, Monty Montgomery <monty at xiph.org> wrote: > On Mon, May 31, 2010 at 10:51 PM, Timothy B. Terriberry > <tterribe at email.unc.edu> wrote: >> Chris Pearce wrote: >>> ? Hi Guys & Gals, >>> >>> I need you guys to decide whether we want to include extra granulepos >>> fields to Skeleton 4. Given the

On Sat, 23 Aug 2014, Silvia Pfeiffer wrote: > What does oggz-info tell you about the file when you've merged it > (without skeleton)? It may say that there are two logical video > bitstreams, because they've come from different files. So, two > skeletons may actually be correct. There should be (and are) two logical video streams - I'm trying to create a file with a

On Sat, 23 Aug 2014, Silvia Pfeiffer wrote: > I would merge them with oggz-merge without skeleton and then add > skeleton using oggindex e.g. > http://git.xiph.org/?p=OggIndex.git;a=summary . (oggindex is also > available from http://firefogg.org/nightly/ ) Ah, that looks like the tool I was looking for! Nearly there now... With a theora+speex file, or a theora+opus file, it

Chris Pearce wrote: > Hi Guys & Gals, > > I need you guys to decide whether we want to include extra granulepos > fields to Skeleton 4. Given the underwhelming discussion regarding this, > I'm guessing the need and/or desire for these fields isn't really there. I haven't commented mostly because I don't know what Monty's plans for a "grand unified

Is anyone working on liboggplay, and if so, is there any plan to support keyframe-based seeking? I found this, but seems to me that the feature ought to be part of liboggplay: http://pearce.org.nz/2009/05/video-seeking-improvements.html Is there a more appropriate list to post to regarding liboggplay? Shayne Wissler -------------- next part -------------- An HTML attachment was scrubbed...

I'm happy with it. How are you creating the new message header fields? A default role of audio/main and video/main on the first tracks? And a default of "audio_1" and "video_1" on the name? Or is it enforced as parameters on the command line? Cheers, Silvia. On Fri, Jun 11, 2010 at 10:16 AM, Chris Pearce <chris at pearce.org.nz> wrote: > ?Hey all, > >

One of the issues I've consistently run into with the cortado player app is seek behavior, so I was curious to see how cortado handles video encoded with the latest ffmpeg2theora (0.26) and the new -seek-index option, so I tried converting an h.264 video: ffmpeg2theora tronlegacy-tsr1_480p.mov --seek-index This output the following advisory messages: > Allocated 372 bytes for theora

I've been looking over Benjamin Schwartz's Skeleton A-mod proposal. I've been pretty busy with other projects over the past few months, so haven't had a chance to look at Ogg indexing until now... In general, I think Benjamin's ideas are sound, they're improvements, and I'm open to being convinced to take them in the next index version. We may as well get the index

Hi, What are the two granule rates in a fishead packet supposed to be for ? Since each of the streams has a corresponding fisbone packet with its own granulerate in it, and they can be all different, wha does the presentationtime num/den means ? Also for hte basetime num/den, since the UTC time which is also present in fishead seems to be a textual representation rather than a linear count ?

I need to be exposed to a way of seeking theora streams. I have repeatedly found the same question asked on a different forums but could not find an answer. I'm working on a game and started integrating video with theora, the sound works just fine with ogg/vorbis(i find it easy to seek using ov_raw_seek for audio files). Could someone please point me to some example/code of how can i seek with

Oggz 0.9.8 Release ------------------ Oggz comprises liboggz and the command-line tools oggzinfo, oggzdump, oggzdiff, oggzmerge, oggzrip, oggz-chop, oggz-comment, oggz-scan, oggz-sort and oggz-validate. oggz-chop can be used to serve time ranges of Ogg media over HTTP by any web server that supports CGI. liboggz is a C library providing a simple programming interface for reading and writing Ogg

Oggz 0.9.8 Release ------------------ Oggz comprises liboggz and the command-line tools oggzinfo, oggzdump, oggzdiff, oggzmerge, oggzrip, oggz-chop, oggz-comment, oggz-scan, oggz-sort and oggz-validate. oggz-chop can be used to serve time ranges of Ogg media over HTTP by any web server that supports CGI. liboggz is a C library providing a simple programming interface for reading and writing Ogg

As the title says. Cheers -------------- next part -------------- A non-text attachment was scrubbed... Name: oggzinfo-leaks.diff Type: text/x-patch Size: 2591 bytes Desc: not available Url : http://lists.xiph.org/pipermail/ogg-dev/attachments/20080602/9e045616/attachment.bin

On 11/06/2010 1:48 p.m., Benjamin M. Schwartz wrote: > On 06/10/2010 09:25 PM, Chris Pearce wrote: >> I looked at Benjamin's proposal, it does indeed produce much better >> compression. However I decided not to use it because I felt it was too >> complex. > For the record, the Skeleton 4.0, as implemented by OggIndex, currently > requires a multi-round iteration to

David Flynn has proposed a new Ogg Dirac mapping. The draft is here: http://davidf.woaf.net/dirac-mapping-ogg.pdf This is a much bigger break from other codecs than my draft (at http://wiki.xiph.org/index.php/OggDirac). We talked a bit about it on IRC today. Below is my summary; hopefully David can correct anything I got wrong or misleading. Comments? There are two main differences