get_iplayer forums

After not having a Laptop for a month I only got one about a week ago & so I installed the latest version of GiP, v3.06.
My system now is an Intel i5 Gen. 6 processor with a 256GB SSD & 8GB RAM running Windows 10 Home Edition.
On my previous & now broken Laptop I was running v2.97 or 2.99 & all was OK including downloads.
But now, using the same internet connection but better & faster Laptop I've been getting a lot of the following problem.
Below is just one programme but the problem over the course of the download occured many more times than what is shown here.
It doesn't happen with all programmes but it happens too often & it only tries to continue downloading about 5 times before I have to strart it manually again.

WARNING: Unexpected size for file segment [465]
WARNING: Expected: 2009720 Downloaded: 1994481
WARNING: Retrying download
INFO: Downloading tv: 'Gymnastics: World Championships: 2017 - 3. Women's All-Round Final (b097fd7c) [shortened]'
INFO: Downloaded: 88.49 MiB (00:06:55) @ 1.22 Mibit/s (hvfhigh1) [audio+video]

WARNING: Unexpected size for file segment [361]
WARNING: Expected: 1690872 Downloaded: 1384321
WARNING: Retrying download
WARNING: Retrying tv: 'Gymnastics: World Championships: 2017 - 3. Women's All-Round Final (b097fd7c) [shortened]'
INFO: Downloaded: 194.55 MiB (00:15:21) @ 1.93 Mibit/s (hvfhigh1) [audio+video]

WARNING: Unexpected size for file segment [481]
WARNING: Expected: 1696888 Downloaded: 1381583
WARNING: Retrying download
WARNING: Retrying tv: 'Gymnastics: World Championships: 2017 - 3. Women's All-Round Final (b097fd7c) [shortened]'
INFO: Downloaded: 1.62 MiB (00:00:08) @ 0.40 Mibit/s (hvfhigh1) [audio+video]

WARNING: Unexpected size for file segment [482]
WARNING: Expected: 1757048 Downloaded: 375789
WARNING: Retrying download

Now today, when I've started downloading for the first time since last night I'm getting the following error with every programme I'm trying to download & I've tried 5 different programmes.

C:\WINDOWS\system32>get_iplayer --url https://www.bbc.co.uk/iplayer/episode/b0...episode-28 --tvmode=hlshd1
get_iplayer 3.06.0, 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.

ERROR: Could not parse JSON PID info: http://www.bbc.co.uk/programmes/b097rs7k.json
WARNING: Could not determine PID type (b097rs7k). Trying to record PID directly.
Matches:
2457: Gardeners' World: 2017 - Episode 28, BBC Two, b097rs7k
INFO: 1 matching programmes
WARNING: Could not parse programme metadata from http://www.bbc.co.uk/programmes/b097rs7k.json
(malformed JSON string, neither array, object, number, string or atom, at character offset 0 (before "<!DOCTYPE HTML SYSTE...")
at C:\Program Files (x86)\get_iplayer\get_iplayer.pl line 4326.)
WARNING: No programmes are available for this PID with version(s): default

C:\WINDOWS\system32>

Any ideas please?
And I'm not sure how to produce logs that you request for when investigating a problem.
Thanks.

(05-11-2017, 05:52 PM)And I'm not sure how to produce logs that you request for when investigating a problem.
Thanks.

This post will walk you through what the command does so you will be able to easily use it to create the log file.

/threa...ml#pid7024

Thank you Squarepenguin I shall take a look at that soon because I thjink I've answered my own one question to my last highlighted problem.
The 'ERROR: Could not parse JSON PID.......' problem does seem to be an internet connection problem as I've tried it through my phone when tethered weith my Laptop & I'm getting the programmes to download.
I will do the logs for the other problem of disconnecting a.s.a.p.
Thanks.

The "WARNING: Unexpected size for file segment" messages are symptoms of poor upstream connectivity. Don't bother producing a log for those. It is unlikely you would be able to replicate the exact same errors, and there is nothing get_iplayer can do to help, anyway. If you don't mind gaps or potentially unplayable files, use --no-verify to skip the segment size checks. Not recommended, of course.

The "ERROR: Could not parse JSON PID info" messages indicate that request for a JSON file has been redirected by the BBC servers to an HTML page, probably an error page of some sort. Unless the request is getting mangled on the way to the BBC, I'm not sure if connectivity can be blamed. However, it's not worth producing a log for that error either because get_iplayer won't display enough detail. If you can load that .json URL in your browser and receive some kind of error message, post a screen grab of that.

The fact get_iplayer works on one connection and not another tells me that there is nothing wrong with get_iplayer itself. I think you just need a better connection.

Thanks for the quick reply Dinky & Squarepenguin.
When you had replied Dinky I managed to read what you had put but I couldn't reply until now as I had to disconnect from the Net until I got home.
Anyway, I did suspect & you are nearly 100 percent correct in saying that the "WARNING: Unexpected size for file segment" error is more than likely to do with poor connectivity although using the live performance graph in Task Manager didn't show any dropped connections at the time of the error occuring, otherwise it would've been clear to me what had happened & why I got that error message. I'm going to assume that the error I've posted above is GiP v3.06 equivalent to the GiP v2.97/2.99 which used to say "Connection Timed Out". So again if I got that error message like I used to at times with GiP v2.97/2.99 then I would know what was going on. But what you've said Dinky has confirmed what I sort iof thought what was happening & I totally understand that no logs need to be produced as a bad connection is nothing to do with GiP. And may I say that I didn't imply or meant to imply that the problems I have was to do with GiP & the latest version. I post my problem on here because I have to admit there are a lot of people who are more experienced & informed than I & if anybody has experienced the same thing & has a solution to pass on then that's what I would be looking for. So problems posted on here by myself & people like me may not have anything directly to do with GiP. And like most people before me we appreciate people like Dinky who have maintained this software whereas the rest of us less experienced etc could not do it.

I take on board the other problem i.e. "ERROR: Could not parse JSON PID info" Dinky & I'll look into that because the internet connection I had when I got that error I didn't & haven't had prior to today. At some point this week I shall be in the position to connect via that internet connection again & I'll see what, if any, error messages I will get.

I'll go now & I'll just say "Thanks" again to those that maintain GiP & are willing to help out those people less experienced than them.

These forums are archived

See this post for further info

Forum archived. Posting disabled.

WARNING: Unexpected size for file segment

user-991

user-30

user-991

user-2

user-991

These forums are archived

See this post for further info