FITS produces illegal start elements when the video framerate is 25 fps. For example:
ebucore:start
<ebucore:editUnitNumber editRate="0" factorNumerator="1000" factorDenominator="1001">0</ebucore:editUnitNumber>
</ebucore:start>
ebucore:duration
<ebucore:editUnitNumber editRate="1000" factorNumerator="1" factorDenominator="1">3097360</ebucore:editUnitNumber>
</ebucore:duration>
The editrate attribute is define in the schema as a positiveInteger. An edit rate of 0 is non-sensical and illegal.
Also, it is confusing that the file has its time expressed in two different time-bases since a file can only really have a single timebase for any given video stream. I believe the timebase in the start above of 1000/1001 is incorrect since you don’t see that rate in 25fps video normally.
FITS produces illegal start elements when the video framerate is 25 fps. For example:
ebucore:start
<ebucore:editUnitNumber editRate="0" factorNumerator="1000" factorDenominator="1001">0</ebucore:editUnitNumber>
</ebucore:start>
ebucore:duration
<ebucore:editUnitNumber editRate="1000" factorNumerator="1" factorDenominator="1">3097360</ebucore:editUnitNumber>
</ebucore:duration>
The editrate attribute is define in the schema as a positiveInteger. An edit rate of 0 is non-sensical and illegal.
Also, it is confusing that the file has its time expressed in two different time-bases since a file can only really have a single timebase for any given video stream. I believe the timebase in the start above of 1000/1001 is incorrect since you don’t see that rate in 25fps video normally.