When working with large (several thousand stories) queues the CTMS performance takes a nose dive. Frequently attempts to update a story fail with a Gateway Timeout error. This usually has a knock-on effect in that the story unlock also fails leaving the queue with unwanted locked stories. This also impacts on the client performance as each failure introduces

Using the ia:queue-stories-by-id link it is possible to obtain a list of stories together with their attributes. There is an issue when using the "self" link to subsequently update the details of a story. An example of a genuine "self" link is shown below. Note that it reflects the original request in that the embed query includes

Unlike Interplay Web Services it does not appear possible to move production items from reserved folders using the loc:move-items call.

Sorry, these are questions that Avid should be answering.

When using CTMS to retrieve the attributes of a master clip the com.avid.workgroup.Property.System._OMM_MOB_COMPLETE attribute is not returned. This means that it is not possible to determine whether a master clip is complete or not when using CTMS. If someone has inadvertantly (or perhaps foolishly) created a USER version of _OMM_MOB_COMPLETE then

Hi Kenneth, This intrigued me so I did a quick investigate and found that you can specify the proxy host rather than just defaulting to localhost. In your project.config.json add the parameter "proxyHost" after the "proxyPort" connection parameter. Set that to the IP address of the machine you use for testing, it should then be possible

Hi Vadym, sorry for the late response! I have now inserted an additional call to retrieve the "self" object from the newly created folder and then use the move item(s) link from that. This has removed the unwanted (and erroneous) error. Thanks, Mike

Tilman is most probably using a paltform service, i.e. a service that connects to the Avid Platform Bus and can therefore be communicated with directly from the UI application.See http://developer.avid.com/connector_api/

Scenario is that an asset in a Production Management folder needs to be moved to a sub folder which does not currently exist. Sequence of events is (1) create new sub folder, (2) move existing item into it. The operation succeeds but returns a status code of 500, internal server error. If the sub folder already exists then the error does not occur.

Hi Nikin, You can't "send" anything from MCUX to Media Composer, you essentially have to "pull" material into Media Composer from Media Central Production (Interplay). You could potentially create a common "Render Required" folder in Media Central Production to which you could push sequences that need rendering then