Forum

Quoted from minimoose

Why would you record with something which isn’t divisible by 30?

200 fps —> 30 fps?

Smoother models etc. ya know, the end product is at 60 fps.

My problem is that the encoder doesn’t encode the full movie, with my 2 minute engie video it did 12 seconds and with another clip it cut off 4 seconds.

I used to be able to encode in full length clips, no matter what fps rate/program i used.

NTSC color encoding is used with the system M television signal, which consists of 29.97 interlaced frames of video per second, or the nearly identical system J in Japan. Each frame consists of a total of 525 scanlines, of which 486 make up the visible raster. The remainder (the vertical blanking interval) are used for synchronization and vertical retrace. This blanking interval was originally designed to simply blank the receiver’s CRT to allow for the simple analog circuits and slow vertical retrace of early TV receivers. However, some of these lines now can contain other data such as closed captioning and vertical interval timecode (VITC). In the complete raster (ignoring half-lines), the even-numbered or ‘lower” scanlines (Every other line that would be even if counted in the video signal, e.g. {2,4,6,…,524}) are drawn in the first field, and the odd-numbered or “upper” (Every other line that would be odd if counted in the video signal, e.g. {1,3,5,…,525}) are drawn in the second field, to yield a flicker-free image at the field refresh frequency of approximately 59.94 Hertz (actually 60 Hz/1.001). For comparison, 576i systems such as PAL-B/G and SECAM uses 625 lines (576 visible), and so have a higher vertical resolution, but a lower temporal resolution of 25 frames or 50 fields per second.

The NTSC field refresh frequency in the black-and-white system originally exactly matched the nominal 60 Hz frequency of alternating current power used in the United States. Matching the field refresh rate to the power source avoided intermodulation (also called beating), which produces rolling bars on the screen. When color was later added to the system, the refresh frequency was shifted slightly downward to 59.94 Hz to eliminate stationary dot patterns in the difference frequency between the sound and color carriers

This is why. Nowt to do with the human eye. You certainly dont add the two eyes together to get 60Hz! One thing I do know about is the human eye and vision.

Quoted from Rake

[…]
ITT: True story in good english.

The reason 30/60 fps are used, is only because of them looking good and fluid. Then again, as far as I know, 24 fps should be used on video material that is to be uploaded on youtube, as that’s the max supported there, and 30fps makes for slightly jittery playback, since YT drops 4 frames per second. Correct me if I’m wrong however, I just remember reading that somewhere.

It used to be 24, YouTube does 30 nowadays.

The only way that 24fps could ever look good though is with interlacing, and that crap gives me a headache.

Quoted from minimoose

[…]

Im not talking about how high it is, im saying, why would you record at 200 fps when it isn’t divisible by 30 or 60… Surely that means when you’re encoding to 60 or 30 fps you’re missing frames at integer times, unless you use frame blending, but then even that would work better if you use a whole number ratio. 240/30 = 8, 200/30 = 6.66

If you’re frame blending it shouldn’t matter, but yes, if you are just dropping frames then it’s not a good idea to be recording at 200.

Quoted from pykow

just record at 30 fps. Thats enough and it will be clearly smoothie ;)

Leave this thread. Now.

Recording at 30 fps is only rivalled in stupidity by recording in <29 fps. Footage recorded at 30 fps will look choppier than 60fps made into 30fps.

Just try a lower DXlevel while recording.
so for example use the command: mat_dxlevel 90.
you still have all the particles and you will get more performance.
just try it by your self. Start TF2 with the PLDX tool. Open console and typ the command mat_dxlevel 90. than just start your demo files and record.

this will fix your problem ;)

BTW. If u dont have enough performance and u want to create a move. Then is 30 FPS the minimum ! Thats all what im saying. Ofcourse 60 FPS is better.

I hope this will solve your problem. When im try to encode it with the pldx tool. Ive got the same problem. So try this solution ;)

You do realize there’s a massive performance loss when using dxlevel 90 instead of 95 or 98, due to the older (read worse) technology behind it. That’s the theory anyway, and testing on my pc also suggests that. And why would you need “better performance” anyway, when you can just use startmovie to record 3500fps on any computer that loads tf2.

Quoted from pykow

Start TF2 with the PLDX tool. Open console and typ the command mat_dxlevel 90. than just start your demo files and record.

you should really stop posting