[gst-devel] state change stuff
Thomas Vander Stichele
thomas at apestaart.org
Sun Jul 25 06:54:06 CEST 2004
some recent changes in the state change code have completely altered the
behaviour of state changes in bins.
Before the changes, bins would go from NULL to PLAYING by making
children pass through each state change together. Ie, all kids would go
from NULL to PAUSED first, and so on.
Currently, looking at the logs and changes, it looks to me that it
directly brings each of the children into the final state before moving
on to the next. This seems a pretty big change, and alters order of
state changes in all my current test pipelines. That by itself is
probably not that big of a deal, but it seems to me that the previous
order of changing children's state was more correct and logical.
I'm assuming that, for example, this will increase the time between a
source like v4lsrc being in PLAYING and its respective sink.
Is there something inherently better about the new order, or is it just
by accident ?
Dave/Dina : future TV today ! - http://www.davedina.org/
<-*- thomas (dot) apestaart (dot) org -*->
Is there a voice unkind
in the back of your mind
saying "maybe you didn't know him at all"
<-*- thomas (at) apestaart (dot) org -*->
URGent, best radio on the net - 24/7 ! - http://urgent.fm/
More information about the gstreamer-devel