Welcome to our community

Be a part of something great, join today!

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

4k, 3k, 2k editing in fcp

bernd katzmarczyk

Well-known member
Joined
Sep 25, 2007
Messages
116
Reaction score
0
Points
0
Age
51
Location
munich
Website
www.thewhitepage.eu
hello to everyone,

we need some help! yesterday we shot a musicvideo and started today editing with the qt M proxies in fcp. but bringing the 3k proxies into the same timeline we still put the 4k qt it needs to be rendered?? can anybody give me some advice?? urgently:wacko: :w00t: :construction: :pinch:

thanx in advance
 
It's not to clear what you are doing here or what your actual problem is. Can you give us some more info? What resolutions did you shoot in? What resolution are you posting in, etc. Your post kind of alludes to you wanting to post in 4k, which you can not do in FCP at this time.:blush:
 
It's not to clear what you are doing here or what your actual problem is. Can you give us some more info? What resolutions did you shoot in? What resolution are you posting in, etc. Your post kind of alludes to you wanting to post in 4k, which you can not do in FCP at this time.:blush:

ok, here is the workflow:
we shot 4k 25F/s for lipsync and 3k 36F/s also lipsync - in a classic way to get the smooth parts... for editing we brought the 4k quiktime medium proxies into fcp and also the 3k quiktime medium proxies. the big problem: the quiktime m proxies are different in size to 3k quiktime m proxies (it´s the the same for f, h, p). 4k and 2k qt proxies match in size, but 3k does not! so fcp says "pleas render" to 3k quiktime medium proxies... thus fcp obviously does not accept redcode files with different in size
 
Back
Top