Hi dazulrich.
Testing conducted on the image 16117 (GST 1.10.0).
Results:
mediasink.statechg - nok ( avi smoothly, m3u8 not smooth)
mediasink.statechg_synctrue - nok ( avi smoothly, m3u8 not smooth)
mediasink.sync_true - nok ( avi smoothly, m3u8 not smooth)
Result replacement: - nok ( avi smoothly, m3u8 not smooth)
Previously, I had a reverse substitution test:
The result is: -ok (avi not smoothly, m3u8 smoothly)
I want to draw attention to "in libgstdvbvideosink.so introduced changes to work with libgstmpeg4p2unpack.so"
Makes his conclusion: the problem does not depend on the version of the GST, the same does not depend on libgstdvbaudiosink.so. There is a direct relationship only libgstdvbvideosink.so, at which it became "avi smoothly, m3u8 not smooth".
This is very similar to avi playback until patching.
Visually, this manifests itself as a "forwarding frames", ie, there is a discrete moving objects in the frame.
I did log on 16117. Where the "smooth" replaced only libgstdvbvideosink.so.
I assume that the problem does not depend on the CPU load.
It is not correlated (independent of libgstdvbaudiosink.so).
Maybe it's important. When Using a third-party player able to play m3u8 (ie not from userbouquet), the effect of "not smooth" can be eliminated by changing the playback position. Ie using the numeric keys change positions, or TimeSeekBar.
In my humble opinion, by making changes to better play avi, more harm than good.
I hope you are not too tired.
Regards, ingo