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

Do Not Mix Footage!

bernd katzmarczyk

Well-known member
Joined
Sep 25, 2007
Messages
116
Reaction score
0
Points
0
Age
51
Location
munich
Website
www.thewhitepage.eu
I just started this thread to let you know that working with quiktime proxies of 3k and 4k shots do not fit in the same timeline in fcp version 6.0.3. as we decided to shoot 4k 25f/s and 3k 36f/s for a music video, we were not aware of these big problems. we´d better shot 2k 36f/s!
we decided to do the crimson workflow just because of the masses of footage - 220 gig! ProRes wasn´t really an option. rendertime was timed more than 2 days and redcine isn´t reliable at the moment with that much footage. I become a little bit scared thinking about finishing with the crimson workflow for the online in redcine to scale to hd 1080.

I hope apple or/and red will give attention to this for the future...... thanks guys:shifty:
 
You can render proxies to prores in compressor for a render time of around 2:1, especially if it's 3K (this does not apply to the 16:9 4K proxies that doesn't work in quicktime yet).

At that point you wouldn't only have had more stable files to edit with, you could also have adjusted them all to be the same size and ruled out render time in your edit.

My 2 cents

Fredrik
 
You can render proxies to prores in compressor for a render time of around 2:1, especially if it's 3K (this does not apply to the 16:9 4K proxies that doesn't work in quicktime yet).

At that point you wouldn't only have had more stable files to edit with, you could also have adjusted them all to be the same size and ruled out render time in your edit.

My 2 cents

Fredrik

thank you frederik, sounds interesting, but we´d to render all 220 gig to use it in one timeline cause redcode proxies do not fit with ProRes in one timeline either. we used redalert to render 3k to hd Prores files. so we still tried this:wacko:
 
I just started this thread to let you know that working with quiktime proxies of 3k and 4k shots do not fit in the same timeline

have you understood why a 1K proxy from a a 4K file can't fit in the same 1K timeline with a 1k proxy from a 3k file?

1k proxy should be 1k proxy independently from what file (3 or 4k) is extracted ?
 
have you understood why a 1K proxy from a a 4K file can't fit in the same 1K timeline with a 1k proxy from a 3k file?

1k proxy should be 1k proxy independently from what file (3 or 4k) is extracted ?

indeed I thought that a 1k proxy of 3k does fit with a 1k proxy of 2k or 4k. but even though I was wrong, you should be able to edit files in different size in a fcp 6.0.3 timeline. I can edit footag 720, 1080, sd in a fcp timeline... so I came from doing it the same with redcode proxies...
 
thank you frederik, sounds interesting, but we´d to render all 220 gig to use it in one timeline cause redcode proxies do not fit with ProRes in one timeline either. we used redalert to render 3k to hd Prores files. so we still tried this:wacko:

Yes but that was REDAlert with redcode files (I assume). I'm talking about converting quicktime proxies in compressor. Way faster!!!


fredrik
 
Back
Top