FPS question
- LightningCountX
- Joined: Tue May 20, 2003 8:35 am
- Location: Bayside, NY Interests: Your Mom ^_^
- Contact:
FPS question
Whats the difference between 24 fps and 29.97 and all the other ones? Just wanna start experimenting with different things in editing.
- Anime2Envy
- Joined: Tue Jan 07, 2003 11:37 pm
- Location: Ohio, for now
- Contact:
I will assume that you know what FPS means. It takes roughly 24 FPS to fool the human eye. Standard NTSC resolutions are 23.976 and 29.97 while PAL is 25 FPS. 24, 30 FPS are just rounded numbers commonly used on computer systems since there is no set FPS. With pure progressive footage it is very hard to tell the difference between the different rates.
The way I see it, it is best to encode in 23.976 FPS, This will look good on a computer and can be easily transferred to a DVD with the "3:2 pulldown flag" set.
That should cover the basics. If I messed anything up let me know.
.
The way I see it, it is best to encode in 23.976 FPS, This will look good on a computer and can be easily transferred to a DVD with the "3:2 pulldown flag" set.
That should cover the basics. If I messed anything up let me know.
.
- DJ_Izumi
- Joined: Wed Oct 03, 2001 8:29 am
- Location: Canada
- Contact:
Actually, a lot of Anime DVD's are in both 30 and 24fps. It varies threwout the episodes as to weather the content is at 'true' 30fps interlacted, or if it's 30fps that's been interlaced up from 24fps using a 3:2 pulldown.
So when you decimate the true 30fps sections and everything else down to 24fps, you actually CAUSE jerkyness. Meanwhile, you don't, and just de-interlace you get ghosting. Damned if you do, damned if you don't.
Of course, usually less then 25% of the episode is at 30fps, so it's best to decimate.
So when you decimate the true 30fps sections and everything else down to 24fps, you actually CAUSE jerkyness. Meanwhile, you don't, and just de-interlace you get ghosting. Damned if you do, damned if you don't.
Of course, usually less then 25% of the episode is at 30fps, so it's best to decimate.
- bum
- 17747114553
- Joined: Sat Nov 08, 2003 9:56 pm
- LightningCountX
- Joined: Tue May 20, 2003 8:35 am
- Location: Bayside, NY Interests: Your Mom ^_^
- Contact:
in vdub(1.4.10) i changed the settings to...
FPS: 23.976
Frame Rate Decimation: Process All Frames
Inverse Telecline(3:2 PullDown Removal): Reconstruct from fields - adaptive
having these changed settings all i notice is that my huffyuv's dont lag and skip as much as the ones under 29.97 with all frames and none(progessive).
Are these the right settings to use?
FPS: 23.976
Frame Rate Decimation: Process All Frames
Inverse Telecline(3:2 PullDown Removal): Reconstruct from fields - adaptive
having these changed settings all i notice is that my huffyuv's dont lag and skip as much as the ones under 29.97 with all frames and none(progessive).
Are these the right settings to use?
- DJ_Izumi
- Joined: Wed Oct 03, 2001 8:29 am
- Location: Canada
- Contact:
- bum
- 17747114553
- Joined: Sat Nov 08, 2003 9:56 pm
- DJ_Izumi
- Joined: Wed Oct 03, 2001 8:29 am
- Location: Canada
- Contact:
Lithtech? I do not speak of the Lithtech engine. I do not speak of the Quake 3 engine.
Half-Life and all mods for Half-Life use the Half-Life engine. (The term here people, is 'Duh') Half-Life's engine dates back to 1997, while it is based on the core from the old Quake 1 engine, 70% of the Half-Life engine is new code, very little of the Quake 1 engine even exists in the HL engine. Offically, and legally however, Half-Life is it's own engine it is not by far considdered to be a Quake 1 Engine mod.
I find it interesting how you say you get 150fps in Q3 in an attempt to correct me, especially as Quake 3 isn't Half-Life. This is like saying 'You're wrong! A Volkswagon Jetta is really fast, because my Lambergini (sp?) is fast!."
On a side note, getting 150 frames per second in Quake III is also pretty fruitless, you're monitor is most likely operating somewhere between 70-90hz, this of course means that the screen is only refreshed about 80 times per second. So while you may be rendering at more 150 frames per second in the game, your screen is only showing you somewhere around 70-90 FPS. So a lot is going down the drain.
Half-Life and all mods for Half-Life use the Half-Life engine. (The term here people, is 'Duh') Half-Life's engine dates back to 1997, while it is based on the core from the old Quake 1 engine, 70% of the Half-Life engine is new code, very little of the Quake 1 engine even exists in the HL engine. Offically, and legally however, Half-Life is it's own engine it is not by far considdered to be a Quake 1 Engine mod.
I find it interesting how you say you get 150fps in Q3 in an attempt to correct me, especially as Quake 3 isn't Half-Life. This is like saying 'You're wrong! A Volkswagon Jetta is really fast, because my Lambergini (sp?) is fast!."
On a side note, getting 150 frames per second in Quake III is also pretty fruitless, you're monitor is most likely operating somewhere between 70-90hz, this of course means that the screen is only refreshed about 80 times per second. So while you may be rendering at more 150 frames per second in the game, your screen is only showing you somewhere around 70-90 FPS. So a lot is going down the drain.
- Scintilla
- (for EXTREME)
- Joined: Mon Mar 31, 2003 8:47 pm
- Status: Quo
- Location: New Jersey
- Contact:
- LightningCountX
- Joined: Tue May 20, 2003 8:35 am
- Location: Bayside, NY Interests: Your Mom ^_^
- Contact:
eh, i still havent learned the whole d2v scripting thing, so im just using vdub till i get that. Are the settings i have above correct?Scintilla wrote:If you want 23.976 progressive footage, why don't you just Telecide() and Decimate() the D2Vs in AVISynth before feeding them into VirtualDub? Then you won't have to touch VDub's frame rate settings.