mp4 file repair - UPDATE 1

William Salibrici bsalibrici at
Fri Nov 10 14:45:03 UTC 2017

Hi Prabhakar,
I am using the mp4mux and looking at the inspect data sheet I see that the reserved-max-duration, reserved-moov-update-period, and reserved-bytes-per-sec are all non-zero by default. The same is true for the qtmux. So they should be in operation. However, when I make a recording using these default values and unexpectedly interrupt the recording, the resultant recording file is unreadable for the standard windows media player. My development machine is windows 7. I just did a test using gstreamer version 1.12.3 with the gstreamer pre-built binaries for windows.
Am I missing something?
How do you get the reserved-* properties to work?
Thanks in advance for any help you can give.



-----Original Message-----
From: gstreamer-devel [mailto:gstreamer-devel-bounces at] On Behalf Of Lad, Prabhakar
Sent: Thursday, November 09, 2017 4:29 PM
To: Discussion of the development of and with GStreamer <gstreamer-devel at>
Cc: lists at
Subject: Re: mp4 file repair - UPDATE 1


On Thu, Nov 9, 2017 at 3:00 PM, William Salibrici <bsalibrici at> wrote:
> I came to that conclusion myself after reading the inspect data sheet 
> for the qtmoovrecover element.
> I noticed that it has no pads and has an internal pipeline.
> Thanks for your confirmation – I will give it try.
alternatively you could use the reserved-* of qtmux so that the moov atoms are written periodically and you can still play the file.

--Prabhakar Lad
gstreamer-devel mailing list
gstreamer-devel at

More information about the gstreamer-devel mailing list