Kodi Community Forum

I just built Kodi on Windows 7 (for the first time in about a year) and ffmpeg is not cooperating.  This is a fork, but it's almost identical to xbmc/master as it currently sits.  I used VS 2017 for the build.

https://paste.ubuntu.com/p/W736MQv9PK/

I tried to play the files with names starting with S34E21, S35E96 and S35E97.  These are MP4 files, which play fine on a Linux machine with a build from the same kodi source.  On this Windows build, I see the "wait" spinner for about ten seconds, then it goes back to the selection screen.

The first attempt is at around line 529.  At line 580 is this:
 

Quote:22:24:17.551 T:5820 DEBUG: ffmpeg[16BC]: [mov,mp4,m4a,3gp,3g2,mj2] STSC entry 77796 is invalid (first=205568 count=0 id=0)
22:24:17.551 T:5820 DEBUG: ffmpeg[16BC]: [mov,mp4,m4a,3gp,3g2,mj2] reached eof, corrupted STSC atom
22:24:17.551 T:5820 ERROR: ffmpeg[16BC]: [mov,mp4,m4a,3gp,3g2,mj2] error reading header22:24:17.553 T:5820 ERROR: CDVDDemuxFFmpeg::Open - Error, could not open file F:\Video\THE_SHOW.mp4
22:24:17.553 T:5820 ERROR: CDVDFileInfo::ExtractThumb - Error creating demuxer
22:24:18.216 T:340 ERROR: CDVDDemuxFFmpeg::Open - error probing input format, F:\Video\WheelofFortune\S34E21 [20180714-2330] 20161010.mp4
22:24:18.216 T:340 ERROR: CVideoPlayer::OpenDemuxStream - Error creating demuxer

Update:  I can play MPEG2 streams.  MP4s fail.  I don't need to play MP4 streams for what I'm doing, so for now the above error is a simple curiosity.

(2018-09-20, 05:42)MatthewLundberg Wrote: [ -> ]I just built Kodi on Windows 7 (for the first time in about a year) and ffmpeg is not cooperating.  This is a fork, but it's almost identical to xbmc/master as it currently sits.  I used VS 2017 for the build.

https://paste.ubuntu.com/p/W736MQv9PK/

I tried to play the files with names starting with S34E21, S35E96 and S35E97.  These are MP4 files, which play fine on a Linux machine with a build from the same kodi source.  On this Windows build, I see the "wait" spinner for about ten seconds, then it goes back to the selection screen.

The first attempt is at around line 529.  At line 580 is this:
 

Quote:22:24:17.551 T:5820 DEBUG: ffmpeg[16BC]: [mov,mp4,m4a,3gp,3g2,mj2] STSC entry 77796 is invalid (first=205568 count=0 id=0)
22:24:17.551 T:5820 DEBUG: ffmpeg[16BC]: [mov,mp4,m4a,3gp,3g2,mj2] reached eof, corrupted STSC atom
22:24:17.551 T:5820 ERROR: ffmpeg[16BC]: [mov,mp4,m4a,3gp,3g2,mj2] error reading header22:24:17.553 T:5820 ERROR: CDVDDemuxFFmpeg::Open - Error, could not open file F:\Video\THE_SHOW.mp4
22:24:17.553 T:5820 ERROR: CDVDFileInfo::ExtractThumb - Error creating demuxer
22:24:18.216 T:340 ERROR: CDVDDemuxFFmpeg::Open - error probing input format, F:\Video\WheelofFortune\S34E21 [20180714-2330] 20161010.mp4
22:24:18.216 T:340 ERROR: CVideoPlayer::OpenDemuxStream - Error creating demuxer

 What does almost identical mean?
Have you tried if this problem also happens with stock kodi master?

Edit:
While being at it, could you share a snippet of the mp4 you try to play, so that we can try to reproduce it on other platforms etc.?

"Almost identical" means that there is no difference in the code.  I added "-ggdb" for Linux release builds, and "-0g" for Linux debug builds, plus modified the files cmake/install/addons.txt and system/addon-manifest.xml.  All of these changes are for my convenience while working on some code.  I will extract a snippet of the file.  Where should I put it?

if you have a dropbox link or google drive or whatever would be good.

Are you running ffmpeg master branch on the Linux box?

I found a ffmpeg ticket: https://trac.ffmpeg.org/ticket/7165
Bug fixed but fix not backported to 4.x

ffmpeg is as the current (well, two days ago) Kodi master branch pulled down during the build.  Does this mean that you guys can fix this?

(2018-09-21, 18:11)MatthewLundberg Wrote: [ -> ]ffmpeg is as the current (well, two days ago) Kodi master branch pulled down during the build.  Does this mean that you guys can fix this?

 I guess with "current" you mean master branch, which is not a release. If this is the case, it will be fixed automatically once ffmpeg has put the fix into a release and we (kodi) will upgrade ffmpeg.