Log in

View Full Version : I am "losing time" after encoding... frustrating...


EWR-COflyer
19th January 2003, 15:43
Here's my scenario... everything was going just fine until my XP system files were corrupted, I had to debug my HD, reinstall, etc etc etc. Now I have a really peculiar problem that I can't seem to shake, and it is not just on one DVD, seemingly all of them now. (Perhaps it was the old ones too, I haven't looked yet)

I am using SmartRipper, VFAPI, CCE, pulldown and IfoEdit. DELL P4 1.7G, 600+MB RAM, etc.

For Example:
DVD to backup - 127mins
.m2v ripped from DVD played back - 86mins
*d2v-vfapi.avi - 127 mins
.m2v after CCE re-encoding - 52mins
.m2v after pulldown - 52 mins
sum of time from .VOBs after IfoEdit authoring - 103mins

Times are from playing via Windows MediaPlayer & RealOne Player, both have given me idential #'s to work with.

But, the whole movie appears to be there, from beginning to end credits... the timing just appears to be way off base. Even though the .m2v's say 52mins, the movie is there from start to credits, it's not like it just "stops" midway through.

Another movie that I backed up had a similar issue, although I don't have those files on my hard drive anymore to give time stamps. Movie run time is 131mins, however when I played the backed up version on the DVD player there is a major discrepancy in run-time (as shown on the DVD time counter) when comparing the same scene on each version.

For example, the originial DVD shows something like ~127min for the start of the credits, yet the backup displays something like ~108mins. Even though the whole movie appears to be backed up and there is nothing choppy or cut out of it as far as I can tell.

Yet another example, Lord of the Rings - Fellowship... DVD says runtime is 178 mins, my backup plays the whole movie yet it tells me that the movie was 130 mins long.

Any ideas?

facts
24th January 2003, 05:49
i'm having the same problem too.

EWR-COflyer
25th January 2003, 16:38
Somehow it works now... I re-reinstalled SmartRipper 2.41 and now it works. I don't quite understand why it didn't work the first time, I *DID* reinstall it once already.

But who cares, it works!

facts
25th January 2003, 16:40
apparently this bug is due to using forcefilm on NTSC films and is a problem with ifoedit.