> For some users, myself, the NP is in the library because it is referencing tracks which are in the library.

By that token NP would be "in" My Computer because it references tracks which are in My Computer.

In truth NP is outside the Library and My Computer, as the tree shows.

MM's "Remove" command and others should accord to MMs own structure, rather than the conceptual restructuring employed by users of a sub-set of its facilities.

For some users, myself, the NP is in the library because it is referencing tracks which are in the library.

Forgot to add, it really doesn't matter to me one way or the other because I rarely remove tracks from the library, so having it your way or the way it is now is a moot point for me.

> if I remove it from the library than I want it removed from NP and everything else within my library.

"Else"? NP is not in the library, note. If it was, I agree removal from it would be appropriate. But it is not, so it is not.

Good, bad, logical or illogical, my personal opinion is if I remove it from the library than I want it removed from NP and everything else within my library. And if I choose the remove from Library and Computer option, then I want it removed from the library, NP and the computer. Just my opinion but I prefer the behavior it is using now. And as stated earlier, I only use the in Library option, not the MC option, so this is the only area I am speaking on.

> If it's added through the MC node (or externally), then it's probably referenced via the file path ...

Cewrtainly it seems that was true until 1131 - see http://www.mediamonkey.com/forum/viewto ... 24#p126024 .

> Whereas if it's a library track, I would guess it references those through the ID.

I can see no good reason for such an inconsistency.

> Thus, if you delete it from the library, that ID no longer exists to reference.

Since the ID is not required to reference it, the code could simply switch that reference to a filepath.

> If that is the case, there may be performance benefits from using the ID

I would have though the main performance effect would be detriment, since using the ID adds an indirection through the DB.

No, someone removing a song from their library should instantly incinerate every reference to the recording that has ever existed, duh. Though on this one, I'm going to have to agree with Chris. If you choose to delete it from the library, I see no reason for it also being removed from the NP list. As the NP list may contain references to Library tracks as well as tracks not contained within the library. Now if the individual selects to delete it from the Library & Computer, then I think there is some logic for also removing it from the NP list (and player).

This may come down to how the NP list references tracks however. If it's added through the MC node (or externally), then it's probably referenced via the file path and name. Whereas if it's a library track, I would guess it references those through the ID. Thus, if you delete it from the library, that ID no longer exists to reference. If that is the case, there may be performance benefits from using the ID and I would think this behavior would be an acceptable trade off.

> I think it's done for clarity. It would probably confuse some if the tracks remained in the Now Playing.

I wonder where that logic stops. "For clarity" should the track be removed also from the player? From your HD?? From the web store you bought it from???

I think it's done for clarity. It would probably confuse some if the tracks remained in the Now Playing. Although I have no issue with the track remaining in the Now Playing I think it's more clear if it's removed from the Now Playing when removing from the Library.

> Since that is the behavior it is exhibiting I am going to go out on a limb and assume that is the way it is supposed to behave.

Since the behaviour MM exhibits has changed in reponse to over a hundred reports of mine, I'm going to go out on a limb and suggest we wait and see

> Sorry to clog up your post with my expectations.

You're welcome!

chrisjj wrote:> Tell me why wouldn't you expect it to be removed from NP??

Because no-one asked for it to be removed from NP.

How much stuff does MM do that I did not ask it to do? But all that aside, if that is how the developers programmed it to be, then that is how it is, whether we want it that way or not. Since that is the behavior it is exhibiting I am going to go out on a limb and assume that is the way it is supposed to behave. I assume that MM is programmed to have different behavior with the removal of tracks from the library and those that are in NP that are not in the library.

Sorry to clog up your post with my expectations.

> Tell me why wouldn't you expect it to be removed from NP??

Because no-one asked for it to be removed from NP.

> Keep in mind I do not use or listen to tracks from the MC node so I am unfamiliar with it's expected behavior.

Ah, there's the difference between us. I often use NP for playing tracks from MC and Explorer. And for collecting a list to be exported to M3U. I don't want this messed up just because cleared library junk just happened to include one of those tracks.

I guess this one is all about expectations, unless I am missing the point you are making, I expect it to remove it from the library, NP and any playlist references. Tell me why wouldn't you expect it to be removed from NP?? It is my understanding that tracks selected from the My Computer node can be in the NP list, but I would expect the behavior to be different for tracks which are added to NP that are actually in the library. Keep in mind I do not use or listen to tracks from the MC node so I am unfamiliar with it's expected behavior. I deal only with tracks in my library and I expect them to be removed from NP if I remove them from my library.

Actually not. Try it and see.

chrisjj wrote:Thanks, but it wasn't. And it makes no difference.

Obviously it does, since that is how the developers programmed it to be....

nynaevelan wrote:If the track was added from the library

Thanks, but it wasn't. And it makes no difference.