-
i made a big big mistake!
allright! i screwed up! i have to deliever a music video today! it is 4 minutes long and i need to put it on digibeta. instead of rendering it 29.97 i did render the video in 30fps. what do i do now?
is there a way to convert the footage to the right frame rate without rerendering it. that would save me a lot of trouble!
would be grateful for any help!
fow
-
8 Replies
-
How did you render it to 30fps? If it is DV, it will be 29.97fps…PERIOD. You can’t get it to 30fps. It can only be 29.97. ALL SD video is 29.97…unless it is black and white.
NOW, do you mean the TIMECODE is NON-DRop frame, instead of being drop frame? That is an EASY fix. Press Apple-0 to get to your timeline settings and switch to drop frame.
Shane
Littlefrog PostGETTING ORGANIZED WITH FINAL CUT PRO DVD now for sale!
http://www.lfhd.net -
i created the piece in 3D … i just need final cut to output it on a digibeta! the footage is 30FPS!
-
Then make a 29.97 fps timeline, uncompressed SD or ProRes, and copy and paste the footage into that and render.
DO you have a capture card? You might use the presents for that card…Kona Uncompressed 8-bit, for example.
Shane
Littlefrog PostGETTING ORGANIZED WITH FINAL CUT PRO DVD now for sale!
http://www.lfhd.net -
really? that simple? don’t i have problems with the synch or stuttering?
otherwise! YOU SAVED MY DAY!
thanks a lot
-
Unless I’m really mistaken, 29.97 runs at 30fps. The 29.97 is just a counting system–no actual frames are “dropped” during playback, but the numbers on the timecode are so it reflects real time. That way a 30 minutes show is actually 30 minutes long.
Or I could be completely wrong. I need to google it again.
Michael.
-
[Michael Hancock] “Unless I’m really mistaken, 29.97 runs at 30fps.”
You are mistaken. 29.97 is 30fps, but doesn’t really run at 30 SOLID FPS. It runs slightly slower….so after an hour it really is only 59 min, 58 seconds or so.
[Michael Hancock] “The 29.97 is just a counting system–no actual frames are “dropped” during playback, but the numbers on the timecode are so it reflects real time. That way a 30 minutes show is actually 30 minutes long.”
You have this backwards. You are talking about drop frame and non drop TIMECODE. We aren’t talking timecode here, but ACTUAL frame rate.
Are you SURE that it is 30solid fps? Because I swear, that nothing runs at 20 solid fps…because color signals run at 29.97fps…it was blackand white TV that was 30fps…and when color came along, it slowed it to 29.97, thus the need for drop frame code.
And yes, it will be that simple.
Shane
Littlefrog PostGETTING ORGANIZED WITH FINAL CUT PRO DVD now for sale!
http://www.lfhd.net -
Like I said, I could be wrong!
Thanks for the clarification Shane.
Michael.
-
When NTSC standards were laid down in 1948 there was only luma. The frame rate was set at 30 or more accurately 60 fields per second. The reason this was selected was so vertical sync could be tied to the AC frequency the TV was plugged into.
When color came along instead of telling everyone to throw out their TVs and buy a new ones. Engineers settled on a system of integrating a chrominance subcarrier onto the existing luma signal. But there was too much interference between the two. To make room for color the luma frequency was dropped .001% to 59.94. This made for exceptable video but interference can still be seen in dot crawl on hard edges and rainbowing in areas of tight patterns.
Drop frame was created to compensate for this frequency change so TC will match the wall clock. In a 1 hour program non drop TC is 108 frames over the wall clock. So the first 2 frames in TC at the start of every minute are skipped except minutes that contain a zero ie 00, 10, 20, 30, 40, & 50.
The difference between 30 and 29.97 is so slight that no one can tell the difference. Just drop the footage into a NTSC sequence and ETT away. But if you are really concerned you can conform the QT in Cinema Tools to 29.97. I guarantee you’ll not be able to tell the difference.
Reply to this Discussion! Login or Sign Up