Annaël Beauchemin
Forum Replies Created
-
what I meant is that it is only a few little bugs that jeopardize the entire online-offline workflow. Somethimes it works fine, but everytime I need to inspect the edl carefuly, which takes time…
-
[johan skaneby] “does anyone know af a workaround to this?”
Most problems occur when you either use variable speed, or when you modify a speed changed clip on the timeline.
To reconnect properly, a clip must have only 2 Time Remap keyframes: one EXACTLY on the IN point, another EXACTLY on the OUT point.
For some reason, FCP sometimes adds keyframes outside of the used portion of the clip. You must delete them. Note that there is often a keyframe very far away from the OUT, this is normal.
When you move the IN or OUT point of a clip after it has been speed changed, sometimes the time remap keyframe will not follow. You must either move it back exacty on the IN/OUT point, or rebuild the sequence clip to make sure it’s “clean”. For this you select the sequence clip, you hit “f”, you apply the speed change while still in the viewer (command-J) and drop back the clip in the timeline.
But even then, they might slip a bit or screw up if you add dissolves… I really wish Apple would have corrected those little quirks which makes FCP a bit of an unreliable offline editing software…
-
[derek woods] “and it’s not even wireless? what a waste! microsoft intellimouse 10 bucks cheaper and wireless and reliable”
…until the batteries discharge.
-
[_OOO_] “Nope. It’s a video clip with no scaling applied. Straight clean DV footage from the viewer. I can’t be the only person noticing this”
I see what you mean. I was also surprised to discover this… you’re not alone 🙂
It would be great if FCP didn’t deinterlace/interpolate when you zoom at more than 100%… no other software do it.
-
[Bret Williams] “What it should do (but doesn’t) is delete render files that are no longer used. Still pretty much no way to do that.
Humm. FCP does delete unsued render files when it either reaches the undo level treshold or when you close a project. And if you want to delete active renders, the Render Manager is right there in the Tools menu.
-
[Bill Portune] “Unfortunately it isn’t a feature, it’s an error in the way FCP processes the DVCPROHD compression in 4.5 “
I have seen this problem with the NTSC – DV codec too. FCP 4.5, QT 6.5.2 also. A real big pain with transitions…
-
do you have variable speed clips?
-
but be warned of the gamma shift issue with PNGs…
-
is your rendering mode set to 10bits or high precision YUV? Some of those filters do not work well when rendering in more than 10bits. Solution is to nest the problematic clips in a 8bit sequence.
-
> Also, as it sounds like we don’t know which video will be slowed down, and which will not, that shooting it all at high shutter
> speed might look odd…I’ve never really shot as high as 1/500 since it requires lots of light, but I agree that shutter speeds which aren’t a multiple of the recording FPS look odd.
To me, higher shutter speed just look sharper in the motion since there’s less motion blur. To some point, it might flicker so much it’s sharp. But at least all frames are equally “motion blured” (or as sharp).
I feel that handheld footage is the most problematic footage to be slowed down because some frames are sharp, some others not because of the uneven motion of the camera. Played back at full speed we don’t notice it since it feels natural. When slowed down, the motion blur becomes visible and stops being “natural” since the motion itself is much slower. I think higher shutter speeds (and turning off the image stabiliser) might help to reduce this unequal motion blur.