Page 1 of 1
Playback crash back to main menu and NCSI error
Posted: 16 Nov 2017, 00:25
by cosmoxl
https://gist.github.com/anonymous/2b53b ... 82fa963f98
That's the log.
A few times recently I've had a crash from playback back to the main menu. This is the first time I've bothered to get a log for it.
I'm really puzzled why a curl call to
http://www.msftncsi.com/ncsi.txt is being asked for by MrMC. BTW, that whole domain is blocked by my firewall on purpose.
Re: Playback crash back to main menu and NCSI error
Posted: 16 Nov 2017, 03:37
by davilla
The call to "
http://www.msftncsi.com/ncsi.txt" is a check for CCurlFile::IsInternet. Think of it as a ping to check that the box is actually connect and can route to the internet.
If "
http://www.msftncsi.com/ncsi.txt" fails, it will fall back to "
http://www.w3.org/"
These two sites are always present unless someone blocks them.
As for the player stop, can't see why it stopped. It does look like it tried to display switch. Might increase the delay time.
Re: Playback crash back to main menu and NCSI error
Posted: 16 Nov 2017, 13:47
by cosmoxl
davilla wrote: 16 Nov 2017, 03:37
The call to "
http://www.msftncsi.com/ncsi.txt" is a check for CCurlFile::IsInternet. Think of it as a ping to check that the box is actually connect and can route to the internet.
If "
http://www.msftncsi.com/ncsi.txt" fails, it will fall back to "
http://www.w3.org/"
These two sites are always present unless someone blocks them.
As for the player stop, can't see why it stopped. It does look like it tried to display switch. Might increase the delay time.
Thanks. I do think resolution switching might have been the problem as that file's fps couldn't be accurately detected by
mediainfo or any of our various playback methods/devices. It had the decoder confused I'm sure. I trashed it and .... made another.
As for the ping,
www.w3.org isn't blocked, so should I assume that it's working properly?
Re: Playback crash back to main menu and NCSI error
Posted: 17 Nov 2017, 06:27
by davilla
cosmoxl wrote: 16 Nov 2017, 13:47
As for the ping,
www.w3.org isn't blocked, so should I assume that it's working properly?
yes