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

Final Cut Drop Frames - HELP!

armorant

Member
Joined
May 24, 2008
Messages
5
Reaction score
0
Points
0
Hello, I am new to the RED and to Final Cut. However, I have been cutting for years on Avid.

I am getting a dropped frame error whenever doing a dissolve in Final Cut Pro 6.0.3. I am on a MacBook Pro with a Core 2 Duo 2.2ghz with 2Gb RAM and an external firewire Harddrive for my media.

I have used the M Proxy QT and the P Proxy QT, same results.. I have set Unlimited RT and have played with the compression settings. No luck. If I turn off STOP ON DROPPED FRAMES in the settings I obviously don't get this.

This is super frustrating. Any advice on how to fix this? Should I just turn off STOP ON DROPPED FRAMES and proceed? Will this affect my final output?

Help!
 
best way is to trancode your m-proxies to prores via compressor and then edit...

or you could download the log and transfer plug in
from red.com/support...

for more detailed help it would be nessecary to know more about your final delivery format and then take the best workflow based on this info
 
This is super frustrating. Any advice on how to fix this?

You can't fix it. There is simply not enough processing power to decode the Redcode files, do a quick debayer, and reformat to your screen, and do this for two streams in real time. If you cut directly with the proxies, you will have to render all dissolves and other effects in order to see them play smoothly. That is one of the reasons many here choose not to edit with the proxies.
 
Apart from CPU power I doubt that a single FW drive will cut it, I'm working with a small SATA-RAID on my MBP for far better throughput.

Regards,

Uli
 
Thanks!

Thanks!

Thanks, everyone. I am going the ProRes route and that seems to be a good solution.

Question -- I won't have any issues going back to the 4k files from ProRes when I do my final output?
 
I would also recommend more RAM. You really should consider a better drive scenario as well. Perhaps consider using a capture card such as the Kona 3.
 
MAJOR PROBLEM.... FYI pro res doesnt work with scratch so if your using that as your output you have to re out put in the end. I use dvv pro HD for everything. Hope this helps-JSTL
 
Back
Top