2012-04-06, 06:32
Thought I'd post a thought I had up for discussion.
One issue with exporting your library to separate files so that the info is stored with the media files is that you need to do this regularly or it will be out of sync.
What about an option whereby after watching/listening to media (whether you stop it halfway or finish it), xbmc will write the data to the separate file there an then. What delays/speed issues might implementing this introduce? Obviously xbmc will be updating the database AND be writing this out to file(s). If it does introduce speed issues / delays, is it possible to run it in a separate thread so that the user can continue to use xbmc?
I see possible issues with starting and stopping multiple files in quick succession (depending on how long updating the library and external files might take)....
But anyway, thoughts?
One issue with exporting your library to separate files so that the info is stored with the media files is that you need to do this regularly or it will be out of sync.
What about an option whereby after watching/listening to media (whether you stop it halfway or finish it), xbmc will write the data to the separate file there an then. What delays/speed issues might implementing this introduce? Obviously xbmc will be updating the database AND be writing this out to file(s). If it does introduce speed issues / delays, is it possible to run it in a separate thread so that the user can continue to use xbmc?
I see possible issues with starting and stopping multiple files in quick succession (depending on how long updating the library and external files might take)....
But anyway, thoughts?