Thomas Vander Stichele
thomas at apestaart.org
Wed Feb 11 03:12:06 CET 2004
On Thu, 2004-02-05 at 19:05, in7y118 at public.uni-hamburg.de wrote:
> The reason why everything clocking related is in such a bad state is because
> clocking was extremely broken even in 0.6 and I only fund out at the beginning
> of January when we were supposed to be API stable.
After going over the old and new clocking system, and trying to figure
out what you think was broken, I'm pretty much lost. Basically, if
you're going to claim it was "extremely broken" I think you should back
that up with an explanation :) FWIW you seem to call things either
perfect or broken.
The clocking system already passed the basic test Christian layed out in
0.6, and it is really hard to evaluate why your start of a rewrite is
better at all. After discussing it a little with Wim yesterday I really
don't see what problem was unsolvable in the 0.6 clocking system, so I
have the feeling doing such fundamental changes so late in the cycle was
wrong and we should revert and figure out how to properly do clocking.
> Getting this fixed correctly with thinking about how it should be done,
> implementing and testing it would have taken until February and would have
> involved API changes.
So, could you please outline what was broken in your view, with simple
explanations, and why it is now better ?
As Andy said, there were people who knew and used the old system, and it
seemed to work fine for them. Also, conceptually, the old system makes
a lot of sense. I'm not saying the new one does not, I'm saying I have
no way of telling if it makes more sense and if it was right to make the
Dave/Dina : future TV today ! - http://www.davedina.org/
<-*- thomas (dot) apestaart (dot) org -*->
a quiet life a handshake
of carbon monoxide
<-*- thomas (at) apestaart (dot) org -*->
URGent, best radio on the net - 24/7 ! - http://urgent.fm/
More information about the gstreamer-devel