+- Kodi Community Forum (https://forum.kodi.tv)
+-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33)
+--- Forum: Add-on Support (https://forum.kodi.tv/forumdisplay.php?fid=27)
+---- Forum: Video Add-ons (https://forum.kodi.tv/forumdisplay.php?fid=154)
+---- Thread: Release ESPN 3 (/showthread.php?tid=230418)
RE: ESPN 3 - awaters1 - 2016-05-11
That issue with FFMPEG is going to be difficult to work around. I use Linux so I have my own compiled version of FFMPEG that is linked with a different version of openssl/gnutls so it doesn't have that issue.
RE: ESPN 3 - User 272336 - 2016-05-11
(2016-05-11, 03:38)awaters1 Wrote: That issue with FFMPEG is going to be difficult to work around. I use Linux so I have my own compiled version of FFMPEG that is linked with a different version of openssl/gnutls so it doesn't have that issue.As I stated in one of my previous posts, I appreciate all that you have tried.
I must also say that my hopes were never too high since I had already spent time attempting to remedy a similar issue on the NBCSN validation. Sadly, that never worked either except thru the browser.
Again, I know you spent quite a bit of time on this and it is truly appreciated.
RE: ESPN 3 - siuside - 2016-05-11
(2016-05-11, 00:11)awaters1 Wrote: @siuside:
I checked in the log but I did not see anything suspicious, you might need to enable debug logging.
22:32:01 T:5748 NOTICE: ESPN3: args {'EVENT_ID': ['2810800'], 'SIMULCAST_AIRING_ID': ['118953519'], 'DESKTOP_STREAM_SOURCE': ['HLS'], 'MODE': ['PLAY'], 'NETWORK_ID': ['n360']}
22:32:07 T:6468 ERROR: Playlist Player: skipping unplayable item: 0, path [plugin://plugin.video.espn_3/?EVENT_ID=2810800&SIMULCAST_AIRING_ID=118953519&DESKTOP_STREAM_SOURCE=HLS&MODE=PLAY&NETWORK_ID=n360]
Somewhere between those two lines things went wrong but I cannot tell.
Debug logs uploaded here
RE: ESPN 3 - mrdally204 - 2016-05-11
(2016-05-11, 03:38)awaters1 Wrote: That issue with FFMPEG is going to be difficult to work around. I use Linux so I have my own compiled version of FFMPEG that is linked with a different version of openssl/gnutls so it doesn't have that issue.
Is it a bug in the FFMPEG, or does your Linux version have special cases built in to accommodate for this? If it is a bug, maybe filing it to FFMPEG will get it corrected in time for the next release of Kodi.
RE: ESPN 3 - locomot1f - 2016-05-11
hmmm... i use Linux too.
I just updated to ubuntu 16.04.
even with the 14.04 version of ubuntu FFMPEG, i was not having a problem.
hard to imagine that these feeds would be different from the free ESPN3 feeds...
RE: ESPN 3 - V8MEM - 2016-05-11
you can use a external HLS downloader (livestreamer etc) via proxy script.
the hls downloader in ffmpeg has been garbage for years and i dont see it getting fixed any time soon.
RE: ESPN 3 - locomot1f - 2016-05-11
wait... just thought of this... doesn't Kodi have it's own ffmpeg since v.15
RE: ESPN 3 - MetalChris - 2016-05-11
(2016-05-11, 18:48)locomot1f Wrote: wait... just thought of this... doesn't Kodi have it's own ffmpeg since v.15
I believe you are correct sir.
RE: ESPN 3 - awaters1 - 2016-05-12
I use Gentoo Linux so Kodi is compiled from source and linked with ffmpeg through a shared library, which also links openssl/gnutls through a shared library. So right now I use ffmpeg 2.8.7, gnutls 3.3.22 and openssl 1.0.2h. I'm not sure what versions precompiled Kodi comes with.
The free ESPN3 feeds don't use AES encryption so they don't have to contact espn's servers over HTTPS to obtain the key to decrypt the data.
RE: ESPN 3 - Chessie - 2016-05-14
I'm still seeing the same problem as siuside with your latest code (Brighthouse is my provider). Should we be seeing a cookies file in the addon_data directory after a successful login? Is it possible for you to add some extra debugging in during the login process? Brighthouse, and siuside's provider TWC, are somewhat related and probably use the same authentication process.
Thanks
RE: ESPN 3 - awaters1 - 2016-05-14
Yes, within the userdata addon directory for the plugin there should be the files auth.token, cookies.lwp, device.id, player_config.xml, provider.info, providers.xml, settings.xml, and user_data.xml. For extra debugging information you can follow http://kodi.wiki/view/Log_file/Easy any more debugging might expose your provider username/password so it isn't recommended.
RE: ESPN 3 - siuside - 2016-05-14
(2016-05-14, 02:15)awaters1 Wrote: Yes, within the userdata addon directory for the plugin there should be the files auth.token, cookies.lwp, device.id, player_config.xml, provider.info, providers.xml, settings.xml, and user_data.xml. For extra debugging information you can follow http://kodi.wiki/view/Log_file/Easy any more debugging might expose your provider username/password so it isn't recommended.
Sorry looks like you might have missed my debug log, just re-quoting myself here for convenience. I don't think the debug log provide any more info than the error you caught earlier? I still do not see cookies.lwp and auth.token in the addon data folder. In your very first version, I seem to recall these were created but ESPN3 and other channels authorization was still failing.
(2016-05-11, 00:11)awaters1 Wrote: @siuside:
I checked in the log but I did not see anything suspicious, you might need to enable debug logging.
22:32:01 T:5748 NOTICE: ESPN3: args {'EVENT_ID': ['2810800'], 'SIMULCAST_AIRING_ID': ['118953519'], 'DESKTOP_STREAM_SOURCE': ['HLS'], 'MODE': ['PLAY'], 'NETWORK_ID': ['n360']}
22:32:07 T:6468 ERROR: Playlist Player: skipping unplayable item: 0, path [plugin://plugin.video.espn_3/?EVENT_ID=2810800&SIMULCAST_AIRING_ID=118953519&DESKTOP_STREAM_SOURCE=HLS&MODE=PLAY&NETWORK_ID=n360]
Somewhere between those two lines things went wrong but I cannot tell.
Debug logs uploaded here
RE: ESPN 3 - User 272336 - 2016-05-14
...
RE: ESPN 3 - awaters1 - 2016-05-14
@siuside: Can you go to this URL http://broadband.espn.go.com/espn3/auth/espnnetworks/user and post the results?
RE: ESPN 3 - Chessie - 2016-05-14
This is the result I get from that URL:
{ "espn3":"invalid", "networks":"invalid" }
This is from a Windows PC browser that just watched live ESPN3, so no issues with authentication on that system.