Hi Duncan,
Unfortunately, many US cable stations run their programs back-to-back with
no commercial breaks in-between programs. Indeed, the closing scene and
narrative are broadcast simultaneously with the closing credits. As soon as
the credits end, the next program starts. They put their commercials
(adverts) elsewhere during the program.
Anyway, I found that recordserver.py has the following code to delay the
start of recording until 45 seconds into the minute, so I changed it to
sec=0:
kaa.AtTimer(recordserver.handleAtTimer).start(sec=45)
Now, recording starts at the top of the minute.
The one remaining problem is that, if I have consecutive recordings, the
second program's start time is delayed by 1 minute. This occurs even when
using all the default settings ("sec=45" in recordserver.py and no PRE/POST
recording padding values in local_conf.py). In the recordserver log, it
shows "overlap_duration=0", yet the second recording doesn't start
immediately even though the previous program has already ended:
2009-03-09 22:29:50,898 INFO recordserver.py (1337): RECORD_STOP Mon Mar
09 22:00->22:30 (22:00) I6.28455235.microsoft.com Frasier
2009-03-09 22:30:45,002 INFO recordserver.py (910): overlap_duration=0
2009-03-09 22:30:45,004 INFO recordserver.py (924): CALLED RECORD STOP
1: Mon Mar 09 22:00->22:30 (22:00) I6.28455235.microsoft.com Frasier
2009-03-09 22:30:45,005 INFO recordserver.py (942): delaying: Mon Mar 09
22:30->23:00 (22:30) I12.28456406.microsoft.com Family Guy
2009-03-09 22:31:45,002 INFO recordserver.py (944): going to record: Mon
Mar 09 22:30->23:00 (22:30) I12.28456406.microsoft.com Family Guy
2009-03-09 22:31:45,005 INFO recordserver.py (962): start recording: Mon
Mar 09 22:30->23:00 (22:30) I12.28456406.microsoft.com Family Guy
In my Freevo 1.7.3 installation, the second program starts immediately after
the first program ends, without the 1 minute delay.
Art S R
On Tue, Mar 10, 2009 at 1:40 PM, Duncan Webb <dun...@freevo.org> wrote:
> Art S R wrote:
> > I checked my Freevo 1.7.x installation (where recordings start at the
> > correct time) and see that recordserver.py (revision 9844) has some code
> > to check for the "top of the minute" in startMinuteCheck(self) and
> > minuteCheck(self). These aren't in recordserver.py for Freevo 1.8.3.
> > Is there some other routine in the current version that syncs
> > recordserver to start recordings at the beginning of the minute (0
> > seconds) instead of 45 seconds later?
>
> It is quite unusual for a broadcaster to be so punctual with their
> broadcast times. The default should start recording 15 seconds before
> the program is due to start recording, this is intended so that the TV
> card will be fully operational when the program starts. The IVTV cards
> take a few seconds to get the MPEG stream steady.
>
> It is quite possible that the code is incorrect and starts recording 45
> seconds late. Need to test the code for the problem that you have
> described.
>
> The way I get round this is to use the VPS signal (PAL only?) which
> tells a VCR when a programme is really starting and finishing; then
> start recording from this point and stop it when the programme has
> finished. There may well be a similar process to for NTSC.
>
> Duncan
>
> > 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
> > <http://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 <http://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 <http://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
> > <http://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
> > <http://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 <http://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 <http://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
> > <http://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
>
>
>
> ------------------------------------------------------------------------------
> Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
> powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
> easily build your RIAs with Flex Builder, the Eclipse(TM)based development
> software that enables intelligent coding and step-through debugging.
> Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
> _______________________________________________
> Freevo-users mailing list
> Freevo-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freevo-users
>
------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
_______________________________________________
Freevo-users mailing list
Freevo-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freevo-users
