Steffan Andrews
Steffan Andrews
> Penguin Keyword is not used for the clip range. Not sure what's going on there without more in-depth tests. I also noticed that some keywords are being repeated in...
Actually, it's already possible. `--label clipKeywords`. Updated README to include the updated CLI help block with it. But I will add a max char limit.
I am now trimming leading and trailing whitespace, removing duplicates, and sorting alphabetically. This cleans up the keyword list a lot. Previous output before the keyword cleanup:
I have a theory regarding the spurious `penguin` keyword appearing. In the keyword extraction function, if there is an error when reading a keyword's range, the keyword is included by...
Ok I believe I have fixed the spurious keyword extraction.
I posted a new alpha release for testing: https://github.com/TheAcharya/MarkersExtractor/releases/tag/0.3.6-alpha2
`Clip In` and `Clip Out` Timecode as well as `Clip Type` should be easy to do. However I ran into a funny issue when investigating the clip and camera metadata....
I just realized that for the same reason why we should remove `Clip Filename` (#65) from the output manifest, `Media Duration` is not a viable field. As you mention in...
Just to be clear, for our purposes, `Clip In` and `Clip Out` timecodes will be absolute timecodes (based on main project timeline) and not the local media's timeline.
Yes, but I only mention it because within Final Cut Pro's clip inspector, clip start and end timecodes are shown in relation to the its own media's timeline, as it...