Playbin cant play high bit rate video whereas playbin3 can

[deeps8us]

I tried to play a 4k h265 video using both playbin and playbin3 using
gst-launch. Video played properly when using playbin3 but not when using
playbin (got stuck in READY state).
The pipeline created internally (by both playbin and playbin3) is filesrc !
tsdemux ! h265parse ! avdec_h265 ! glimagesink
The stream is about 800 MB in size.

Then for experimentation, I truncated the stream to about 200MB and found
that playbin can play the stream.

Is there any high bit rate issue or buffering issue related to playbin.?  Is
there any additional option to be supplied along with gst-launch for
playbin?



--
Sent from: http://gstreamer-devel.966125.n4.nabble.com/
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

[Baby Octopus]

Both playbin and playbin3 would be built on same decoders.
One way to debug would be to get the dot diagram in both cases
and see if there are any differences between both the pipelines

~BO



--
Sent from: http://gstreamer-devel.966125.n4.nabble.com/
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

[Nicolas Dufresne-5]

Le 14 mars 2018 04:57, "deepthips" <[hidden email]> a écrit :

I tried to play a 4k h265 video using both playbin and playbin3 using
gst-launch. Video played properly when using playbin3 but not when using
playbin (got stuck in READY state).
The pipeline created internally (by both playbin and playbin3) is filesrc !
tsdemux ! h265parse ! avdec_h265 ! glimagesink
The stream is about 800 MB in size.

Then for experimentation, I truncated the stream to about 200MB and found
that playbin can play the stream.

Is there any high bit rate issue or buffering issue related to playbin.?  Is
there any additional option to be supplied along with gst-launch for
playbin?

Yes, the maximum queue size is hard-coded to avoid memory attacks, while in plabin3, it is also limited, but base on a different queueing model. Could be something else of course in this case, but this is likely. We update these from time to time, e.g. to accommodate recent 4K and I-Frame / Lossless streams.

In case of TS though, very often the muxer is at fault, the audio and the video are too far from each other, and would require a rediculously large buffer to synchronize.

--
Sent from: http://gstreamer-devel.966125.n4.nabble.com/
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel