On 03/08/16 20:12, Shevek wrote:
On 3 August 2016 at 17:27, Jim web wrote:
In this case it isn't a problem I recall encountering before. Yet it has
now happened many times in the space of a few days. So the simplest answer
may be that something has actually changed. The
hello
i would note that the Warning:
> "WARNING: Segment not found (xxx)"
> "WARNING: There may be a gap near yyy secs in programme"
Indicates that there "MAY BE A GAP", the operative word being "MAY"
it is not saying that there is definitely a gap.
given the wording of the warning message, it
On 3 August 2016 at 20:12, Shevek wrote:
> [...]
> "WARNING: Segment not found (xxx)"
> "WARNING: There may be a gap near yyy secs in programme"
>
> If I then retry using FLASHHD the download completes without error.
>
> So, it appears that the beeb's HLS encoding/streaming
On 03/08/16 20:12, Shevek wrote:
On 3 August 2016 at 17:27, Jim web wrote:
In this case it isn't a problem I recall encountering before. Yet it has
now happened many times in the space of a few days. So the simplest answer
may be that something has actually changed. The
hello
I run into premature terminations several times a week. I chalk them
up to 'Internet Hiccups'. Restart and everything is fine.
Remember Occam's Razor:
"Among competing hypotheses, the one with the fewest assumptions
should be selected." or paraphrased: "The simplest answer is normally
the
I encountered this problem again this morning. This time for two programmes
with the pids b0085b0s and b07n2hmt. As before my usual hls fetch method
ended prematurely without gip reporting any actual errors. But using
--type=tv --mode=best
then worked for both. Albeit rather more slowly than my
On Mon, Aug 01, 2016 at 06:52:14PM +0100, John Bray wrote:
> Do you know how the BBC will enforce there new online licence rules?
I expect that they'll enforce it the same way as they do now for live
streaming via iPlayer, and the same way as they do for receiving
broadcast television. That is,
7 matches
Mail list logo