Post-processing

[Alex. Rhodes]

Using an event entry gives more flexibility.

Essentially the post-processing command would be a call to EventCreate -
which would write an info entry to the Application log with a predefined ID.
Associated with the event would be an event triggered task, which would
start a PowerShell script that would:

Scan the download cache for the last entry
Check for the existence of the file in the last entry (and other sanity
checks)
Read the generic XML if it exists (gets various details about the download)
Generate an XBMC .nfo file from the XML file
Move the data to the relevant remote storage

If any of the steps fail, delete the entry from the download cache and
remove the downloaded files (essentially triggering a new download for that
item on the next scheduled PVR run).

I wouldn't want to call the PowerShell script directly from GiP though.

-----Original Message-----
From: get_iplayer [mailto:get_iplayer-bounces at lists.infradead.org] On Behalf
Of Peter S Kirk
Sent: 06 January 2015 20:26
To: get_iplayer at lists.infradead.org
Subject: Re: Post-processing

On 6 Jan 2015 at 16:12, Jeremy Nicoll - ml get_iplayer Jeremy Nicoll - ml
get_iplayer <jn.ml.gti.91 at wingsandbeaks.org.uk> wrote:

> I'm not sure I'd do it at all though, because I find I always want to 
> sanity check the size of fetched files, and for TV programmes I always 
> load what's arrived into VLC and make sure that the end credits are
actually there.

Snap, I do the same as in the past I had found some missing last x minutes
and no longer on iplayer
 
> I fetch files with a "$GRAB" prefix on their names that shows me that 
> the file that's arrived has not yet been checked; when I'm sure a file 
> is ok I strip that off.

That's a good idea. I sort download folder by date, but this will help
identify those not checked when I do a bulk download.

Cheers

_______________________________________________
get_iplayer mailing list
get_iplayer at lists.infradead.org
http://lists.infradead.org/mailman/listinfo/get_iplayer