One thing to bear in mind is that Synced projects is not like project sharing - no locked bins or anything like that - because when multiple users open up a synced project they get their own project to work in that is a mirror image of the original synced project in Interplay. If you go to 3.0 you could experiment a bit with a synced project and see what you think of the workflow. You can have a mixture of synced and regular projects in Interplay, so you can choose whether you want to work with a Synced project or not. So it is a little bit different from the previous Interplay workflow of manually checking in.
Features static (client-side) UIs for simplified integration of JavaScript libraries. For example, use it to integrate a web-based project management system, or your own custom software offerings.
Everything gets checked in to a Synced Folders area of the Interplay database by default. The MediaCentral UX Toolkit includes everything you need to integrate external tools and services into MediaCentral UX workflows as a UI plug-in.
Mediacentral ux no server update#
Also, if a user in Interplay added clips in your bin folder in Interplay, an update from interplay would put those clips in your bin. Same thing if you created a sequence in the bin.
So when you create a bin in a synced project, it automatically creates a folder in the Interplay database. Synced projects are a way of offering an automatic check in to Interplay (without having to do the manual check in process). For more information on MediaCentral Platform Services compatibility with the MediaCentral UX mobile app for iOS devices, see Avids Knowledge Base.Comprehensive access View all of your system.
0 kommentar(er)
