rvanar: Thank you for your feedback.

Alex Probe: we have this in pipeline. To expedite, it would help us know your use case. Feel free to book a time on my calendar here - https://calendly.com/anshul-gumlet/meet

Anshul: This would be really helpful to have! I guess you currently think of a manual replace operation:

1) User uploads video, describes, tags and embeds it to content

2) User finds some issue with the asset and fixes it

3) User re-uploads and performs manual replace operation (in Gumlet)

Even better workflow:

1) Upload from spot that Gumlet can check anytime, e.g. Server-Folder

2) User in Gumlet describes video, tagstags, and embeds it to content

3) User again 😠 finds some issue with the asset and fixes it

4) Updated video gets detected and replaced by Gumlet 😃.

Users would simply reopen the video project on their local machine, do their changes in Premiere, Final Cut or whatever editing tool and re-render the clip (by overwriting the old output). When done, the asset would magically refresh on their website.

To make such happen, two things had to be in place:

a) An automation that picks up new or updated local files in some sync-folder and drops them to a location Gumlet can access. That's of course an issue the customer must take care of. But it's pretty simple – we have such sync folders running anyway.

b) Some Cronjob of sorts that makes Gumlet periodically check uploaded assets for changes (save date, file-size). If an update gets found, the asset gets replaced.

hus: Thanks for the detailed explanation. We are working on this already and will be available through normal workflow.

Anshul: Thank you, that sounds great! To round things up, you might consider supporting xmp metadata (such as keywords) in clips. This open metadata supports video and lives in the asset itself. Gumlet could extract pre-existing keywords / tags in files (for search and filtering) and treat them as if they were created in Gumlet.

With this in place, content editors could take care of all media tagging / categorizing already on their offline machine.  You'll know that a lot of media will get shared on other platforms as well –  hence it's best to have a single source of truth. 

Metadata inside source files (in contrast to all proprietary tagging schemes) survives any platform-migrations. Upon streaming, you guys will very likely strip all metadata – but the originals remain untouched.

If this sounds interesting, I can provide a sample clip.

I thought I'd rather not wait, but simply post a sample. Here is a 5 sec. clip that contains some metadata, which already got added on the local machine:

I have tested by re-downloading the asset from the video CMS again – Gumlet does not strip existing metadata in files while it pre-processes it. In other words – you could target these metadata-fields – and your users were ready to control video-metadata, including descriptions, from their Desktop machines.

Here is what an online metadata reader can read in the file:

Finally, a screenshot of the metadata panel of the Adobe asset management tool I used on my Desktop machine.

kyvoamedia: Thumbnail replacement is already available - https://docs.gumlet.com/docs/video-asset-management#change-thumbnail