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

Every second frame gets blurred.

Per von Koch

Per von Koch

Well-known member
Joined
Aug 9, 2010
Messages
296
Reaction score
0
Points
0
Location
Sweden
Per,

I don't have an answer for you but you are not alone. I have had this happen to me only shooting 2k at highspeed over 100fps. Always outside and often with grass or trees in the shot. I thinks its a codec thing but have never confirmed. It stops always after a restart but will usually come back after a while of shooting again. My guess is its not a camera hardware thing but software or codec choke.

Good luck

Taylor
 
There was a camera firmware build where this occurred, but was fixed in the next one. Are you both up to date on your camera firmware as released on Red.com?
 
They announced that the new firmware fixed the problem, and it didn't. I had a shoot where this happened. Red said they were aware of the problem. Told me to reshoot. Way to go Red !

Nick
 
Nick Gardner said:
Red said they were aware of the problem. Told me to reshoot. Way to go Red !

Nick
Click to expand...
Damn. So they told you to go shoot again even though the problem is still there and you most likely would get unusable material again?
 
They announced that the new firmware fixed the problem, and it didn't. I had a shoot where this happened. Red said they were aware of the problem. Told me to reshoot. Way to go Red !

Nick
Click to expand...

So I guess the best way to avoid it is to never go above 100 fps? Cause you can't really see the artifacts on the LCD monitor. Especially when your out in the field...
 
Per von Koch said:
So I guess the best way to avoid it is to never go above 100 fps? Cause you can't really see the artifacts on the LCD monitor. Especially when your out in the field...
Click to expand...
The question then is why is 120fps enabled?
 
Supposedly builds since v30.5.0 "Resolved image capture error with 2K resolution recording at 117 – 120 fps".

Which build are Per, Taylor and Nick on?

I've never gone above 100fps for a job, so not directly encountered the problem.
 
Yeah the "Resolved image capture error with 2K resolution recording at 117 – 120 fps" is wrong. Red knows it's wrong. They claim they fixed it in the next beta build. Red told me that I should change my settings and reshoot. The problem only happens at 2k over 100fps. My client was not happy, and had to spend a bunch of money to fix the fucked up shot.

I still can't believe they haven't said, "oh hey! warning! don't shoot above 100fps or your footage is useless." Pretty negligent in my opinion. Aside from the large amount of money blown on a shot that can't be used, losing a client and looking like a jack ass can cost you many tens of thousands of dollars. I get paid to make sure everything goes smoothly and protect the investment of the client by making pretty pictures. I hope that enough people see this thread that the problem can become common knowledge. Red certainly isn't doing anything to make the information available, quite the opposite they say IT'S FIXED in the build notes.

Nick
 
Nick, understand the frustration. Let me look into this for you. Can you give me the exact conditions you were shooting in, including description of the shot(s), lens, temperature, etc? Also, was this M or M-X? How were the shots processed? REDcine-X? Which build?

I will do some tests to see if I can replicate it.
 
@Steve

I talked to Red about it. It not a mystery. Over 100fps is fucked up. They said it happens under certain circumstances, I'm guessing fine detail as that was when I saw it, and when others have seen it.

Twas - MX sensor 2k 16x9 100fps temp between 25-30. ASA 800 shot around a t-16 to hold the exposure on the fire effects. Shot was a commercial for Binelli shot guns. Here is a link to the shot -

http://www.benelliusa.com/supervinci/

The shot is the one with the pyro and the girl. The shotgun had to be replaced because it just went to complete shit every other frame (super pixelated). It seemed to happen when the little sparkly fire effects went off.

Thanks for the help,

Nick
 
Nick Gardner said:
@Steve

I talked to Red about it. It not a mystery. Over 100fps is fucked up. They said it happens under certain circumstances, I'm guessing fine detail as that was when I saw it, and when others have seen it.

Twas - MX sensor 2k 16x9 100fps temp between 25-30. ASA 800 shot around a t-16 to hold the exposure on the fire effects. Shot was a commercial for Binelli shot guns. Here is a link to the shot -

http://www.benelliusa.com/supervinci/

The shot is the one with the pyro and the girl. The shotgun had to be replaced because it just went to complete shit every other frame (super pixelated). It seemed to happen when the little sparkly fire effects went off.

Thanks for the help,

Nick
Click to expand...

RC28 or RC36? If you were using Drive, you'd be able to get 100fps at either compression. Cards would be limited to RC28.
 
High speed 2K

High speed 2K

Nick Gardner said:
Yeah the "Resolved image capture error with 2K resolution recording at 117 – 120 fps" is wrong. Red knows it's wrong. They claim they fixed it in the next beta build. Red told me that I should change my settings and reshoot. The problem only happens at 2k over 100fps. My client was not happy, and had to spend a bunch of money to fix the fucked up shot.

I still can't believe they haven't said, "oh hey! warning! don't shoot above 100fps or your footage is useless." Pretty negligent in my opinion. Aside from the large amount of money blown on a shot that can't be used, losing a client and looking like a jack ass can cost you many tens of thousands of dollars. I get paid to make sure everything goes smoothly and protect the investment of the client by making pretty pictures. I hope that enough people see this thread that the problem can become common knowledge. Red certainly isn't doing anything to make the information available, quite the opposite they say IT'S FIXED in the build notes.

Nick
Click to expand...

Can you send us a LOG file from your camera please?

You can send it to stuart@red.com
 
Stuart, I am assuming that I would need the file related to the footage. This shoot was right before Christmas and the footage is long gone off of my drives.

@steve yes redcode 28.

I am in india on a shoot at the moment (red is performing great as expected ;-)).

Actually, I have my drives with me - And I think that footage may still be on one - I'll check.

Nick
 
Which build are Per, Taylor and Nick on?
Click to expand...

I'm on build 30.6.12 (aka the latest).


Can you send us a LOG file from your camera please?
Click to expand...

Stuart, I'm sending you my log file as well. There was that clip at 120 fps in the first thread.
 
Nick Gardner said:
Stuart, I am assuming that I would need the file related to the footage. This shoot was right before Christmas and the footage is long gone off of my drives.

@steve yes redcode 28.

I am in india on a shoot at the moment (red is performing great as expected ;-)).

Actually, I have my drives with me - And I think that footage may still be on one - I'll check.

Nick
Click to expand...
Let me shoot at both RC 28 and RC36.
 
Stuart,

So the original footage is long gone from my drive, and I have shot a bunch of stuff since then. I have never had to get a LOG file before. Is there anything useful for you guys that I can do?

Nick

Edit - I just looked up the LOG file thing. I'll do that tomorrow and send it off. Thanks.
 
How prevalent is this error? I have an upcoming job that will be shooting strictly to CF cards and will be doing a lot of overcranking. Would do 100fps @ RC36 but if I need 120fps I'd be dropping to RC28. Does this error happen at both 36 and 28 data rate?
 
You must log in or register to reply here.
Back
Top