camera reporting.

[Zakaree Sandberg]

I generally post stuff like this in OFF TOPIC..

but i feel like this may be a useful tool for a lot of us.

I currently have my own "camera log" that I keep.
Every Job I go on, I Log the serial number, where the camera came from, and any issues or reports that i may have with the camera.
That way, Next time im on a prep/Job and, i get a known problematic camera.. I can take precaution.

It might be a good idea to start a Public log so that everyone can be informed to certain problems cameras might have.

Lets say i get 2274.. I can check the log and oh look.. Mike B. signed in with that camera and reported LONG BOOT times.. or AUDIO FAILURE.. whatever...
Now i know too reject that camera or test for those issues before taking the camera on the field...

What do you guys think?

[Ed Watkins]

Nice idea, but somewhat open to abuse, like ebay comments used to be.

[sander kamp]

I think it would be difficult to keep it fair to the owners of the camera. What if a camera had some problems but it got fixed? And who is the administrator of the log? If anybody can change it I would immediately undo any negative feedback on my camera.

[Greg M]

then there's always operator error...from my experience 75% of the "camera problems" are actually operator errors.

[Dave Weber]

then there's always operator error...from my experience 75% of the "camera problems" are actually operator errors.

I hear that. There is a local camera here in the OC that keeps having "trouble" and the stories scare clients off. I'm about 95% sure it's OE.

[Casey Green]

Yeah, nice idea, but not practical.

[mikeburton]

Lets say i get 2274.. I can check the log and oh look.. Mike B. signed in with that camera and reported LONG BOOT times.. or AUDIO FAILURE.. whatever...
Now i know too reject that camera or test for those issues before taking the camera on the field...

What do you guys think?

Hey, why me? :) BTW - mine is 2322 and has been kickin butt ever since it landed. I guess this is a prime example of why a community log would get flooded with people protecting their cameras rental status. Even though I know Zak was just giving an example I felt obliged to let everyone know that my cam is working great with only the normal, noted firmware issues/bugs.
It would be a good thought but I think the thread would be hounded by defendants rather than useful info. Also, if that camera once had an issue that was repaired and has not had issue since the repair it would not be accurate any longer.

[rod bradley]

I agree, nice idea but too open to potential inaccuracies, falling out of date, et cetera -- and of course we need to check out everything in advance anyway. And still, that can't totally prevent the random aberration.

[Vigen Vartanov]

Ok , but it is happens once on set . Camera can work and then something can happens on set .
You are not protected from it. If camera is with problem , better to send it to repair .

[Zakaree Sandberg]

Mike.. didnt mean to say that YOUR camera had a problem.. just A camera you may have worked on..

I get its not practical in an open forum like this.. but In my tight network I would love to have an on going log.
I understand the fairness thing. I would hate for my camera to have a problem and then be Pinned down on the shit list and never get a rental again..
The idea was more or less (this has happened in the past.. so test the crap out of this camera to make sure that when im shooting in timbucktoo, the camera wont error on me) Maybe only REAL dit's can submit to this log:) PRE-APPROVED DIT's. NO OP ERROR allowed;-)