[gst-devel] oggmux max-delay & max-page-delay default

Gergely Nagy algernon at bonehunter.rulez.org
Fri Apr 22 01:53:23 CEST 2005


At the moment, oggmux has a default value for max-delay and
max-page-delay of 5000000000. I admint I haven't the
slightest clue about exactly what these mean, but they
cause problems, as they're too high.

Muxing an theora+vorbis stream with the defaults does not
immediately make the problem obvious, as for example
both totem and mplayer (and probably xine too) play the
result flawlessly.

However, try to play it with Cortado, from a live source,
and the audio/video sync goes nuts. Playing the same stream
with the usual players, and you don't see the problem.

I've just spent 30 minutes trying to figure out what's wrong,
adding delays here, adding delays there, but that resulted
in the stream being out of sync either in Cortado or
in Totem. It wasn't perfect in both of them at the same time.

After half an hour, I remembered Thomas mentioning on IRC
something like oggmux's max*-delay default being bad for
flumotion, so I lowered them: divided the default by 1000.

And behold! Both Totem and Cortado play the stream just fine,
and if I save it to file, and play that back, it is still

As far as I see, there were no negative consequences, and
this change alone fixed the sync problems I had. So even
though it's just a guess, I'd rather trade a
has-known-broken-cases guess to a worked-in-every-case-I-could-think-of
guess anytime.

Are there any objections? If no, I'll most probably commit
this change soonish (like, sometime next week, unless
there's enough positive feedback)


More information about the gstreamer-devel mailing list