Resolume Arena Slices not Aligning
Posted: Mon Mar 16, 2026 11:05
Hi, Will try and put all details of what I'm dealing with below.
Using 1 LED display, 3584 x 640, running through 2 LED 1080p Novastar screen processors, so sending 2 Displays out of my graphics card at 1920x1080, mapped to do each half of the screen, each output running 1792x640 pixels.
If I put in the exact mapping in the slices to split graphics between the 2, I get a 1 pixel black gap between the 2 slices. If I move the mapping across, I get a misaligned line in the centre. If I close resolume and look at the 2 displays on the screen, it doesn't have the pixel gap.
Running on a PC with Nvidia GTX-1080, 2 display port outs. Have tried running into the processor on both HDMI and DVI, and tried different a graphics card.
If I use exactly the same slicing settings on my Mac M1 Pro, displays show as they should, without the pixel missing.
Input and Output transformations as follows (not sending them as NDI, just since I'm not in front of the processors now)
Would put it down to misscaling or something with the processors, but only happens on the PC not the Mac.
Using 1 LED display, 3584 x 640, running through 2 LED 1080p Novastar screen processors, so sending 2 Displays out of my graphics card at 1920x1080, mapped to do each half of the screen, each output running 1792x640 pixels.
If I put in the exact mapping in the slices to split graphics between the 2, I get a 1 pixel black gap between the 2 slices. If I move the mapping across, I get a misaligned line in the centre. If I close resolume and look at the 2 displays on the screen, it doesn't have the pixel gap.
Running on a PC with Nvidia GTX-1080, 2 display port outs. Have tried running into the processor on both HDMI and DVI, and tried different a graphics card.
If I use exactly the same slicing settings on my Mac M1 Pro, displays show as they should, without the pixel missing.
Input and Output transformations as follows (not sending them as NDI, just since I'm not in front of the processors now)
Would put it down to misscaling or something with the processors, but only happens on the PC not the Mac.