MacBook Pro (2017/2019) output issue

[MNCreative]

Hi!

I'm currently having a problem with a LED wall setup.

Let me first give you an overview:
Windows-PC with Resolume Arena - HDMI Cable - Video Scaler (which is actually just acting as a DVI splitter and HDMI-DVI converter) - DVI - Sending Cards - Receiving Cards - LED Wall

Scaler is set to 1080p60. Every slice of the wall is within this area.

Everything is fine with Windows and the custom Advanced Output of Resolume.

When I connect my MacBook Pro (15" 2017) via the same HDMI input to the video scaler the edges of the slices are kind of "bleeding". Some slices that are directly next to each other (couldn't make one slice because of pixel real estate - also no chance for a 4K input) are divided by one pixel or they mash together and become a little brighter. Of course I tried to move the slices in the output map to compensate it, but this doesn't work. If I move them closer thy start to blend into each other, if I move them apart, a black pixel line appears (of course). Even half-pixel steps don't help in any way.
The same issue with a MacBook Pro (16" 2019).

Now the interesting part of the story: a M1 MacBook doesn't show this effect. The output is perfect, like on the Windows machine.

So my conclusion so far:
It must be something to do with the GPU. Both MacBooks have a Radeon inside, the Windows machine has got a nVidia GeForce *something* and the MacBook M1, well the M1.
All machines run the latest Resolume Arena version.

I have attached an image to show the difference on a simple red solid.

Did anyone else have this problem? Any suggestions on how to solve this?

[Fabian2702]

Interestingly if we use the LED Wall as a normal external screenweI don't run into this kind of issue and there is no visible line. It just happens when using Resolume. Using an external GPU (Radeon) didn't resolve the problem either.

Any ideas on how to resolve that issue? Perhaps there is anything we oversee?

[Zoltán]

Can you share your advanced output preset?

Is your mac output running as HiDPI?

[MNCreative]

Hi Zoltan!

Please find our advanced output attached.
Can you specify what you mean by HiDPI? We didn't tweak anything so far, so everything should run like a usual monitor we connect to our MacBooks. No scaling - the scaler/dvisplitter introduces itself as 1080p60 like it is supposed to.

Thanks,
Martin

[Zoltán]

You have some polygon points at fraction pixels, that can behave unexpectedly on AMD vs nvidia. Other slices have the diagonal lines over 1 pixel on the edges.

[MNCreative]

Hello Zoltan!

I understand that this could lead to problems.
The thing is that those values became these values all by themselves. When I type in a pixel perfect value and move for example the whole slice by exactly one pixel and I grab a corner of the slice (with turned off snap function of course) then the value is again at a very suspicious value very near the actual value but not without any decimals. But this is not the core problem I think....because....

Of course I could move the while slice by one pixel (or even a fraction of it), but as stated in my first post, this either led to a full black pixel row or a "light bloomed" area. And I went with 0.05 steps. So there was literally no way of achieving a perfect image, while on any other machines with Windows/nVidia or M1 there was no problem with just loading the same advanced output .xml

[Zoltán]

Is it the top right slices you have issues with?

[MNCreative]

Hello Zoltan!

No, its Slice4-1, Slice 4-2, Slice 4-3 & Slice 4-4. So alle 4 slices that build the center led wall.

Kind regards,
Martin

[Zoltán]

Yeah, those have points at fraction pixels too.

[MNCreative]

Yes I know, but I can only cite myself in this case:

I understand that this could lead to problems.
The thing is that those values became these values all by themselves. When I type in a pixel perfect value and move for example the whole slice by exactly one pixel and I grab a corner of the slice (with turned off snap function of course) then the value is again at a very suspicious value very near the actual value but not without any decimals. But this is not the core problem I think....because....

Of course I could move the while slice by one pixel (or even a fraction of it), but as stated in my first post, this either led to a full black pixel row or a "light bloomed" area. And I went with 0.05 steps. So there was literally no way of achieving a perfect image, while on any other machines with Windows/nVidia or M1 there was no problem with just loading the same advanced output .xml

My first reaction WAS to place everything pixel perfect, but this didn't solve the problem.