search for: indclud

...the description on the wiki. For skeletons generated with ffmpeg2theora or libtheora, the message header offset is set to 0x2c=44. That's the start offset of 52 within the bone, less the size of the fisbone\0 identifier. oggi-index is generating them with the message header offset of 52, so indcluding the fisbone length, *but* still seems to write the the message headers from 52 bytes in from the start of the fisbone (not 60 as the offset might suggest). Is that a bug, or am I just mis-understanding something? Thanks Nick

...on the > wiki. For skeletons generated with ffmpeg2theora or libtheora, the message > header offset is set to 0x2c=44. That's the start offset of 52 within the > bone, less the size of the fisbone\0 identifier. oggi-index is generating > them with the message header offset of 52, so indcluding the fisbone > length, *but* still seems to write the the message headers from 52 bytes > in from the start of the fisbone (not 60 as the offset might suggest). Is > that a bug, or am I just mis-understanding something? > > Thanks > Nick > ____________________________________...

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