John Vonmutius
Forum Replies Created
-
Aha! You can’t smooth center point keyframes in the viewer, but if you have wireframe overlays turned on in your canvas, you should see a motion path for your media with green points representing the keyframes. Here, you can right-click and choose ease in/ease out.
—
Exploring the pitfalls of the 5D workflow. The many, many pitfalls… -
What attribute are you trying to smooth? How many keyframes do you have on that attribute?
—
Exploring the pitfalls of the 5D workflow. The many, many pitfalls… -
5 hours from when you posted this? That’s ridiculous. Best suggestions I can give are: Work in a SD sequence and set your playback quality to low and your playback frame rate to half or quarter. That should help you edit faster, but there’s nothing you can do to keep the machine from reading the full HD files from a slow server. By the time you make low-res proxies to work faster, you’d be out of working time.
—
Exploring the pitfalls of the 5D workflow. The many, many pitfalls… -
You can still do that. Just right-click the keyframe and choose ‘smooth’.
—
Exploring the pitfalls of the 5D workflow. The many, many pitfalls… -
Show me what the motion looks like in FCP, on your computer monitor.
—
Exploring the pitfalls of the 5D workflow. The many, many pitfalls… -
I’m sorry, I just noticed that you’re using Final Cut Express. Apparently, that is not able to edit H.264. Final Cut Pro 7, however, can handle it well.
Importing iMovie projects is not something I’m familiar with, but in my experience, adding intermediate steps to a workflow like that only introduces more opportunities for things to go wrong. And, according to another commenter here, iMovie is converting your raw footage to AIC anyway. So why not just export your own raw footage as AIC or some other codec and rest easy knowing your source files will render efficiently and accurately in Final Cut Express? If you want the features available in the software, you have to make your files compatible.
—
Exploring the pitfalls of the 5D workflow. The many, many pitfalls… -
I’ve never used that feature in Quicktime 7 (enable Final Cut Studio color correction) and I can’t imagine what good it is unless you’re reviewing your own videos for accuracy. Once you output it, the color is locked in to the codec. Everyone who views it, whether on their computer or a television, will have very different color settings and gamma settings, so changing how YOU view it in QT 7 will not really help you achieve your end goal. You need to test it in a real-world environment using the final output movie.
—
Exploring the pitfalls of the 5D workflow. The many, many pitfalls… -
Final Cut is more advanced, which is why it asks you to use more advanced video formats.
You can edit h.264, by the way, just don’t layer multiple video tracks or you’ll have to render.
For your edification: H.264 is frame-by-frame codec, which means that every frame is a highly-compressed individual image. Final Cut was not designed to play well with it because all footage at the time the software was created was tape-based (and not captured using frame-by-frame codecs). Most professional footage – even tapeless media – is still recorded using codecs that group frames together for better motion estimation, greater color depth, and faster/smoother playback rates, as opposed to smaller file size.
—
Exploring the pitfalls of the 5D workflow. The many, many pitfalls… -
There is no ‘QT color’ or ‘FCP color’, there is only codec color space and compression. So, what codec is your original footage and what codec are you exporting? Codecs have sometimes wildly different color spaces and ways of interpreting color pixels.
—
Exploring the pitfalls of the 5D workflow. The many, many pitfalls… -
Good idea. Wish I’d thought of it. 🙂 I’ve learned with FCP that if it doesn’t keep me from working, it’s probably not worth messing around with. There are quite a few bugs and odd behaviors that I generally ignore. And, yes, the whole thing might crash at any time, but that’s not because of thumbnails, it’s just because FCP has some issues. That’s why Autosave is so great.
—
Exploring the pitfalls of the 5D workflow. The many, many pitfalls…