final cut pro - shutter plugin?

[smok3]

my workflow is as follows:

shot to:
interlaced xdcam, 1440x1080 50i
the output must be:
smooth 25p
the problem: shutter seems to fast, motion is strobing, especially pans

this seems to go well so far (technically speaking):
sony xdcam transfer (rewraps mxf to mov) -> final cut (editing and grading), just making the use of 'native' xdcam timeline -> exporting natively to interlaced xdcam.mov -> avisynth deinterlacing, stabilizing the noise

the avisynth script i used was like:
# editing in final cut pro, using sony xdcam transfer software to rewrap into mov,
# edit natively in xdcam INTERLACED timeline
# plugins like looks3 seems to get correct field order and there is no chroma bleeding (not so in premiere cs5)
# this script is applied to interlaced xdcam mov with the idea to stabilize noise movements and to make it fake progressive
LoadPlugin("t:\utility\avisynth\ffmpegsource\FFMS2.dll")
LoadCPlugin("t:\utility\avisynth\yadifNew\yadif.dll")
a=ffaudiosource("film.avi")
v=ffvideosource("film.avi")
audiodub(v,a)
assumetff()
FFT3DFilter(sigma=2, sharpen=0.1, interlaced=true)
yadif()
resize(1920,1080) # or any other size you need
# ColorYUV(gamma_y=-34, gamma_u=-34, gamma_v=-34) # 220 -34 = 186 ? <- would this be mac to pc monitor gamma correction?

question:
a. is there a cool way to achive slow shutter effect? plugins for fcp? plugins or scripts for avisynth?
b. other comments on the workflow?

[poisondeathray]

qtgmc has shutter speed motion blur you can try (also better deinterlacer than yadif)

re:vision fx real smart motion blur for AE is ok , and has plugin version for FCP

[smok3]

qtgmc has shutter speed motion blur you can try (also better deinterlacer than yadif)

re:vision fx real smart motion blur for AE is ok , and has plugin version for FCP

thanks, any clues if re:vision can operate on interlaced input correctly? (that could save me some extra steps)

[poisondeathray]

thanks, any clues if re:vision can operate on interlaced input correctly? (that could save me some extra steps)


I don't think so; besides premiere and AE doen't handle interlaced YV12 chroma properly , and upsample is low quality compared to avisynth method (FCP low quality upsample too - point resized chroma) . And this filter functions in RGB (at least the AE version does) , so you will have to upsample to RGB somewhere along the line if you plan to use this

[Mug Funky]

i'd do the project in 50i (transcode to prores if you haven't already - XDCAM crashes final cut like crazy...), then add the motion-blur in avisynth, then output an uncompressed motion-blurred master using qtoutput (it'll do blackmagic 8-bit), then pop that back into FCP as progressive and do your online there (titles, etc).

if you give avisynth the full field-rate to work with, it'll give you very stable motion blur.

[smok3]

i'd do the project in 50i (transcode to prores if you haven't already - XDCAM crashes final cut like crazy...), then add the motion-blur in avisynth, then output an uncompressed motion-blurred master using qtoutput (it'll do blackmagic 8-bit), then pop that back into FCP as progressive and do your online there (titles, etc).

if you give avisynth the full field-rate to work with, it'll give you very stable motion blur.

xdcam 50i seems to edit nicely (no crashes), so i will end it like that and then export as xdcam.mov and then avisynth everything (but it seems the deadline will kill that part...).

[Mug Funky]

you're one lucky man if FCP is holding up on XDCAM :)

[smok3]

yeah, but its really weird, whoever i talk with has a different format preferences for FCP, some guys just finnished a full-lenght movie, editing native 5D AVC stuff... (that would crash every 2 minutes for me...). Lucky? Actually the only good thing about xdcam (so far) seems to be the easy of editing, quality totally sucks (every wide shot is full of blocks, just not the picture one would expect in 2011 - was an older camera).

p.s. i have used the sony xdcam importer utility for rewraping the files (if that makes any difference), also this is some older format, mediainfo reports 4:2:0 color space (and due to really problematic grading it most likely is).

[poisondeathray]

yeah, but its really weird, whoever i talk with has a different format preferences for FCP, some guys just finnished a full-lenght movie, editing native 5D AVC stuff... (that would crash every 2 minutes for me...). Lucky?


Not native in FCP (at least not until FCP X). They would have transcoded to Prores if using FCP , unless they were using Premiere


also this is some older format, mediainfo reports 4:2:0 color space (and due to really problematic grading it most likely is).

There are 2 common varieties of "XDCAM" , both are 8-bit

XDCAM-EX is MPEG2 VBR 35Mb/s 4:2:0

XDCAM-HD is MPEG2 CBR 50Mb/s 4:2:2

[smok3]

hmm, liers! :P (i guess that was premiere crashing every two minutes then...)

[sara.furry]

hmm, liers! :P (i guess that was premiere crashing every two minutes then...)

Or hanging up for ages :x ;)