Maybe you should dig more into cinematography. If this is the case perhaps BM could come up with a one touch fix in resolve. Kyle Gordon wrote:Mark Im not an expert, but I think I understand. A 7 bit recording has half as many steps of resolution as a 8 bit recording etc.Īnyway I may be totally off base here, but if it's a tradeoff for image quality, either please dont implement it, or make it a user define-able choice please! Losing one stop or bit HALVES the total number of quanta for expressing the variation in the image. Im not an expert, but i think each "stop" is like a bit in digital information. ![]() I don't really like any skin tones Im seeing with the 4k camera the way i like them on the BMCC 2.5k - and yet there is only supposed to be a stop of difference. I love the way this camera renders an image. I think that to put a hard cap on what comes out of the sensor, so that no channels clip out of proportion to other ones, youd have to lose dynamic range, making the response of the sensor have less bandwidth. I think it has to do with the debayer and the fact that there are 2 green photo sites for each red and blue pair. I think the purplish color of the error isnt random. Mark Im not an expert, but I think I understand. Personally I think they should stop trying to find a perfect global solution and just have the fixes as user switchable options and let us decide if and when we want to use them. Since they have yet to find a reliable way to fix this issue with any false positives they have chose not to implement any of the fixes they have so far. ![]() BM has tried to fix this issue via software but the issue is that it is not perfect and can/does generate false positives, it will fix areas of the image that shouldn't be fixed on occasion. The problem is there is no way to know for sure if these dark pixels are overloaded sensels or just dark sensels. The BMCC doesn't have this feature, I don't know but suspect that the sensor just outputs a 0 or very low value at a sensel when it is overloaded. Don't know any specifics but something to this effect. The pocket had a sensor level fix, meaning there was a feature of the sensor that could detect the black hole and either correct for it automatically or possibly output the data in a way that made it easy to isolate - recording -1 as a brightness value when the sensor is overloaded as a possible example. That's one update I would'nt be chancing till some brave few do it first to test the waters with the colour. It was definitely a while ago.they should say something about it now methinks. ![]() I fully endorse a fix.but if its gonna mess with the image.then I say don't "fix" it. Yeh I fully agree with you that it may be hellish for some people as we all shoot different things. The black sun issue has the potential to be a nightmare for everyone using the camera not Just me so it is in all our interests. That was a while ago now and would like to see some progress on this. Well The last thing I want is for image quality to be affected If I remember correctly it wasn't that image quality WOULD be affected but they had to be careful in making the fix. You'd better learn how to deal with it in post. It hardly ever is a problem for me personally. The it is possible to fix it on the BMCC however at the possible cost of colour science being affected negatively. The pocket has newer tech making it easier to fix. Darren Scott wrote:BMD already spoke about this issue.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |