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

Failed To Lock Image Buffer.

Ido Karilla

Ido Karilla

Well-known member
Joined
Oct 7, 2007
Messages
555
Reaction score
1
Points
18
Location
Tel Aviv, Israel
we have discovered a new problem with our material. checking our first day clips we have discovered in two of them blue screens with the message: " FAILED TO LOCK IMAGE BUFFER" it happened several times in those two clips varying from 2 frames to 16 frames.

Ido.
 
I've had this on the last 3 shoots and I'm talking with RED who are on the case.

Hopefully a fix will be available soon, very soon :-)
 
roryhinds said:
I've had this on the last 3 shoots and I'm talking with RED who are on the case.

Hopefully a fix will be available soon, very soon :-)
Click to expand...

i think it happens when transfering the footage from the drive/cf to your hdd...

maybe you use the same hardware that causes it not knowing it...

simple questions for both....
was your faulty footage originated
on cf.....
drive.....

i think both of you used 4k 2:1 23,98 fps redcode 28


which hardware or port did you use...?

did you moved the footage around?
internally/another raid?

keep me informed
 
We are shooting 4K 16:9 24 fps shutter 1/50 to a red drive.
I just copied the matirial to my internal raid on the mac, opened in redcine and saw the blue screen with the error messege on the discussed frames.
One intresting thing is that those clip directories on the red drive have several R3D files, most of them empty if you load them in Redcine.

Red team, any suggestions?
It is the first day of shooting of a feature film and it makes everyone on the production quite nervese.

Ido.
 
Since the product is still in development and bugs like this could crop up at the worst times, it would be helpful if there was some sort of error reporting in the LCD/EVF whenever frames aren't recorded. Sure you might lose a great shot but at least you'd know right away and could reshoot. I can't even imagine losing frames at random without knowing about it till later.
 
happens when shooting both 16:2 or 2:1
REDCODE 28 or 36
from 3 different cameras
2 different RED Drives
2 different Mac's
23.97fps, 24fps, 29.97fps

I don't see this as a isolated problem and think its a coding problem with REDCINE.

RED please, we need a fix now.
 
I've seen this on occassion and usually rebooting Redcine seemed to fix it. For me it was a redcine issue rather than anything wrong with the footage. It typically happened after outputting some footage.

Paul
 
Trash the files in Library/Redcine. This mostly solves REDCINE problems like that.
 
RED Alert doesn't work with 16:9 footage.

I've seen this on both 2:1 and 16:9
using build 13 and 15 and version of it.
 
Same problem here.
Build 15 v 2.2.5
Footage shot at 113fps, shutter 173 degrees - onto a card.
Our assumption was that the card was not handling the high frame rate. We haven't run into the problem when recording on a drive yet.
Frames showed green in the quicktime proxies - all versions, and showed blue with the error message in RedCine.
In Red Alert not visible at all...

Brie Walsh
Data Wrangler
 
Brie said:
Same problem here.
Build 15 v 2.2.5
Footage shot at 113fps, shutter 173 degrees - onto a card.
Our assumption was that the card was not handling the high frame rate. We haven't run into the problem when recording on a drive yet.
Frames showed green in the quicktime proxies - all versions, and showed blue with the error message in RedCine.
In Red Alert not visible at all...

Brie Walsh
Data Wrangler
Click to expand...

Weird, it's reacting exactly as if it were a dropped frame.
 
You must log in or register to reply here.
Back
Top