Colin Mcquillan
Forum Replies Created
-
My Mbox Mini (protools 8 installed) will not work as an audio I/O in FCP.
Though I haven’t had any issues with both FCP(7) and Protools installed on the same boot. I have both installed and running fine on my MacPro and MacBook Pro
Colin McQuillan
Vancouver, B.C.“Live, love, laugh and be happy.”
-
Changing the frame rate.. as in “conform” it from one frame-rate to another.
Again… Cinema Tools cannot do this to Long-GOP codecs like HDV.
The OP needs to convert the footage to an intra-frame codec, like Prores, before he will be able to change the frame rate (or conform, per se) in Cinema Tools.I agree though that this should be a function within FCP… Or FCP should at least better handle over-cranked footage… It currently butchers over-cranked footage unless “conformed” in Cinema Tools first.
Many people think they can simply drop 60fps footage onto a 30fps timeline and pull frame to frame 50% slo-mo… Unfortunately this is not the case…
Colin McQuillan
Vancouver, B.C.“Live, love, laugh and be happy.”
-
You need to convert your footage to a different codec before running it through Cinema Tools.
Long GOP formats, like HDV and XDCam, cannot be conformed. Use Compressor to convert your footage to ProRes first.Colin McQuillan
Vancouver, B.C.“Live, love, laugh and be happy.”
-
Haha! Hats off to the kid for ingenuity.
What ever the story as to why he is shooting a wedding like this, I love it (at the same though glad I didn’t hire him to shoot my wedding 😉
Colin McQuillan
Vancouver, B.C.“Live, love, laugh and be happy.”
-
Couple options.
1. In FCP try changing the Motion Tab render setting to Best (found in sequence settings) this might help a little, but don’t expect too much2. Go back to Motion. For better realtime playback for editing the move you want to achieve lower the display canvas resolution and change the render setting to Draft and make sure Motion Blur is turned off. This will give you heaps of realtime. Add your keyframes, once you are happy with the movement and are ready to render, change the render setting back to Best. Some might tell you Normal is good enough, but not when dealing with high-res images. Best will help reduce that ugly video-noisy too sharpish look. Also, keep off Motion Blur unless you are specifically wanting it.
Another thing I would consider if you decide to go with Motion is importing the stills as an image sequence rather than the Prores files you created from them. The Prores codec can have undesired effects on things when using non-broadcast standard frame dimensions.
Colin McQuillan
Vancouver, B.C.“Live, love, laugh and be happy.”
-
LOL, Very clever :-p
But I guess easy to say for any question anyone ever asks.. so I guess why does anyone ever need to ask questions ever…?
Maybe for personal insight you cant get from google… Maybe for hidden gems not sitting on the top hits page of google… maybe…..
I for one am tired of seeing the so many folks so ready to jump on posters with “go google it” as their cry…
Colin McQuillan
Vancouver, B.C.“Live, love, laugh and be happy.”
-
[Dave Po] “I do suppose writing to a different hard drive would help, eh?”
It definitely does. When doing batch conversion and such I typically point my destination to a different drive than where my source is located. Let one drive read, while the other writes rather than only one drive doing both! The cost though can be the fragmenting of your project so it is good to have a workflow set out for this. Personally I keep all my source project material on my primary RAID and have an ‘Exports/Conversions” folder on another media drive.
Another consideration is the codec you are using, and how/why you are exporting. Prores can address more cores when rendering than some of the other codecs. Also, if converting to various formats other than the editing codec I find it best/fastest to first export a self-contained QT file from FCP and use virtual clusters in Compressor to do the encoding (setting the destination to a drive other than the one where the source QT file is located.)
Colin McQuillan
Vancouver, B.C.“Live, love, laugh and be happy.”
-
Have you tried loading/rendering with a different sequence preset?
I work with XDCam 422 50mbps footage often but always edit with a Prores timeline and never have any trouble.Colin McQuillan
Vancouver, B.C.“Live, love, laugh and be happy.”
-
I would definitely be doing this in Motion (or After Effect, either will work)
Those are some sizeable chunks! Time to start bringing a lens brush and micro-fibre cloth out on location!!
do you see any picture detail through the chunks?
From this picture it looks to me like any picture detail behind the chunk is lost.. If so cloning-in the surrounding pixels might be the way to go… This band-aid method is most noticeable on moving shots but definitely better than those lens-chunkies.Colin McQuillan
Vancouver, B.C.“Live, love, laugh and be happy.”
-
Is the footage behind the dust-spot still OK looking aside from the brightness/colour levels?
If so try this: (I did this with excellent results to repair light spill/lens flare on priority footage I had no choice but to use)1. Duplicate the footage
2. on the upper layer draw a mask around the dust spot
3. add a colour correction filter and a contrast/or gamma filter.
4. adjust the colour and gamma/contrast until the dust spot looks the the footage outside of the mask area. (the footage is probably slightly washed of contrast and colour saturation from the dust spot)
5. feather out the mask so it blends into the rest of the frame.
6. Duplicate the upper layer and redraw its mask around the next dust spot and adjust the colour/contrast correction to work with that spot.If the footage is optically distorted from the spots then use a combination of the masking steps above and cloning in/blurring the surrounding pixels.
Colin McQuillan
Vancouver, B.C.“Live, love, laugh and be happy.”