-
Problem – Shift fields filter added
Hi, All,
Recently (perhaps since FCP 5.0.4), Final Cut has been automatically adding the shift fields filter to all HDV clips placed on a properly-setup HDV sequence — ONLY when FCP is set up to output component HD through my Kona 3. When FCP adds this filter the clips demand to be rendered. At first this wasn’t a big problem, just a glitch in the workflow because I have to remove the filter manually. However, I just started doing a multiclip edit, and each time you cut from one angle to another FCP reapplies the shift fields filter. Therefore realtime multiclip editing is not possible in this configuration because the screen goes to an unrendered state.
The only workaround for this is to change the setup to exclude the Kona 3 card from the operation, removing the option to monitor the work. This isn’t acceptable.
I have seen on the FCP forum that people using Blackmagic cards have had the same problem, so my guess is that this is an FCP bug in the newer versions that generically relates to the use of these cards.
Does anyone know if there’s a better workaround or when this is likely to be fixed?
Thank you,
Mike
My system: G5 quad, 4gigs memory, Kona 3, FCP 5.1.1
-
7 Replies
-
Try selecting “play base layer only” in the RT Effects Pop up menu. It makes FCP ignore effects that require rendering.
Not a perfect solution, but it may help.
-
This is a dumb question but without info from you we have no idea
Are you working in 50i HDV? because that was an issue with the 5.04 version of FCP not rendering the field order correctly for the 50i video.
yes with multiclp editing you will find the need to have content rendered as the FCP wants the GOP structure to be rebuild when you are making multiple edits in multiple tracks.
gary adcock
Studio37
HD & Film Consultation
Post and Production Workflows -
Thanks for the responses.
I am using 60i HDV.
When I remove the Kona 3 from the FCP process by changing the Audio/Video Settings so that Video Playback shows “None”, I can usually get the multiclip to work in real time. Yes, it eventually needs rendering to get a final product, but at least I can edit it.
Here’s how it works: In the browser, none of the angles that go into the multiclip have the shift fields filter installed. I put the multiclip together, then put it on the timeline. Now all the angles have the shift fields filter. The timeline goes to red and requires rendering.
I then remove the shift fields filter from each of the angles of the multiclip. The red line goes away. I then start to edit, switching between angles using the Viewer, as I have always done. But each time I cut between angles, FCP automatically reinserts the shift fields filter on the angle that I have chosen. The timeline goes back to red and the screen only shows the unrendered media message.
It seems very buglike to me that FCP puts the shift fields filter on every clip every time it is placed on the timeline ONLY when FCP is outputting to the Kona 3. If it were putting the shift fields filter on accurately that would be another matter, but in fact the shift fields filter changes the dominant field to the opposite of what the sequence settings say it should be, thus forcing a render.
Thanks for any advice.
Mike
-
It also does the same thing with BM cards as well
-
How about removing the “Shift Fields” filter, so FCP can’t apply it.
It’s located in the Final Cut Pro App bundle…
Control click on the App icon….select “Show Package Contents”
Then look in Resources/English.lproj/FXScripts/Filters/Video
Remove the filter called “Shift Fields.txt” and put it in a safe place (in case you need to put it back)
Sorry, I cannot fully test it, as I do not have any HDV footage, but I can attest that removing it causes no ill effects to FCP.
-
Many thanks!
Dumped the filter and it seems to have worked. I’ll just stick the filter back in if I need it.
Thanks, too, for taking the trouble to explain in detail how to remove the filter. I wouldn’t have known.
I’m also planning to recompress the project to DVCPRO HD, which doesn’t appear to have the same problem.
Many thanks for all the responses. I hope this gets fixed soon.
Mike
-
Glad it seems to have worked!
Hopefully the forthcoming 5.1.2 Update will deal with this problem.
Reply to this Discussion! Login or Sign Up