Welcome to our community

Be a part of something great, join today!

  • 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 :)

Strange color in single frames

Rob Kaczmark

New member
Joined
Jun 15, 2013
Messages
3
Reaction score
0
Points
0
Has anyone come across this before. I didn't notice it on set, but when I got in post this appeared on a single frame. Luckily
framegrab1.jpg
it wan't an important one.
 
Hey Rob,
I've seen that issue a couple times before but have always been able to trace it back to faulty backup disks and/or copying process (not using a program that does sum cross checks for example). In my cases the material straight off the SSD was always fine and recopying the file should make the corrupt frame disappear. I've always removed the harddisk where it cropped up from circulation just to be sure.

Christian
 
Thanks Christian and Ryan. So unfortunately the red mags were already formatted, because we had another shoot the next day that we need the cards for, so I'm unable to check if the footage was okay on the SSD. The footage did get moved a few times from where it originally got dumped so that might have been the cause, but I have done that before and never had this come up. Do you guys just drag and drop the footage from the SSD to the editing HD or do you use extra software to cross check things? Thanks again for both of your help with this.
 
Hey Rob,

I do a copy to two hard drives (one working, the other for redundancy) then check a random sample of footage. Some people use software to check the integrity of the footage, something I may do in the future but things are too crazy right now to update my work flow.

I noticed that on this past Wednesday's shoot I had a few clips that seemed to be missing a bunch of frames so I'll be submitting a ticket to RED for that. When you've had my luck, you start scrutinizing everything. It just sucks when the client is there watching over your shoulder and asking why the footage is f*cked.
 
Hey Rob,
I've seen that issue a couple times before but have always been able to trace it back to faulty backup disks and/or copying process (not using a program that does sum cross checks for example). In my cases the material straight off the SSD was always fine and recopying the file should make the corrupt frame disappear. I've always removed the harddisk where it cropped up from circulation just to be sure.

Christian

I too have seen this a few times and it was always a data copy error for me.
 
I had a shoot a couple of weeks ago where we backed up onto four hard drives. Two were brand new and the others I had used before on other shoots. As time was limited I only drag and dropped the material and only had the chance to check the new hard disks, never a good idea. When I finally got a chance to check the other disks I had the same issues you had. Recopying the files from the new disks worked, but for some reason it took longer than it should have.

I usually use a program like r3d data manager, carbon copy cloner or arRsync to copy the files as they automatically check for any discrepancies. Never had a problem when using them.
 
I've also heard of people having hits like that in their footage, and if they were using a Rocket or Rocket-X card, they end up doing a render with out that and just go straight GPU and it gets through the transcode without the error.
 
On average, a modern magnetic or SSD drive will mis-write a bit every few hundred terabytes. If your process involves copying multiple times, you're almost guaranteed to have an error once or twice a year, and who knows how often that ends up with a visible glitch. Using a copy verification will eliminate this, if you have extra time.
If you're on Windows, Microsoft RichCopy is free and a lot more powerful than the Explorer window. I use it for all my 100GB+ copies.
 
I had about 6-7 of these in one project when I used Firewire + Macbook Pro. Never had it since but always copy the mag twice, especially from my anecdotal experience on OSX + Firewire.
 
I had a shoot a couple of weeks ago where we backed up onto four hard drives. Two were brand new and the others I had used before on other shoots. As time was limited I only drag and dropped the material and only had the chance to check the new hard disks, never a good idea. When I finally got a chance to check the other disks I had the same issues you had. Recopying the files from the new disks worked, but for some reason it took longer than it should have.

I usually use a program like r3d data manager, carbon copy cloner or arRsync to copy the files as they automatically check for any discrepancies. Never had a problem when using them.

If a copy takes much longer than expected then run a thorough format and diagnostic on the old disks before reusing them. Disks which are about to fail will often have trouble writing/reading and require multiple tries by the OS which takes more time, hence the slow performance.
 
Back
Top