Posts: 31,445
Joined: Jan 2011
Ned Scott Wrote:It's only an issue if they are in HD, and some might even play then. If you have HD xvid avi's that are not playing well then I would go and find better copies of them that are in h.264. Better quality per byte, plus it should work without issue. I don't know why people still insist on making HD avi's with xvid. It's a hacked together media container with an outdated codec, and when HD rips were gaining popularity (due to HD sources being available) h.264 was already here.
Although if Apple makes an ATV3 with the A5 SoC (System on a chip. CPU, GPU, and some other stuff) like the iPad and its A5, then the CPU would be able to handle a lot more. However, I doubt this would happen anytime soon. Apple seems to update ATVs very very slowly, and the ATV2 already has so much untapped potential (untapped via official channels, that is)
What I do think might happen is that later this year when Apple gets around to releasing an iPod touch with an A5, that will become a tempting alternative to the ATV2. (if we get true HDMI output, that is). Should even do 1080 output.
Posts: 31,445
Joined: Jan 2011
GoodOmens Wrote:Looking at this recent commit - would that help decoding none H264 files by making it multi-threaded on the A5 chip? Just curious - would be helpful for iPad2 users.....
Hardware decoded files will be unaffected. This will help in software decoded files, the GUI, etc.
Posts: 16,946
Joined: Feb 2011
Reputation:
256
threading implementation was changed ...
AppleTV4/iPhone/iPod/iPad: HowTo find debug logs and everything else which the devs like so much:
click here
HowTo setup NFS for Kodi:
NFS (wiki)
HowTo configure avahi (zeroconf):
Avahi_Zeroconf (wiki)
READ THE IOS FAQ!:
iOS FAQ (wiki)
Posts: 32
Joined: Apr 2009
Reputation:
0
Sadly either the multi-core rendering isn't working as intended, or ffmpeg just doesn't gain much benefit from it. I am getting almost identical results from playback of slower files. Oh well :/