-
So… Motion blur is still broken for 10-bit YUV?
Man, this was one of the features I really wish they had worked out in version 5. While FCP’s built-in motion blur does look much better in FCP5, it still artifacts and is basically unusable on most graphics while processing YUV in 10-bit. The obvious workaround is to downgrade the “Video Processing” to RGB, but that isn’t really desirable either. Not to mention the inability to combine a drop shadow with a motion blur.
Am I the only one that this bothers?
-Todd Beabout
Vazda Studios -
8 Replies
-
I.m with you, especially about the second pass or nesting needed for a drop shadow!!
-
No. It has never looked good so I don’t hardly ever use it. Never thought that YUV vs. RGB might have some effect. Would be nice touch if they improved it next time… along with a boat load of other stuff!
-
Yeah, the problem seems to be only with 10-bit and YUV combination. Which is of course the default highest quality setting. Thought about just going to 8-bit and see if that helps, but all my footage is already 10-bit so…
At least I know others have the same problems.
-Todd Beabout
Vazda Studios -
Seems like there are so many problems with 10-bit YUV that it’s not worth using if you have to do anything more than cuts and dissolves in the timeline. Photoshop artifacts, drop shadow artifacts, motion blur artifacts…at least we still have Combustion and After Effects to do stuff that we need to look really good. I had hoped to be able to build more layers in FCP. Oh well.
Joe Murray
-
I have had this problem which I thought was down to my Decklink, but the boys at BMD have tested and say it’s FCP. They have reported to Apple.
Roddy Jamieson
-
Both “10bit” and “High Precision YUV” rendering have always been broken. They fixed a couple of bugs for FCP5 but not all.
Graeme
– http://www.nattress.com – Film Effects and Standards Conversion for FCP
-
10 bit? High precission YUV? FCP’s Motion Blur is a bad joke, regardless of any specific bug with a color space. It’s certainly not a Motion Blur process in the sense any motion graphics or compositing app use the term. For starters, it blurs internal motion which is something it shouldn’t do at all (there’s always a cheap “Trails” effect for that) and the stepping is so awfully obvious. Finally, it takes ages to render!
I never understood what they had in mind when they did this. Will they ever care to re-write it?Adolfo Rozenfeld
Buenos Aires – Argentina
https://www.adolforozenfeld.com
adolfo@adolforozenfeld.com -
On the occasion that FCP will render the motion blur, and with settings different than the default, the “look” of the motion blur has somewhat increased in version 5. (The settings I use are 100/16+ samples.) The only reason/time that I use this, though, is when I’m in a crunch and I need to fly a graphic on in say… 4 frames or so. Throwing the motion blur on that, if it renders (i.e. no drop-shadow on it), will look better than without doing it, and be quicker than jumping into AE or combustion. But for anything “important” I use FCP basically for cuts, and then jump into combustion for any compositing or motion graphics.
I’m expecting a lot from Apple at NAB this year. Hopefully they have heard some of these complaints about things that should be fixed at the core of this application. I mean, the feature set is terrific. Let’s get the bugs worked out and the functionality up to spec.
-Todd Beabout
Vazda Studios
Reply to this Discussion! Login or Sign Up