Breakthrough
Ability to modify the start timecodes (STC) of created EDL files to match the on-screen timecodes of video files.
Problem/Use Case It would be nice to have the generated EDL files from PySceneDetect match the on-screen (or any other form) timecode from video files. This is helpful when importing directly into other applications, or using PySceneDetect as one chain in the process.
Solutions Add the option for the user to set a flag in the CLI or with the API to stamp the first detected cut or start of the edl with a custom timecode Proposed Implementation: One nice to have would be that SceneDetect doesn't worry about the inclusion of (:) characters in the SMPTE timecode, allowing for quicker entry of codes and better parity with other post-production tools.
Examples: As an example, Matchbox allows users to set a custom timecode so that any edits or detection's made match up in a NLE/DAW (when creating a shot track).
This should be possible, I'll see if we can get this done for the next release.
One nice to have would be that SceneDetect doesn't worry about the inclusion of (:) characters in the SMPTE timecode, allowing for quicker entry of codes and better parity with other post-production tools.
I'm not totally sure what you mean by this. Could you provide some more details about this or an example of what you mean?
I'm not totally sure what you mean by this. Could you provide some more details about this or an example of what you mean?
Was more of a thought if we ever had a GUI... it's just that a majority of applications in audio post/video post allow the entry of timecodes if you omit the (:) 02:01:34:15 would be entered like 02013415, this just makes entry easier on a numpad.
Was more of a thought if we ever had a GUI... it's just that a majority of applications in audio post/video post allow the entry of timecodes if you omit the (:) 02:01:34:15 would be entered like 02013415, this just makes entry easier on a numpad.
I'm happy to support this in the CLI as well if you think it would be useful.