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

file didn't record?!?

Dustin Cross

Well-known member
Joined
Mar 6, 2007
Messages
1,240
Reaction score
0
Points
0
Location
Austin, Texas
Website
www.sandust.com
On a shoot last night we had a take that didn't get recorded. We have a 64K R3D file in the folder and nothing else. I think the record button was double bumped, but was not on set, so I am not sure. Also if it was double bumped I would think there would be a false roll when the AC tried to stop the record and there is not.

All takes before and after are good.

It was hot and we did get a heat warning on camera at this location. Between takes one the camera locked up. We put ice pack on camera.

Could this be the camera getting hot and locking up?

AC and operator did not notice anything when they were recording.

Has anyone else experienced having an incomplete R3D file that will not open.


Mahalo,
Dusty
 
just in case your listening brent, thats what i was trying to desribe to you the other day.
we are re-installing build and ill let you know what happens.



all the best
Sergio
 
The AC says the missing footage happened just before the camera locked up. He said everything seemed to be working normal before the lockup, but we were moving fast and he might have missed it.

Mahalo,
Dusty
 
The AC says the missing footage happened just before the camera locked up. He said everything seemed to be working normal before the lockup, but we were moving fast and he might have missed it.

Mahalo,
Dusty

I would recommend trying redundead just in case the missing footage is still there.
 
Okay,

I had this happen again today. Another file that didn't record anything except a 64k R3D that is unreadable. I tried to recover with REDundead, but no luck.

It was very hot, but we had ice packs on the camera and did not get any heat warnings or shut downs.

Any idea what is causing this?


Thanks,
Dusty
 
Okay,

I had this happen again today. Another file that didn't record anything except a 64k R3D that is unreadable. I tried to recover with REDundead, but no luck.

It was very hot, but we had ice packs on the camera and did not get any heat warnings or shut downs.

Any idea what is causing this?


Thanks,
Dusty

Are you using a remote trigger (preston, gpi, etc)?
 
We are pushing the red button on the back of the camera.

We are using two 320GB red drives, but I did not keep track if the problems happened both on the same drive. We typically use drive 1 the first half of the day and drive 2 the second have. First error happened the second half of the day and the second error happened the first half of the day , but AC could have grabbed the wrong drive.

The first error happened at 77GB and the second error happened at 81GB. Those are fairly close so I am guessing both errors happened on Drive 1 unless you think that is too far apart. Is there anything I can do to the drive. Zero out on OSX or something to find bad spots?

The drives have been getting VERY HOT but are still working.

Any input is gladly accepted.

I sent Sean this info in a text from my phone, because I am on set and don't have good interenet.


Thanks,
Dusty
 
Editor just called me with another weird issue. One of our clips from last night has a single frame from a different take. The first frame is from a different shot than the rest of the clip. Everything else about the clip is fine, but it seems a little strange, that the first frame is from something else?

Just thought I would share.


Mahalo,
Dusty
 
Hi Dustin, Deanan. i am taking on the issue that sergio arguello reports on the second message.

The issue at that time, (i was on set as DIT) and today happen again ends with a 64kb r3d, but we can take this at the moment because the camera never close the clip. Other times when this happen, i mean we record the take and when we want to stop the camera stay in post (red) for ever. We need to turn off the camera to continue. Then when we look at the clip we found this empty clip. The issue happen different days with different kind of media also. CF and RED DRIVE.

we are runing BUILD17
tomorrow i will try the redundead tool.

regards...
 
Hi Dustin, Deanan. i am taking on the issue that sergio arguello reports on the second message.

The issue at that time, (i was on set as DIT) and today happen again ends with a 64kb r3d, but we can take this at the moment because the camera never close the clip. Other times when this happen, i mean we record the take and when we want to stop the camera stay in post (red) for ever. We need to turn off the camera to continue. Then when we look at the clip we found this empty clip. The issue happen different days with different kind of media also. CF and RED DRIVE.

we are runing BUILD17
tomorrow i will try the redundead tool.

regards...

Hi Sebastian,

If you had to turn off the camera because it was stuck in post then redunded could likely recover the last file. I'd recommend turning off generation of the quicktime wrappers in the camera if this is happening to you.
 
This has happened to me and it usually is when i upgrade from one build to another, a drive or card formated with an old build sometimes gets confused and post takes long. a reformat of card has always helped me.

Rodney James.
 
Having the same problems, tiny R3d files, no proxies and no issues noticed when recording...?

did any one have any success recovering the files with redundead?

I had the problem a while ago on the first take, so no harm done... but this time it was the money shot? help?
 
Hi Sebastian,

If you had to turn off the camera because it was stuck in post then redunded could likely recover the last file. I'd recommend turning off generation of the quicktime wrappers in the camera if this is happening to you.

hi deanan... what recommendation for recover that file? i will try redundead but i dont have a disk with the file here.... if your are talking another kind of recovery please advice me regarding this before this happen again...

i will be prepare to run a redundead operation but if you know that i will need another tool please tell me...

thank you in advance
 
Back
Top