GNOME Bugzilla – Bug 703370
eos unnormal
Last modified: 2014-10-30 15:40:00 UTC
I used gstreamer1.0 to record an mp4 file by python on ubuntu Linux.At the end of the stream ,I send an eos to the pipeline,and the bus can receive "message::eos".It worked well,and I can get the correct mp4 file.But when I upgraded to gstreamer1.1.1,the bus can not receive the eos,and the file is not correct.
I record the file by rtp streams(video and audio).
Could you provide a gst-launch-1.0 pipeline or a program/script to reproduce the issue?
*** Bug 703436 has been marked as a duplicate of this bug. ***
There's some more info, and a question for you in bug #703436: > What exactly is wrong with the resulting file when using 1.1.1? > Are there any warnings printed on the terminal?
(In reply to comment #4) > There's some more info, and a question for you in bug #703436: > > > What exactly is wrong with the resulting file when using 1.1.1? > > Are there any warnings printed on the terminal? Thank you: there is no warning on the terminal. the problem is that the bus can not receive the 'message::eos',or received it but not callback my function. And the mp4 file is not correct ,its frame rate is 7 frame/s. But in the gstreamer1.0,it is 21 frame/s.
As per Tim's comment #2: Could you provide a gst-launch-1.0 pipeline or a program/script to reproduce the issue? I think you missed this comment when you replied to the later question.
This yields an unplayable file: gst-launch-1.0 videotestsrc ! avenc_mpeg4 ! qtmux ! filesink location=test.mp4 This yields a playable file: gst-launch-1.0 -e videotestsrc ! avenc_mpeg4 ! qtmux ! filesink location=test.mp4 So it seems the EOS is received/handled fine in that case at least, so I'm going to move the bug from critical to normal, at least pending more information.
Let's just close this. Troy, please re-open if you can provide a test program that demonstrates the issue. Thanks!