Search the Community
Showing results for tags 'netrender'.
Found 1 result
-
Before I begin trying to find the source of this bug I'd like some opinions as to what might be happening. Attached are two "versions" of four sequential TIF files (545 through 548) from an on-going Netrender job. If there is a "b" (for bad) in the filename it is the first frame rendered by any one of the my four cores. If there is a "g" (for good) it was either not a Netrender first frame or it could be any frame rendered within A:M itself. I've numbered the files so you can sequentially show them bad, good, bad, etc. When I cycle through them on my monitor, the bad ones seem a bit darker and noisier but nothing that says "obviously this is what's wrong"; they're just poorer quality. All subsequent Netrender images are totally fine. The work-around is trivial but wastes some render time. Debug will take stripping down the choreography until this stops happening but I'm open to suggestions as what to change/remove first. 01_b0545.tif 02_g0545.tif 03_b0546.tif 04_g0546.tif 05_b0547.tif 06_g0547.tif 07_b0548.tif 08_g0548.tif
