Welcome to our community

Be a part of something great, join today!

Log in
  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

Ever seen this?

Tell me if I'm being paranoid, but I really believe he's trying to make equipment malfunctioning to cover. Could his UPS be the cause of any of these problems?
 
The issue is probably because of overheat to the cardreader. I have found that it's safer not to use a firewire 800 card reader but instead use a USB2.0 reader together with high speed disks with ESATA on the output side.
That way, the read will cut of the speed so that the reader isn't overheated, hence reducing/eliminating the risk of bad files.

But always check the checksum or confirm that the folder size is exactly the same to the smallest byte. Together with that always view everything in RedCine...
NEVER view from the card directly, it will probably overheat before doing the transfer causing the errors even though the playback looked nice.

But I think that's something the DIT-guy should know... otherwise he isn't a DIT, just someone trying to make a buck thinking you don't need knowledge.
 
Cheap/Bad USB 2.0 card readers are a bigger cause of problems than firewire 800 readers in my experience.

I've taken CF cards out of circulation on set before because of read errors.

A laptop (even my i7 macbook pro) is not really the best tool for data management unless you are in some sort of deep remote location or something.

Another of my beliefs is that media should only be formatted on the camera side. AC's love to push the formatting over to the computer - and this to me, is a recipe for disaster.

If you have time to test a card that is giving errors, perhaps zero it out using disk utility, then format it on camera, then run a battery of tests.

Sounds like a very bad situation no matter how you slice it. Good Luck.
 
Christoffer Glans said:
or confirm that the folder size is exactly the same to the smallest byte
Click to expand...

This is not a good way of checking for anything other than a complete and utter copy failure. A few bits here and there flipped to different values are enough to corrupt your footage without changing the file size at all.
 
I had the same problem a week ago, a lot of footage was busted. Just got no idea what wus the reason i dont get that problem again (strange because i use the same cables, card readers and all).After that i just play all the files and watch them after downloading it with R3D data manager.Its the safest way.
 
You must log in or register to reply here.
Back
Top