|
|
| synogen |
| Posted: Apr 13 2003, 08:53 AM |
 |
|
Unregistered
|
i opened one file with 33178 frames and 23,976 fps with virtualdub 1.5.1 and exactly the same file with virtualdubmod 1.4.13, then skipped to the last frame to get the total video length and while
vdub showed
0:23:03.800
vdubmod showed
0:23:03.788
as total length
so i calculated manually
33178 frames / 23.976 fps = 1383,8004671338004671338004671338 secs,
which would be (rounded of course) virtualdubs result, so my question is if this is a bug in virtualdubmod ?
ps: the difference in lengths gets worse the longer the file is
|
|
| phaeron |
| Posted: Apr 13 2003, 09:28 AM |
|
|
Virtualdub Developer
Group: Administrator
Posts: 7773
Member No.: 61
Joined: 30-July 02
|
The accuracy of VirtualDub's timing calculations was improved in 1.5. VirtualDubMod is showing an error in your case because you are using a version that is based off of the official 1.4.13 codebase, which computes the duration on the timeline as follows:
1,000,000 / 23.976 fps = 41,708 microseconds/frame
41,708 microseconds/frame * 33,178 frames = 1,383,788,024 microseconds
1,383,788,024 microseconds = 0:23:03.788
1.5+ uses the direct rational framerate from the AVI. The VDubMod team is probably already integrating the changes over if they haven't already done so.
|
|
| synogen |
| Posted: Apr 13 2003, 10:35 AM |
|
|
Unregistered
|
ok, thx a lot for the valuable help |
|
|
