<br><br><div class="gmail_quote">On Wed, Feb 11, 2009 at 11:27 PM, Nigel Pearson <span dir="ltr"><<a href="mailto:nigel@ind.tansu.com.au">nigel@ind.tansu.com.au</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
I am trying to share commercial block markup data with someone local,<br>
and am having problems with the accuracy of the cutlists.<br>
<br>
It seems that my recordings are often up to 3s offset with his<br>
cutlist data. Looking at the recorded table, the starttime is<br>
_always_ an integral minute (i.e. 20:27:00, 21:30:00).<br>
<br>
Haven't looked yet, but suspect its just the way the code works.<br>
e.g. Recording 1 ends at 8:30. Recording 2 starts at 8:30 on<br>
the same card, The scheduler and file IO takes 3sec to create<br>
a new recording file, update the database, et c., but the start<br>
time is recorded as the scheduled time of 8:30.</blockquote><div><br>Just curious. How does *your* system know, given only the cutlist and the starttime to jump/cut at the right places? It seems that even your local data would suffer from this same "drift" given only those pieces of information.<br>
<br>Kevin</div></div><br>