Mark L. Pederson
REDuser Sponsor
I'm posting this here because I can't code and I know a few folks on this forum can. If I could code .... I'd create the following:
R3D Integrity Verification Utility
Corruptions in R3D media are extremely rare. In our experience, (multiple RED features shooting per day), I peg the likely hood LESS than getting scratches on your film neg from a magazine or a "flashed can". That being said, it can happen - card reader goes bad, cable or connection goes bad, etc. - and if and when it does - it's critical to detect it as soon as possible.
When you shoot film, you can not "verify" the film negative on set while you are shooting. You take the negative to the lab. The next day (typically) you get a LAB REPORT - or in many cases, depending on your relationship with the lab - you would get a phone call if they say any "issues" (scratches, flashed cab, etc.).
I'd like a utility that I can run in the background on a folder of R3Ds on the set that uses the SDK combined with a SCENE DETECTION ALGORITHM to flag potential corruptions.
I have seen Red Rushes fail to render a clip with corruptions - and RedAlert can display a decode error message with some bad R3Ds - but we have also seen some R3Ds with corruptions go through the Red tools without crashing them and have white or black frames -
This is why I would add a scene detection algorithm - which would flag a "glitch" or "bad frame".
Here's a LINK to an example of how to code scene detection
I suspect that one could do a MUCH SMALLER SCALE debayer to optimize for speed and still flag the any potential errors.
Anyway, I'd love a utility like this and I have a selection of recode with different types of corruptions caused by various things collected over a year and half - so I'm pretty sure I could test such an app to know if it works.
Anyone game ...
R3D Integrity Verification Utility
Corruptions in R3D media are extremely rare. In our experience, (multiple RED features shooting per day), I peg the likely hood LESS than getting scratches on your film neg from a magazine or a "flashed can". That being said, it can happen - card reader goes bad, cable or connection goes bad, etc. - and if and when it does - it's critical to detect it as soon as possible.
When you shoot film, you can not "verify" the film negative on set while you are shooting. You take the negative to the lab. The next day (typically) you get a LAB REPORT - or in many cases, depending on your relationship with the lab - you would get a phone call if they say any "issues" (scratches, flashed cab, etc.).
I'd like a utility that I can run in the background on a folder of R3Ds on the set that uses the SDK combined with a SCENE DETECTION ALGORITHM to flag potential corruptions.
I have seen Red Rushes fail to render a clip with corruptions - and RedAlert can display a decode error message with some bad R3Ds - but we have also seen some R3Ds with corruptions go through the Red tools without crashing them and have white or black frames -
This is why I would add a scene detection algorithm - which would flag a "glitch" or "bad frame".
Here's a LINK to an example of how to code scene detection
I suspect that one could do a MUCH SMALLER SCALE debayer to optimize for speed and still flag the any potential errors.
Anyway, I'd love a utility like this and I have a selection of recode with different types of corruptions caused by various things collected over a year and half - so I'm pretty sure I could test such an app to know if it works.
Anyone game ...
