I can see it on the iplayer website. Says it's available for 26 days. I can see the pid.
It doesn't appear in the index oddly (was broadcast yesterday though).
I've tried downloading via the pid, and the iplayer web url but I don't get any error or any downloads.
http://www.bbc.co.uk/iplayer/episode/b08...out-14-hiv
Using the latest and greatest get_iplayer on debian.
What am I missing?
Odd that it works for you... with verbose logging it says it's a future program.
If that is the case, could you tweak the default log on the next release to state that - better to have something in the log for 1st line debug.
Code:
get_iplayer --pid=b08rvdwp --type=tv --verbose > gip.log 2>&1
cat gip.log
get_iplayer v3.01, Copyright (C) 2008-2010 Phil Lewis
This program comes with ABSOLUTELY NO WARRANTY; for details use --warranty.
This is free software, and you are welcome to redistribute it under certain
conditions; use --conditions for details.
NOTE: A UK TV licence is required to legally access BBC iPlayer TV content
INFO: encodinglocale = UTF-8
INFO: encodinglocalefs = UTF-8
INFO: encodingconsoleout = UTF-8
INFO: encodingconsolein = UTF-8
INFO: ${^UNICODE} = 0
INFO: User prefs dir: /root/.get_iplayer
INFO: System options dir: /etc/get_iplayer/options
Current options:
encodingconsolein = UTF-8
encodingconsoleout = UTF-8
encodinglocale = UTF-8
encodinglocalefs = UTF-8
ffmpeg = /usr/local/bin/ffmpeg
pid = b08rvdwp
refreshexclude = cbbc,s4c,cbeebies,bbc alba,BBC One Northern Ireland,BBC News,BBC Parliament
refreshexcludegroupstv = local
tvmode = best
type = tv
verbose = 1
ybbcy = 1
INFO: Search args: ''
INFO: ffmpeg version string = 3.1.5-static
INFO: ffmpeg version number = 3.1
INFO: Will try prog types: tv
INFO: Loaded history for first check.
INFO: Loading recordings history
INFO: Programme not in history
INFO: Got 4034 file cache entries for tv
INFO: Ignoring Future Prog: '3570: The Truth About... - HIV - 2017-05-31T23:20:00+01:00'
p.s. my date is correct
root@gdserver:~# date
Mon 29 May 20:38:09 BST 2017
In an earlier thread, the "--future" flag fixed a similar problem.
No idea how you managed to index only the upcoming repeat and not the original broadcast, unless you changed your refresh parameters in the last few days. As for the log message, that entire bit of code will likely disappear in the next release.
We had a power cut on Wednesday - and we were without power for 14 hours. Power on server after and thought no more of it. It runs the my script at 1am which updates the cache and runs the pvr.
Other than that, nothing unusual happened.