Matt Harris
Forum Replies Created
-
Hey Randy, I did sort it out, kind of. It’s just the way it is. Resolve shows a little more contrast than FCPX. When upload to vimeo it plays somewhere in between on Safari (mac) but in firefox its closer to the way Resolve looks. This isn’t a screen calibration problem but a decoding variation between different plays. They just read the files differently, so you kind of have to ballpark it.
By the way, the human eye adjusts to each pretty quickly, so I don’t thinks its a huge deal.
-
Hey Breanna, I’ve learned that Apple just does this when watching with Quicktime or in FCPX. I can play the same file with FLC and it looks different. I think it best no to grade in FCPX because of this. When something is uploaded into vimeo it generally will look closer to Davinci Resolve than FCPX. I can even watch the same vimeo file in Firefox and then in Safari and they will look different. I’f anything is compressed then it has to be decoded in some way, and I think that process probably varies a lot.
-
Solved. I had Imported my master clips into the timeline twice.
Still runs like crap on my Retina macbook with mavericks. Used to be much better
-
Yes. FCPX and Quicktime look different than everything else, so I cant grade accurately even for my own computer screen.
-
I understand, but if a monitor lies, wouldn’t it lie the same amount in each program? The top pic is from resolve, and the bottom is from fcpx. There is no way the scopes will read the same.
-
Wow, thank you so much for taking the time to respond!
This was my first project where I denoised each clip with neatvideo in premiere and then sent to resolve.. I’ve added grain after roundtripping back from resolve. I wonder I’f I should have added some before the premiere export? Anyway thanks for all the help.
-
I did what you said. The ProRess 422 export from FCP looks cleaner, and has slightly more contrast. The PP 422 export has less contrast and blocking. This isn’t something that film grain smooths out either.
-
I’ll give that a try. Both files are 1920 but I just shrunk the windows down to fit.
-
My work flow was 5dmkii h.264 footage edited in Premiere Cs6. Then export to Prores 422 and bring that into Davinci Resolve. Send Prores 422 out from resolve back into premiere for sound mixing and touchups, then export the final h.264 for vimeo.
The 5d had some sensor heat noise going on becuase I had used it all day, but it dosent look like the problems in the pictures.
I swear its something to do with Adobe media encoder. I exported from premiere on 2 different computers and they both have the same problem on h.264, proress 422, and even HQ. I then exported the same file from FCP 7 to Pro Ress 422 and h.264 and neither had any problems. -
Its also happening when I export h.264 footage with the vimeo 720p preset as well. These block dance all over the place. the only thing that looks clean is a proress 444. Does this make any sense? thanks for any help.
