AW: Pipeline fails after exactly 2.5 hours

[Henk Schurink]

Thornton, Keith wrote
> Hi,
> we have a similar problem caused by two frames with the same timestamp
> being sent down the pipeline. The h264parse plugin changes the timestamp
> of the second frame to CLOCK_TIME_NONE and the qtmux in splitmuxsink thows
> the buffer_has_no_PTS error
> You could try adding a pad_probe which detects this situation to confirm
> that you are suffering from the same problem.

Hello,

I've removed the h264parse element from my pipeline and now it's been
running steadily for the last 10 hours. I couldn't thank you enough! Best
regards.



--
Sent from: http://gstreamer-devel.966125.n4.nabble.com/