[gstreamer-bugs] [Bug 583030] [flvdemux] reset in pull mode doesn't work

[GStreamer (bugzilla.gnome.org)]

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=583030

  GStreamer | gst-plugins-good | Ver: 0.10.11




------- Comment #4 from Sebastian Dröge  2009-05-27 08:47 UTC -------
Hm, unrelated to this bug, the API of those Java bindings doesn't look that
nice. It's only static classes with the C API inside them. It's even required
to do memory managment by hand by calling unref. Isn't it possible to create
Java bindings that look like real Java (i.e. Pipeline pipeline = new Pipeline
("foo") and automatic memory managment by the garbage collector, ...)? Or is
something like this the standard way of doing GObject-like bindings in Java?



Your code itself looks quite weird though... this could be much simpler :)

One thing I'd change would be to install a bus watch and handle EOS from
there... the bus watch will be called from the main thread, not the streaming
thread. The event probe isn't the correct solution IMHO.
Another thing is, that you should a) add all elements to your pipeline and b)
only set the state of the pipeline to NULL instead of setting the state of all
elements to NULL. I think this could be one of the reasons why it doesn't work.
In any case, my test code (C# but should be easy to understand) is at
http://pastebin.ca/1435996 and this works just fine.

And then you could simply use decodebin(2) for the video decoding part.

Could you check if it works if you change your code like this?


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=583030.