|
|
| Belgabor |
| Posted: Feb 21 2003, 01:39 PM |
 |
|
Developer of VirtualdubMod
Group: VirtualdubMod Team
Posts: 100
Member No.: 998
Joined: 24-November 02
|
@phaeron: I don't know if you read the doom9 forum, but some people there have a strange crash, have a look here please.
Cheers
Belgabor
--------------------
[VirtualDubMod Homepage]
Please submit any bugs/patches/feature requests also using the respective tracker on our sourceforge page |
|
| phaeron |
| Posted: Feb 22 2003, 03:40 AM |
|
|
Virtualdub Developer
Group: Administrator
Posts: 7773
Member No.: 61
Joined: 30-July 02
|
It's due to an uninitialized variable in the frame timing that is now being differently uninitialized in 1.5.0 -- in effect, a bug that was there before but was harmless until now. Strangely enough, neither I nor three other people encountered this until after release, probably because it is sensitive to your UI setup. 1.5.1 will be out within a few days to address this and a few other bugs.
To fix it, patch PositionControl.cpp to check the numerator (getHi()) instead of the denominator (getLo()), and then patch InitStreamValues() in command.cpp to check whether an input file is actually loaded before setting the frame rate.
|
|
