Graphics

In order to update/add templates accessible in ENPS, we have to export the entire project file package - it can take upwards of 45min, involves multiple steps (each with their own possibility of hang-up or failure), and leaves us without ENPS template access until the entire update is complete.

Is there a way of updating/adding templates to the project file for ENPS access without deploying the entire package? (Xpressions v4.1 & ENPS) Thank you.

You need to purchase the XPression Project Server. It will automatically deploy ONLY changes made to the project. Additionally, it will automatically deploy projects - no more manually deploying projects on the preview and playout engines.

In the meantime - you should try and delete unused materials and assets in your project to cut down on the size. Also, are you trying to export/deploy the package across a network share or USB? That will drastically slow down the export and deployment times.

#XPression

We're deploying across a network, which definitely doesn't help our time constraints.

Thank you, Garner - I'll take a look at the Project Server. Thank you, also, for your quick response!

#XPression

It *might* be a little faster to deploy to the local disk - copy to the network share - copy to the other machines local disk - and then deploy. Although - with all the transferring it might actually end up being slower.

Project Server is definitely the way to go though!

#XPression

If you have one massive project for one show, it still must be published to the Project Server as an entire project, and that may take a few minutes still, though ours publishes pretty quickly.

To my understanding, Project Server is for managing multiple projects in the same XPression system. We have 2 TV stations in one building, with unrelated graphics packages, so that is the reason why we have a Project Server.

I quickly learned that the Project Server tries to publish any unused files sitting in the project folders, and if I have materials that live in temporary folders, it re-created those folders on the machines the projects were deployed to, so now I make sure to keep everything well organized.

#XPression

That's correct - the first publish to the project server will take almost as long as an export, because it has to upload everything to the project server. The first deployment from the project server will also take just as long, it has to download everything to the engine.

However - after that it should be very quick, as only changes should be published and deployed. MBs of data instead of GBs.

Project server was designed for multi-project workflow, but its still very useful for a single project workflow site.

- projects are all stored in one location

- only changes are published and deployed - much faster update times

- projects are automatically deployed to the playout and preview engines - no longer requires manually loading the project on each engine one by one - the system does it itself

Lorraine, you can stop the system from publishing all unused files sitting in the project folders by un-checking this box during the publishing process:



#XPression