Project is time-wise bigger in Shotcut than it actually is

[Austin]

MLT does conversion in a way that is fully reversible without ambiguity due to floating point precision errors. This can account for some unexpected time gaps, but they are consistent within MLT. See below.

Also remember to base all timestamps on the zero point of the timeline or clip. Don’t add one time span to the previous time span directly. There will be accumulation errors. Convert to frames, add frame counts together to get a new position, then convert the frame count back to a timestamp.

Problem with calculated timestamps

Here is the code. If you attempt to state how it is wrong, bear in mind that it was written to make unit tests pass the enforce that a conversion from frame count to timecode and back to frame count (see other code in the same file) gives the same count for every 32-bit signed int. Any suggestion on your part must be in the form of a pull request that passes the unit tests included in the repo: