Help! - Embedded timecode is altered on export when Separate Files or Merge Cuts

[deqimages]

Hi, new here and really need a helpful answer.
Just using LosslessCut for the first time and extremely impressed with its functionality.
I needed a quick and simple editor to view 2 weeks of footage from multiple cameras, and then trim them quickly down to manageable sizes.
All the functionality is there in LosslessCut, but I've got one big problem... If I take any footage from a DJI Osmo Action 4 camera with timecode already recorded on that camera's video, and then put it in LosslessCut, as soon as I segment the footage, either as separate files, merged or chapters, the exported file's timecode has been moved/changed and does not match the original camera recorded timecode!!!

I've fiddled with LosslessCut settings, but I just can't seem to get this to work.
If I just view and export the same footage without doing any cut or merge functions, then the timecode stays intact and correct.
Am I missing something here or is this a problem, as I need to view and trim a hell of a lot of footage and it needs to keep the original camera timecode when exported out of LosslessCut.
Any help or advice would be most greatly appreciated.

[mifi]

by timecode you mean tmcd embedded timecode data right? I think such timecodes are not really supported in LosslessCut, see #506

[deqimages]

Thank you for coming back with a reply as I know there are many others out there needing your time.
Ok... understand but of course disappointed as your program really is well thought out and easy to use, just unfortunately I need to preserve the original footage/camera timecode no matter whether it's segmented or shortened, as there are multiple cameras involved here, and all this footage will need to be synced in Premiere Pro for a large edit session, so keeping all the cameras locked to their originally recorded 'time-of-day' timecode is paramount.
So... unfortunately it looks like LosslessCut won't work for me which is a great shame as I needed a fast trimming app, but many kudos to you for making a very simple, elegant but powerful program.
Thanks, Alvin.

[mifi]

Alright, I'm sorry to heard that. Yea unfortunately I don't know how to make ffmpeg preserve the timecodes. I will add a note about it under "Known issues".

Just to be sure: are you saying that the timecode from the source file when cutting+exporting gets

1. completely dropped?
2. shifted by a random/unknown amount?
3. totally mangled?

I've seen other people say that timecodes do get preserved (but not shifted according to the start-cutpoint as one would expect), so it could be some difference with your particular timecode.

[deqimages]

Not dropped and not mangled, but the exported file from LosslessCut when played back/imported into Premiere Pro, the now segmented file, although still retaining readable timecode may shift anything from approx 13 seconds to a minute away from the original camera timecode, when compared to the original camera file.
Sometimes this exported shift (after multiple experimenting) can stay around 13 seconds different, but at other times (and I can't exactly remember the sequence of events) when exporting as separate but merged, it can be a larger amount of offset.
I'm running out of time to go through all this footage, so I'm sorry I can't sit down and give you a full account of what's going on here, but I hope this is of some use.
As said, really a shame LosslessCut gets lost/confused over timecode here, as it's a waaaaay more elegant way to review and tighten tons of camera footage, instead of having to do this in something like Premiere Pro which is way more clunky and like using the proverbial sledgehammer to crack a walnut. (;->
Thanks again, Alvin.