2016-05-15, 20:13
(2016-05-15, 19:15)milli Wrote:(2016-05-15, 03:46)awaters1 Wrote: That is good to hear the ESPN3 part is working, yes it looks like that FFMPEG error showed up again "ERROR: ffmpeg[1A6C]: [tls] An illegal TLS extension was received.". I don't know if there is anything that I can do on my end to prevent that error.
Edit: The premium channels get their SSL cert from https://broadband.espn.go.com (details at http://www.ssltools.com/certificate_look...spn.go.com) while the ESPN3 feeds get the SSL cert from uplynk.com (details at http://www.ssltools.com/certificate_look...uplynk.com)
@milli: Yes Comcast should work with all channels, is there any more to that stack trace? possibly something that mentions a python script in the plugin.video.espn_3 directory.
Here you go and hope it helps. Thanks!
Code:16:57:01 T:123145305063424 ERROR: /Users/u/Library/Application Support/Kodi/addons/script.module.beautifulsoup4/lib/bs4/builder/_htmlparser.py:163: RuntimeWarning: Python's built-in HTMLParser cannot parse the given document. This is not a bug in Beautiful Soup. The best solution is to install an external parser (lxml or html5lib), and use Beautiful Soup with that parser. See http://www.crummy.com/software/BeautifulSoup/bs4/doc/#installing-a-parser for help.
"Python's built-in HTMLParser cannot parse the given document. This is not a bug in Beautiful Soup. The best solution is to install an external parser (lxml or html5lib), and use Beautiful Soup with that parser. See http://www.crummy.com/software/BeautifulSoup/bs4/doc/#installing-a-parser for help."))
16:57:01 T:123145305063424 ERROR: EXCEPTION Thrown (PythonToCppException) : -->Python callback/script returned the following error<--
- NOTE: IGNORING THIS CAN LEAD TO MEMORY LEAKS!
Error Type: <class 'HTMLParser.HTMLParseError'>
Error Contents: bad end tag: u"</scr' + 'ipt>", at line 109, column 208
Traceback (most recent call last):
File "/Users/u/Library/Application Support/Kodi/addons/plugin.video.espn_3/addon.py", line 431, in <module>
PLAY(args)
File "/Users/u/Library/Application Support/Kodi/addons/plugin.video.espn_3/addon.py", line 380, in PLAY
PLAY_PROTECTED_CONTENT(args)
File "/Users/u/Library/Application Support/Kodi/addons/plugin.video.espn_3/addon.py", line 250, in PLAY_PROTECTED_CONTENT
media_token = adobe.GET_MEDIA_TOKEN()
File "/Users/u/Library/Application Support/Kodi/addons/plugin.video.espn_3/adobe.py", line 302, in GET_MEDIA_TOKEN
success = self.GET_IDP_DATA()
File "/Users/u/Library/Application Support/Kodi/addons/plugin.video.espn_3/adobe.py", line 251, in GET_IDP_DATA
(content, url) = self.handle_url(opener, content_action, body)
File "/Users/u/Library/Application Support/Kodi/addons/plugin.video.espn_3/adobe.py", line 142, in handle_url
redirect = self.check_redirect(content)
File "/Users/u/Library/Application Support/Kodi/addons/plugin.video.espn_3/adobe.py", line 121, in check_redirect
content_soup = BeautifulSoup(content, 'html.parser')
File "/Users/u/Library/Application Support/Kodi/addons/script.module.beautifulsoup4/lib/bs4/__init__.py", line 196, in __init__
self._feed()
File "/Users/u/Library/Application Support/Kodi/addons/script.module.beautifulsoup4/lib/bs4/__init__.py", line 210, in _feed
self.builder.feed(self.markup)
File "/Users/u/Library/Application Support/Kodi/addons/script.module.beautifulsoup4/lib/bs4/builder/_htmlparser.py", line 164, in feed
raise e
HTMLParseError: bad end tag: u"</scr' + 'ipt>", at line 109, column 208
-->End of Python script error report<--
16:57:01 T:140735155544064 ERROR: Playlist Player: skipping unplayable item: 0, path [plugin://plugin.video.espn_3/?EVENT_ID=2800744&SIMULCAST_AIRING_ID=18949544&DESKTOP_STREAM_SOURCE=HDS&MODE=PLAY&NETWORK_ID=n502]
16:57:31 T:123145303990272 WARNING: CreateLoader - unsupported protocol(plugin) in plugin://plugin.video.espn_3/?EVENT_ID=2811157&SIMULCAST_AIRING_ID=119099814&DESKTOP_STREAM_SOURCE=HLS&MODE=PLAY&NETWORK_ID=n360
I've seen this before. Seems html.parser doesn't always work well on Mac OSX (or Android). I've since switched to using html5lib as the parser with my add-ons, and haven't seen this since.