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

Timelapse = CLIP FAULT (nothing recorded!)

Kyle Mallory

Kyle Mallory

Well-known member
Joined
Jan 18, 2007
Messages
620
Reaction score
0
Points
0
Age
54
Location
Salt Lake City
Website
www.ifastudios.com
I was out shooting some stock tonight, and for one shot, we setup to shoot a timelapse of the sunset. 1/48sec, 1 frame every 5 seconds. We let it roll for 45 minutes through sunset. Went to play it back, and immediately got a CLIP FAULT. Discouraged, I decided to wait until I got back to the computer.

Nothing in RedCine, and RedAlert won't load the clip. No errors or indications of an error, just nothing.

So I go into the file folder for the clip. The file is 64k, and no proxies. WTF?

So I decide to put the drive back on the camera and setup for timelapse again. I shoot 3 or 4 short clips. EVERY ONE = CLIP FAULT on playback. No error or message while recording. Every test clip recorded is 64kb in size.

What gives? Anyone else seen this? RED?
 
You had the timelapse trigger set to external/GPI.

When you enable the Timelapse checkbox in the Timelapse menu, before you move the cursor off the checkbox, take a look at the far right of the menu.

You want it to say "Internal", not external or whatever the other choice is (it's escaping me right now).

I got bit by this a couple times on a timelapse job couple weeks ago.
 
Make sure You are not in a "burst" mode. I made the same mistake on my first timelapse. On the monitor in the bottom right corner it should read something like (1 frame 3 sec). If it reads (burst) - go to the timelapse menu and while at the checkbox twist the cursor to select the appropriate option...
 
It was not in burst mode. I did have the trigger set to external. Sigh.

So this begs the question(s) for RED:

Why does the camera default to external? It seems Internal is the obvious *default* choice, since external requires something other than the camera to make it work.

Does the external trigger start/stop interval recording or does it simply expose a frame at each trigger? If the later, then perhaps disable/grey/something the interval setting, since this has no relevance for an external trigger. This would also provide some other visual indication of the mode (since once you move the cursor off the "Enable" Timelapse option, you can't see whether you are external or internally triggered (am I'm looking where the highlight is, not the other side of the screen). If the first (start/stop interval) then in the main view, some kind of visual indicated, after the record button has been pressed, that tells you the camera is still waiting for another trigger before recording begins.

I get that this is just user knowledge stuff, and pretty trivial, and I for one won't ever have to go through this again (lesson learned), but there are some simple UI changes that could make the user experience a little better.

For one, change the "CLIP_FAULT" to "EMPTY CLIP" or "NO CLIP DATA" or something, so I immediately know that there simply isn't data to play back, rather than a cryptic message that make me think something is corrupt or the camera is on the fritz.

Thanks guys.
 
one of the many, many, many UI tweaks to be made. Cameras are art, but menus are science.

-mike
 
idiot proofing

idiot proofing

I second the motion for graying out the interval setting when on trigger mode -- lesson learned here too the hard way

I figured out afterwards that a good way to confirm is to see if the timecode is advancing

:err:
 
We had something similar happen today on a Harley Davidson commercial shoot. Everything had been going great when, suddenly, the DP decided to hit the record button on the Origo that was plugged in.

Well, all of a sudden, the camera went into burst timelapse mode! And it had never been turned on! This was the first shoot that we had done since it came back from the RED upgrade.

It took a bit of time to figure out what was going on. . . very strange.

Stephen
 
Stephen, it's likely that the Origo was plugged into the second Aux port which defaults to interval recording if I'm not mistaken.

After each firmware change I go into that option and change both to RECORD (since I use the Birger mount as well which gives errors when plugged in the same way as your Origo).

HTH

Paul
 
Yes, I got a 64kb file the first two times I tried timelapse. I can't remember what setting I missed, but I was doing something wrong. It does work, try again, you're using the wrong mode possibly.
 
Timelapse menus

Timelapse menus

Whether Art or Science I don't know, however we have an interesting challenge with customers coming from disciplines with conflicting jargon. But we are always open to suggestions...

The default settings for GPI A is Record Start / Stop and for GPI B is One-Shot Record. So that Origio was probably plugged into the lower Aux 12V port.

In the Time Lapse menu, we could have chosen Interval as the default setting but instead its set to One-Shot. If you set it to Interval the camera will remember that across power cycles.

There is a Burst setting but that doesn't change whether you are recording based on an Interval vs One-Shot, its defining whether you are capturing a single frame v's multiple frames each time.

The GPI A and B settings can be re-programmed using the System / Setup / Preferences / GPIO

See Pages 8, 29 - 30, 53 and 68 of the Operations Guide
 
Thanks Stuart.
I can't seem to find the answer to the question of what the correct GPI settings are for having 1 Origo control the start stop record function of two Reds. Currently I have the Origo feeding the top port on Cam 1, and another cable going from the Bottom port of Cam 1 to the top port of Cam 2. This should work, right??? Can you enlighten us with some information regarding that?
Thanks!

Stuart English said:
Whether Art or Science I don't know, however we have an interesting challenge with customers coming from disciplines with conflicting jargon. But we are always open to suggestions...

The default settings for GPI A is Record Start / Stop and for GPI B is One-Shot Record. So that Origio was probably plugged into the lower Aux 12V port.

In the Time Lapse menu, we could have chosen Interval as the default setting but instead its set to One-Shot. If you set it to Interval the camera will remember that across power cycles.

There is a Burst setting but that doesn't change whether you are recording based on an Interval vs One-Shot, its defining whether you are capturing a single frame v's multiple frames each time.

The GPI A and B settings can be re-programmed using the System / Setup / Preferences / GPIO

See Pages 8, 29 - 30, 53 and 68 of the Operations Guide
Click to expand...
 
Dual Record

Dual Record

Eli Jarra said:
Thanks Stuart.
I can't seem to find the answer to the question of what the correct GPI settings are for having 1 Origo control the start stop record function of two Reds. Currently I have the Origo feeding the top port on Cam 1, and another cable going from the Bottom port of Cam 1 to the top port of Cam 2. This should work, right??? Can you enlighten us with some information regarding that?
Thanks!
Click to expand...

Nope .. that is not a supported cable configuration...

You will need to run two Origios - one to each camera....
 
I had same problem. I solved is by just recording one frame on the interval, and shortening the exposure time.
 
You must log in or register to reply here.
Back
Top