SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
@stormtracknole, are there any other addons that aren't working that we could try on our end? I don't have an ESPN login, so I can't try it on my system.
Looking through the SlackBuild's changelog, I don't see where it's changed. He still has it optional, but has it disabled by default. I've been using his SlackBuild since 2015 and it's always used an internal ffmpeg (before that, I was building kodi and xbmc manually). I don't remember ever running into an issue where it wasn't working as planned.
I think by the SlackBuild removing the cmake files, it becomes difficult building add-ons.
I'm currently building kodi right now using the default SBo from the slackbuilds site. It is using it's own FFMPEG.
abga,
I was having the same problem with the arm version.
I've never ran into problems with addons not being able to be installed, however, I do pretty much keep to the official kodi addons (except for one 3rd-party addon that I use to watch a program that is streamed twice a year).
What addons haven't you been able to install because of that line? And if you present that info to Larry, he might be willing to change his script. He switched libmicrohttpd from an optional to required dependency after I requested it and explaining why I thought it should be default.
In order to (please pay attention) build(compile) & install add-ons you'll need the cmake files that Larry is deleting, the ones that should be available in /usr/lib/kodi/
I wasn't talking about the add-ons you have available in the Kodi repository and only need to download & install.
You also need to build the two core Kodi add-ons platform & kodi-platform to start with: https://www.linuxquestions.org/quest...2/#post5804551
(Section - Kodi Addons: - sorry for the bad formatting, I was new on LQ and didn't know/care how to properly format posts)
You can build the add-ons during the compilation of Kodi, but I found that approach a little too complicated.
No, I meant that I was building kodi, and before that xbmc, manually. I've been building xbmc/kodi since Dharma and have always used the internal version. In older versions, ffmpeg was included directly in the xbmc source, but in the newer versions (from Helix on up), they grab the tarball from their own github and will build during kodi's compilation (see tools/depends/target/ffmpeg/autobuild.sh). Larry's script will take a pre-downloaded tarball and link it to the correct spot in the source tree so kodi doesn't download ffmpeg itself (since SBo doesn't permit downloading things once the SlackBuild has been run).
I know the history of xmbc, never used it and only started with Kodi 16, actually it was 17 beta for my first use on Raspberry, and I thought you had a typo there. As said, I'm always manually compiling Kodi and ffmpeg separately and only under Slackware ARM.
@stormtracknole, are there any other addons that aren't working that we could try on our end? I don't have an ESPN login, so I can't try it on my system.
I'll check and see which ones I can use.
Sorry to report, but using the included version of ffmpeg did not make a difference. Still seeing the same errors. :/
In order to (please pay attention) build(compile) & install add-ons you'll need the cmake files that Larry is deleting, the ones that should be available in /usr/lib/kodi/
You edited it after the fact to mention "build", so I didn't see that in my initial reply. So, I did pay attention to your initial post (you'll see that my reply includes your original quote that only talked about installing addons, nothing about building them). I've never had a need to build my own addons, which is likely why I've never ran into an issue with this.
Am I just understanding you never got a reply? If so, maybe this could be addressed using the SBo mailing list.
Quote:
Originally Posted by abga
I know the history of xmbc, never used it and only started with Kodi 16, actually it was 17 beta for my first use on Raspberry, and I thought you had a typo there. As said, I'm always manually compiling Kodi and ffmpeg separately and only under Slackware ARM.
Nope, no typo. I've always let xbmc/kodi use its own version of ffmpeg and then I'll build my own ffmpeg to use on my main machine.
I guess with you running into the same problem with the internal version that it is less likely to be related to your specific system, but I'd still be happy to try any addons that don't require a login on my machine and see if there's a problem with mine as well.
Quote:
Originally Posted by stormtracknole
Sorry to report, but using the included version of ffmpeg did not make a difference. Still seeing the same errors. :/
That's a bummer... I had no clue if it was related to your specific build of ffmpeg or not, but at least you can let the kodi forum people know you've tried it with both the internal version of ffmpeg and your self-compiled version.
You edited it after the fact to mention "build", so I didn't see that in my initial reply. So, I did pay attention to your initial post (you'll see that my reply includes your original quote that only talked about installing addons, nothing about building them). I've never had a need to build my own addons, which is likely why I've never ran into an issue with this.
Yep, 1 minute difference between my edit and your post Which means you were writing your reply to my post while I was editing it. I edited the post because it was full of mistakes and also added "build" for clarification. I don't know how to highlight all the edits, or if it's even possible in the simple edit mode I use on LQ. Sometimes, when I have more time, I just use bold for the edits.
Quote:
Originally Posted by bassmadrigal
Am I just understanding you never got a reply? If so, maybe this could be addressed using the SBo mailing list.
If you're registered with the SBo mailing list, you can do it if you like, mention that the cmake files are needed and shouldn't be deleted in the cleanup line. As for me I don't use Larry's Slackbuild and not sure I'll ever compile Kodi on x86. The one I butchered for Raspberry Pi (Slackware ARM sub-forum) doesn't contain the cleanup line.
Quote:
Originally Posted by bassmadrigal
Nope, no typo. I've always let xbmc/kodi use its own version of ffmpeg and then I'll build my own ffmpeg to use on my main machine.
As said, I couldn't on Slackware ARM for the Raspberry target, I made the ffmpeg source tarball available (as Larry is doing in his build script) for Kodi to unpack it and build it. The ffmpeg build was always successful, installed by the Kodi scripts somewhere in the compilation directory and then the Kodi (configure ?) scripts couldn't find it, just stupid. But that was already some years ago (Krypton 17 beta) and I never cared to check again if it's working, instead I just documented the ffmpeg build and used it as shared: https://www.linuxquestions.org/quest...on-4175612537/
I give up! I went to my Raspberry Pi 3 and started kodi and the ESPN3 add-on. It works as it is supposed to. Here's my logfile. I am completely perplexed...
[https] the user-agent option is deprecated, please use user_agent option
entry in the Slackware ARM log and I'm wondering why since it's the same ffmpeg version (the source - https://github.com/xbmc/FFmpeg/archi...on-17.5.tar.gz ), just compiled separately and used by Kodi as shared. I don't know if you tried this already on x86, but you could uninstall any ffmpeg version you have there and compile ffmpeg on your own, using the source: https://github.com/xbmc/FFmpeg/archi...on-17.5.tar.gz
and the options used by Kodi when it builds ffmpeg on its own from the end of post #17, then recompile Kodi by using Larry's SlackBuild and specify that you have ffmpeg (use it as shared):
Code:
# Optional ffmpeg is still available but not turned on by
# default.
if [ "${FFMPEG:-no}" == "yes" ]; then
OPT_DEPS="--with-ffmpeg=shared"
else
OPT_DEPS=""
fi
Side note: I noticed a lot of errors related to the CEC adapter in your Kodi - Slackware ARM log and was wondering if you want to use it. Have you installed libcec and compiled Kodi with CEC support ? https://github.com/Pulse-Eight/libcec
If negative, you could disable it from the Kodi GUI:
Settings > Input Devices > Perpipherals > CEC Adapter
Last edited by abga; 01-13-2019 at 08:59 PM.
Reason: typo in the Side note
[https] the user-agent option is deprecated, please use user_agent option
entry in the Slackware ARM log and I'm wondering why since it's the same ffmpeg version (the source - https://github.com/xbmc/FFmpeg/archi...on-17.5.tar.gz ), just compiled separately and used by Kodi as shared. I don't know if you tried this already on x86, but you could uninstall any ffmpeg version you have there and compile ffmpeg on your own, using the source: https://github.com/xbmc/FFmpeg/archi...on-17.5.tar.gz
and the options used by Kodi when it builds ffmpeg on its own from the end of post #17, then recompile Kodi by using Larry's SlackBuild and specify that you have ffmpeg (use it as shared):
Code:
# Optional ffmpeg is still available but not turned on by
# default.
if [ "${FFMPEG:-no}" == "yes" ]; then
OPT_DEPS="--with-ffmpeg=shared"
else
OPT_DEPS=""
fi
Side note: I noticed a lot of errors related to the CEC adapter in your Kodi - Slackware ARM log and was wondering if you want to use it. Have you installed libcec and compiled Kodi with CEC support ? https://github.com/Pulse-Eight/libcec
If negative, you could disable it from the Kodi GUI:
Settings > Input Devices > Perpipherals > CEC Adapter
I'll try that tomorrow. Remember that the arm log comes from Raspbian and not Slackware. I had a Fedora x86_64 box recently, and kodi worked fine there to (the ESPN3 add-on).
Apologies, I thought I mentioned Raspbian in my previous post. I did not. Sorry about that.
Last edited by stormtracknole; 01-13-2019 at 09:12 PM.
I'll try that tomorrow. Remember that the arm log comes from Raspbian and not Slackware. I had a Fedora x86_64 box recently, and kodi worked fine there to (the ESPN3 add-on).
Well, then don't try anything because I thought you were on Slackware ARM and not on Raspbian, you didn't specify that in your statement:
Quote:
I give up! I went to my Raspberry Pi 3 and started kodi and the ESPN3 add-on. It works as it is supposed to. Here's my logfile. I am completely perplexed...
Sorry, get on the Kodi forum and provide them the Slackware X86 failure log as I'm running out of ideas and I cannot help you with this ESPN3 add-on.
Don't know where to find the compilation details for Kodi under Raspbian, but these look to be the configuration options Debian is using for compiling Kodi 17.6:
They also look to build ffmpeg separatelly (--with-ffmpeg=shared is used) and there are no other options I could spot, different than the ones used in the kodi SlackBuild, that could resolve the errors you're getting. I'm really out of ideas now.
Well, then don't try anything because I thought you were on Slackware ARM and not on Raspbian, you didn't specify that in your statement:
Sorry, get on the Kodi forum and provide them the Slackware X86 failure log as I'm running out of ideas and I cannot help you with this ESPN3 add-on.
I realized that after I saw your post. I appreciate very much your help on this. You already have done a lot! I was looking at Fedora's kodi.spec file (since it works for them) and I noticed that they use cmake instead of the configure script to stage everything. I'll inspect some more tomorrow.
Thank you all for your help so far. If I come up with the solution, I'll post it here.
After checking the Kodi compilation in my previous post, I spent some time verifying if the ffmpeg compilation is different in Debian (Raspbian), fearing that there might be some additional stuff required in order to be able to play HLS.
Found nothing extra and it looks like the HLS protocol is enabled by default in the "core" of ffmpeg: https://ffmpeg.org/ffmpeg-protocols.html#hls
I went and played with ffmpeg under Slackware 14.2 ARM where I have my Kodi stuff (ARM - should be the same as x86), simulating the requests Kodi was doing in your log. I was aware that I wouldn't succeed (no authentication) but just wanted to make sure that ffmpeg is sane and is not failing due to some external libs:
Code:
ffmpeg -loglevel debug -hide_banner -i "https://x-live-espn-stgec.uplynk.com/ause/slices/e17/d09b16c953aa40c98dd8c513526aca5a/e178438e3b224c2fb20cd3c8814fde82/H00000127.ts?pbs=365bdeae66cf41999e62b8e62949ccae&_jt=l&euid=ESPN3_VDMS&chid=d0695f6fa2f143eb95c7a41d96d581c4&ptid=ESPN_tvOS_VDMS&si=0"
Splitting the commandline.
Reading option '-loglevel' ... matched as option 'loglevel' (set logging level) with argument 'debug'.
Reading option '-hide_banner' ... matched as option 'hide_banner' (do not show program banner) with argument '1'.
Reading option '-i' ... matched as input url with argument 'https://x-live-espn-stgec.uplynk.com/ause/slices/e17/d09b16c953aa40c98dd8c513526aca5a/e178438e3b224c2fb20cd3c8814fde82/H00000127.ts?pbs=365bdeae66cf41999e62b8e62949ccae&_jt=l&euid=ESPN3_VDMS&chid=d0695f6fa2f143eb95c7a41d96d581c4&ptid=ESPN_tvOS_VDMS&si=0'.
Finished splitting the commandline.
Parsing a group of options: global .
Applying option loglevel (set logging level) with argument debug.
Applying option hide_banner (do not show program banner) with argument 1.
Successfully parsed a group of options.
Parsing a group of options: input url https://x-live-espn-stgec.uplynk.com/ause/slices/e17/d09b16c953aa40c98dd8c513526aca5a/e178438e3b224c2fb20cd3c8814fde82/H00000127.ts?pbs=365bdeae66cf41999e62b8e62949ccae&_jt=l&euid=ESPN3_VDMS&chid=d0695f6fa2f143eb95c7a41d96d581c4&ptid=ESPN_tvOS_VDMS&si=0.
Successfully parsed a group of options.
Opening an input file: https://x-live-espn-stgec.uplynk.com/ause/slices/e17/d09b16c953aa40c98dd8c513526aca5a/e178438e3b224c2fb20cd3c8814fde82/H00000127.ts?pbs=365bdeae66cf41999e62b8e62949ccae&_jt=l&euid=ESPN3_VDMS&chid=d0695f6fa2f143eb95c7a41d96d581c4&ptid=ESPN_tvOS_VDMS&si=0.
[NULL @ 0x1a44390] Opening 'https://x-live-espn-stgec.uplynk.com/ause/slices/e17/d09b16c953aa40c98dd8c513526aca5a/e178438e3b224c2fb20cd3c8814fde82/H00000127.ts?pbs=365bdeae66cf41999e62b8e62949ccae&_jt=l&euid=ESPN3_VDMS&chid=d0695f6fa2f143eb95c7a41d96d581c4&ptid=ESPN_tvOS_VDMS&si=0' for reading
[https @ 0x1a44ad0] Setting default whitelist 'http,https,tls,rtp,tcp,udp,crypto,httpproxy'
[https @ 0x1a44ad0] request: GET /ause/slices/e17/d09b16c953aa40c98dd8c513526aca5a/e178438e3b224c2fb20cd3c8814fde82/H00000127.ts?pbs=365bdeae66cf41999e62b8e62949ccae&_jt=l&euid=ESPN3_VDMS&chid=d0695f6fa2f143eb95c7a41d96d581c4&ptid=ESPN_tvOS_VDMS&si=0 HTTP/1.1
User-Agent: Lavf/57.41.100
Accept: */*
Range: bytes=0-
Connection: close
Host: x-live-espn-stgec.uplynk.com
Icy-MetaData: 1
https://x-live-espn-stgec.uplynk.com/ause/slices/e17/d09b16c953aa40c98dd8c513526aca5a/e178438e3b224c2fb20cd3c8814fde82/H00000127.ts?pbs=365bdeae66cf41999e62b8e62949ccae&_jt=l&euid=ESPN3_VDMS&chid=d0695f6fa2f143eb95c7a41d96d581c4&ptid=ESPN_tvOS_VDMS&si=0: Input/output error
ffmpeg -loglevel debug -hide_banner -i "crypto+https://x-live-espn-stgec.uplynk.com/ause/slices/e17/d09b16c953aa40c98dd8c513526aca5a/e178438e3b224c2fb20cd3c8814fde82/H00000127.ts?pbs=365bdeae66cf41999e62b8e62949ccae&_jt=l&euid=ESPN3_VDMS&chid=d0695f6fa2f143eb95c7a41d96d581c4&ptid=ESPN_tvOS_VDMS&si=0"
Splitting the commandline.
Reading option '-loglevel' ... matched as option 'loglevel' (set logging level) with argument 'debug'.
Reading option '-hide_banner' ... matched as option 'hide_banner' (do not show program banner) with argument '1'.
Reading option '-i' ... matched as input url with argument 'crypto+https://x-live-espn-stgec.uplynk.com/ause/slices/e17/d09b16c953aa40c98dd8c513526aca5a/e178438e3b224c2fb20cd3c8814fde82/H00000127.ts?pbs=365bdeae66cf41999e62b8e62949ccae&_jt=l&euid=ESPN3_VDMS&chid=d0695f6fa2f143eb95c7a41d96d581c4&ptid=ESPN_tvOS_VDMS&si=0'.
Finished splitting the commandline.
Parsing a group of options: global .
Applying option loglevel (set logging level) with argument debug.
Applying option hide_banner (do not show program banner) with argument 1.
Successfully parsed a group of options.
Parsing a group of options: input url crypto+https://x-live-espn-stgec.uplynk.com/ause/slices/e17/d09b16c953aa40c98dd8c513526aca5a/e178438e3b224c2fb20cd3c8814fde82/H00000127.ts?pbs=365bdeae66cf41999e62b8e62949ccae&_jt=l&euid=ESPN3_VDMS&chid=d0695f6fa2f143eb95c7a41d96d581c4&ptid=ESPN_tvOS_VDMS&si=0.
Successfully parsed a group of options.
Opening an input file: crypto+https://x-live-espn-stgec.uplynk.com/ause/slices/e17/d09b16c953aa40c98dd8c513526aca5a/e178438e3b224c2fb20cd3c8814fde82/H00000127.ts?pbs=365bdeae66cf41999e62b8e62949ccae&_jt=l&euid=ESPN3_VDMS&chid=d0695f6fa2f143eb95c7a41d96d581c4&ptid=ESPN_tvOS_VDMS&si=0.
[NULL @ 0x26f390] Opening 'crypto+https://x-live-espn-stgec.uplynk.com/ause/slices/e17/d09b16c953aa40c98dd8c513526aca5a/e178438e3b224c2fb20cd3c8814fde82/H00000127.ts?pbs=365bdeae66cf41999e62b8e62949ccae&_jt=l&euid=ESPN3_VDMS&chid=d0695f6fa2f143eb95c7a41d96d581c4&ptid=ESPN_tvOS_VDMS&si=0' for reading
[crypto @ 0x26fad0] No default whitelist set
[crypto @ 0x26fc40] decryption key not set
crypto+https://x-live-espn-stgec.uplynk.com/ause/slices/e17/d09b16c953aa40c98dd8c513526aca5a/e178438e3b224c2fb20cd3c8814fde82/H00000127.ts?pbs=365bdeae66cf41999e62b8e62949ccae&_jt=l&euid=ESPN3_VDMS&chid=d0695f6fa2f143eb95c7a41d96d581c4&ptid=ESPN_tvOS_VDMS&si=0: Invalid argument
So far so good, it seems.
Then I focused on the Kodi Add-on itself. According to the first post from this ESPN_3 thread, you need two additional add-ons (python plugins) as dependencies for the espn_3 add-on: https://forum.kodi.tv/showthread.php?tid=230418
Normally the add-ons installation will resolve the dependencies automatically if it's done through the Kodi GUI, these will be downloaded from the Kodi official repository. However, when I installed the espn_3 add-on in Kodi 17.4 under Slackware 14.2 ARM, I only observed that the Dateutil plug-in was added, nothing about m3u8.
I checked your logs again and found all the required plug-ins initialized in both cases. You can find them in the beginning of the logs, just after the line : NOTICE: Running database version Addons27
Just for testing and making sure it's not something related to the add-on installation and dependency resolution, I'd suggest to uninstall the espn_3 add-on in Kodi (GUI - Add-ons Section - My Add-ons) and reinstall it manually by using zip files: https://kodi.wiki/view/HOW-TO:Instal...from_zip_files
Last thing to try: - the espn_3 add-on has some options that you can play with. In the advanced section there are two interesting options, first one is to clear the cache and the second one is to disable the Certificates Checking/Verification.
Disabling the certificates checking was mentioned in some places as a workaround for some issues, maybe you're lucky
That's pretty much it, my limitations - end of the road for me, get on the Kodi forum and ask for further support. This thread should be the one appropriate for your help request: https://forum.kodi.tv/showthread.php?tid=230418
Last edited by abga; 01-14-2019 at 03:13 PM.
Reason: EDIT - LQ auto emoji crap
@stormtracknole, are there any other addons that aren't working that we could try on our end? I don't have an ESPN login, so I can't try it on my system.
I tried the CNN add-on, and got some errors. However, it also did not work under Raspbian. I tried the HGTV one for the heck of it, and that worked fine. I can't remember right now which other application to try. If you can download the ESPN add-on, can you select the content listed under ESPN3? That should be free content and no sign in is necessary. Thanks!
Quote:
Originally Posted by abga
After checking the Kodi compilation in my previous post, I spent some time verifying if the ffmpeg compilation is different in Debian (Raspbian), fearing that there might be some additional stuff required in order to be able to play HLS.
Found nothing extra and it looks like the HLS protocol is enabled by default in the "core" of ffmpeg: https://ffmpeg.org/ffmpeg-protocols.html#hls
I went and played with ffmpeg under Slackware 14.2 ARM where I have my Kodi stuff (ARM - should be the same as x86), simulating the requests Kodi was doing in your log. I was aware that I wouldn't succeed (no authentication) but just wanted to make sure that ffmpeg is sane and is not failing due to some external libs:
Code:
ffmpeg -loglevel debug -hide_banner -i "https://x-live-espn-stgec.uplynk.com/ause/slices/e17/d09b16c953aa40c98dd8c513526aca5a/e178438e3b224c2fb20cd3c8814fde82/H00000127.ts?pbs=365bdeae66cf41999e62b8e62949ccae&_jt=l&euid=ESPN3_VDMS&chid=d0695f6fa2f143eb95c7a41d96d581c4&ptid=ESPN_tvOS_VDMS&si=0"
Splitting the commandline.
Reading option '-loglevel' ... matched as option 'loglevel' (set logging level) with argument 'debug'.
Reading option '-hide_banner' ... matched as option 'hide_banner' (do not show program banner) with argument '1'.
Reading option '-i' ... matched as input url with argument 'https://x-live-espn-stgec.uplynk.com/ause/slices/e17/d09b16c953aa40c98dd8c513526aca5a/e178438e3b224c2fb20cd3c8814fde82/H00000127.ts?pbs=365bdeae66cf41999e62b8e62949ccae&_jt=l&euid=ESPN3_VDMS&chid=d0695f6fa2f143eb95c7a41d96d581c4&ptid=ESPN_tvOS_VDMS&si=0'.
Finished splitting the commandline.
Parsing a group of options: global .
Applying option loglevel (set logging level) with argument debug.
Applying option hide_banner (do not show program banner) with argument 1.
Successfully parsed a group of options.
Parsing a group of options: input url https://x-live-espn-stgec.uplynk.com/ause/slices/e17/d09b16c953aa40c98dd8c513526aca5a/e178438e3b224c2fb20cd3c8814fde82/H00000127.ts?pbs=365bdeae66cf41999e62b8e62949ccae&_jt=l&euid=ESPN3_VDMS&chid=d0695f6fa2f143eb95c7a41d96d581c4&ptid=ESPN_tvOS_VDMS&si=0.
Successfully parsed a group of options.
Opening an input file: https://x-live-espn-stgec.uplynk.com/ause/slices/e17/d09b16c953aa40c98dd8c513526aca5a/e178438e3b224c2fb20cd3c8814fde82/H00000127.ts?pbs=365bdeae66cf41999e62b8e62949ccae&_jt=l&euid=ESPN3_VDMS&chid=d0695f6fa2f143eb95c7a41d96d581c4&ptid=ESPN_tvOS_VDMS&si=0.
[NULL @ 0x1a44390] Opening 'https://x-live-espn-stgec.uplynk.com/ause/slices/e17/d09b16c953aa40c98dd8c513526aca5a/e178438e3b224c2fb20cd3c8814fde82/H00000127.ts?pbs=365bdeae66cf41999e62b8e62949ccae&_jt=l&euid=ESPN3_VDMS&chid=d0695f6fa2f143eb95c7a41d96d581c4&ptid=ESPN_tvOS_VDMS&si=0' for reading
[https @ 0x1a44ad0] Setting default whitelist 'http,https,tls,rtp,tcp,udp,crypto,httpproxy'
[https @ 0x1a44ad0] request: GET /ause/slices/e17/d09b16c953aa40c98dd8c513526aca5a/e178438e3b224c2fb20cd3c8814fde82/H00000127.ts?pbs=365bdeae66cf41999e62b8e62949ccae&_jt=l&euid=ESPN3_VDMS&chid=d0695f6fa2f143eb95c7a41d96d581c4&ptid=ESPN_tvOS_VDMS&si=0 HTTP/1.1
User-Agent: Lavf/57.41.100
Accept: */*
Range: bytes=0-
Connection: close
Host: x-live-espn-stgec.uplynk.com
Icy-MetaData: 1
https://x-live-espn-stgec.uplynk.com/ause/slices/e17/d09b16c953aa40c98dd8c513526aca5a/e178438e3b224c2fb20cd3c8814fde82/H00000127.ts?pbs=365bdeae66cf41999e62b8e62949ccae&_jt=l&euid=ESPN3_VDMS&chid=d0695f6fa2f143eb95c7a41d96d581c4&ptid=ESPN_tvOS_VDMS&si=0: Input/output error
ffmpeg -loglevel debug -hide_banner -i "crypto+https://x-live-espn-stgec.uplynk.com/ause/slices/e17/d09b16c953aa40c98dd8c513526aca5a/e178438e3b224c2fb20cd3c8814fde82/H00000127.ts?pbs=365bdeae66cf41999e62b8e62949ccae&_jt=l&euid=ESPN3_VDMS&chid=d0695f6fa2f143eb95c7a41d96d581c4&ptid=ESPN_tvOS_VDMS&si=0"
Splitting the commandline.
Reading option '-loglevel' ... matched as option 'loglevel' (set logging level) with argument 'debug'.
Reading option '-hide_banner' ... matched as option 'hide_banner' (do not show program banner) with argument '1'.
Reading option '-i' ... matched as input url with argument 'crypto+https://x-live-espn-stgec.uplynk.com/ause/slices/e17/d09b16c953aa40c98dd8c513526aca5a/e178438e3b224c2fb20cd3c8814fde82/H00000127.ts?pbs=365bdeae66cf41999e62b8e62949ccae&_jt=l&euid=ESPN3_VDMS&chid=d0695f6fa2f143eb95c7a41d96d581c4&ptid=ESPN_tvOS_VDMS&si=0'.
Finished splitting the commandline.
Parsing a group of options: global .
Applying option loglevel (set logging level) with argument debug.
Applying option hide_banner (do not show program banner) with argument 1.
Successfully parsed a group of options.
Parsing a group of options: input url crypto+https://x-live-espn-stgec.uplynk.com/ause/slices/e17/d09b16c953aa40c98dd8c513526aca5a/e178438e3b224c2fb20cd3c8814fde82/H00000127.ts?pbs=365bdeae66cf41999e62b8e62949ccae&_jt=l&euid=ESPN3_VDMS&chid=d0695f6fa2f143eb95c7a41d96d581c4&ptid=ESPN_tvOS_VDMS&si=0.
Successfully parsed a group of options.
Opening an input file: crypto+https://x-live-espn-stgec.uplynk.com/ause/slices/e17/d09b16c953aa40c98dd8c513526aca5a/e178438e3b224c2fb20cd3c8814fde82/H00000127.ts?pbs=365bdeae66cf41999e62b8e62949ccae&_jt=l&euid=ESPN3_VDMS&chid=d0695f6fa2f143eb95c7a41d96d581c4&ptid=ESPN_tvOS_VDMS&si=0.
[NULL @ 0x26f390] Opening 'crypto+https://x-live-espn-stgec.uplynk.com/ause/slices/e17/d09b16c953aa40c98dd8c513526aca5a/e178438e3b224c2fb20cd3c8814fde82/H00000127.ts?pbs=365bdeae66cf41999e62b8e62949ccae&_jt=l&euid=ESPN3_VDMS&chid=d0695f6fa2f143eb95c7a41d96d581c4&ptid=ESPN_tvOS_VDMS&si=0' for reading
[crypto @ 0x26fad0] No default whitelist set
[crypto @ 0x26fc40] decryption key not set
crypto+https://x-live-espn-stgec.uplynk.com/ause/slices/e17/d09b16c953aa40c98dd8c513526aca5a/e178438e3b224c2fb20cd3c8814fde82/H00000127.ts?pbs=365bdeae66cf41999e62b8e62949ccae&_jt=l&euid=ESPN3_VDMS&chid=d0695f6fa2f143eb95c7a41d96d581c4&ptid=ESPN_tvOS_VDMS&si=0: Invalid argument
So far so good, it seems.
Then I focused on the Kodi Add-on itself. According to the first post from this ESPN_3 thread, you need two additional add-ons (python plugins) as dependencies for the espn_3 add-on: https://forum.kodi.tv/showthread.php?tid=230418
Normally the add-ons installation will resolve the dependencies automatically if it's done through the Kodi GUI, these will be downloaded from the Kodi official repository. However, when I installed the espn_3 add-on in Kodi 17.4 under Slackware 14.2 ARM, I only observed that the Dateutil plug-in was added, nothing about m3u8.
I checked your logs again and found all the required plug-ins initialized in both cases. You can find them in the beginning of the logs, just after the line : NOTICE: Running database version Addons27
Just for testing and making sure it's not something related to the add-on installation and dependency resolution, I'd suggest to uninstall the espn_3 add-on in Kodi (GUI - Add-ons Section - My Add-ons) and reinstall it manually by using zip files: https://kodi.wiki/view/HOW-TO:Instal...from_zip_files
Last thing to try: - the espn_3 add-on has some options that you can play with. In the advanced section there are two interesting options, first one is to clear the cache and the second one is to disable the Certificates Checking/Verification.
Disabling the certificates checking was mentioned in some places as a workaround for some issues, maybe you're lucky
That's pretty much it, my limitations - end of the road for me, get on the Kodi forum and ask for further support. This thread should be the one appropriate for your help request: https://forum.kodi.tv/showthread.php?tid=230418
Can you see if you can play the content listed under ESPN3? There is no need to authenticate when viewing content on ESPN3. See if you can get that to play. I spent all day tweaking the ffmpeg build to match as close as possible to the Raspbian one. No matter what I do, I still get the same error.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
Which means you were writing your reply to my post while I was editing it. I edited the post because it was full of mistakes and also added "build" for clarification. I don't know how to highlight all the edits, or if it's even possible in the simple edit mode I use on LQ. Sometimes, when I have more time, I just use bold for the edits.
ateutil (wiki))
