Oh, by the way I do have a life! I just like working on little projects like this. This means matching scenes between episodes which seems to work well.
I've been cutting and reassembling my original multiple episode Doctor Who videos into single videos so I don't have to listen to all the theme music between the episodes. It's easy to find your keyframe cut point using 2 running copies of VirtualDub2 working on the same video. However one weird note: You have to subtract exactly 0.1 second from all the keyframe readings to get the exact cut points even when starting at 0.0 which becomes -0.1 seconds. If you use the keyframes from VirtualDub2 in your ffmpeg cutter command, you should get the correct length. The VirtualDub2 keyframe readings match exactly the ffprobe keyframe readings. Try to figure out what you can deal with and then focus on projects you can handle with current equipment.I've found that the keyframe readings using Avidemux are 0.066 seconds larger than those when using VirtualDub2, at least on MP4 video files. I have to live with it cause there's no way I can do pro work for long form, etc. Personally, I have a high end computer and stuff and can MAYBE do high end tv commercial stuff ( 60 seconds of full HD ). Import clips and trim them down and organize it with the computer you have if it is good enough to do it. You only care about telling the story and it starts when actors hear " action " and it ends when director yells " cut" basically you first have to get rid of the junk that is useless. Now you put junk into editor and cut all the junk before slate and after cut yelled by director. and take and camera ( might be more than one shooting at same time on set with common slate but slate will say cama and camb )
There's a slate and that slate has info about sc. Let's say you have bunch of clips from movie you are editing and doing rushes for.if you can imagine that. It's basically the beginning of editng process.