[Cin] OGG validation?
good1.2guy at gmail.com
Sun Mar 15 16:58:22 CET 2020
It appears to be the same basic code. Valid just means "ready to write".
The queue is written until there are no more valid pages. The older
implementation does not have a "magic" queue limit (32). I think that ogg
has had so many mistaken implementations, that media exists with bad
timestamp data, and the limit prevents some situations like, output a giant
chunk of audio, and then output a giant chunk of video. Not a good sign
really. A better move may be to mux data as long as you have both audio
and video, and wait for more when it is not clear which should be next.
Then the queue limit makes more sense, and the chunky effect is somewhat
On Sat, Mar 14, 2020 at 10:38 AM Andrew Randrianasulu <
randrianasulu at gmail.com> wrote:
> I recall some strangeness with recently re-added OGG/theora output.
> I found this comment in old CinCV repo:
> "r636: j^'s (j at v2v.cc) patch to mux ogg in a way compilant with
> specification y - makes oggz-validate
> happy and probably some players also"
> I followed app name and landed here:
> Oggz comprises liboggz and the tool oggz, which provides commands to
> inspect, edit and validate Ogg files.
> The oggz-chop tool can also be used to serve time ranges of Ogg media over
> HTTP by any web server that supports CGI.
> liboggz is a C library for reading and writing Ogg files and streams. It
> offers various improvements over the reference
> libogg, including support for seeking, validation and timestamp
> The latest version is 1.1.1, released Apr 29 2010.
> git has some improvements over it ....
> I hope it will helpful in catching those strange errors about not marked
> keyframes ...
> Cin mailing list
> Cin at lists.cinelerra-gg.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Cin