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

Color Space Toggle. What's going on?

Lindsay Mann said:
solved
Click to expand...

uhh...rather than just deleting your original post, would to care to share how you "solved" this issue?

(sorry, this is a huge pet-peeve of mine...i find "hit and run" forum posts to be rather rude)
 
Yeah, if you leave up your question, and maybe add a brief explanation of how you solved it, it can always add to the forums usefulness. Changing your post to "solved" just turns it into a waste of a mouse click.
 
I didn't really solve it yet. No one responded and I didn't want to waste people's time. I don't know how to delete the post.

My workaround is not importing the damaged footage. Here's the deal:

Nearly every clip of mine from a recent short that has highlights approaching being blown out has evidence of the operator checking to make sure highlights aren't clipping. I'll see most of the clip as the colorspace with which I was monitoring on set, and then a switch to what looks like RAW footage with more latitude.

The question was whether this was baked into the footage or not. And having captured it and transcoded to ProResHQ and it still being there, I'm assuming there's no solution. But I'd love to be proved wrong.
 
Lindsay Mann said:
I didn't really solve it yet. No one responded and I didn't want to waste people's time. I don't know how to delete the post.

My workaround is not importing the damaged footage. Here's the deal:

Nearly every clip of mine from a recent short that has highlights approaching being blown out has evidence of the operator checking to make sure highlights aren't clipping. I'll see most of the clip as the colorspace with which I was monitoring on set, and then a switch to what looks like RAW footage with more latitude.

The question was whether this was baked into the footage or not. And having captured it and transcoded to ProResHQ and it still being there, I'm assuming there's no solution. But I'd love to be proved wrong.
Click to expand...

Probably not quite enough info yet for us to help... but we would love to. Can you open an r3d that is indicative of the problem in RED Alert! and slide the exposure up or down and get the entire image inside the histogram? If so, how many stops did it take to do that? There are a lot of ways to see if you are screwed or not, this is just one of them. Many here would love to help but we need a bit more info. You will likely be surprised at how much info is actually in the RAW data that you have. Processing is usually a good way to throw info away (until you go back and do it again properly).

Jim
 
OK. The adjustment actually doesn't show up on the r3d file in Red Alert as far as I can tell, but why would it show up when I log and transfer to ProResHQ? I'll try to post an example soon and maybe that will help.
 
I have seen a similar bug a couple of months ago on a build 17 camera.
The colorspace and Gammaspace switched randomly from REC709 to Redspace in the middle of the shot in the QT Reference files... Very strange...
But the R3Ds were fine, and setting the Look back to Redspace in Redalert and rendering the files solved it...
 
There is a Color space bug in build 17 that gets activated after playback.

It only happens if you set system:preferences:playback:look to clip instead of camera.

I have notified Red through 2 different channels but haven't heard that it was fixed.
Not many people see to be aware of the problem.
 
Newly released build 20.1.2 has new colour space fixes as well as revised False Color info.

Will test it tomorrow on a short movie I'll be shooting.

HTH

Paul
 
I have been testing Red..even if I record Raw..when I see the test in FCP the raw footage also looks like Redspace/Rec709...and yes I'm using build 17. is there any solution for build 17?
PS: this is a SOS.I start shooting in 2days..its a 45+day schedule.
 
Yes, raw is not a color space for proxies. RAW is only a viewing space for on camera exposure testing. FCP most likely is showing you REDSPACE.

There is no fix as it is not broken.

As to the "playback clip" colorspace switch it is known and is still be worked out. When playback is set to "clip" the camera will switch into REC 709. It's that simple.
 
You must log in or register to reply here.
Back
Top