Hi! Ralph Glasstetter wrote:
>>I added some additional checks. dvbcut will now tell you how many video >>frames are missing (approximately, at least). If there are too many of >>them, you'd better cut before and after the gap. > > > Ok, I see... but how do I have to interprete this... > > sequence number reset (6 => 0) > inserting delayed picture (8) > missing frame(s) before B frame 49426 (3 != 2) > missing frames in GOP (49416, 49434): 19542 > > Does all this relate to the same error? Yes, more or less. The number of missing frames is calculated from the timestamps of the corresponding I frames (49416 and 49343), the expected number of frames (pts difference / time for a single frame) and the actual number of frames (i.e. 49343-49416). If there is a difference, the message appears. I've never seen such a huge gap, though. > Just stored the messages in a log and don't know if they occured at the same > time... ;-) According to the frame index numbers, they did. > If not, it would be helpful to have the frame number or the time stamp where > the first errors occured... That's not hard. The error occurred somewhere between frame 49343 and frame 49416. > I don't have to worry about the missing frames around GOP 49426, because I > cutted the video on my PVR at that position. And the PVR didn't correct the timestamps after the cut? That would explain the missing ~12 minutes. > And since it cannot cut > everything up to the end I always have to leave a few frames at the end. That's another bug^H^H^Hfeature I would like to change... Michael. ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ DVBCUT-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dvbcut-user
