Welcome to our community

Be a part of something great, join today!

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

Timelapse Woes

Eli Jarra

Eli Jarra

Well-known member
Joined
Dec 30, 2006
Messages
317
Reaction score
0
Points
16
Location
Los Angeles
Website
www.thinkpictures.com
I love the imbedded timelapse/intervolometer feature in my Red. I've only shot a handful of TL since getting the cameras. I find the feature very flexible and easy to use and for the most part reliable...Now I'm starting to notice a pattern of missed frames that is just bummin' me out when shooting. With timelapse you get one shot at getting it right, if you miss it, or there's a technical glitch then that is a lost opportunity probably never to happen again. Once in a while you can chalk it up to Murphy but after two or three times, there is definitely something wrong and needs addressing.


Over the weekend, I had the camera blasting away on a storm that came through So-Cal, after a satisfying period of time, I stopped recording and noticed the 'post' time taking longer than usual. This is the third time its happened and the last two experiences ultimately shortened the result clip by a considerable amount of frames. The first time was on set, shot for 45 seconds, retrieved only two from the r3d file. The second time was a time-lapse that was going for about two hours, again only 2 seconds returned. Same with this third time. All have the consistent extended post time followed by a "playback Error Internal Fault" message when trying to review the clip on the camera. In fact, when this error occurs, you are not able to view ANY clips on the drive through the camera. This is problematic since you must have an extra drive ready to go at a moment’s notice. Also, note camera would not boot up with said drive attached, boots only on drive being dis-connected. I’ve done some searching for the ‘playback error: internal fault but haven’t come across anything substantial. I remember reading a post by Stuart a while back asking to disable QT proxies and see if that helps. My next email is to support but I wanted to run this by the forum and see if any of you are having similar issues with the Red Raid. Oh and a time-lapse feature request please: Have the number of frames executed/recorded so far in the display to help keep track of how many frames you should expect.

Some questions... Are the frames there but just not accounted for or readable by the system? Is there anyway to retrieve them? How do I circumvent this from happening again.

Thanks for your time and insight.

System specs:
Cam 392
Beta 14, (first and second instance happened running beta 13)
Red Raid (multiple raid units)
A/C power
QT proxies OFF (third instance only)
Timelapse mode, interval 5 seconds,
Shutter 1/48
 
I had something kind of similar happen to me when I was trying to do some timelapse. I also got the three frame loop on my LCD that would only go away after I re-booted the camera. I haven't been running the TL function on my Red because it doesn't work no matter what settings I have it on. I was told at Red Day that it was still being worked on. So for now I'm just going to stick to doing either 1fps timelapse or using my 40D to get the shots.
 
Thats a real bummer as I do a lot of time lapse work and had thought that my camera would help out with some new and exciting possibilities.
I thought I read some where that the problem with the time lapse was that it worked on the CF card but still had problems with the RED drives. I don't know but maybe you could check to see if that helps.
 
Russ Fill said:
Thats a real bummer as I do a lot of time lapse work and had thought that my camera would help out with some new and exciting possibilities.
I thought I read some where that the problem with the time lapse was that it worked on the CF card but still had problems with the RED drives. I don't know but maybe you could check to see if that helps.
Click to expand...

I've had good luck w/CF, I'll be shooting like crazy this weekend...(really good weather) I'll post the results plus any suggestions given by support.
 
Maybe a dumb Q&A drew but are you using Red CF cards? And maybe formating them using disc utility first. Sometimes I need to do that with my stills camera cards to get rid of a corruption problem.

Powrslave: Good to hear you can at least get going. Let us all know what happens as I said a lot of my work depends on TL. Also could you let me know how slow you can get the shutter? And the intervals? I would love to hear a 2 sec shutter with a 4 or 5 sec intv.
 
Russ Fill said:
Maybe a dumb Q&A drew but are you using Red CF cards? And maybe formating them using disc utility first. Sometimes I need to do that with my stills camera cards to get rid of a corruption problem.

Powrslave: Good to hear you can at least get going. Let us all know what happens as I said a lot of my work depends on TL. Also could you let me know how slow you can get the shutter? And the intervals? I would love to hear a 2 sec shutter with a 4 or 5 sec intv.
Click to expand...

