Hi all,
I noticed that the beginnings of my recorded TV programs were truncated, so
I looked in recordserver-1000.log and saw that recordserver was starting all
recordings 45 seconds *after* the scheduled start time for each program:
2009-03-04 17:30:45,001 INFO recordserver.py (944): going to record: Wed
Mar 04 17:30->18:00 (17:30) I9.28458213.microsoft.com BBC World News
2009-03-04 17:30:45,004 INFO recordserver.py (962): start recording: Wed
Mar 04 17:30->18:00 (17:30) I9.28458213.microsoft.com BBC World News
2009-03-04 17:30:45,516 INFO recordserver.py (1329): RECORD_START Wed
Mar 04 17:30->18:00 (17:30) I9.28458213.microsoft.com BBC World News
2009-03-04 17:59:51,116 INFO recordserver.py (1337): RECORD_STOP Wed Mar
04 17:30->18:00 (17:30) I9.28458213.microsoft.com BBC World News
In the sample above, the recording should have started at 17:30:00, but it
started at 17:30:45 instead. My local_conf.py has 'TV_RECORD_PADDING_PRE =
0', so the recordings should be starting at the designated time. Anyway, I
decided to compensate by changing this value to 'TV_RECORD_PADDING_PRE =
45'. However, this resulted in the recordings starting 15 seconds *before*
the scheduled start time, as shown below (17:59:45 instead of the expected
18:00:00):
2009-03-05 17:59:45,003 INFO recordserver.py (944): going to record: Thu
Mar 05 18:00->18:30 (18:00) I28.28460456.microsoft.com BBC World News
2009-03-05 17:59:45,006 INFO recordserver.py (962): start recording: Thu
Mar 05 18:00->18:30 (18:00) I28.28460456.microsoft.com BBC World News
2009-03-05 17:59:45,520 INFO recordserver.py (1329): RECORD_START Thu
Mar 05 18:00->18:30 (18:00) I28.28460456.microsoft.com BBC World News
2009-03-05 18:29:59,563 INFO recordserver.py (1337): RECORD_STOP Thu Mar
05 18:00->18:30 (18:00) I28.28460456.microsoft.com BBC World News
I played around with various values for TV_RECORD_PADDING_PRE and found that
if the value is 15 to 45, recordings will start 15 seconds too early. If
the value is less than 15, then recordings will start 45 seconds too late.
I see that there's in comment in local_conf.py that, although the padding
time is designated in seconds, precision is only at the minute level. This
could explain why I couldn't set a start time in between 15 seconds too
early or 45 seconds too late (-15 secs to +45 secs = 60 secs). However, I
am able to set TV_RECORD_PADDING_POST to sub-minute precision. In the first
set of log entries above, note that the stop time for the program was at 51
seconds (9 seconds before the scheduled stop time). I added some seconds to
TV_RECORD_PADDING_POST and you'll note in the second set of log entries that
stop time was at 59 seconds (1 second before the scheduled stop time). In
other words, I was able to tweak the stop time by a few seconds via
TV_RECORD_PADDING_POST, but a similar action with TV_RECORD_PADDING_PRE did
not yield any change less than 60 seconds (1 minute).
Anyway, I can accept the inprecision of TV_RECORD_PADDING_PRE, but how can I
get my recordings to start exactly at the scheduled start time without
trying to compensate via TV_RECORD_PADDING_PRE (which doesn't yield good
results anyway -- 15 seconds too early or 45 seconds late are both bad).
What's causing recordings to start 45 seconds too late with the default
settings?
Thanks for any help anyone can offer.
Art S R
--
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H___
Freevo-users mailing list
Freevo-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freevo-users
