[Bug 731853] New tool : Add a CodecAnalyzer

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=731853
  GStreamer | gst-devtools | unspecified

Stefan Sauer (gstreamer, gtkdoc dev) <ensonic> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|ensonic at sonicpulse.de       |

--- Comment #20 from Stefan Sauer (gstreamer, gtkdoc dev) <ensonic at sonicpulse.de> 2014-07-08 05:15:49 UTC ---
(In reply to comment #18)
> (In reply to comment #17)
> > Not a showstopper for submission, but it would be nice to have some top-level
> > comment block in main classes to describe how it works, e.g. gst-analyzersink
> > could have one.
> > On the other hand I am not super fond of the filesystem interaction. What about
> > using nested GstStructures for the data and emitting them as GstBusMessages?
> 
> Do you mean to keep pipeline alive all the time during the analysis?
> Right now the pipeline is active only during parsing time. After that it is all
> about xml data manipulation and there is no gstreamer interaction.
> 
> Anyway Edward had also some ideas about emitting parser info as GstMessages.
> But that we can discuss later since it needs more changes in videoparser
> plugins too. what do you think?

Not all the time, the pipeline would run with sync=false and the app would
store the messages in memory (And yes I meant to put the GstStructures into a
GstMessage). As it receives messages it can update the UI.

Another suggestion would be to make the analyzersink a filter and end the
pipeline with fakesink. A filter is simpler code wise and multiple filters can
be chained. This would make it easier to re-use the analyzer. Finally a closer
integration with the parser libraries might be interesting. I am wondering if
the actual parser element could get a "message" property and actually emit the
messages.

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.