-
I am absolutely amazed…
I am absolutely amazed at what a lousy program FCP5 is. I have been working with it now for about a week and just started assembling a new still image sequence that is due shortly. After wading through the myriad of RT, Dynamic RT, full, medium, low and other assorted “Real Time” check boxes…not to mention the vast array of render status codes and colors, I find it interesting how badly FCP renders the basic motion of a still image. This is a simple DV25 project with slow zooms and pans on still images formatted and saved, imported and key-framed exactly as my trusty user manual recommends.
So far my best result is to simply turn OFF Final Cut Pro Effects handling and go for a straight render of every animation. That in it self would be fine, my G5 handles that job pretty quickly but unfortunately the end result yields an out-of-focus image that steps badly from one pixel to the next as it moves. It sort of reminds me of the not so distant past when After Effects had no solution for sub-pixel rendering. Quite frankly, it’s pathetic.
Given the amount of money required to move to a FC solution and the incredible emphasis assigned to the Apple “Pro” delineation, I really expected a rock-solid production solution. Instead I have a flaky application that now enjoys giving me the virtual bird every 30 minutes in the form of “The application Final Cut Pro quit unexpectedly“…how nice.
So really the point of this thread is to see if just maybe…since I have no prior experience with earlier versions of FCP i.e. FCP 4, 4.5 etc. I may be experiencing some new bug or programming oversight that did not exist before.
It’s also quite possible that despite my honest yet seemingly wasted efforts to assure I have every setting correct, I am overlooking something.
This has been a very frustrating start to what I had hoped to be a new level in video editing.