Jim Lesurf
2018-08-26 10:05:09 UTC
Until yesterday I've been using an old version of gip to fetch radio
programmes. This is on my usual "Ain't broke" -> "Don't fix" basis. However
yesterday when I tried to get the latest set of R3 Proms files it failed
for the items that started with the pids that begin with 'm'.
As an aside, I know zip about perl. But I did experiment with seeing if
this was a filter problem I could fix. I found a couple of places in the
version I was using that seemed to be requiring a 'p' or 'b' and added 'm'
in the '[ ]' braces. But no cigar. Out of curiosity, if this should have
been possible I'd welcome someone explaining. However, on with the main
reason for writing this...
I got the current version of gip, and this did let me fetch the files.
However each time it began it popped up some comments to the effect
"Error response 500 Can't connect to aod-hls-uk-live ...
... certificate verify failed."
It then said to ignore this if the download worked. Which it did. But my
questions are: Can I tell it to skip this apparent attempt to 'verify' and
not prompt or have to report the error? Or am I doing something wrong?
FWIW I've been using a series of settings
--type=radio --mode-hafhigh --force --no-tag --pid (then the pid)
Doing the above, there is something else I can report in case someone can
comment or find it of interest.
I fetched a series of half a dozen 'Proms' files inc. some of the
'headphone mix' ones which I'm in two minds about. The first fetch ('m'
prefix pid) popped up an error partway though the process.
502 bad gateway
and said a segment was missing.
The others were all OK.
I refetched the first file and this time it came without any 502. Comparing
the two files, they have exactly the same length, but I've not yet had a
chance to compare them to spot any diff.
The 502 was curious. But I also noticed that the first series of fetches
all ran at about the same, moderately slow, rate. Whereas the re-fetch ran
much faster. Which strenghtens a feeling I have that items more than a few
days old are slower to transfer, but can then get into some kind of 'cache'
which means they then can be obtained more quickly until bumped out by
something else. Is this correct?
Cheers,
Jim
programmes. This is on my usual "Ain't broke" -> "Don't fix" basis. However
yesterday when I tried to get the latest set of R3 Proms files it failed
for the items that started with the pids that begin with 'm'.
As an aside, I know zip about perl. But I did experiment with seeing if
this was a filter problem I could fix. I found a couple of places in the
version I was using that seemed to be requiring a 'p' or 'b' and added 'm'
in the '[ ]' braces. But no cigar. Out of curiosity, if this should have
been possible I'd welcome someone explaining. However, on with the main
reason for writing this...
I got the current version of gip, and this did let me fetch the files.
However each time it began it popped up some comments to the effect
"Error response 500 Can't connect to aod-hls-uk-live ...
... certificate verify failed."
It then said to ignore this if the download worked. Which it did. But my
questions are: Can I tell it to skip this apparent attempt to 'verify' and
not prompt or have to report the error? Or am I doing something wrong?
FWIW I've been using a series of settings
--type=radio --mode-hafhigh --force --no-tag --pid (then the pid)
Doing the above, there is something else I can report in case someone can
comment or find it of interest.
I fetched a series of half a dozen 'Proms' files inc. some of the
'headphone mix' ones which I'm in two minds about. The first fetch ('m'
prefix pid) popped up an error partway though the process.
502 bad gateway
and said a segment was missing.
The others were all OK.
I refetched the first file and this time it came without any 502. Comparing
the two files, they have exactly the same length, but I've not yet had a
chance to compare them to spot any diff.
The 502 was curious. But I also noticed that the first series of fetches
all ran at about the same, moderately slow, rate. Whereas the re-fetch ran
much faster. Which strenghtens a feeling I have that items more than a few
days old are slower to transfer, but can then get into some kind of 'cache'
which means they then can be obtained more quickly until bumped out by
something else. Is this correct?
Cheers,
Jim
--
Electronics https://www.st-andrews.ac.uk/~www_pa/Scots_Guide/intro/electron.htm
Armstrong Audio http://www.audiomisc.co.uk/Armstrong/armstrong.html
biog http://jcgl.orpheusweb.co.uk/history/ups_and_downs.html
Audio Misc http://www.audiomisc.co.uk/index.html
Electronics https://www.st-andrews.ac.uk/~www_pa/Scots_Guide/intro/electron.htm
Armstrong Audio http://www.audiomisc.co.uk/Armstrong/armstrong.html
biog http://jcgl.orpheusweb.co.uk/history/ups_and_downs.html
Audio Misc http://www.audiomisc.co.uk/index.html