|
|
Posted by Steve Wills on 08/22/06 23:17
Wow...Thank you very much!
On 8/21/06 10:00 PM, in article
rebus-CD1B04.19004421082006@news.isp.giganews.com, "rebus"
<rebus@bctonline.com> wrote:
> In article <C10F1067.1A4F4%steventv@insightbb.com>,
> Steve Wills <steventv@insightbb.com> wrote:
>
>> Thank you!
>>
>> Yes, I'm using DV.
>>
>> The slo-mo quality seems to rather poor in FCP.
>>
>> Re-shooting in progressive at 60fps may be the answer I really need.
>>
>> Thank you for the reply. I'll try Shake.
>>
>
> OK! here are a couple of tips for you.
>
> you need 3 nodes, filein - setalpha - fileout
>
> in filein set de-interlacing to even
> under the timing tab set retime to speed,
> use the slider to adjust the speed.
> leave other settings as is until you
> get the speed right (see below).
>
> You may not need the setalpha node, if you do
> set alpha to 0. My file had random lines in alpha
> after quicktime conversion.
>
> The file out node sets the file format and codec. I used
> Quicktime and apple DV/DVCPRO-NTSC.
>
> Performance: you have to render a flipbook to play
> at full speed, even with the basic setting.
> When you are ready for the best result, set retimeMode
> in the filein parameters to adaptive. Run a new flipbook
> it will take a lot longer, but will look better.
>
> To get a file you need to render the fileout node, there
> is a maxthread field. try higher numbers for better speed.
>
> Finally, the file. If you set in and out points and send to
> Shake, Shake can see the whole clip. and when you change
> the speed all the frames get renumbered. Make a subclip
> and export it to quicktime.
>
> And after all that, it still won't look as good as shooting
> high speed.
>
> good luck!
Navigation:
[Reply to this message]
|