I haven't thought of a possible solution yet but I would not even try and do this with a scene based script. Making the scene change its own framebuffer during any part of the prepare or beforeonline or runtime phase will definitely case instability and lockups.
If there is a solution its going to have to be modifying the take items before they go online, or using the play command itself to change the layer.
Original Message:
Sent: 07-19-2023 17:30
From: Sean
Subject: Override sequencer take item layer
Hey James, we have a fully automated workflow using a custom software that lives on each Xpression machine and talks to it through the COM API, so unfortunately a Dashboard situation wouldn't work in this case. Thanks though.
------------------------------
Sean Henry
Original Message:
Sent: 07-19-2023 15:31
From: James Hessler
Subject: Override sequencer take item layer
Hey Sean,
What are you using to trigger scenes remotely?
In DashBoard, I have been able to reassign output layer for a specific takeID.
I didn't make it change generically, but the approach might come close.
James.
------------------------------
James Hessler
WAAY TV (ALLEN MEDIA BROADCASTING)
Original Message:
Sent: 07-18-2023 09:26
From: Sean
Subject: Override sequencer take item layer
Thanks Red. Yes, unfortunately that is precisely the problem. Our app is explicitly setting the layer in the xml, so that's what I'm trying to overcome, at least on a temporary basis. The obvious fix is to remove that from the generated XML, but that app itself is a fully featured cloud-based platform, so it requires time from one of our dev teams and unfortunately they most likely won't have time to work on it for some time. I'm basically just looking for a workaround until that change can be made.
To your previous question, ideally I'm looking for something that can be put into an OnBeforeOnline script of a particular scene that modifies the layer before it gets to the framebuffer.
------------------------------
Sean Henry
Original Message:
Sent: 07-18-2023 05:41
From: Red
Subject: Override sequencer take item layer
I just went to look at how the xml's are formatted and there is something called "targetlayer" could you use that in you app?
Here's an example line;
<template name="Soccer GIP" scenename="Soccer GIP" projectname="example_1.42" targetid="10062" groupid="1" targetfb="1" targetlayer="0" targetsvrchannel="0" tcstart="00:00:00.00" tcstop="00:00:00.00">
------------------------------
Simon Redmile
Senior Graphic Programmer & Designer
Ross Video
Bristol United Kingdom
Original Message:
Sent: 07-18-2023 05:38
From: Red
Subject: Override sequencer take item layer
Is your app setting the layer to be 1? I am sure if you set no layer in the XML it will take whatever the default for the scene is set within layout.
You can move items between layers using scripting, depends how you want to do it, would it be a script you want to trigger or something you'd want to build into the online of the scene to move automatically?
I would check first that the scenes don't just take their default layers, seems odd to me that they would be forced to layer 1, perhaps the app is doing that?
------------------------------
Simon Redmile
Senior Graphic Programmer & Designer
Ross Video
Bristol United Kingdom
Original Message:
Sent: 07-17-2023 17:39
From: Sean
Subject: Override sequencer take item layer
Hey all, I am using the sequencer XML watch folder function to build my show sequences. These XML files are generated by an in house developed app and pushed to Xpression.
I'd like to override the playout layers of specific scenes in my package, since the XML overrides the Take Item layer property and puts everything at layer 1. For various reasons we don't have the dev resources at the moment to reconfigure how our in house app exports the XML files, so is there any way to override the assigned sequencer layer of a take item at runtime, through scripting or otherwise?
We don't have graphic operators, and our graphics are triggered remotely via API calls, so manually setting the layers for each broadcast isn't a viable option.
Thanks,
Sean
------------------------------
Sean Henry
------------------------------