similar to: [PATCH] liboggz: Update Dirac granulepos definition

Hi, I've now got another way of encoding granule (oh, not *again*, I hear you cry). I believe it's an improvement over the existing "generic" method, so I'll outline it here for your consideration. Again, it's different from what Skeleton can handle, but it's a simple superset and would be easy to add to Skeleton (and liboggz). It is also compatible with other

Hi, do you still think you need all this, if you are allowed to have equal granulepos on subsequent pages? Conrad. On 18/02/2008, ogg.k.ogg.k@googlemail.com <ogg.k.ogg.k@googlemail.com> wrote: > Hi, > > I've now got another way of encoding granule (oh, not *again*, I hear > you cry). I believe it's an improvement over the existing "generic" > method, so

On 2008-11-21, Conrad Parker <conrad at metadecks.org> wrote: > 2008/11/15 David Flynn <davidf+nntp at woaf.net>: >> On 2008-11-14, Conrad Parker <conrad at metadecks.org> wrote: >>> 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

Hi, this fixes a potential SIGSEGV. -------------- next part -------------- A non-text attachment was scrubbed... Name: oggz_tools.c.diff Type: text/x-patch Size: 553 bytes Desc: not available Url : http://lists.xiph.org/pipermail/ogg-dev/attachments/20080206/c921f084/oggz_tools.c.bin

A widely used platform doesn't bother to have C99 integer types, so this allows building with it. Reported by sirlemonhead on IRC. Index: src/tools/oggz_tools.c =================================================================== --- src/tools/oggz_tools.c (revision 3827) +++ src/tools/oggz_tools.c (working copy) @@ -450,7 +450,7 @@ dg->pt = (iframe + pframe) >> 9;

Hi Sahana I must admit I'm not an expert in Theora. But the error message "Could not set keyframe interval to 64" might indicate that an attempt to set the keyframe frequency failed. Have a look at the keyframe_granule_shift attribute in the th_info struct. It says: The maximum distance between key frames is 1<<keyframe_granule_shift. So I could imagine that the error might

When I try to 'make' oggz (0.9.9), I get the following compile error make[4]: Leaving directory `/c/liboggz/src/tools/oggz-chop' make[4]: Entering directory `/c/liboggz/src/tools' /bin/sh ../../libtool --tag=CC --mode=link gcc -g -O2 -Wall -Wextra -g -std=gnu99 -Wdeclaration-after-statement -Wno-unused -o oggz-info.exe oggz-info.o skeleton.o oggz_tools.o dirac.o

On 2008-11-13, Conrad Parker <conrad at metadecks.org> wrote: > I'm wondering if the Dirac granulepos parsing in liboggz and display > in 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

On 15-Feb-08, at 6:44 AM, ogg.k.ogg.k@googlemail.com wrote: > Well, it doesn't quite work because the second part of the gpos is > an offset, > rather than absolute, and the precision we shed on one, we need to > recover > on the other one, to keep the ability to timestamp events at the > correct > granularity. It would have worked if the second part was absolute

I have almost finished integration of Theora into our videoconferencing program. Since a videoconferencing program is realtime, it is UDP-based and wraps the Theora stream in RTP (More on that later). The problem here is that most examples I could find, wraps the theora stream in ogg, and used over tcp or files. I send over UDP and clients need to be able to start in the middle of the stream.

Hi There, i want to stream some pictures out of my application using the Theora codec. I can stream to a socket or a file. The current work based on the png2theora example. Something while enconding went wrong: I can see the whole video in VLC, but the complete duration of the file will not be displayed. If i play the video in Firefox, the first 2 seconds will not be played. I think the

Dear all I'm aware that there have been several discussions about the seeking issue and I'm sorry to bring this up again. To solve the problem with Inter-Frame garbage, a seek to the previous keyframe has to be made. The keyframe number should be extracted from the granulepos of the frame where we want to seek to. I hope I understood the theory - unfortunately a few questions have

On 2008-11-14, Conrad Parker <conrad at metadecks.org> wrote: > Should oggz-comment be modified to disallow modification of Dirac > streams, ie. does Ogg Dirac never contain VorbisComment metadata? Correct; there is no metadata handling capability in the current mapping spec. > It seems oggz chop, merge and sort will need some attention to deal > with the Dirac granulepos and

>>> http://trac.annodex.net/changeset/3801 >> >> I'll test this shortly. Ok, i've tested muxing some audio and video together and that works fine. woo. >> My only initial concern is about the definition >> of granule_rate. My intention is to add some guidance to the oggdirac >> mapping spec on how to apply oggskeleton. This raises the slight

4) Subtract 1 from the keyframe, then repeat step 3). 5) Begin reading from the frame discovered in step 4. Drop any packets which are output on the first page. Count down until we reach the keyframe, dropping packets until then. 6) Continue counting down until we reach the target frame, we are now decoding each frame/packet. At the target frame produce the YUV output. Steps 4 and 5 are

hem here it is the patch. ;) bye kysucix -------------- next part -------------- Index: conf/icecast.xml.in =================================================================== --- conf/icecast.xml.in (revisione 10365) +++ conf/icecast.xml.in (copia locale) @@ -62,6 +62,7 @@ <port>8001</port> </listen-socket> --> +

2008/11/21 David Flynn <davidf+nntp at woaf.net>: > On 2008-11-21, Conrad Parker <conrad at metadecks.org> wrote: >> 2008/11/15 David Flynn <davidf+nntp at woaf.net>: >>> On 2008-11-14, Conrad Parker <conrad at metadecks.org> wrote: >>>> It seems oggz chop, merge and sort will need some attention to deal >>>> with the Dirac

<br> 4) Subtract 1 from the keyframe, then repeat step 3).<br> <br> 5) Begin reading from the frame discovered in step 4. Drop any packets<br> which are output on the first page. Count down until we reach the<br> keyframe, dropping packets until then.<br> <br> 6) Continue counting down until we reach the target frame, we are now<br> decoding each

2008/11/15 David Flynn <davidf+nntp at woaf.net>: > On 2008-11-14, Conrad Parker <conrad at metadecks.org> wrote: >> 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. > > ok. -- may be worth having them 'warn' if they are operating

Hi, I'm wondering if the Dirac granulepos parsing in liboggz and display in the oggz tools is currently correct, as I'd like to do a release of these soon. A couple of days ago David Schleef mentioned there were some problems. David, is that currently true (ie. since David Flynn's recent updates to support Dirac), and if so could you please explain what the problems are, or point me