Oliver Peters
2
Apple Final Cut Pro X Coins
6
Avid Coins
17
COW Coins
1
DaVinci Coin
1
Premiere Pro Coin
Forum Replies Created
-
[Neil Goodman] “because its quicker FOR ME to just grab it from there”
Seems like a good time to add this:
https://digitalfilms.wordpress.com/2017/06/07/bricklayers-and-sculptors/
– Oliver
Oliver Peters – oliverpeters.com
-
[Bill Davis] “Expectations about the value of the techniques you KNOW, is one of the hardest things to overcome in editing, in my opinion. But you’ve GOT to if you truly want to become efficient at this stuff.”
First – I would be careful about assuming features and functions that appeal to your own preferences are somehow superior to other methods. There are many editors who use the timeline as a “scratch pad” and that works quite effectively for them. FCPX does not make it easy to do this, while other NLEs do. Whether that’s “good” or “bad” is merely a matter of personal workflow and preference.
Second – the client shouldn’t really care how you get the results as long as you can get there quickly by whatever means suits your style.
– Oliver
Oliver Peters – oliverpeters.com
-
Despite my exasperation, this was good faith effort. The location audio was very noisy in places, so in order to get a head start – the cam op did some noise reduction/repair overnight while on location. The mistake was that he erroneously thought he had inserted the cleaned up audio (only) back into the files and wasn’t overwriting the video.
Just another day in post ☺
– Oliver
Oliver Peters – oliverpeters.com
-
[Tangier Clarke] “I started scouring the interwebs because I was intrigued that you got back a DNxHR file at all from the C300 MKii. I can’t find that spec anywhere”
OK, I’ve gotten to the bottom of this. I just found out that the camera operator at night resynced the clip with other audio and rewrote that back into the folder structure on the drive, thus overwriting the original clip. I’m not sure how he did that, but this retained the same file name, but unfortunately a different codec, which FCPX does not support. Damn, what a mystery!
– Oliver
Oliver Peters – oliverpeters.com
-
FWIW – I thought Apple had added back DNxHR support, but I guess only in MOV-wrapped files. Not helpful, as these are MXF and that’s generally what apps using DNxHR will use. These files will not open with picture in QT Player, but they will in Switch.
– Oliver
Oliver Peters – oliverpeters.com
-
I checked with the cam op and he did not overtly change settings. However, this was a run-and-gun situation and the two adjacent clips have a TC restart between. So most likely the camera was powered down in between and it automatically reset to DNxHR. This is either a default setting or a bug in the camera.
– Oliver
Oliver Peters – oliverpeters.com
-
I had some time to poke around in the files this morning. Apparently the files that do show up in FCPX are AVC-Intra/H264/10-bit. The files that show up only as audio are DNxHR/8-bit. So it’s a codec support issue on the part of Apple. Why the camera op changed settings between takes is a mystery to me. Unless the camera switches automatically based on real-time or slomo recording.
– Oliver
Oliver Peters – oliverpeters.com
-
LOL!
– Oliver
Oliver Peters – oliverpeters.com
-
[Brett Sherman] “Why not use Compounds instead of Projects?”
True, it is a solution. Although, it does seem a bit inelegant to me.
– Oliver
Oliver Peters – oliverpeters.com
-
FYI – Apple’s white paper for the XDR Pro Display.
https://www.apple.com/pro-display-xdr/pdf/Pro_Display_White_Paper_Feb_2020.pdf
– Oliver
Oliver Peters – oliverpeters.com