2014-04-16, 20:09
(2014-04-16, 19:29)Koying Wrote: Those having divx/xvid/mp4 issues, could you try adding:
to advancedsettings.xml.Code:<advancedsettings>
[...]
<video>
<stagefright>
<useMP4codec>0</useMP4codec>
</stagefright>
</video>
[...]
</advancedsettings>
This disable h/w decoding for mp4, but the chip should be able to decode it in software easily.
This does seem to make a difference. Odd, I tested pure software decoding before with multithreading enabled and I don't remember it looking much better. Can someone else confirm this I feel like my eyes are playing tricks on me. Also it only seems to be using 3 of 4 cores no matter how I configure it. Is there any way around that?
(2014-04-16, 19:51)Tinwarble Wrote:(2014-04-16, 19:21)n3on Wrote: Because I have 10+ years of a media collection and not the resources/desire to re-encode them all. Also what container do you recommend? I find it incredibly hard to believe that playing old 480p video in Xvid/Divx should be a problem considering my xbox running xbmc4xbox streams it flawlessly. There's gotta be a simple solution if it was mastered 10+ years ago.
Again, those are just containers. Most likely they are MPEG 4 (codec), which is supported by the Fire TV, but that does not mean that divx/xvid/MPEG 4 is supported, Amazon doesn't make the distinction.
Yes, h.264 may be having the same or similar issues but that doesn't mean that they are caused by the same thing and it depends on what you mean by "jerky" since if you have a lot of jerkiness then it's not the same as h.264 which is small and irregular.
But as far as recommendation, either mkv/h.264 or mp4/h.264 which are more "universal".
Also, you don't necessarily need to re-encode. You could just run them through mkvtoolnix and do container swap, which should only take a couple of mins. per vid.
The jerkiness/stutter whatever you want to call it is mostly noticeable during panning scenes. I uploaded a sample a few pages back. Thanks for the tip on the container swap. I might give that a shot. Why would the hardware care what kind of container it's in? Wouldn't XBMC strip the container and feed the GPU straight MPEG4 making the container issue moot?