Hi all, new to Corona and loving the product so far. I’m currently working on a maxscript that breaks a render into smaller tiles, and have come across some minor issues:
- To test my script, I am taking a simple 768x512 pixel rendering and splitting it into six 256x256 pixel tiles (3 columns x 2 rows)
- I am using the #crop functionality in maxscript and saving the output as .tifs
- My script calculates the “top left” and “bottom right” pixel coordinates for each tile as illustrated below:
The script works as expected, except when I try to reassemble the tiles I get noticeable seams (see below in red box):
So apparently this is a pretty common problem with distributed rendering, most sources say the solution is to create a 10-20 pixel overlap between tiles that gets trimmed away in post. I've done that and although it helps a little, it doesn’t completely eliminate the problem, even with a 128 pixel overlap:
20 Pixel Overlap: 128 Pixel Overlap: Curious whether anyone knows a workaround to this problem. I’ve tried some minor tweaking to the render settings but still getting the same issues. Is it better to use #region vs. #crop? Are there render region controls native to the Corona VFB that work better for splitting the image? Appreciate any feedback!
Some additional background:
- I’m using Alpha v6 right now (but will definitely buy the most recent version if I can get this working)
- I’m just rendering on one machine at the moment (this isn’t a backburner related issue)
- Using bucket rendering, quality settings are generally set very low at this point
- As mentioned, I’m saving the images as TIFs so I don’t think the seams are the result of compression artifacts