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

Best 4k 16:9 build for important job in a few hours?

W

Warren Kommers

Well-known member
Joined
Apr 21, 2007
Messages
475
Reaction score
0
Points
0
Website
www.fofp.com
Hello Friends,

I'm heading out shortly on a higher profile shoot and am returning to 4k 16:9 for the first time since it was crashing on me with Beta 15 builds. The shoot will be for theatrical and VFX so I can't crop into 2:1 for 16:9. There will also be lots of detail and motion.

Is release 15 4k 16:9 stable? I haven't had time to test it since it crashed in beta hard. It seemed fairly solid on earlier builds. Does anyone recommend a previous build to carry as back up for 4k 16:9 that was practically bullet proof?

Thoughts? I'm leaving in an hour.

Thanks!

-Warren
 
You can shoot 4K 16:9, but you can only open it for export in REDCINE, it's not supported by the proxies, Red Alert or Final Cut. Seems that build 15 v2.2.5 is the most stable release overall. But I can't comment on how stable 16:9 is in 4K on the camera -- haven't shot it due to the post support issues.

Can you shoot 3K? Or shoot 4K 2:1 and crop to 16:9 in post?
 
That also means that audio wont be enabled in the camera.
 
On high contrast / lot of details shot you will get "codec error" in 4K 16:9 mode with ver15.
Search forum for "codec error".

Priit
 
I've successfully shot 4K 16x9, including audio, with no camera problems.

Process picture with RedCine to 720p or 1080p.

Import all sound take proxy files to FCS.

DO NOT try to play the proxies or even scrub them!!! Do not even try to view the picture!

Protect the picture track and load all the proxy files to the sequence.

Now, protect the sound track and unlock the picture track; you may now add the associated picture files from RedCine.

All syncs perfectly with no problems.

Except for the down-conversions to SD which I've described at length.

Good shooting and best regards,

Leo
 
We've had troubles- esp the dreaded codec error in build 15 with 16:9. I'd use it in a controlled studio environment. but for an important critical gig where it's my first time out with it, I'd stick with 2:1 which is much more solid at this point.

Noah
 
My commercial shoots have been both studio and location, INT and EXT, with zero camera problems or RedCine failures, when RedCine is restarted clean before the session.

I'm recording to Red Drives and using Redcode 28 at 23.97.

I'm typically very cautious, but I would not hesitate to do any job at 4K 16x9 using MY camera and post setup.

Your situation may be far different, so Noah's advice may be prudent.

Good shooting and best regards,

Leo
 
Does anyone know if 16:9 4K footage at Redcode 36 is viable -- or will become viable in post. All the proxies are corrupted, and RedCine on Mac crashes when I try to open a file.

I've had no trouble with 2:1 4K Redcode 36 footage. All this on build 15.
 
I've had no trouble with 2:1 4K Redcode 36 footage. All this on build 15.
Click to expand...

We've had problem with 4k 2:1 36. It look like film scratches.

Kinda cool but I can't control it.

Wish I could.

LOL

I think 4k 2:1 28 is good enough for me, for now.

It's the most stable on CF cards, and cheaper to post at the moment.

Tek
 
Jeff Kilgroe said:
You can shoot 4K 16:9, but you can only open it for export in REDCINE, it's not supported by the proxies, Red Alert or Final Cut. Seems that build 15 v2.2.5 is the most stable release overall. But I can't comment on how stable 16:9 is in 4K on the camera -- haven't shot it due to the post support issues.

Can you shoot 3K? Or shoot 4K 2:1 and crop to 16:9 in post?
Click to expand...

Thanks for the help guys. I'm very aware of all the proxy post issues. My question was if the codec camera recording was improved. 2:1 to 16:9 and 3k 16:9 are not options. Critical VFX and theatrical presentation being done here.

I shot yesterday with no problems. Tomorrow is a bigger day with more contrast and lots of speed! Hope to god she doesn't let me down because there will be no take two.

Thanks for your help.
 
HOLLYWOOD SCHMOLLYWOOD said:
Thanks for the help guys. I'm very aware of all the proxy post issues. My question was if the codec camera recording was improved. 2:1 to 16:9 and 3k 16:9 are not options. Critical VFX and theatrical presentation being done here.

I shot yesterday with no problems. Tomorrow is a bigger day with more contrast and lots of speed! Hope to god she doesn't let me down because there will be no take two.

Thanks for your help.
Click to expand...

I did some tests with Build 15 2.2.5 (?) a couple of weeks ago.

16x9 4K redcode 36 did indeed generate codec errors on slightly overexposed and high detail shots. V. annoying. And it did it even I tried to vary the shot or change the exposure. I was shooting a widish shot, Cooke 15-40, Handheld, from inside looking outside, but in overcast conditions. It would also crash when I tried to playback almost any of the shots, even ones that didn't have codec errors.

There's no way way I would want to count on it.

And of course all the other post issues as well.

jb
 
embarrassing crashes in front of client with build 15 16x9 redcode 28.

more to come.

also don't use red drive with NASCAR
 
Fellas,

I totally understand the 16:9 out of 2:1 and it does yield great results but I've got to say that full frame 16:9 needs to be supported in this camera. Especially when intercutting with 35mm and needing to match frame and DOF.

In the end it all worked out. But 16:9 not working yet is well.....frustrating.

I'll maybe post the frame that killed it but it's a high detail shot of course.

We did get some great shots though and I'll see if I can get permission to post in the footage section.

Thanks for your help.
 
I am in no way condoning 16:9s bugginess, it's sort of... eh... not very good...
That's not my point, and I do understand your frustration.

:)

BUT, the current workaround is the "nextbest" crop thing.
 
You must log in or register to reply here.
Back
Top