APPLE FINAL CUT PRO: Apple Final Cut Pro X FCPX Debates FCP Legacy FCP Tutorials

Re: Why is FCP7 Log/Transfer cropping video?

COW Forums : Apple Final Cut Pro Legacy

FAQ   •   VIEW ALL   •   ADD A NEW POST   •   PRINT
Respond to this post   •   Return to posts index   •   Read entire thread


Ted Coakley
Re: Why is FCP7 Log/Transfer cropping video?
on Apr 4, 2014 at 7:19:47 pm

Hi Shane, thanks for your reply!


[Shane Ross] "It is a direct copy, only the container is changed from MXF to MOV"

When I view the camera original footage on computer (an editor can use a MXF/P2 viewer like P2ViewerPlus, don't need to be the shooter) what I SEE that FCP has made is clearly NOT a "direct copy" of what I see that the HVX200 made. I can see this by the fact that there are outer/edge image elements in the camera-original footage that are seen in P2ViewerPlus, that are NOT seen in FCP's Log/Transfer .MOV files.

Despite being a shooter for 20 years, and an every-blue-moon editor (going back to "The Cube" and Razor if you remember those! plus FCP 2-7 and various Premieres), I don't fully GET scaling/anamorphic/squeezing/containers/codecs. I know how to frame/compose/block/light/expose/direct, but I'm no tecchie and it's always a struggle for me to keep up with the changing formats/technologies!

What I DO know is that this HVX200 DVCPro HD camera original shows outer/edge parts of the image that the FCP .MOV files don't.
Regardless of the explanation, it IS happening.
Not much is being cropped, yes a small fraction, no not a huge chunk.


[Shane Ross] "Camera Viewfinders are set to OVERSCAN...so you can see all of the image. And several broadcast monitors have this option too, so you can see all the way to the edge."

I hear ya, I think about that, too! But, regardless of camera viewfinders or broadcast monitors being set to overscan, I'm looking on a computer screen in a P2ViewerPlus window that shows all the camera original MXF/HVX200/DVCProHD image - which does NOT show up in the FCP Log/Transfer .MOV files.


[Shane Ross] "Know that TVs and Computer displays will crop that edge anyway...and you cannot plan to have the full image seen. This is why there are ACTION SAFE and TITLE SAFE zones."

I do know that many TVs will crop the edge (albeit mostly older models, tubes and the like), but computer app windows (i.e. QT, VLC, FCP, etc) don't typically crop image files. Even if some TV or app DOES crop the image, I don't want FCP Log/Transfer (or anything else) pre-cropping my camera-original in the first place! Otherwise, there should be a FCP-LOG/TRANSFER CROP zone in my viewfinder in addition to ACTION SAFE and TITLE SAFE, right?


[Shane Ross] " I'm wondering if FCP's and QTs interface crops a little of those edges."

I'm wondering that, too :-) It appears it does do that - and not just on the display, but FCP maintains the same cropped image on Export (as I can see the same cropped image exported in Finder). Is it doing that? If so, then a) is it supposed to? b) Is there a way to get it to NOT destroy part of my image, or are we to be stuck with that edge destruction (cropping) as an inherent quality of FCP Log and Transfer? I'm thinking those are the questions I need answered, if anyone here knows those answers.

Thanks!!


Posts IndexRead Thread 


Current Message Thread:





© 2020 CreativeCOW.net All Rights Reserved
[TOP]