Hi Peke,
Peke wrote: ↑Sun Dec 10, 2023 7:13 pmI could not replicate your behavior. Even I have incorrect credentials and use my app to change them I can play the tracks normally afterwards.
You are probably not testing what I am trying to report.
I am talking about a situation where credentials are not supplied:
- either the User got challenged, and then pressed Cancel, intending find and supply the credentials later, either via MM or some other way
- or the User didn't see the challenge ... easily done because MM5 does not do a good job of keeping these dboxes on top of itself... MM5 doesn't present these as a modal dbox, so if the user never responds MM5 keeps ob chugging along, giving no indication that it is waiting for something
- or the User accidently closes the challenge dbox
From this point MM5 never checks again. It relies on a stale cached status setting for the device.
Peke wrote: ↑Sun Dec 10, 2023 7:13 pm
Aren't 1 and 3 same thing? 1,2,3. You play track and it gets un dead link then you can edit properties. But yes this is a BUG opening properties should check accessibility.
1 and 3 are alike from the POV that they both make MM5 look buggy, but I think that they are different as they present differently to the User.
In #1 MM5 won't let me edit album art because it is inaccessible, whereas it it is editable using a different route through the UI.
In point #3 the tracks is reported as being inaccessible, when it obviously not because I can see it via the Folders view which looks directly at the file, ie. doesn't use the the file tags stored in the MM5 db.
If you are reporting that the only problem is with the File Properties facility, you are missing part of what I am trying to report.
There is at least one other situation where MM5 is use the stale cache of resource availability, ie. the FilesToEdit>DeadLinks report.
There are likely to be multiple other situations also.
The main point is that MM5 is using a stale cached value for resource availability status
It takes no account of a situation where the user has been challenged, failed to provide the credentials, and the User then provides the Credentials to Windows outside of MM5.
MM5 persists with the view that the resource is unavailable. And there is no indication as to the cause of the erroneous errors. And there is no way to get MM5 to recheck availability, without closing and restarting MM5.