John Molohan wrote: > Duncan Webb wrote: >> Elizabeth Dodd wrote: >> >>> Recording on a couple of occasions has stopped way before time >>> One time I got 4 min of a 60 min program and tonight I got 22 min of a 60 >>> min >>> program. >>> Nothing in the recordserver log for the time at all. >>> Nothing else wanting to start recording >>> I'm using 1.6.3 and have the upsoon plugin. >>> I haven't got any way of chasing it up yet >>> but what ideas do people have to find what happens so that I can set up >>> suitable logging? >>> >> Just set DEBUG=1 and CHILDAPP_DEBUG=1 in your local_conf.py >> >> If you wanted to record two overlapping programmes the first one would >> be cut when the second one started. >> >> Duncan >> > Is there an easy way to change this behaviour? I think it would make > more sense to let the first recording run through to the end then try > start the overlappinig program. > > An extra help would be to have the recordserver automatically write a > note to a fxd file for the recording that was started late that the user > could then see when they browse to the recording in freevo. They'd see > something like 'this recording started 8 minutes late due to an overlap > with recording - Lost:SkyOne:21:00-22:00' or some such.
Not a bad idea. IIRC this behaviour has changed in 1.7.x, something to do with the priorities of recordings. Plus an overlapping recording shows up in the TV guide with an orange background. Duncan ------------------------------------------------------------------------- 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/ _______________________________________________ Freevo-users mailing list Freevo-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freevo-users
