I am not using early start and late end padding. Also I have in /etc/rc.d/rc.local
/usr/sbin/ntpdate -b time.nist.gov I dont think it is a problem with the clock setting. It seems that the PVR250 takes a little longer time to stop the recording so that mythtv thinks it is busy when the next recording is scheduled to start. The end result is a missed recording for that time slot anyway. Mythtv tries to record the same show at a later time. This doesn't happen with my software encoders. Sorry if there is a double post, I am having trouble with my email client. On Sun, 2005-07-24 at 02:44, Bruce Markey wrote: > Christopher Isip wrote: > > I have a pvr 250 setup as my primary tuner on my myth network and it is > > housed in a slave backend ( I changed the card's id in mysql so it gets > > picked first in order to use up the slave backend local storage first). > > Everything works and when there are simultaneous recordings, tuner 2 and > > tuner 3 from the master get second and third priority. My problem is > > when there is only one recording scheduled at a time but for consecutive > > times. For example, show A 10:00-11:00. Show B 11:00-12:00. Both are > > scheduled for the pvr 250 to record. However, Show B doesn't get > > recorded because mythtv complains that the tuner is already busy. > > Anybody have a workaround for this? > > http://www.ntp.org/ > > -- bjm > > ______________________________________________________________________ > _______________________________________________ > mythtv-users mailing list > mythtv-users@mythtv.org > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users _______________________________________________ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users