Welcome to our community

Be a part of something great, join today!

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

Help! ProRes 4444 looks TERRIBLE in FCP

I have to come back to an unaswered question.

Is there a braodcast monitor with a video card (like AJA) feeding it in the equation here?

If not, then I have to say that from what I have seen (an underexposed unlit clip) being viewed within FCP (which displays one filed at 8-bit) is the problem here. I do not think it is a problem with the renders. I have rendered hours of footage to this codec through RC-X now and I have to say that I have not seen this problem.

Garbage in. Garbage out.

I've been following this thread (with a pretty alarmist title that contributes to FUD) and that's what I would chalk this one up to.

David
 
What some of the more supercilious amongst you might think, aside from anyone else, I'm willing to bet the majority of users are viewing through FCPs own viewer, rather than through a broadcast monitor.

and i also have an unanswered question: its not with every kind of ProRes, its just 4444.
 
I'm still willing to bet that this lies in the QT component 4.1 beta somehow gargling the info from redcine-x and not transferring all the data properly. That is if you have your FCP system setup properly.....that is strange that you would only get problems with 4444 transcoded clips. you have rt. clicked on the clip and gone to item properties and verified ALL the clip properties yes?
 
BajaProductions said:
I'm still willing to bet that this lies in the QT component 4.1 beta somehow gargling the info from redcine-x and not transferring all the data properly. That is if you have your FCP system setup properly.....that is strange that you would only get problems with 4444 transcoded clips. you have rt. clicked on the clip and gone to item properties and verified ALL the clip properties yes?
Click to expand...

Yep. I've been discussing it with Graeme Nattress, and he's stumped too.
 
Hi,

I'm having a similar problem, but inconsistently. I graded a short film for a client, in Color (not RedCine-X) but with the beta Red plugin, rendered to ProRes 4444 and sent back to FCP. When viewed on a JVC tube monitor and on a JVC 10 bit projector (via double HD-SDI to an AJA hdmi converter), via a Blackmagic multibridge, it looked fine. The client took the FCP project home, and when he views it, and he's tried numerous machines, there is strong banding (or quantization) going on. He brought back the project, I openend it in FCP, and suddenly I could see the banding on the projector, but note the tube monitor ! I launched Color to see what was going on there, rerendered a few clips, went back to FCP, and the banding was gone (on the projector) even on the clips that were not rerendered.

Baffling, but I would say it is a QT, FCP, MAC OSX, ProRess issue.

Our system : Octocore 2008 MacPro, Snowleopard, FCS3, Multibridge, ATI 4870

I think the next step will be rerendering everything to ProRes 422 HQ.

Cheers,
Damien
 
Good news everybody! The new RedCine X build 246 finally matches when it transcodes to ProRes4444!

Looks the same in QT as it does in the RCX, and looks the same in FCP!

Yep, no more washed out QT files, it's like a 98% match, which is more than close enough for me!

Great day!
 
When Deanan mentioned that the new beta REDLINE now supports curve and stuff, I was thingking that was the actual cause for the inconsistency, too.

Great.
 
jimhare said:
Good news everybody! The new RedCine X build 246 finally matches when it transcodes to ProRes4444!

Looks the same in QT as it does in the RCX, and looks the same in FCP!

Yep, no more washed out QT files, it's like a 98% match, which is more than close enough for me!

Great day!
Click to expand...

Are you sure? Does not match for me....in fact I'm having to regrade EVERY clip in Color. RCX transcodes to prores 4444 or 422 are FAR from what they look like as raw R3d's in my case.
 
Haven't tested with the last couple of builds, but we established at some point that ProRes transcodes matched what we saw in RCX only when "Use restricted SMPTE range" was off. Turning it on resulted in washed out ProRes files.
 
Chris Kenny said:
Haven't tested with the last couple of builds, but we established at some point that ProRes transcodes matched what we saw in RCX only when "Use restricted SMPTE range" was off. Turning it on resulted in washed out ProRes files.
Click to expand...

I'd have to say that I see it about 85% close. Tested using 10bit out to cc monitor R3d's via RedRocket card; then 10bit out via QT movie to CC. monitor as well....and they are just not quite there. Big improvement from previous builds, but still seeing the prores at slightly under-saturated. Yes, build 261 is now a big improvement. I find that i keep getting unstable transcodes via RRcard if i continue working on RCX while RR is transcoding as another bug.
 
Are the master clips looking bad in the Viewer? Are your sequence settings set to a lower resolution?
 
You must log in or register to reply here.
Back
Top