search for: fisbone

...Role = video/main * Content-Type = video/theora * Bone 3 - Message Headers: * Name = video_1 * Role = video/main * Content-Type = video/theora How can I edit that to say which video is main and which is alternate? Are there options to pass to ogg-index for that? Or is there a magic fisbone-comment / skeleton-comment tool out there I need to use? Oh, and one other thing - I'm not sure that the fisbone's generated by ogg-index are quite right, at least not based on the description on the wiki. For skeletons generated with ffmpeg2theora or libtheora, the message header offs...

...; with it! If there is one file containing video #1 followed by video #2, I could see it wanting multiple skeletons. I may have mis-read the specs, but for one video with main video + alternate angle video + english audio + french audio, I would've thought that should be one skeleton with a fisbone per track, with the fisbone's describing the relations between the tracks? Thanks Nick

Hi, this updates the sizes of the fisbone ogg_packets after the removal of the x- prefixes. Not tested, don't have ffmpeg on this machine, but compiled nonetheless :) Cheers -------------- next part -------------- A non-text attachment was scrubbed... Name: ffmpeg2theora-fisbone-size.diff Type: text/x-patch Size: 2632 bytes Desc: not...

...video/theora > * Bone 3 - Message Headers: > * Name = video_1 > * Role = video/main > * Content-Type = video/theora > > How can I edit that to say which video is main and which is alternate? Are > there options to pass to ogg-index for that? Or is there a magic > fisbone-comment / skeleton-comment tool out there I need to use? > > > Oh, and one other thing - I'm not sure that the fisbone's generated by > ogg-index are quite right, at least not based on the description on the > wiki. For skeletons generated with ffmpeg2theora or libtheora, the...

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" and "end time" fields. * The index packets for...

I've developed an indexer which embeds a keyframe index track in Ogg files. It embeds the index in its own track, so that players that don't understand or don't want to use the index can just ignore it. Ogg needs this to make seeking over networks faster and more efficient. Currently we must do a bisection search when seeking, which usually takes aound 6 HTTP requests, give or

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 ? Thanks

...ogg-dev, where people (*cough* Silvia *cough) might have a better view of how to use those. He mentioned the possibility of using X-Language-Category as well. Essentially, I'm not sure if the choice for those fields has any impact on anything using Skeleton, since this might find its way into a fisbone. Cheers

...If there is one file containing video #1 followed by video #2, I could see > it wanting multiple skeletons. I may have mis-read the specs, but for one > video with main video + alternate angle video + english audio + french > audio, I would've thought that should be one skeleton with a fisbone per > track, with the fisbone's describing the relations between the tracks? > > Thanks > Nick > _______________________________________________ > ogg-dev mailing list > ogg-dev at xiph.org > http://lists.xiph.org/mailman/listinfo/ogg-dev

...en type needing different roles+names. I've also produced proposed patches for all three problems, which seem to fix the issues enough for my needs. For anyone interested in the problems and/or interested in reviewing + applying the patches, the bugs are: https://trac.xiph.org/ticket/2041 - fisbone header offset https://trac.xiph.org/ticket/2042 - unsupported stream error message https://trac.xiph.org/ticket/2043 - roles+names on subsequent streams Nick

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

Hi All I'm currently trying to put together an ogg file with two theora streams, a handful of audio streams (probably mixed vorbis and opus), and a Skeleton stream that describes their relationships to each other. I had hoped to be able to use the oggz suite of tools, but I can't seem to get that to work. To generate my theora files, I'm using ffmpeg2theora, which will happily

...html [1] RFC3533: http://www.ietf.org/rfc/rfc3533.txt New in this release ------------------- The hogg tool contains new subcommands: sort, selfcheck Improved handling of Ogg Skeleton tracks in chop, merge and rip subcommands: * merge: Ensure that the output contains only one Skeleton track. Fisbones from Skeleton tracks of second and subsequent files are copied into the first Skeleton track. * chop: Handle rewriting of Skeleton when chopping files which already have a Skeleton track. Ensure to re-use the existing track serialno and metadata, but rewrite the presentation tim...

...s and skeleton bistream is present > in the file. The command line options are -k and --skeleton. > > The skeleton API has also been updated. Fields to hold version number > has been added in fishead_packet. Also new methods are added to allow > conversion from ogg_packet to fishead/fisbone packets. A method to > write an ogg_page to file has been added to remove dependency. > > Cheers, > --tahseen

...ferent logical bitstreams. * identification of logical bitstreams: http://annodex.net/TR/draft-pfeiffer-annodex-02.txt Skeleton provides all the functionality required to get information about the logical bitstreams without a need for decoding. The logical bitstream's serial number is in the fisbone header. In addition, each of the logical bitstreams gets protocol-type information through the message-header field. "Content-type:" is mandatory (it has the mime type as currently being specified by http://wiki.xiph.org/index.php/MIME_Types_and_File_Extensions. There is currently not a &...

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

...e (*cough* Silvia *cough) might have a better view > of how to use those. He mentioned the possibility of using X-Language-Category > as well. Essentially, I'm not sure if the choice for those fields has > any impact on > anything using Skeleton, since this might find its way into a fisbone. > > Cheers > _______________________________________________ > ogg-dev mailing list > ogg-dev at xiph.org > http://lists.xiph.org/mailman/listinfo/ogg-dev >

On Wed, 2008-07-16 at 13:37 +0900, Conrad Parker wrote: > was this all since 0.9.8? > > If it was a little before that, it may have been an instance of > http://trac.annodex.net/ticket/404 > > otherwise, if you do come across such a case please keep the file and > report it -- it's not easy to find corner cases. if there is a skeleton stream in the file it could be the

Hi, I've seen several implementations of Ogg demuxing that use a zero granulepos to detect headers. However, I do not recall seeing this in the Ogg docs - is this an abuse that happens to work because Vorbis is timed by end granule, or is it a proper way to check ? Thanks

Ralph, Conrad, Now that we have ROE as a means to describe a multi-track ogg file - i.e. a means to author Skeleton - I assume this is supposed to describe how we map ROE information into Skeleton through the use of fisbone message header fields, right? In this case I wonder if you have gone over all the current ROE spec and made sure that all this information is either in ROE or easily extractable from a logical bitstream? I just wonder if this might expose some unsolved issues for ROE. Looking forward reading the...