Re: [Openpvr-devel] Simple question: 'seenput' commands

[Brian J. M. <942...@in...>]

On Sun, Mar 30, 2003 at 06:36:24PM -0500, Alan Murrell wrote:
> Hello,

Hi.

> Well, I have "schedule" working now, though I am using
> my own "record" script (which uses 'at' to schedule
> the recordings) because I use mencoder, which records
> the show into DivX already.

So why not modify record and send in a patch so that others can
benefit from your work?

> A sample output from my run of "schedule" looks like
> this:
>=20
> at 22:00 05.04.03 <<EOF
> /usr/local/openpvr/record --device 0 --end "epoch
> 1049612399" --channel "11 CHAN" 'Andromeda: Angel
> Dark, Demon Bright'; /usr/local/openpvr/seenput
> 'Andromeda' 'Angel Dark, Demon Bright';
> EOF
> /usr/local/openpvr/seenput 'Andromeda' 'Angel Dark,
> Demon Bright' 1049608800 3600 '11 CHAN' 0
>=20
> I know it give the command to cut-and-paste, and I
> understand that the
>=20
> /usr/local/openpvr/seenput 'Andromeda' 'Angel Dark,
> Demon Bright'
>=20
> puts the entry into the 'seen.db' file so that it
> isn;t scheduled on a subsequent run of 'schedule'
> (looks like this is done at the same time the 'at'
> recording command is done??)  However, I am a little
> puzzled by the
>=20
> /usr/local/openpvr/seenput 'Andromeda' 'Angel Dark,
> Demon Bright' 1049608800 3600 '11 CHAN' 0
>=20
> Is this putting the entry into the 'seen.db' file
> again?  If so, is there a reason for this, since it
> was already put in  there by the first 'seenput'
> command?

Yes.  There are two states in the seen database:  a) scheduled and b)
recorded.  The seenput in the at command, that end up being executed
subsequent to the recording tells schedule that the episode has been
recorded.  The seenput tha happens when the at job is scheduled tells
schedule that the episode has been scheduled to record but not yet
recorded.

> TIA for your help.

NP.

b.

--=20
Brian J. Murrell