While there's no question that there are a number of ways that we at Adobe could make metadata workflows more powerful, versatile, and efficient, I respectfully disagree with MEM's assessment that Prelude offers no real advantages.
I'm not familiar enough with the Prelude's full feature set to do the program justice, but I'll at least call out a few that impress me:
- setting multiple subclip markers, which are then automatically converted to subclips in Premiere when you import the clip.
- Batch renaming via XMP (as opposed to renaming the file on disk). This offers great advantages when working with filebased content that the camera named C0001 or 0002DP or A002_C001_0419UG_001.
- Metadata tagging. Despite some of the shortcomings that MEM calls out, metadata can have value today in your Adobe workflow, and Prelude is a very good tool for injecting metadata.
My impression is that Prelude's value increases with the scale of the operation. At networks and large production houses with tremendous volumes of content coming in daily, entry level employees can be trained quickly to handle ingest and tagging, which not only relieves higher-skilled people of this work on the front end but also saves them time to focus on more creative work but also saves them time by leverag