Hi Jeff, IPWS cannot parse complex sequences properly. What you might be seeing is the result of motion effect in the corresponding sequence. Thanks

Hi Mark, Followed up on this issue in email. Troubleshooting typically requires engineering engagement and a support agreement in place.

Hi Marcel, Could you please provide more details on the modules structure? App creator tool/starter kit let you publish app that is packaged into a single docker image. Packaging multiple docker images would be a manual process for now, so we would like to have a better understanding of the case here. It may be easier to merge modules into a single

Thanks for looking further into it Rich, So it appears that IPWS call to generate tape based mobs for batch ingests adds it. We are not using it as its quite old method and should not be used for file based mobs. I'm able to reproduce this behavior

Rich, Attempting to explain full logic of the GetLatest operation doesn't make a lot of sense now that IPWS is in maintenance mode and migration to CloudUX is coming. There is more complicated logic than just database in place that accounts for the master mobs inside of the composition aaf at the time of the check-in. Database gets more updates

I don't see the Video attribute created in my environment. AAF toolkit allows you to create any attribute, so you can try to find what creates those and see if that is updated by MediaComposer check-ins for example. Thanks

Current Video Resolution is the attribute set by Video Editing application typically to match the project/relink video format on the last check-in or by Ingest to match the format of ingest. This is not automatically updated if available resolutions are changed later unless another check-in has been performed. There is no pre-defined Video attribute

Hi Rich, You're describing multirez scenario here. Sequence only references assets so when underlying assets are checked-in with a different current resolution IPWS will return it. IPWS does not support dynamic relink so cannot retrieve a resolution of interest for you, but you still should be able to get all resolutions using the GetFileDetails

Hi, Public APIs documentation is avaialbe at http://developer.avid.com which is being updated periodically. CTMS is platform APIs while IPWS is PAM API. There is no intent to make direct replacement of IPWS in CTMS but we can look into availability of the calls needed for the integration of your workflows. As you may see at the http://developer.avid

This is system attribute which is readable through IPWS. The attribute is not set for regular imports/ingests. Only EWC/Frame Chase workflows (should) create this attribute.