Steegy wrote:What event would be used to update this NP backup? The OnChangedSelection event would only be partially helpful, and would be called way too much. A timer could be a solution, but still it would be a performance hit on large NP's.
I am not very familiar with all of the events available, but if there is an event for NP track added and NP track removed, perhaps it could be used to add/prune the library nowplaying playlist?
What would happen? The easiest way to backup would be to clear and filled the backup playlist each time (searching for differences and then insert/remove tracks (kind of AI) seems way to difficult for me, and for the computer).
Yea this was my initial thought, I don't know the processing overhead this would cost every time the NP list changed tho.
2 things for the monkey (MM) itself: always make that the mediamonkey.m3u list is accurate, and don't crash.
Agree, if MM did not have problems with saving of settings/NP list this would be less of an issue.
I personally would prefer to remove all reference to external mediamonkey/winamp m3u files for normal MM operation. I do not keep any m3u files in my library and generally only use them for special situations.
I do think that some plugins rely on the now playing m3u file, which might be one of the factors for its continued existence.
Here is something even simpler than my original suggestion:
Don't delete the temp playlist on startup, simply delete (or clear) and refill it on shut down.
This would mirror current mediamonky.m3u behavior, you might have an old now playing list if MM does not shut down properly, but at least it won't be empty.
Last.FM Node