Hi folks,
I notice this morning that my web PVR manager is failing to locate any media streams.
"WARNING: No media streams found for requested programme versions and recording modes."
I've tried re-loading the latest version (2.99) which I was already using. I've tried manually updating the cache but that didn't help and the tiny number of updated programmes suggests that it was already up to date.
The only preference I have for recording is 'recording mode' set to 'best'.
However, if I go into a command line interface and then run the code using the PID from any of the failed programmes (e.g.
Code:
get_iplayer --modes=best --type=radio --pid=p04tnnmy
) in there, everything works ok, though I have noticed that in every case it seems to be taking rather longer than usual to locate a stream after it goes off to search for it. (Sometimes 20-30 seconds.) I'm wondering whether there's some sort of 'timeout' feature in the web pvr manager and if a stream hasn't been found before that time, it aborts and moves on to the next in the list?
I'm running v2.99 on Windows 10 in Firefox 51.0.1 with output being stored on the local drive, before being manually swept across to my fileserver afterwards.
Any suggestions?
Ta,
David.
Works fine here. The "No media streams found" message indicates that multiple resource downloads have failed or timed out. There are timeouts in get_iplayer, but they are pretty generous. BBC servers enforce timeouts as well, but they are also generous. Given your description, the culprit would seem to be poor upstream connectivity from your ISP or something wrong on the BBC side. There is no way for you to tell which. Either way, there is nothing you or get_iplayer can do about it, except to try again another day.
OK. I'll see how it gets on during the week (nothing needing recording at present). I didn't notice any massive latency problems accessing anywhere else this morning but that might not be telling me anything useful anyway, as you say.
Many thanks for your efforts on this fantastic product, btw! (I wish there was an equivalent for other broadcasters' catch-up services, though given the effect on my storage media, perhaps it's just as well!)
:-)
Just to update:
It's usually the weekend when I do my big weekly trawl and I'm finding the same problem again. I can select programmes I want, then run the PVR but it fails to find any streams for download. However, once again, when going to a CLI and running get_iplayer for each programme manually - no problem.
What I noticed this time is that the PVR doesn't seem to be delaying while looking for any streams to use - it just instantly moves on to the next. This was noticeable when it got to the list of 'once' recordings where it just catapulted straight through them in about a tenth of a second. I have noticed when using the CLI that there's the long latency I mentioned previously before it finds a stream to use.
I'm wondering whether it's possible that I've somehow set the PVR to be looking in the wrong location or for the wrong types of files (though goodness knows how) and so when I manually go to a CMD window and do it there, it works ok because I'm not asking it to do the same thing? (I can't see any file that contains settings that I can load in here to let you see.)
Could it be anything to do with cookies? I notice there's a file called C:\Users\David\.get_iplayer\cookies.get_iplayer
Just in case it's anything to do with the way that the individual programmes are stored for the PVR , here's a record of one that just failed to find a stream during a PVR run but downloaded fine when done manually from CMD window.
Code:
fields name
modes Best
subtitles 0
thumb 0
type tv
search0 Britain in Focus
I doubt that it helps, though!
Ta,
D.
Look carefully at the command you're using with CLI and the pvr job definition you posted. See if you can spot the crucial difference.
Well the main difference is that I did it by PID in the CLI, thus:
Code:
get_iplayer --modes=best --pid=b08h95jk
However, the fact that I'm now getting this problem with TV and Radio series that I've had in the PVR list for ages just made me wonder whether I'd somehow accidentally set something incorrectly to default in get_iPlayer that I shouldn't have done but I can't find a definition file that lists the default settings.
Post the equivalent pvr job for that command.
Ummm. Not quite sure what you mean. If you mean to try to do a search and queue operation using that pid rather than the series name so as to get the 'once' file (assuming that's stored in the same place as the other persistent pvr request files) then it won't let me unless I force it, as I've now already downloaded it using the CLI.
Would you like me to try it with 'force' and report what is stored?
Never mind. You should have mentioned that your CLI command was for "Britain in Focus", whose pvr job you posted earlier. Anyway, back to my original point: Look carefully at your CLI command and the pvr job definition and see if you can spot the crucial difference. Hint: the fact you used --pid is irrelevant.
Ah! Capital B?
I did accidentally let a load through with default so went through and manually edited the lot! Arrghh!
(Oh yes - and I've set it using a capital B in the recording settings too!)
Is that it?
Doh!
Can't believe how daft I was not to think of that!
Many thanks. I'll go back and re-amend them to what they should have been in the first place! :-)