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

Build 20 Black R3D Files

U

ULY

Member
Joined
Apr 8, 2008
Messages
11
Reaction score
0
Points
0
Website
www.pillefilm.de
Hallo Everyone
We were shooting with Build20, new Soundboard 4K 16:9 RC28 on 16GB CF Cards with 1 Chanel Audio (line in)

We had a playback on the Camera but if I open the QuickTemes i only hear the sound, but the image is black... same in RED Cine(20.0) or Red Alert... :confused:

Anyone an Idea?

I Hope you can halp me...
 
Open the R3D in Red Alert and choose "Make Quicktime". I had that issue on build 18. I think the levels are getting corrupted in the QT proxies. I'll bet your R3D is just fine.
 
There may be issues with the in-camera settings.
If you post a screenshot of the left hand side of REDAlert (the settings area) with one of the clips loaded that might help in diagnosing the problem.

Cheers
Hans
 
Oh Man You were right...
The R,G and B settings were all ZERO
Setting to default i got the image... thank you!
The Camera is still shooting at the moment, but i will check the on Camera settings later this day.
 
I checked the Camera settings...
The Operator had accadently set the "Master Gain" to zero...
This was why the Files were black...
But I think its some kind of a bug, that you dont see the changes on the Camera Monitor.
Even in REDSpace ore Rec709 View.
 
Master Gain

Master Gain

Yes there is a known bug in Build 20 where the Master Gain setting isn't affecting the RGB monitor path.

But it is being captured as metadata. We know about this and will fix a.s.a.p.
 
Same problem faced by us

Same problem faced by us

Stuart English said:
Yes there is a known bug in Build 20 where the Master Gain setting isn't affecting the RGB monitor path.

But it is being captured as metadata. We know about this and will fix a.s.a.p.
Click to expand...

This is the same problem we have faced and it was really embarrasing in front of client when every thing went smoothly on the shoot and when it goes to
edit every thing was black
Thanks to other red owner and friend Sandeep Dey he helped us out

The red community rocks.. Thanks now every thing is under control
but had to spend more time on post to work out the same feel what cinematographer wanted and was seeing on the monitor
 
Build 20 All Black frames - how to fix proxy QTs?

Build 20 All Black frames - how to fix proxy QTs?

I've just un-archived some media for a filmmaker.

All QT Proxies appear black- probably shot on the above mentioned build. In RCX, Resolve, or Media Composer, I can just change the source settings so that RGB isn't 0 0 0, and the image is excellent. It used to be that you'd 'make QTs' using RedAlert. How can the client make the proxy QTs visible without 'RedAlert?'
There doesn't appear to be an .rsx file- I know that's gone away, but haven't had to mess with proxies recently, so haven't paid attention to that part of the new workflow.

For grins, I pulled up the last build of redalert, and was able to remake one set of QTs... but is there a better way? TIA
 
Greg Huson said:
I've just un-archived some media for a filmmaker.

All QT Proxies appear black- probably shot on the above mentioned build. In RCX, Resolve, or Media Composer, I can just change the source settings so that RGB isn't 0 0 0, and the image is excellent. It used to be that you'd 'make QTs' using RedAlert. How can the client make the proxy QTs visible without 'RedAlert?'
There doesn't appear to be an .rsx file- I know that's gone away, but haven't had to mess with proxies recently, so haven't paid attention to that part of the new workflow.

For grins, I pulled up the last build of redalert, and was able to remake one set of QTs... but is there a better way? TIA
Click to expand...

You should be able to remake the QTs in RCX also.
Sounds like you may have to reset the metadata to defaults first.
 
You must log in or register to reply here.
Back
Top