Finding the exact decoding time by ffdec_h264 for MOV files

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Finding the exact decoding time by ffdec_h264 for MOV files

arunav.kumar
This post was updated on .
Dear all,
I am new to GStreamer platform, and presently finding the time taken in decoding one frame of MOV files.
After exploring GStreamer code, and enabling all the debug logs (--gst-debug=5), I could find information about different states of pipeline. But still, I could not sure about, how to find the exact decoding time (frame-by-frame) of  MOV playback, or a single frame.

I have the following MOV file with me:
MOV name: H.264_1280x720_35fps.mov
Resolution: 1280x720
Frame rate: 35.24
Length: 2.39Minutes or 143.4 Sec

Experiment:
I launched the following command with the fakesink as follows:

./gst-launch-0.10 --gst-debug=3 filesrc location= /H.264_1280x720_30fps.mov ! qtdemux name=demux demux.video_00 ! queue ! ffdec_h264 ! ffmpegcolorspace ! videoscale ! fakesink

And found the following time:
---logs---
New clock: GstSystemClock
Got EOS from element "pipeline0".
Execution ended after 17893485514 ns.
Setting pipeline to PAUSED ...
---logs---

So total time in execution with fakesink is  : 17.893485514 Seconds

I used fakesink, so that time in autovideosink display should be avoided.

If I dont enable the fakesink and let it run using autovideosink, the whole execution takes 2.66508974545 Sec

---logs---
Setting pipeline to PLAYING ...
New clock: GstSystemClock
Got EOS from element "pipeline0".
Execution ended after 159905384727 ns.
Setting pipeline to PAUSED ...
---logs ---

So total time with autovideosink is 159.905384727 Seconds

So the time taken with autovideosink (159.905384727) - original length of Video (143.4 Sec) = 16.505384727 Seconds

Please help me to validate, if I can consider this time (17.89 Sec) coming with fakesink or  16.505384727  coming after (autovideosink-original length as the Decoding time for the MOV file,

Thank you,
Arunav
-- BR Arunav
Reply | Threaded
Open this post in threaded view
|

Re: MOV file decoding time using ffdec_h264 through Good Plugin

Sebastian Dröge-3
On Di, 2016-05-24 at 01:00 -0700, arunav.kumar wrote:

> *Execution ended after 17893485514 ns.*

> Execution ended after 159905384727 ns.
> Setting pipeline to PAUSED ...
> ---logs ---
>
> The difference is 2.366864987 Sec, 

The difference is actually 142 seconds

> Please help me to validate, if I can consider this time (17.89 Sec)
> as the Decoding time for the MOV file, 

It is the time for reading the whole file, demuxing the MOV container,
decoding the video and possibly doing colorspace conversion and
rescaling. The last two will be no-ops in your case though.

If you only want to measure the decoding time, you should only look at
the actual decoder.

--
Sebastian Dröge, Centricular Ltd · http://www.centricular.com


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

signature.asc (968 bytes) Download Attachment