Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo
what means this messages:
17:25:00:02 channel 1 Timecode discontinuity: 2 frames missing at frame=4304308
17:25:00:02 channel 0 Timecode discontinuity: 2 frames missing at frame=4304363
and this message
15 13:58:50.763186 chan 0: lastframe=3993333 tick/2=4006709 hwdrop= 0 tc=13:57:38:23 tc_err=562
15 13:58:50.777457 chan 1: lastframe=3993278 tick/2=4006229 hwdrop= 0 tc=13:57:38:23 tc_err=562
15 13:59:08.129537 chan 0: Timestamp differs from expected by -77 ms
15 13:59:08.131902 chan 1: Timestamp differs from expected by -77 ms
15 14:59:07.647172 chan 0: Timestamp differs from expected by -77 ms
15 14:59:07.662521 chan 1: Timestamp differs from expected by -77 ms
15 15:59:08.134093 chan 1: Timestamp differs from expected by -10077 ms
15 15:59:08.134138 chan 1: lastframe=4173714 tick/2=4186665 hwdrop= 0 tc=15:57:46:07 tc_err=-252
15 15:59:08.168421 chan 1: Timestamp differs from expected by 9999 ms
15 15:59:08.168461 chan 1: lastframe=4173715 tick/2=4186666 hwdrop= 0 tc=15:57:56:08 tc_err=250
15 15:59:08.185052 chan 0: Timestamp differs from expected by -77 ms
15 15:59:08.223077 chan 1: lastframe=4173716 tick/2=4186667 hwdrop= 0 tc=15:57:56:11 tc_err=2
15 16:59:07.658461 chan 1: Timestamp differs from expected by -76 ms
15 16:59:07.658512 chan 1: lastframe=4263702 tick/2=4276653 hwdrop= 0 tc=16:57:55:20 tc_err=-2
15 16:59:07.664627 chan 0: Timestamp differs from expected by -76 ms
15 16:59:07.704325 chan 1: lastframe=4263703 tick/2=4276654 hwdrop= 0 tc=16:57:55:23 tc_err=2
Timecode discontinuity: We expect consecutive frames to have consecutive timecodes, i.e. timecode increments by one for each successive frame. If that is not the case, a warning is displayed.
If your timecode source is not locked to video or the different video inputs are not locked to each other, small timecode discontinuities can occur. These are not usually a cause for concern. The recorded file does not have per-frame timecodes, only a start timecode, so there will be no discontinuity in that.
Timestamp differs from expected: We expect capture times of successive frame (as reported by DVS card) to differ by approximately one frame period. If this is not the case, a warning is displayed.
There can be occasional glitches in reported timestamp. It's hard to say if yours are a cause for concern. Could there have been any disturbance to input video at this time?
I don't know. The Servers are not in house.
Could a to large Timestamp differs interrupt the recording?