2008-02-28, 04:22
With the advent of the new scraper allowing higher quality posters to be fetched, XBMC is starting to struggle when there are a lot of posters to load and resize on the fly.
If there were a few different resolutions stored for each thumbnail, xbmc could be more selective about which thumbnail to load and perhaps save some cpu cycles by not having to do the dynamic resize ?
Instead of ab01cd02.tbn xbmc could store something like
ab01cd02_sml.tbn
ab01cd02_med.tbn
ab01cd02.tbn -> default, high res
I don't know how exactly thumbnails are handled now, but I would guess that a possible way to implement this would be:
- The first time a view is requested where the small icon is needed, the ab01cd02_sml.tbn file is created and stored somewhere under UserData/Thumbnails/
- Each subsequent fetch of the same thumnail would pull the _sml file, if it exists.
I believe this would speed up page up/page down navigation in views such as PMIII's Media Info, since the large version of the thumbnail would only have to be loaded on highlighted movies.
This feature wouldn't come for free, since it would involve extra disk reads to look for the presence of each thumbnail version. I don't know how expensive disk reads are for XBMC though ?
There would also be extra storage requirements, but disk space is cheap. Besides, my thumbnail folder now takes up about 80MB. Smaller versions would only take up a fraction of that.
If there were a few different resolutions stored for each thumbnail, xbmc could be more selective about which thumbnail to load and perhaps save some cpu cycles by not having to do the dynamic resize ?
Instead of ab01cd02.tbn xbmc could store something like
ab01cd02_sml.tbn
ab01cd02_med.tbn
ab01cd02.tbn -> default, high res
I don't know how exactly thumbnails are handled now, but I would guess that a possible way to implement this would be:
- The first time a view is requested where the small icon is needed, the ab01cd02_sml.tbn file is created and stored somewhere under UserData/Thumbnails/
- Each subsequent fetch of the same thumnail would pull the _sml file, if it exists.
I believe this would speed up page up/page down navigation in views such as PMIII's Media Info, since the large version of the thumbnail would only have to be loaded on highlighted movies.
This feature wouldn't come for free, since it would involve extra disk reads to look for the presence of each thumbnail version. I don't know how expensive disk reads are for XBMC though ?
There would also be extra storage requirements, but disk space is cheap. Besides, my thumbnail folder now takes up about 80MB. Smaller versions would only take up a fraction of that.