|
|
Something like this was already fixed? |
|
|
Ludek
2012-02-13 10:10
developer
~0030386
Last edited: 2012-02-13 10:11
|
Zvezdan, I am not sure that I understand, are you talking about UPnP tracks added to library and presented in
Collection/Location/Media Servers node?
Could you attach a small screengrap?
|
|
|
|
Yes, I am talking about tracks from the Media Servers node inside of any collections: Entire Library, Music...
Take a look at the screenshot, Media Servers node in the root of the tree has sub-folders, but not the Media Servers node inside of collection. In the Path column of the tracklist you could see that some files are from sub-folders of that UPnP server.
http://img826.imageshack.us/img826/7554/upnpfolders.png |
|
|
Ludek
2012-02-13 23:45
developer
~0030406
Last edited: 2012-02-13 23:52
|
OK, this is a low priority issue and is not generally fixable. Some servers (like MediaMonkey server) presents track URL as http://IP:Port/TrackID.mp3 but presents the same track in various locations when browsing the server. The locations can change dynamically as they are just virtual containers, so it doesn't make sense to store them in the MM.DB
|
|
|
|
> The locations can change dynamically
How the location could change dynamically if I have fixed structure of folders in the UPnP server?
> it doesn't make sense to store them in the MM.DB
You already have them stored in the MM.DB. Here is the track stored in the Path field of the Songs table:
uuid://79ebf701-e4d2-0a70-e5a5-de0405d58264/0/0/Music/Dance/Deepface%20-%20I%20Want%20to%20Live%20%5BOriginal%20Radio%20Edit%5D.mp3
That path already contains folders which cannot be changed dynamically without breaking the link to the file. |
|
