On 19 April 2012 00:11, dinkypumpkin <[email protected]> wrote: > On 18/04/2012 21:51, Andy Bircumshaw wrote: >> >> --pvrqueue clearly *isn't* a "delayed search" mechanism, because it >> *always* converts the search results into a PID. > > It may look up the PID for programmes to construct the pvr search params, > but the search itself isn't handled differently for a queued pvr entry. > get_iplayer still searches the cache all over again when the pvr runs.
This is technically true, but in practice from a user's point of view I'd side with Andy. You can't add something using pvrqueue unless it's available in the cache at the time you add the programme, and then the programme is added by PID - that is, the search resolves down to a set of programme PIDs that are available /at the time of adding/. When the pvr is run, the cache is searched again, but only for the specific programme PIDs, which are always unique and will only match those programmes selected when the queued items were added. thus in any user-oriented sense pvr-queue is certainly not a delayed /search/. For delayed search use a normal search and pvr-add. forcing --future is of very dubious value: it doesn't do anything unless there are future programmes in the cache, which only happens if the user already knows to use --refresh-future. and if the user knows to use --refresh-future, then unless they happen to have found or noticed this quirk, will probably use --future anyway. I'd vote to take it out. :-) Jon _______________________________________________ get_iplayer mailing list [email protected] http://lists.infradead.org/mailman/listinfo/get_iplayer
