mp4 file repair - UPDATE 1

[William Salibrici]

Hi Michael,
Thanks for clarifying that.
I'm up and working now.

Regards,

Bill


-----Original Message-----
From: gstreamer-devel [mailto:gstreamer-devel-bounces at lists.freedesktop.org] On Behalf Of Michael MacIntosh
Sent: Friday, November 10, 2017 8:39 PM
To: gstreamer-devel at lists.freedesktop.org
Subject: Re: mp4 file repair - UPDATE 1

Hey Bill,

The default unit of time in gstreamer is the nanosecond (10^-9 seconds), so unless otherwise stated, assume nanoseconds.  This is because the clocks gstreamer use have that level of precision, so usually everything just follows that.

Hope that helps!

Cheers,
Michael.


On 11/10/2017 12:13 PM, William Salibrici wrote:
> Thank you Michael.
> Do you know the units for the reserved-moov-update-period property?
> Would that be milliseconds or seconds?
>
> Regards,
>
> Bill
>
> -----Original Message-----
> From: gstreamer-devel 
> [mailto:gstreamer-devel-bounces at lists.freedesktop.org] On Behalf Of 
> Michael MacIntosh
> Sent: Friday, November 10, 2017 2:38 PM
> To: gstreamer-devel at lists.freedesktop.org
> Subject: Re: mp4 file repair - UPDATE 1
>
> You need to change the default values, they are max 64 bit unsigned int by default.  Which means it will only update the moov table every 585 years.  Try changing them to other values.
>
>
> On 11/10/2017 6:45 AM, William Salibrici wrote:
>> 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.
>>
>> Regards,
>>
>> Bill
>>
>> -----Original Message-----
>> From: gstreamer-devel
>> [mailto:gstreamer-devel-bounces at lists.freedesktop.org] 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 lists.freedesktop.org>
>> Cc: lists at svrinformatica.it
>> Subject: Re: mp4 file repair - UPDATE 1
>>
>> HI,
>>
>> On Thu, Nov 9, 2017 at 3:00 PM, William Salibrici <bsalibrici at latticeinc.com> 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.
>>
>> Cheers,
>> --Prabhakar Lad
>> _______________________________________________
>> gstreamer-devel mailing list
>> gstreamer-devel at lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel
>> _______________________________________________
>> gstreamer-devel mailing list
>> gstreamer-devel at lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel
> _______________________________________________
> gstreamer-devel mailing list
> gstreamer-devel at lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel
> _______________________________________________
> gstreamer-devel mailing list
> gstreamer-devel at lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

_______________________________________________
gstreamer-devel mailing list
gstreamer-devel at lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel