|
|
The problem can be reproduced rarely on large DB, large NP list and somehow overloaded PC. Repro steps then. 1) place few thousands of tracks to NP list 2) open Playing node, wait for load 3) go to different node, change contents of NP list (e.g. resort, randomize it, etc.) 4) go to Playing node - it displays old list with wrong order and later it refreshes it with new correct list We need copy of the list in Playing node (so temporary resort correctly works then) and it can take some time to do it sometimes. Will try to improve it. |
|
|
Fixed in build 3015. I think I have finally found the original problem. It was related to Reverse list and Shuffle actions made before displaying the Playing node. In case you reproduce it again, please try to write what last actions with NP list did you do just before the problem. But I hope it will be ok now, I cannot reproduce it more. |
|
|
I do not use Shuffle, nor re-order Playing. I only add and remove Albums. |
|
|
I've not seen it in a while, but just saw it twice on 3015. The first it was briefly shown randomized, the second time it took longer to show in the correct order. New log in same place. |
|
|
Still see this on 3018. |
|
|
Hopefully fixed in build 3021. I have found most probable reason, it caused also 0020923. |
|
|
I'm unable to replicate in 3021.. Leaving for Lowlander to confirm/close. |
|
|
Just observed on 3024, in this case files were incorrectly sorted within their Album. It fixed itself quickly. New log added. |
|
|
See this rarely now, but just happened twice in a row on 3027. Playing is sorted on Title, instead of Playlist order when first selecting the Playing node. It takes a bit to show correct order. image-2.png (168,736 bytes) |
|
|
Seen again on 3029. Playing node did not auto-fix to the correct order till F5 was used. image-3.png (208,783 bytes) |
|
|
I added some debug message. I cannot reproduce, but some changes were made, please test in build 3036 and we will see, whether it still happens. In case it happens, I need debug log, thanks. |
|
|
It did happen on 3036 once, unfortunately no debug log. |
|
|
Closing as it hasn't been observed in several builds now. |
|
|
Just seen seen on 3065, new log added. |
|
|
Possibly related: https://www.mediamonkey.com/forum/viewtopic.php?t=106798 |
- Anonymous
