2010-01-02, 17:26
Hi,
I've been thinking for several weeks about it now and I think XBMC needs a standard way to read item info in the background. Right now, if I am not mistaken (possibly I am) thumbnails are the only thing read/created on the background for items in the library. In any case, if more data is read in the background, I could not see a unified or unique place in the code where this is done.
I also think these other data could be set/read in the background:
Ideally this can be read each time the database is pulled. The thing I've got in my mind is that when a list of items is pulled from the database then the SQL does its magic and then foreach item a background process reads all the above information (so no delay is added).
I wanted to start trying to code something for this. So I'd like to ask to the devs, what do you think? Having a unified/common way to read background info for items is useful? Are these options outlined before ok?
Regards and happy new year,
I've been thinking for several weeks about it now and I think XBMC needs a standard way to read item info in the background. Right now, if I am not mistaken (possibly I am) thumbnails are the only thing read/created on the background for items in the library. In any case, if more data is read in the background, I could not see a unified or unique place in the code where this is done.
I also think these other data could be set/read in the background:
- Availability (see thread): File path is checked to see if it is available and marked if not [useful in the file is in removable USB disks, or offline nas, etc.].
- Subtitles (see ticket): So streamdetails can be updated with subtitle info in external files [useful if user has new external subtitles available].
- Hash check to re-read media info if file is different or the first time [useful if user change the file keeping the name, I guess to update to a better version, don't know if this is very common though as I rarely have done it].
Ideally this can be read each time the database is pulled. The thing I've got in my mind is that when a list of items is pulled from the database then the SQL does its magic and then foreach item a background process reads all the above information (so no delay is added).
I wanted to start trying to code something for this. So I'd like to ask to the devs, what do you think? Having a unified/common way to read background info for items is useful? Are these options outlined before ok?
Regards and happy new year,