A bit more information as I’ve now managed to capture some logging.
First problem is that ‘deinterlace’ isn’t being found, so I need to investigate why that’s not getting deployed.
I can see multiple gst_event_new_caps entries in the log (which occur in groups), so it looks as if the source supports multiple formats and re-negotiation takes place from time-to-time. Some of these event have an ‘interlace-mode’ of ‘mixed’ whilst others support ‘progressive’. Is it possible to set a parameter on a generic ‘playbin’ pipeline so that it prefers a non-interlaced format but will still accept interlaced if that’s all that's available?
> On 24 Jul 2016, at 22:49, Chris Tapp <
[hidden email]> wrote:
>
> I’ve upgraded a system from 1.4.5 to 1.8.1 and everything works as expected except that the video looks as if it has interlacing artefacts after the stream has been running for some time (not sure exactly how long, but several hours).
>
> The effect is hard to describe, but it looks very similar to the horizontal jagged-edges that video has when horizontal motion is present in an interlaced stream.
>
> The pipeline is using playbin to capture frames from a DVB-T source (generated by MuMuDVB) and makes them available to the application using “appsink" - the same source looks ok when viewed using VLC.
>
> Any ideas what could be causing this or what I should look at to understand what’s going on? The system has limited memory / disk resources, so I’ve not been able to capture anything using diagnostics that gives any clues.
>
> --
>
> Chris Tapp
>
[hidden email]
> www.keylevel.com
>
> _______________________________________________
> gstreamer-devel mailing list
>
[hidden email]
>
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel--
Chris Tapp
[hidden email]
www.keylevel.com
----
You can tell you're getting older when your car insurance gets real cheap!
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel
Locked
