-
Unable to select “drop frame” when blacking a tape in “Edit to Tape”
I’m having a problem blacking a tape with drop-frame time code. I launch “Edit to Tape” and I have a tape in the deck (the problem occurs in both my AJ-HD1400 DVCProHD deck and my Sony PVW-2800 Beta deck). When I press the “black tape” icon at the top of the “Edit to Tape” window, a box appears and says, “Black and Code — Settings.” I hit “OK” and the next box is where you input the starting TC. However, the check box to the right, which you select for drop-frame time code, is grayed out and not selectable.
I am running FCP7, with Blackmagic Design DeckLink 6.8.3 running. The strange thing is, I ran a dub a week ago and I was able to select drop frame when I blacked the tape. For full disclosure, I was running Blackmagic Design DeckLink 7.3.2, but I had a problem with spitting out a down-convert signal, which is necessary for the weekly project we have. However, I don’t believe that this downgrade is the issue, because our 2 other edit suites are currently running Blackmagic Design DeckLink 7.3.2 and FCP7 (no downgrade) and they also cannot select drop-frame when doing an “Edit to Tape”.
Is this a problem with FCP7? Did a final cut setting get corrupted?
Any and all help/input is appreciated!! Thanks!!
-
3 Replies
-
Problem solved!!!
I think I’m gonna spray paint the following onto my edit suite wall:
“WHEN IN DOUBT, TRASH THE PREFERENCE FILES!!!”
Once I did that, the drop-frame check box became selectable again!!! What a weird bug!
(FYI, I was editing in DVCProHD 720p59.94, so I knew I should have the ability to layoff a drop-frame tape.)
-
FYI, corrupt preferences are not a “bug”. Just means your preferences were corrupted.
Kevin Monahan
60 Blu-ray Templates for Final Cut Studio 2009
http://www.fcpworld.com
Author – Motion Graphics and Effects in Final Cut Pro -
Maybe I didn’t use the correct term, “bug”, in the strictest sense, but I just wanted to convey that it was a very strange occurrence, and not something that should happen at all while working in FCP. And it happened for no apparent reason…That’s why I referred to it as a “bug.”
Again, the problem is fixed now, but has anyone else experienced this particular…hmm, what word should I use if not officially a “bug”…actually, I don’t know what else to call it, since a [software] bug is defined as, “an error, flaw, mistake, failure, or fault in a computer program…that produces an incorrect or unexpected result, or causes it to behave in unintended ways.”, which is what happened in this case!
Anyways, anyone else run into this?
Reply to this Discussion! Login or Sign Up