I just recently had to restore my system and had to reinstall everything again inculding my favorite converter (canopus procoder). I also downloaded all the good codecs that i used to have before (so i think). Problem is when i try to use the 23.97 fps or 24 fps 3:2 pulldown option i get canopus has encoutered a problem and needs to close. the source file is avi at 25 fps. Now before i did the restore that file would work in the same program just fine. In fact canopus is the the only program i know of that will convert 25 fps avi to 30 fps mpeg2 useing the pulldown option (with no screen jerk- very smooth). i tried to reinstall again and that did not work. it's not an audio problem either because if use the 30 fps option it works but with screen jerk. what do i need so canopus will respon to the pulldown option. could it be the one codec i don't have? somthing tells me no because it shows what codec your useing and it's the ones i allways use divx, xvid, ffdshow,ect. THANX MUCH
If you have an application crash that is reproducible like in your case, then it's a good idea to look in the debug info. You should see something about the execution address cs:eip with a bunch of hex digits after it. Copy & paste the hex digits into Google. Also search the application site support database if there is one. You may find a fix if you get a hit on the cs:eip (that's the register in the processor that points to the instruction to execute. On a crash that's usually the instruction that caused it to crap out.)
I'm not sure what you mean. My application didn't crash, I had to do a full system restore for other reasons. But now that iv'e reinstalled everything (canopus, codecs, and all the other programs i used to have. I'm having the same problem with canopus i did when i first got the program. after installing some codecs and other things, that i can't remember that problem went away with the pulldown not working. and it's doing it again because i must not have somthing i should have and i don't know what it is. The application itself and all the codecs can be ruled out i think. I don't know. very frustrating.
That's a crash. If you looked in the debug info you would see the cs:eip info as I mentioned. If you can't reproduce the problem or get any error messages I don't know how anyone can diagnose it. All you can do is search on a description of the problem or try to reproduce it so you can get some debug information.
