Steffan Andrews

I spent a little time trying to see if I could figure this out. I updated the podspec with the latest metadata and managed to get it to pass pod...

That's what I was feeling. I wanted to see if it was possible to get it working at this stage before throwing in the towel. But I agree, it's fiddly...

This is fixed and will be in 0.3.6.

I did a bit of a deep dive this past week on keywords, so yes. They are already being parsed, just not used yet. In fact I was going to...

This was more complex than anticipated since keywords can apply to an entire clip or to a range of a clip. I've built out the parser logic necessary in DAWFileKit...

Also, this will be implemented in the manifest files the same way `Audio Role & Subrole` was. For CSV/TSV it will be a comma-separated string. For JSON, it will be...

> Should we have flag called `--keyword-range` with `marker` (default) or `clip` options? Trying to avoid flag creep if possible. We can add it if there's a strong need for...

I posted an alpha release for testing: https://github.com/TheAcharya/MarkersExtractor/releases/tag/0.3.6-alpha1 Please give it a try and check all the profiles to make sure they contain the new manifest field and its contents...

> 1. Convert all `Spaces` and `,` `.` to `-`. Unless there are known issue(s) with specific illegal characters, users probably don't want us to sanitize the keyword text. MarkersExtractor's...

> We should also include `Clip Keywords` for the `--label` burn-ins. Certainly possible but there should be a hard character count limit (100?) for it so extremely long keyword lists...