Please Feedback on Release Build 16

[Michael Lindsay]

Speedramps should be done in post. Shoot at the maximum frame rate you will need and let the editor ramp it, perfectly timed, later.

We used to go crazy ramping all over the place when 435's came out, but eventually every director we work with got burned by badly-timed in-camera ramps and started doing them in post. On a Red where the 'cost of film' is so minimal there is really no reason to do them on set.

They simply look better done in camera...

Unlike film, with red you can check the timeing on set and make sure you get it right!

With film I latterly did all speed ramps in post... with Red I choose to get them right.

I am delighted Red can ramp in camera!!

regards

Michael

 

[Jeff Brown]

Baselight...

Baselight...

Hi Martin,

So the baselight can take in an fcp cmx3600 edl using red file naming eg A001_C009_0808RD?

I may have been mistaken in that the DPX filenames via Crimson end up as Z00001_A001_C009_0808RD_Filename.DPX (If anyone has a way of not doing that and ending up with A001_C009_0808RD.DPX it'd be greatly appreciated!)

Cheers

Jeff Brown

Red 708 "Ruby"

 

[Martin Tlaskal]

Hi Jeff,

So the baselight can take in an fcp cmx3600 edl using red file naming eg A001_C009_0808RD?

I may have been mistaken in that the DPX filenames via Crimson end up as Z00001_A001_C009_0808RD_Filename.DPX (If anyone has a way of not doing that and ending up with A001_C009_0808RD.DPX it'd be greatly appreciated!)

Red 708 "Ruby"

If the A001_C009_0808RD string is in the tape name of the CMX event, Baselight will match it whether the tape name lies in the path:
eg /vol/bl1/myjob/A001_C009_0808RD/2048x1556/#.dpx
..in the filename itself:
eg /vol/bl1/myjob/2048x1556/A001_C009_0808RD_#.dpx
..or if it's in the DPX header (via a misuse of the scanner name attribute).

Regards,

-Martin

 

[C.H.Haskell]

you should give haskell a shout. I think he's been bashing on it pretty hard

I have not run into any problems yet with Build 16 and I would say go for it (at your own risk) just as RED will tell you. I updated my RED the moment 16 beta was released since there was no going back I naturally have embraced the build. I still get a green screen on my Panasonic Monitors during 1080 playback but this is a known issue. The only errors I ran into were the Roketio playback error or something like, it only effected playback on camera, no big deal and it was fixed in recent updates...have not seen it since.

I will say that my RED 1781 has shot 3 short films, 2 music videos and couple commercials since the release of 16 and I have no horror stories to report...many of these projects are deep into post and still no one has called me to report any issues with footage.

Every-once in a while (becomes more rare though) the camera does not want to boot, simple to know when this happens cause the rear lcd on the RED says "booting..." for longer then it should (more then 15 sec?), no image comes up on the LCD and if you hear the fans kick up high then definitely shut her down, wait 5 seconds and reboot...ta-da, it boots no problems, I dont even mention it to anyone on set cause I dont want to cause DP, Director, or producer to have nervous breakdown over a non issue (imo). Just power cycle and she is up and running...again I have had to do this a couple of times in build 16 vs build 15 it happened quite often.

We have been running the camera for 16 hour plus days...hot hot hot and she keep chugging, no over heating yet. In my non technical evaluation as of today...INSTALL 16 and enjoy, its rock solid!

Best of luck on your project!

 

[Johann Schulz]

Lots of field notes, Haskell: THANKS!

 

[I Bloom]

is crimson working with 16?

It is. Crimson does build 16. And it does <16 and 16 mixed projects with the same matching tool.

 

[Rainer Fritz]

Thanks for the Input guys! The only question now which is open for me is the 16x9 recording format. Any Codec Errors so far? We need to record 4k@25fps... can anybody report ???

thx
rainer