Resolume Forum

Thanks, t13swift. That's what I meant.

@ elgarf, I'm even more confused now! When you say:

3) create screen 2, it's virtual output. It takes left part of composition. Let's name it left.
and
5) copy screen 2, name it right. It takes right part of composition.

You mean slice 1 in screen 2 and slice 1 in screen 3, correct?

@ t13swift, you're not following elgarf's steps since you're splitting screen 1 & 2 and setting them to left and right but there is no mention of doing that in his steps.

If I follow the steps (assuming you mean slice 1 in screen 2 and slice 1 in screen 3), it works as expected for me. Both virtual outputs (2 and 3) are taking their input from the comp, screen 2 slice 1 is left half and screen 3 slice 1 is right half. Then slice 1 of screen 1 is taking its input from screen 2 (left) and slice 2 of screen 1 is taking its input from screen 3 (right) and I end up with the full composition back on Screen 1.

@ elgarf, I guess, I'm still trying to understand what you're trying to accomplish with these two virtual screens. Can you elaborate?

You mean slice 1 in screen 2 and slice 1 in screen 3, correct?

Yes, I thought it's clear, because screen has 1 slice by default. It's hard to write much text from smartphone.

@ elgarf, I guess, I'm still trying to understand what you're trying to accomplish with these two virtual screens. Can you elaborate?

I often do that, when I'm working with datapath.

Is this whole thing for you to split your screen into the various outputs of a datapath X4?

All you have to do is use one screen with 2 (or 3 or 4) slices, size/position the slices on the input and size/positions your slices on the output to match your datapath X4 outputs.

It's handy to keep screens separately.
I can use just 2/4 slices, but still I have virtual outputs why not to use them? If I need more than one slice on each screen, it organizes interface better for me.

Btw, even if t13swift made all not the same as me, he get some result, which looks not good, isn't he?

I can reproduce your problem, and we're going to see what we can do about it.

I can use just 2/4 slices, but still I have virtual outputs why not to use them? If I need more than one slice on each screen, it organizes interface better for me.

Keep in mind that Virtual Outputs are not free, they come with a performance hit. They take up VRAM and may require an extra render pass. So if you can do something directly, it's always better to do so. Don't use them for organisational purposes or 'because you can'

There are more advantages than disadvantages in virtual outputs for me:)