-
Andrew Kramer FPS question…
Having a bit of trouble with a SWF file that’s been rendered out to a 30fps quicktime and given to me to make a PAL DVD from…(Yes, I told them to animate it at 25, but would they listen?…evidently not!)
Anyway. I downloaded AK’s FPS converter preset and watched the tute..Have I got this right? :-
-I interpret the 30fps QT movie to conform to 25fps (thus shortening it quite considerably)
-Then I make new comp, which is 25fps.
-I add preset and set source and target fps to 30/25 respectively.
—————————————
This gives me a 1’42” clip that is now 56″ long…is that right?Is there any way I can get the clip back to the original length and still keep it decent quality? I’ve timestretched it back to orig length, but it’s taking 20+ seconds just to render one frame and that’s with timewarp set to whole frames! So as you can appreciate I can barely see what’s going on to see if I’m on the right track, even when set to 1/4 res on draft.
I don’t want to set off a many hours render if I’ve got it wrong! I know I’m on a slow PC, but is this how slow working like this should be!?
Any thoughts people?
Thanks.
*Production Studio Premium CS2 / *Combustion 3 / Mocha v1
————————————-
Win XP Pro SP2 / Intel P4 3GHz / 2GB RAM / GeForce FX5200 / DeckLink Pro / Roland DS-5 monitors / Sony BVM-20G1E / DVS SDI Clipstation / Wacom Intuos 3 A4 / 110GB boot/80GB media/600GB RAID-0 -
4 Replies
-
is the 1:42 length the length of the footage after altering the frame rate in the interpret footage settings, or prior to altering the fraem rate? once you change the frame rate from 30 to 25 the duration of the clip should increase too (by 120%, if my math is right). so when you drop that on the make comp icon, it will create a comp witht the false length. then when you apply andrew’s frc it should conform it back to the original duration.
you can do this another way too, without timewarp… so you can compare results, first duplicate your footage and set the interpret footage frame rate of the duplicate back to the original frame rate (30). then drag that to the make comp icon. set the comp’s frame rate to 25fps, then enable frame blending with the method set to pixel motion.
you won’t have as much control over the frame interpolation as you would with timewarp, but this can produce pretty decent results.
looking back at your numbers, things aren’t adding up…. 1’42” and 56″… 56″ is nearly half of the original duration… i think somewhere there may be a wrong value…
Kevin Camp
Designer – KCPQ, KMYQ & KRCW -
Hi Moldy,
I ended up just dropping the un interpretted footage into a 25fps comp. It stayed the same length, but was a bit jerky. I was in a bit of a rush on this one and the client couldn’t tell the difference (they rarely do, even if you’ve spent hours on something!)
However, looking back at it – I looked at the original QT mov’s proprties in Qucktime – it said it was 14.? fps (sorry at home and can’t remember exact number) yet in AE it said it was 30.303 fps (?!?) I know QT usually lies about such things, but this may explain the 1.42 > 56 secs thing.
I still don’t understand why the timewapr thing was taking so long just to render one frame! It hung for almost a minute per frame when set to pixel motion. Odd.
*Production Studio Premium CS2 / *Combustion 3 / Mocha v1
————————————-
Win XP Pro SP2 / Intel P4 3GHz / 2GB RAM / GeForce FX5200 / DeckLink Pro / Roland DS-5 monitors / Sony BVM-20G1E / DVS SDI Clipstation / Wacom Intuos 3 A4 / 110GB boot/80GB media/600GB RAID-0 -
glad it all worked out in the end…
the only thing i can figure for the render time would be if ae was really trying to generate a bunch of frames between the actual frames… a situation where it needed to generate frames to generate more frames. but i’m not sure.
i’ve uploaded a preset, EZFrameRateConverter, that should do Andrew’s frame rate conversion technique without needing to use the interpret footage window to modify the original frame rate or enter values for the source frame rate or target frame rate. i had actually tried this before, but it only worked in one specific situation (oops)… this one should work much better. it uses and expression on time remapping to ‘see’ all the frames in the footage, then uses timewarp to create the new framerate, giving you all the interpolation and fine tuning options in timewarp.
the only oddity is if you want to decrease the frame rate, you should change the time measure in the timeline to frames (rather than timecode). just command-click (mac) or ctrl-click(windows) the timecode in the timeline to switch measures. but if you want to increase the frame rate, then you should use the timecode measure.
Kevin Camp
Designer – KCPQ, KMYQ & KRCW -
Excellent stuff..have d/loaded all your presets and will let you know how they go! Cheers.
*Production Studio Premium CS2 / *Combustion 3 / Mocha v1
————————————-
Win XP Pro SP2 / Intel P4 3GHz / 2GB RAM / GeForce FX5200 / DeckLink Pro / Roland DS-5 monitors / Sony BVM-20G1E / DVS SDI Clipstation / Wacom Intuos 3 A4 / 110GB boot/80GB media/600GB RAID-0
Reply to this Discussion! Login or Sign Up