Graphics

Here's our setup: We have 2 Xpressions running the latest version of Studio. We have a server running Bluebox. Our 2 Xpressions are set up as playout engines and the server with Bluebox is set up as the preview engine. Our newsroom is using ENPS with the MOS plugin for creating graphics.

Here's the problem: I only want our ENPS users to have access to a specific scenes in our graphics package, but they currently have access to ALL of the scenes in the package from within ENPS. How do I limit which scenes they can access? Basically all I did was take our entire project folder and copy it to the server. I can't see any way to only give them access to specific scenes within a larger project and there isn't much documentation on this.

Hi Brian,

It's not possible to control individual access to scenes within a single project.

However, when using XPression Project Server multiple projects can be loaded in the preview/playout engines simultaneously.

With Project Server workflow the XPression ActiveX plugin in ENPS only displays one project at a time, so the user could load a specific project that only contained the scenes that they needed. The additional projects would contain all your other scenes that they don't need access to.

#XPression

How exactly do I load a project into the preview/playout engine?

Since Bluebox is the preview engine and is running on the server, does it give ENPS users access to whichever .xpf projects are on the server's D: drive?

#XPression

And with our setup, are our ENPS users given access to only what is in Bluebox?

#XPression

Also, what is your recommended process for setting up a project with our setup?

#XPression

When using XPression Project Server the system will automatically load the required projects into both the Preview and Playout Engines.

Ex. When a preview is requested from an XPression plugin the Preview Engine will automatically load the required project(s) from the Project Server as well as check for revisions.

Ex. When the Playout Engine load a MOS rundown it automatically loads the required project(s) from the Project Server as well as check for revisions.

With Project Server workflow the XPression ENPS plugin can browse through the projects that are stored on the XPression Project Server and when a project is selected it loads into the Preview Engine. With this workflow the ENPS users could load a specific project that contained just the scenes they need access to and additional scenes (that they don't need) would be stored in other projects they don't need to open.

In short - XPression Project Sever eliminates the need for manually managing the .xpf files and their asset folders. As well as enabling multi-project workflow.

#XPression

Without Project Server the ENPS users are only given access to the project that is loaded in the Preview Engine (BlueBox OFL). And the Preview Engine is only able to load one project at a time.

#XPression

Without Project Server your only option is to have all the scenes you need in one project.

#XPression

I got everything working right, except for some reason it won't remember framebuffer assignments when I set them in ENPS. No matter what everything comes out on framebuffer 1 unless I manually reassign it in Xpression Studio.

Any ideas?

Thanks,

Brian

#XPression

On the XPression MOS Gateway go Gateway > Settings >

See this image:



If it is already set to that change it to something else "“ Click OK "“ Go back in and change to 'Default to Template' "“ Click OK.

Then re-launch a plugin and try it again.

Do you have the default framebuffer set for your scenes?



#XPression

I would check the Virtual Channel mapping in the MOS Gateway settings and ensure you have the virtual channels mapped to the correct physical outputs on each engine. It's possible you have all virtual channels mapped to Output framebuffer 1.

#XPression