The preset you sent over was not aligned pixel perfect.
Maybe try using regular rectangle slices instead of polygons.
I wouldn't recommend AMD GPUs currently.
MacBook Pro (2017/2019) output issue
Re: MacBook Pro (2017/2019) output issue
Software developer, Sound Engineer,
Control Your show with ”Enter” - multiple Resolume servers at once - SMPTE/MTC column launch
try for free: http://programs.palffyzoltan.hu
Control Your show with ”Enter” - multiple Resolume servers at once - SMPTE/MTC column launch
try for free: http://programs.palffyzoltan.hu
-
MNCreative
- Posts: 8
- Joined: Wed Dec 22, 2021 21:14
Re: MacBook Pro (2017/2019) output issue
Hello Zoltan!
I took some time on the last weekend and prepared the advanced output so the point positions of the polygons in "point edit" are perfect pixels with no decimals. Please find the advanced output attached for your review.
I furthermore attached an image of the Resolume testcard. As you can see, everything is perfectly aligned (according to the testgrid etc.), but those blooming lines are on every edge of each slice. I also think that they are on all other slices (slice 1-3 and slice 5-7), but since those are extra physical walls, there is no obvious effect to recognize - so we don't care in this case.
Back to the center wall:
If I move the slices apart by one pixel, there is - obviously - a black pixel-strip. So there is no way that there is something misaligned from our side (in my opinion) - and as I said - on Windows and M1 Macs, everything is fine with this exact advanced output .xml file.
I took some time on the last weekend and prepared the advanced output so the point positions of the polygons in "point edit" are perfect pixels with no decimals. Please find the advanced output attached for your review.
I furthermore attached an image of the Resolume testcard. As you can see, everything is perfectly aligned (according to the testgrid etc.), but those blooming lines are on every edge of each slice. I also think that they are on all other slices (slice 1-3 and slice 5-7), but since those are extra physical walls, there is no obvious effect to recognize - so we don't care in this case.
Back to the center wall:
If I move the slices apart by one pixel, there is - obviously - a black pixel-strip. So there is no way that there is something misaligned from our side (in my opinion) - and as I said - on Windows and M1 Macs, everything is fine with this exact advanced output .xml file.
- Attachments
-
- mapping_v2_pixelperfect.zip
- (4.18 KiB) Downloaded 246 times
-
Re: MacBook Pro (2017/2019) output issue
Hmm, yeah, looks good on my M1 too.
Input slices also pixel perfect?
Input slices also pixel perfect?
Software developer, Sound Engineer,
Control Your show with ”Enter” - multiple Resolume servers at once - SMPTE/MTC column launch
try for free: http://programs.palffyzoltan.hu
Control Your show with ”Enter” - multiple Resolume servers at once - SMPTE/MTC column launch
try for free: http://programs.palffyzoltan.hu
-
MNCreative
- Posts: 8
- Joined: Wed Dec 22, 2021 21:14
Re: MacBook Pro (2017/2019) output issue
Hi again!
I just wanted to keep everyone updated who was following this thread or maybe has the same problem and found this topic after searching for it.
After hours of research and try and error, I found out that the problem is the YCrCb signal a Mac is sending out by default. We had the exact same problem with a Windows PC as well after sending its RGB signal through a Atem Mini (which is able to output YCrCb only - unfortunately). Without the Atem Mini (original RGB signal) everything works fine. On the Mac I forced it to go in RGB mode for this one monitor (LED controller) using a script I found on the internet.
So in conclusion: RGB is the way to go, fuck YCrCb. Therefore fuck Atem Mini and Mac (especially because it's not possible to change the mode on the fly like you can do that on a Windows machine) as well.
Hope that helps someone in the future!
I just wanted to keep everyone updated who was following this thread or maybe has the same problem and found this topic after searching for it.
After hours of research and try and error, I found out that the problem is the YCrCb signal a Mac is sending out by default. We had the exact same problem with a Windows PC as well after sending its RGB signal through a Atem Mini (which is able to output YCrCb only - unfortunately). Without the Atem Mini (original RGB signal) everything works fine. On the Mac I forced it to go in RGB mode for this one monitor (LED controller) using a script I found on the internet.
So in conclusion: RGB is the way to go, fuck YCrCb. Therefore fuck Atem Mini and Mac (especially because it's not possible to change the mode on the fly like you can do that on a Windows machine) as well.
Hope that helps someone in the future!