Posts: 46
Joined: Dec 2013
Reputation:
0
FWIW, I have found that Koyings SPMC versions work without any of the same issues being discussed here.
My Fire TV experience has been virtually flawless. I am also hard-wired with a 100+ Mbps connection which does not hurt…
It was my own direct experience with the recent XBMC versions that forced me to fully switch to SPMC.
Posts: 201
Joined: Oct 2013
Reputation:
1
I don't know if you are using live tv but I do and that's where the issues arise. Both, SPMC and official crashed on live tv but not when playback local contents. I did find a fix. I wanted to test it for a couple of days prior to updating this thread with the steps. I had my fire tv running for a couple of days on live tv and no issues.
Work around that works for me and some one else:
1. Turn off both of the filters (mediacodec and libstagefright) under hardware acceleration.
2. Change hardware acceleration to software.
3. Enable 'allow multi thread software decoding'.
For live tv, you may need to enable deinterlace.
Posts: 109
Joined: Jan 2009
Reputation:
0
I was playing around with that.seems to be most stable for live TV. I wonder if there is a way to set livetv to software rendering and everything else to the hardware . via advanced settings?XML or something.I could live with that solution
john
Posts: 332
Joined: Feb 2010
Reputation:
7
I had alot of crashes too.
Work around was turn off mediacodec ONLY
i enabled libstagefright, otherwise i had problem with playback of 1080p rip files.
Posts: 31,445
Joined: Jan 2011
It has nothing to do with readbufferfactor.
Posts: 63
Joined: Dec 2013
Reputation:
2
I posted this over in the Serverwmc thread. Koying had suggested this in the libstagefright thread.
If you need to use stagefright for example for h.264 or most 1080 content on an android device then you wouldn't want to simply turn of stagefright. Instead you will want to create an advancedsettings.xml file that has the following:
<advancedsettings>
<video>
<stagefright>
<!-- -1 is default, 0 is never used this codec, 1 is always use this codec, bypassing blacklist -->
<usempeg2codec>0</usempeg2codec>
</stagefright>
</video>
</advancedsettings>
This way you can leave stagefright as your hardware acceleration method to handle .h264 content, but disable it for mpg2 files (tv and recorded tv).
I think this was first suggested by Koying, but I can confirm it works extremely well on the AFTV. I was having occasional crash issues with mediacodec turned on, but stagefright wouldn't play all of my files. The above allowed me to use stagefright and all of my files will play.
I hope this helps.
Posts: 1
Joined: Sep 2014
Reputation:
0
I had the regular crash on firetv with both gotham and kodi phase3. Installed spmc week nowmand this works like charm.
Posts: 16
Joined: Jul 2012
Reputation:
0
2014-10-08, 10:09
(This post was last modified: 2014-10-08, 16:35 by Feierstarter.)
Same problem here with SPMC and TVHeadend as a server. Only solution for me is to disable Hardware Acceleration completely.
I also tried to only disable mpeg2 hardware acceleration in advancedsettings, but this is completely ignored. It is not a problem that advancedsettings.xml is being ignored, I have other settings in there that are not ignored, it's only the stagefright stuff beeing ignored.
For Live TV, Codecinfo tells me that stf-mpeg2 codec is used when switching to an mpeg2 channel, but as soon as I see the first picture SPMC immediately crashes. If I stream a recorded file from my NAS I have no crashes, but still the stf-codec is used. As there is no possibility to deinterlace with stf-codec, my preferred solution would be software rendering for mpeg2 and hardware for other stuff.
I will try Kodi Alpha 4 this evening to see if it has the same behavior.
EDIT: After checking again I noticed that I didn't include the <stagefright> stuff into the video-section of advancedsettings.xml. After doing so everything is running as expected, mpeg2 with software rendering, all other stuff with hardware.
Posts: 68
Joined: May 2014
Reputation:
3
I was having this problem consistently.
Since disabling mediacodec AND enabling audio passthrough they have gone away completely ( 4 days straight ).
<knock on wood>
Running Gotham.