Hello Adri, to run your CloudUX App you need the appropriate license on your MediaCentral system. For development systems you can request a generic developer license, valid for 30 days. For production systems you need to register your App with Avid, then request a license for MediaCentral that includes your App. Please contact [email protected] for

I personally don't use the proxy, I had the impression it can get slow and I've been looking for solutions that don't depend on a complex Node stack. Here are some options, I use the last two (HTTPToolkit and mini linux server) for my personal development setup: Use nginx as a reverse proxy to cloudux and modify the response for plugin list

Mike is correct, this is a separate installation bundle and not part of the UI Plugin. When deploying this on a CloudUX cluster you will have to install 2 separate items: the UI and the proxy service. This is a lot of extra work but there are a couple of advantages vs. changing the access control headers: * Your UI plugin won't suddenly cease to

The way I do this is via a proxy service running as part of the CloudUX backend. I send requests from the UI to this proxy service which then communicates with my external services and returns the response back to the UI. This really is the only sensible way to do this because the browser will block most attempts to communicate with other servers directly

Hi Vadym, trying to create a CloudUX plugin following instructions at http://developer.avid.com/mcux_ui_plugin/introduction/doc/development_npmjs/development_npmjs.html results in a crash (see below). In addition the webpack config is at node_modules/cloudux-starter-kit/lib/connector/config/webpack.common.config.js which makes it very hard to customize

The obvious disadvantages are missing support when something does not work. There is not a lot of documentation/specification on how CloudUX loads plugins etc and Avid won't support you if you move away from the official tooling. So unless you are willing to invest the time to dig into issues I would not do it. For me personally it made sense because

Hi Kenneth, I've built my own setup to avoid the outdated toolchain and give me more control over the configuration. YMMV but maybe this is helpful: https://github.com/tilmans/cloudux-simple-app And to build installable packages: https://github.com/tilmans/custom_cloudux_build I don't work for Avid and all of this code could break at any time

Hi Mike, I'm not sure the reference did not exist, they probably have folder items which get moved as well when using Access. This sounds to me like a bug in the CTMS implementation, I'd recommend contacting developer support and posting a bug to them. Cheers, Tilman

Hi, with Media Index you can perform this search now although it's not very obvious: Search for "*", add TBMD > id as a search criterion and set it to "not set". This will return all assets that don't have any markers/locators set. This works with MCUX 2.10