Steffan Andrews

Probably not necessary, since absolute timecode is intuitively obvious in our case. But you could add something to the wiki docs for MarkersExtractor and Marker Data that clarifies this if...

It took most of today to build out the metadata parser but it's mostly done. With any luck, populating the fields should be fairly straightforward. I'll try to get it...

Side note: when new fields are implemented, they automatically become available as thumbnail image `--label` burn-in options.

Ok - now implemented, and seems to be working as expected in my limited testing. Will be in 0.3.6. FCP project: Manifest output:

@IAmVigneswaran new alpha build for testing: https://github.com/TheAcharya/MarkersExtractor/releases/tag/0.3.6-alpha3

It makes more sense just to use angle metadata as default behavior. Grabbing metadata from the multicam container wasn't intentional, it's just the first round of naive parsing that needs...

I believe the best approach is to first grab the angle's media metadata, then grab the angle's metadata and overlay it on the container's, replacing the container's keys with the...

I'm not adding them, this is for my own reference. The parser is gathering all known metadata and filtering out the ones it needs.

Ok multicam metadata is now fixed. Will be in next build. Still need to test other complex clip types which I think will also require special handling. - [x] `mc-clip`...

> Generally speaking: it should always use the source media clip timecode and not the container timecodes. Or at least make this optional. @samplue do you mind clarifying this?