foo_cwb_hooks
Reply #93 – 2006-09-12 22:04:15
As far as i've seen it, updating the whole Db will only notify the components displaying those tracks to update. Someone with 100000 (who will get quite some performance Problems with foobar and most components won't have all those 100000 tracks "in use" - so sending an update for the whole db will actually refresh about 1000 tracks - in any case not more than is done at startup after all. I said it has to be tested and if it's gives acceptable results should be added as an _option_. (If this "brute force" method works, one could als refresh the playing and the active playlist to the refresh - this should for sure refresh every track the user is able to see) Amount of false verifiable info in just the above quote offends me. People have successfully used foobar2000 with close to 100000 tracks. The performance is not what I'd call "perfectly smooth", but it's by several magnitudes better than most of other software. I'll leave flaming you for that statement to TrNSZ when he shows up. I have to credit him for making me invent the metadb_handle system in first place, when the old approach underperformed with his old library of about 20000 tracks. Updating whole media library with each playback state, playback queue state, system time etc change will: - Cause full rebuild of all autoplaylists etc - which means running some query on all items in the library, possibly repeatedly if multiple autoplaylists exist. - Totally kill performance of any other realtime ML viewers (autoplaylist is the only one I'm currently aware of, but we plan to add autorefresh to Album List sooner or later).