- User Since
- Oct 31 2018, 3:41 AM (127 w, 4 d)
Mar 2 2021
Ah yes makes sense, cheers.
Mar 1 2021
Surely values of 0,0,0 should just produce black though?
I work with large scale LED displays that only deal with an 8bit source, an rgb value of 1 in any channel is clearly visible. I've been flooring the black level in editing software and playing back as 8bit h264/h265. When using doing so in other software, a zero value will effectively mean off. However if I'm not careful a video will slip through that hasn't been floored, since its not visible and hard to detect, anything produced in Blender will result in flickering. I could output 16bit png's in all cases ( I do 50% of cases usually depending on efficiency, some diplays have extreme specs) but was thinking that there must something up on Blenders end. Here's a comparison of 8bit PNG's output and exposed from Cinema 4D and Blender.
Dec 8 2020
A heads up, drawing images in POST_VIEW doesn't work at all in the 2.92 Image Editor, could this be related? I've tried various z positons without success in this case though it works fine in 2.91.
Jul 7 2020
Hi, I last saw this issue with the 2.83 alpha but haven't seen white frames using the 2.83 stable release +
May 8 2020
Apr 28 2020
Hi, here's a couples of systems that produced this issue, from one of these machines I found the issue didn't occur in versions above 2.82. but haven't tested on the others yet. thanks.
Apr 24 2020
Apr 23 2020
Apr 22 2020
Mar 7 2020
Hi, I'm the author of an add-on called Shot Manager (free and paid) which deals specifically with complex render path setups. However I've had a number of customers who have complained about the extra file outputs which results in unnecessary memory consumption and awkward file management. Just hoping this issues is a priority. Thanks.