Timecode issue.

[Doug183]

The fewer issues I have to read, the more new features I will have time to implement, so I ask that you please try these things first

• [X] Try with the newest version from GitHub (also it might have already been fixed in latest nightly build)
• [X] Read the documentation and FAQ, Known issues, Troubleshooting
• [X] Search for your problem under Issues or Discussions
• [X] If you have a problem only with a particular file (or file type), use this form instead
• [X] Windows 7, 8 and 8.1 are no longer supported. This is not a question about Windows 8.1 or older.

Operating System

MacOS 12

Steps to reproduce

I posted once before, but here are pictures to illustrate the issue.

0) I am using the latest download from GitHub - Lossless Cut 3.59. However this problem can be recreated with older versions. 1) Main problem. Lossless cut/FFMPEG use timing calculation in that thousands of second format. 2) Videos use frame rates. 3) There is a Time Code drift in Lossless Cut that is not accounted for. This problem can be seen in other simpler video viewers as well (Quicktime X, VLC, FFMPEG, LossLess Cut.). 3a) Adobe Premiere, AVID, and FCP do not have this issue.

Here is 49+ minute video compressed in both H264 and ProResLT with a counter burned in.
H264 version ProResLT

I created comparative screen shots using Lossless Cut and Adobe Premiere at the following time intervals: 6 seconds, 10 Minutes, and then in 5 minute increments and then two different endings.

Expected behavior

Time code should be spot on.

Actual behavior

Time Code drifts.

Share log from developer tools

No response

[Doug183]

Solution. I have had code written for a custom Python script that uses FFMPEG to replace footage which handles the thousand timing issue to frames accurately. I am happy to donate it to the project if someone tells me how. Lossless cut is great app and I think is super valuable to the community.

Here is link to my first post and the fix which in the replies.

Original Post