4 - 5 seconds intv. no problem.
Intervals are 1,2,3,4,5,8,16,32,64,128,256,512,1024 seconds. With beta 13 you could expose up to 1 second. No longer than that unfortunately but we've all expressed interest to Stuart & crew that we'd LOVE to see longer exposure rates for night photography. Also with Beta 14 it seems 1/16 is the longest exposure you can choose. Don't know why that changed, hopefully we'll be able to go longer in 15.
 
I know that the longer you expose the more noise/missing pixels you will start to see when you really heat up the sensor. Maybe that is why they are dragging their heals to just let us have 20 to 30 sec exposure times.
 
Russ Fill said:
I know that the longer you expose the more noise/missing pixels you will start to see when you really heat up the sensor. Maybe that is why they are dragging their heals to just let us have 20 to 30 sec exposure times.
Click to expand...

Actually, based upon typical noise characteristics, longer exposures help to minimize noise. If by missing pixels, you mean dead/hot/dim pixels, then they should be eliminated by calibration process.
 
Joofa, unfortunately Red isn't currently working like that. I shot some timelapse and Varispeed (at 2fps) with the shutter set to 'relative' (ie approx 1/2 sec exposure) and we had a HUGE amount of hot pixels. We then did a 'sensor calibration' on the spot it did not effect the results.
 
timelaps playback problems

timelaps playback problems

I have problem when I trying to playback timelaps, it says: "playback Error Internal Fault" I have build 16. Do anyone know something about it?
// Johan
 
powrslave said:
I love the imbedded timelapse/intervolometer feature in my Red. I've only shot a handful of TL since getting the cameras. I find the feature very flexible and easy to use and for the most part reliable...Now I'm starting to notice a pattern of missed frames that is just bummin' me out when shooting. With timelapse you get one shot at getting it right, if you miss it, or there's a technical glitch then that is a lost opportunity probably never to happen again. Once in a while you can chalk it up to Murphy but after two or three times, there is definitely something wrong and needs addressing.


Over the weekend, I had the camera blasting away on a storm that came through So-Cal, after a satisfying period of time, I stopped recording and noticed the 'post' time taking longer than usual. This is the third time its happened and the last two experiences ultimately shortened the result clip by a considerable amount of frames. The first time was on set, shot for 45 seconds, retrieved only two from the r3d file. The second time was a time-lapse that was going for about two hours, again only 2 seconds returned. Same with this third time. All have the consistent extended post time followed by a "playback Error Internal Fault" message when trying to review the clip on the camera. In fact, when this error occurs, you are not able to view ANY clips on the drive through the camera. This is problematic since you must have an extra drive ready to go at a moment’s notice. Also, note camera would not boot up with said drive attached, boots only on drive being dis-connected. I’ve done some searching for the ‘playback error: internal fault but haven’t come across anything substantial. I remember reading a post by Stuart a while back asking to disable QT proxies and see if that helps. My next email is to support but I wanted to run this by the forum and see if any of you are having similar issues with the Red Raid. Oh and a time-lapse feature request please: Have the number of frames executed/recorded so far in the display to help keep track of how many frames you should expect.

Some questions... Are the frames there but just not accounted for or readable by the system? Is there anyway to retrieve them? How do I circumvent this from happening again.

Thanks for your time and insight.

System specs:
Cam 392
Beta 14, (first and second instance happened running beta 13)
Red Raid (multiple raid units)
A/C power
QT proxies OFF (third instance only)
Timelapse mode, interval 5 seconds,
Shutter 1/48
Click to expand...


powrslave,

Did you fix your problem?
 
Equilibrio said:
powrslave,

Did you fix your problem?
Click to expand...

Much more stable in B16 fortunately. Haven't had an issue quite a while. I'm really gonna be putting it to the test in the next couple of weeks. I'll chime in on any issues.
A couple of things I'd still like to see,
Total frames recorded as the camera is ticking off frames. Would help to know where you're at in terms of duration.
Also, a full second of shutter exposure (which I'm sure is coming back at some point)

thanks for your inquiry!
 
You must log in or register to reply here.
Back
Top