Hello, We're really not sure what the issue is here. Can you please provide a self contained runnable sample Visual Studio project that shows the problem based on the issue reporting template that is included with AMT3 (see documentation). I will create a ticket so our development team can investigate. Best Regards, Dennis

The endpoint is http://<MCIHOST>:8083/api/process/user/list Headers required are: Accept: application/json;version="1.0" Use Basic Authentication with the desired user/password to get that user’s processes. The a sample response looks like this: 1 { 2 "processes" : [ 3 { 4 "id" : "47263952-e6c6-4e58-b8a8

Hello, It sounds like you are trying to exchange MOS messages from EVS with Newsroom Management? Did the thick client have an ActiveX MOS Plugin to communicate with iNEWS? Via MOS Gateway? The need for a plugin does not change with EVS's switch to a Chrome Browser version of their client. To support this workflow, you or EVS would need to develop

HI Adri, Apologies for the delayed reply. Yes, if your application needs to communicate with Cloud UX in any way, a unique App ID and Secret are needed for authorization. Please review the Quickstart Guide (link at the top of developer.avid.com) for infomation on all requirements. Best Regards, Dennis

Hi Mike, did this help?

Hi Mike, I beleive this will help: Rundown app API has changed in Cloud UX comparing to Media Central. In Media Central, it allowed using MOS XML in the drag payload directly. In Cloud UX, on graphics drop into a story, Rundown expects dataTransfer to contain a reference to a graphics template, and template parameters. Then, Rundown calls the graphics

Hi Jonathan, Unfortunately the developer that owns Interplay Web Services is out of the office until 7/27 so there may be a delay in getting you an answer. Apologies! Dennis

Hi Jeff, AMT does not have support for sequences, only clips. from the AMT3 Functions Guide: "1 Note that Media Processor AMT3 functionality is limited to master clips. AMT3 does not expose support for higher complexity objects such as shot lists or compositions (sequences)." I hope this helps. Best, Dennis

Hi Nikin, Interplay Web Services does not work with the MediaCetnral | UX API. For metadata exchange via a MediaCentral Cloud UX plugin, you would need to use the Media Suite API (CTMS).

Hi Nikin, what are you trying to do? If you have an AAF file from Interplay Web Services, where are you looking to save it?