|
Senior Member
|
Quote:
Quote:
|
But wouldn't converting that to 29.97fps not drop any frames, assuming the source framerate was 29.97fps before making it VFR? I haven't noticed any by doing things this way.
|
If the source framerate is 29.97fps it's CFR and you should not be having this discussion in the first place. If the source is VFR you shouldn't say it has "a framerate", because it doesn't and it's much easier once you've come to terms with that.
|
What I meant is, a lot of h264 raws these days do this:
Quote:
..1186,1189,23.9521
1190,1279,29.9700
1280,1283,23.9521
1284,1323,29.9625
1324,1327,23.9521
1328,1347,29.9850
1348,1351,23.9521
1352,1376,29.9760
1377,1380,23.9521
1381,1410,29.9700
1411,1418,24.0240
1419,1448,29.9700
1449,1452,23.9521
1453,1497,29.9601
1498,1501,23.9521
1502,1551,29.9760
1552,1559,23.9521
1560,1584,29.9760
1585,1588,23.9521
1589,1688,29.9760..
|
but the actual playback should be 29.97 fps. That's taken from the timecodes I got out of Shinsen-Raws's ZTC 21 mp4.
Quote:
Originally Posted by TheFluff
This is correct but I don't get why you'd use it at all.
|
Because I don't know how to use avs =\ Since that is the first method I found that works, that's what I've been doing.
My encoding needs mostly lie with OP and ED sequences only, so I don't really run into any problems taking that 120fps avi, dumping it in vdub, and then doing constant 23.976 or 29.97 over the appropriate 1:30 minute framerange.
|