How Gstreamer uses Python code to implement the gst-launch-1.0 -e function

Jetson AGX

I found a problem when recording a video. If I use the following code, even if I force the program to be interrupted, the recorded video can still be played due to the addition of EOS.
gst-launch-1.0 -e v4l2src ! video/x-raw,width=640,height=480 ! videoconvert ! queue ! timeoverlay ! x264enc key-int-max=10 ! h264parse ! qtmux ! filesink

But when I don’t use the -e parameter, after the recording video is forced to be interrupted, the subsequent video cannot be played, and there are indeed fewer moov atomic files.

How can I change the -e function in python code

python code (4.3 KB)

Comparing the results with or without the -e parameter, with the -e parameter, there is a buffer

If you want to record video, we suggest your use the h264 format to save the video. If you want to implement -e paras in the code, you should catch all the inter msg and send EOS msg by yourself.

1 Like

I have set the format like this and msg has been set for him, but the parameters like -e don’t know how to affect my writing to the file (5.2 KB)

Can you help me test it? I still can’t play the output video

There is no update from you for a period, assuming this is not an issue anymore. Hence we are closing this topic. If need further support, please open a new one.

1.You cannot set the -e para in deepstream,cause it’s a gst-launch paras. You can refer the source code of gst-launch.c of Gstreamer to impletation it.
2.We suggest you save it to h264 format instead of mov if you want to force to stop it.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.