Single video cue to multiple surfaces

[ivan birthistle]

Hi all,

I know this was discussed some time ago but was wonder if there is any update.
We are intending to project onto 6 curved screens using 2 datapath 4 units, so far so good.
The processing problem we are having is having to use separate video cues for each surface, which is eating up CPU.
We are essentially mostly playing the same content on each screen so we don't want to have to split our playback across multiple macs.
On V2 there was the option of just selecting multiple outputs natively in the cue (I know there were some processing issues), is there any reasonable workaround for this or am I missing something really simple in the surface editor?
Simply put - can you send a single video cue to multiple surfaces?

Cheers,

Ivan

[Joshua Langman]

No, but you can create a surface that uses multiple screens and send one cue to that surface. Just drag the screens directly on top of each other in the surface editor.

[ivan birthistle]

Thanks Joshua, but the other part of the problem is that with 6 projectors onto curved screens each surface needs to be warped differently, otherwise I could just use a regular splitter.

[micpool]

You still have independent control of each screen warp. Ot have I missed the point here?

Mic

[micpool]

Sorry meant surfaces

There is a workaround to send a video to multiple  Surfaces

Add an extra surface with a syphon output



But I don't think there is any need to do this in Ivan's case, if I am understanding his requirements correctly.

Mic

[micpool]

Here's a screen capture showing 1 video to 3 surfaces on 1 screen.

At the start of the video there is zero latency between screens. The video cue is spun 180 degrees. Towards the end of the video a different color effect is applied to the 3 camera cues which  results in some latency between screens due to the differences in video processing times.

Mic

[ivan birthistle]

Thanks a million Mic, I think the layered surface solution is somewhere along the lines I was thinking, I'll grab the datapath and get a full test done early next week and let you know the results.
I like the workaround too but am having trouble setting up the Syphon camera input - I might be stupid but it is Friday!
Ivan

[micpool]

On Friday, January 19, 2018 at 5:05:01 PM UTC, ivan birthistle wrote:

I like the workaround too but am having trouble setting up the Syphon camera input - I might be stupid but it is Friday!

If you have created a surface with a Syphon output and you can't see it listed in the Camera Patch popup menu, save the workspace close and reopen. It should appear straight away though in the most up to date version of QLab.

Mic

 

[ivan birthistle]

Hi Mic,
I've done a robust test with the Datapath + 2nd output and all was perfect, much easier than expected.
I got the Syphon work-around going too.
Thanks for your help, it all seems so simple now!
Cheers,
Ivan