search for: diracvideo

On Thu, Aug 14, 2008 at 9:14 PM, Silvia Pfeiffer wrote: > The IETF has a final draft of our RFC at > ftp://ftp.rfc-editor.org/in-notes/authors/rfc5334.txt (yes, it goes > from 3534 to 5334 - funny!). Didn't we decide YUV4MPEG should be 8 octets as well? -r

...ecent updates to support Dirac), and if so could you please explain what the problems are, or point me to a bugtracker where they are reported. eg. There's nothing in http://trac.annodex.net/query?status=new&component=liboggz Here's some oggz output that seems a bit fishy. Using http://diracvideo.org/download/test-streams/ogg/sage-640x360.ogg and current liboggz svn, http://svn.annodex.net/liboggz/trunk/ : conrad at chichai:~/share/dirac$ oggz validate --max-errors 0 sage-640x360.ogg 2>&1 | wc -l 135 conrad at chichai:~/share/dirac$ oggz validate sage-640x360.ogg sage-640x360.ogg:...

...ould be 8 octets as well? > > I've just noticed that the URL for the dirac spec is outdated > >> [Dirac] Dirac Group, "Dirac Specification", >> <http://dirac.sourceforge.net/specification.html>. > > Should be: > <http://www.diracvideo.org/specifications/> > > ..david > > _______________________________________________ > ogg-dev mailing list > ogg-dev at xiph.org > http://lists.xiph.org/mailman/listinfo/ogg-dev >

...r as Dirac goes. The question then becomes how well the Dirac mapping would work for other reordering codecs, and whether we want to add two (or three!) additional granulepos interpretation fields to the fishbone spec in case other codecs want to make different resolution tradeoffs. -r * http://diracvideo.org/download/mapping-specs/dirac-mapping-ogg-1.0.pdf

...n the oggz tools is currently correct, as I'd like to do a release of > these soon. I believe it is -- although if correct support in the rest of the liboggz tools is required, a little more work may need to happen. > Here's some oggz output that seems a bit fishy. Using > http://diracvideo.org/download/test-streams/ogg/sage-640x360.ogg and > current liboggz svn, http://svn.annodex.net/liboggz/trunk/ : The only niggle i have with this file is that the EOS page has a bizare timestamp. imho, because there is no picture in the eos page, there is no meaningful time for it, so the gra...

...s Ogg Dirac never contain VorbisComment metadata? It seems oggz chop, merge and sort will need some attention to deal with the Dirac granulepos and dependency ordering, so let's leave them for the next release. >> Here's some oggz output that seems a bit fishy. Using >> http://diracvideo.org/download/test-streams/ogg/sage-640x360.ogg and >> current liboggz svn, http://svn.annodex.net/liboggz/trunk/ : > > The only niggle i have with this file is that the EOS page has a bizare > timestamp. imho, because there is no picture in the eos page, there is > no meaningful...