<br><div><span class="gmail_quote">On 8/28/07, <b class="gmail_sendername">Jesse Guardiani</b> <<a href="mailto:jesse@guardiani.us">jesse@guardiani.us</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
gstreamer is poo. plain and simple. Yes, you need to recreate the<br>pipeline. If you don't, bad things happen, like hanging and such after<br>EOS. And no, EOS detection still doesn't work well in that class despite
<br>my many tries. We abandoned gstreamer support in Kagu for a reason. It's<br>poo. It's much easier to just use OSSO Media Server via dbus and let<br>*it* deal with gstreamer for us.</blockquote><div><br> </div>
<br></div><br>I'm beginning to realize this about gstreamer as well. EOS detection
seems to only work about 95% of time, and when it does work you get
something like 5 messages thrown at you - so why can't it get just one
through on those 5%???
<br><br>Anyway, can you point me to any docs on using dbus to control
OSSO with Python? The whole dbus concept is still alien to me. The
only dbus I've done is the launching with a desktop icon and then using
it to get the screen status (which I copied and pasted from Kagu.)
<br><br>Wait, I bet the next comment from someone will be "Why don't you take a look at Kagu"... lol.<br><br>Okay so I agree gstreamer is out. Now to get a replacement working...<br>