Why can't I find what's wrong with failed processing?
Posted: Mon Oct 03, 2011 9:40 pm
I've processed a video 5 times and it always goes only to 2:20 (out of 7 something).
I checked a dozen ways to Sunday to confirm no missing frames, no extra tracks, etc.
It's processing #6 try right now, and all I've done differently is to go to the end point (2:20), and delete the title slide that it appeared to stop on, and the one that comes shortly after, and re-create them. Then I dragged the video clip this break occurred in, to another track, and re-processed it, then dragged it back. Everything again appears okay.
I'm not worried about the settings I chose, they are the same ones I use for all my videos and in fact had processed 2 other videos out of this material and they were fine.
The end format is .mp4, which I can't play on my computer. (DivX used to work but for some reason doesn't any more.) The only way I've been able to tell something is wrong is to view it after I've uploaded it. Of course I realize that I might have been able to tell by the fact that the video didn't take as long as it should to process, or to upload to the site, but I only figured that out in hindsight. In fact right now I'm still not sure I've fixed it because while it does appear to be taking a good chunk more time to process, I'm rather suspicious that it should be taking a lot longer. Now I have to wait at least 2.5 hours to know for sure.
Is there something technical I could do to pin down a problem like this, to save myself a lot of agony and time? If one part of the fix is to delete the entire clip where the break appears to happen, and create it, is there a trick to pinning down where the start/end points are? I have about 60 clips from this video and have always been confused about how I could know where in the full video length one particular clip comes. E.g., this problem clip might start at 3:30 through 4:15. How does one figure that out?
[EDIT: Ok it did fail again. The file size is the same ... I am going to try to upload it anyway just to see what happens but would appreciate another suggestion for debugging this file.]
Thanks.
I checked a dozen ways to Sunday to confirm no missing frames, no extra tracks, etc.
It's processing #6 try right now, and all I've done differently is to go to the end point (2:20), and delete the title slide that it appeared to stop on, and the one that comes shortly after, and re-create them. Then I dragged the video clip this break occurred in, to another track, and re-processed it, then dragged it back. Everything again appears okay.
I'm not worried about the settings I chose, they are the same ones I use for all my videos and in fact had processed 2 other videos out of this material and they were fine.
The end format is .mp4, which I can't play on my computer. (DivX used to work but for some reason doesn't any more.) The only way I've been able to tell something is wrong is to view it after I've uploaded it. Of course I realize that I might have been able to tell by the fact that the video didn't take as long as it should to process, or to upload to the site, but I only figured that out in hindsight. In fact right now I'm still not sure I've fixed it because while it does appear to be taking a good chunk more time to process, I'm rather suspicious that it should be taking a lot longer. Now I have to wait at least 2.5 hours to know for sure.
Is there something technical I could do to pin down a problem like this, to save myself a lot of agony and time? If one part of the fix is to delete the entire clip where the break appears to happen, and create it, is there a trick to pinning down where the start/end points are? I have about 60 clips from this video and have always been confused about how I could know where in the full video length one particular clip comes. E.g., this problem clip might start at 3:30 through 4:15. How does one figure that out?
[EDIT: Ok it did fail again. The file size is the same ... I am going to try to upload it anyway just to see what happens but would appreciate another suggestion for debugging this file.]
Thanks.