Posts: 1,104
Joined: Oct 2007
Reputation:
2
theuni
Team-XBMC Communication Manager
Posts: 1,104
Ok, that makes me feel better.
I've done a good bit of testing, and it looks like diminishing returns are involved here. Normal (~720p) images are massively sped up. Huge (12-20mpix) images are only sped up somewhat. But they're still faster, so I'll take it.
You'll see another big gain by switching to libjpeg-turbo if you haven't already.
Posts: 89
Joined: Apr 2011
Reputation:
0
I've already switched to jpeg-turbo some time ago. It was quite an improvement.
Regarding the original pull request, feel free to close it if you wish. As I've mentioned above, I'm still sticking with my patch anyway - most of my folders contain several hundred 12 Mpix images, so I can't afford waiting 5 minutes for thumbnail generation. I guess Atom simply can't do any better. My opinion would probably be quite different if I owned an i5.
Posts: 1,483
Joined: Aug 2010
dtviewer Wrote:The number one reason I recently retired my Atom (Revo 1600) and built an inexpensive XBMC HTPC is because it was so painfully slow when viewing my photos.
Photography is a big hobby of mine and like you I have hundreds of fairly large jpg files in folders.
(BTW, the htpc I built uses an AMD A4-3400 w/windows 7 and scrolling through hundreds of pictures is pretty much instant and there is basically no waiting for thumbnails render. As I scroll down they are there.)
Good to know an a4-3400 is capable but XBMC is designed to run on low powered hardware and most people still run their atom/ion. Only problem is that the picture-section doesn't had the attention the video-section had. But it's getting
better and better.
Posts: 124
Joined: May 2011
Reputation:
0
I was wondering what needs to be done to switch to jpeg-turbo. I have installed jpeg-turbo to /usr/local/lib configure doesnt seem to pick it up do I need to pass some specific option to configure to pick it up.
Posts: 26,215
Joined: Oct 2003
Reputation:
187
The ideal would be to do both (exif decode first, full decode that replaces that second).
Really though, it's only an issue the very first time you view the directory, and at < 1 second a file, even for several hundred it isn't that much of an issue.
In fact, part of the slowness for later images is the way the picture thumb loader works - it's a single threaded, so if you scroll to the bottom those won't get their thumbs until all the others are generated. This has changed in one of the branches I have - i.e. thumbs are all handled purely in the texture cache and are cached via jobs (independent threads) - the texture load threads have higher priority, so if you scroll down to the end, those images will be decoded before some of the ones you scrolled past. This basically means that you really only have to wait for what you're looking at to load, no matter where you are in the list.
I might see if I can merge that in before I'm done with the rest of my changes (video thumbs to the texture cache).
Cheers,
Jonathan
Posts: 124
Joined: May 2011
Reputation:
0
Thanks, I just needed to set my LD_LIBRARY_PATH for xbmc to pick it up. I really dont have to pass anything to configure script.
