Scott Witthaus
2
Apple Final Cut Pro X Coins
3
COW Coins
Forum Replies Created
-
And Resolve was on a different machine.
Scott Witthaus
Senior Editor/Post Production Supervisor
1708 Inc./Editorial
Professor, VCU Brandcenter -
[Aindreas Gallagher] “I think this is wonderful. I feel we should celebrate all editing systems, each with their own specific charms. They are all special snowflakes.”
Holy cow! Somebody call a doctor! Aindreas must have fallen and hit his head on something! 😉
Try quitting Twitter. I was on it for a total of 5 days (useless digital noise IMHO) and it took three months for them to finally stop trying to lure me back (“pssst. hey man, we still have your account ready. c’mon, just press that reactivate button in this e-mail. you know you want to….”). Like a damn drug dealer….
Scott Witthaus
Senior Editor/Post Production Supervisor
1708 Inc./Editorial
Professor, VCU Brandcenter -
[Michael Gissing] “The other thing is on the Media page, checking that the clips were forced to data not auto where it may have incorrectly interpreted as Rec 709.”
That is a good clue. Again, it was during a 48 Hour Project so we were all sleepless and rushing. Thanks Michael (I sent the colorist a link to your advice on the Resolve page, so I assume all the steps were followed.).
sw
-
[Oliver Peters] ” never change master clip names except in Media Composer.”
I am with you on that! This is just a very weird thing. I will let you know.
Scott Witthaus
Senior Editor/Post Production Supervisor
1708 Inc./Editorial
Professor, VCU Brandcenter -
Trust me Oliver, I could spot the difference using the same monitor, switching back and forth on the same shot. Pretty obvious. The colorist confirmed that there were no ProRes files in the media pool. However, I have all the material and will do a test soon.
Scott Witthaus
Senior Editor/Post Production Supervisor
1708 Inc./Editorial
Professor, VCU Brandcenter -
Possible or not, it happened. The ProRes proxies would have been very easy to spot. Bug? Who knows? But we ended up doing a quick color balance and then a ProRes HQ output back to me and I tweaked colors on entire scenes for the final (hey, it’s a 48 hour thing. Do what it takes!). I switched back and forth between my proxy cut and the HQ and it was extremely obvious. Very strange. When I get done with this AE gig I have going, I am going to try it again with the same footage and see if I can replicate.
-
Yes, it was DNG files and I misspoke, we transcoded to proRes proxy, so there was no mistaking it. It just seemed that anything I changed, and it was not much, lost the metadata handles. Very odd.
Scott Witthaus
Senior Editor/Post Production Supervisor
1708 Inc./Editorial
Professor, VCU Brandcenter -
(dope-slap to forehead)
That makes perfect sense. Thank you.
Scott Witthaus
Senior Editor/Post Production Supervisor
1708 Inc./Editorial
Professor, VCU Brandcenter -
Great advice. Thank you all. I went with ProRes422 and it seems to be working fine. Really liking AE for what I am doing, which is basic stuff but a great learning experience. Thanks again.
Scott Witthaus
Senior Editor/Post Production Supervisor
1708 Inc./Editorial
Professor, VCU Brandcenter -
Thanks. The XML to Resolve worked well, but with one big oddity. If I changed any of the names of the clips in FCPX (not at the finder level), Resolve will still relink but not see the clip as a RAW clip and have all the handles you get on a RAW clip. Now, that is what I observed; I was not the Resolve editor. As anyone seen this? The editor was working on R11. Thanks.
Scott