Screen tearing out of Advanced output

[anthonydiehl]

Running a show in R6.0.7 on a Windows 7 PC, GTX 1080ti card. The composition is 5760 x 1472. Advanced output is outputing slices to two displays (two Datapath Fx4s running at 3840 x 2160 each). In the grand scheme of the show we are going out of two FX4s at 3840x2160 each into imagepros, converting to 23.98PsF and into video routing. However, we have isolated our issue down to just outputs coming out of resolume. We are getting major tearing out of the advanced output. After extensive testing and troubleshooting, we can see this VERY pronounced horizontal tearing coming out of resolume when creating a simple test comp of this size (5760 x 1472) and outputting through advanced output to a single 3840x2160 display (monitor, not FX4). This seems like an extremely simple setup... a single 4k out. Tested on three completely separate machines and in R5 just for kicks. All variation of the same issue.

V-sync is on. All monitors and displays connected share the same refresh rate. GPU drivers are current.

How can I get a clean, horizontal tear free image out of Resolume? Whats going wrong here?

[Zoltán]

V-sync should do this.
What's your FPS in Resolume when you are not playing anything in a new empty composition?

[Joris]

Do you mean horizontal tearing as in the seperate outputs losing framesync, or horizontal tearing as in a single display showing a horizontal tear in the vertical axis?

[anthonydiehl]

FPS stays at or around 60 in all scenarios.

We have horizontal tearing pulling apart inside individual screens. Sync between screens seems good, or at least not noticeably an issue at this stage.

[anthonydiehl]

Just to illustrate, the type of horizontal sheering/tearing we are seeing on a rolling horizontal line test is below

[Zoltán]

Do you see the tearing in the Output Monitor in Resolume too?

[anthonydiehl]

Yes, tearing showing in the output monitor, although it does not seem to correlate exactly with the tearing actually showing on screen.

[Joris]

So, apparently this was caused by a custom edid that OP had programmed, and it was fixed by using a proper hardware edid.

Topic locked