These observations were made with build 1213.
There are a couple of problem areas with "Accessible Tracks" and the "Available Tracks" pre-defined filter**.
** This filter is defined as follows: Match = "All"; Search Criteria (property) = "Status", Search Criteria (Condition) = "is accessible".
According to what I can see, these two views are identical and should behave the same way.
Accessible Tracks:
When tracks become unavailable (I dismounted a disk containing music tracks) the affected tracks get greyed out. I think they should be removed from the list. And, in fact, when I click on another node and then click on "Accessible Tracks" again, the list is now OK.
++ Also, the list did not get updated when I mounted a disk containing library tracks. Clicking on another node, and coming back to the "Accessible Tracks" node, again, picks up the newly mounted disk.
Available Tracks (pre-defined) filter:
This should behave the same way as the "Accessible Tracks", as I have not modified it. However, it behaves almost the same way with one exception; The greyed out tracks never disappear (++ and the newly mounted disk tracks never appear) . I had to re-start MM before the greyed out tracks were removed from the view.
Accessible and Available Tracks problems? BUG#5204
Moderator: Gurus
-
SlowFoxSoftwareLTD
- Posts: 70
- Joined: Thu Nov 20, 2008 8:17 am
- Location: Toronto, Canada
Re: Accessible and Available Tracks problems?
In other views do inaccessible tracks automatically show they're accessible when you connect the media again?
The issue with both scenarios seems to be a simple refresh issue. The only question is if this is by design or not as in certain situations MediaMonkey doesn't refresh by design. The first one I can live with as I assume F5 resolves it. The second issue should be addressed as it requires more from the user (have you tried switching filters to see if previously inaccessible tracks show up when they're accessible again?).
The issue with both scenarios seems to be a simple refresh issue. The only question is if this is by design or not as in certain situations MediaMonkey doesn't refresh by design. The first one I can live with as I assume F5 resolves it. The second issue should be addressed as it requires more from the user (have you tried switching filters to see if previously inaccessible tracks show up when they're accessible again?).
Download MediaMonkey ♪ License ♪ Knowledge Base ♪ MediaMonkey for Windows 2024 Help ♪ MediaMonkey for Android Help
Lowlander (MediaMonkey user since 2003)
Lowlander (MediaMonkey user since 2003)
Re: Accessible and Available Tracks problems?
Added as Mantis bug 5204.
Download MediaMonkey ♪ License ♪ Knowledge Base ♪ MediaMonkey for Windows 2024 Help ♪ MediaMonkey for Android Help
Lowlander (MediaMonkey user since 2003)
Lowlander (MediaMonkey user since 2003)
-
SlowFoxSoftwareLTD
- Posts: 70
- Joined: Thu Nov 20, 2008 8:17 am
- Location: Toronto, Canada
Re: Accessible and Available Tracks problems? BUG#5204
In all my other views the inaccessible tracks are greyed out (font is grey) and they become "blacked" (font is black) when they become accessible. This is good. None of my other views has a "Status is Accessible" filter.
The problem is only in the view with the "Status is Accessible" filter. F5 (refresh) does nothing. It does not help.
I found two ways to work around this issue: 1) Restart MM; 2) Change filter away from the above filter and then come back to it.
One more symptom I noticed: The Location node is also incorrect with the above scenario.
The Playlists/Accessible Tracks/ node works just fine. F5 refreshes it correctly.
I expected that a "Status is Accessible" filter would work the same way as the "Accessible Tracks" node.
The problem is only in the view with the "Status is Accessible" filter. F5 (refresh) does nothing. It does not help.
I found two ways to work around this issue: 1) Restart MM; 2) Change filter away from the above filter and then come back to it.
One more symptom I noticed: The Location node is also incorrect with the above scenario.
The Playlists/Accessible Tracks/ node works just fine. F5 refreshes it correctly.
I expected that a "Status is Accessible" filter would work the same way as the "Accessible Tracks" node.
SlowFox.