2009-12-09, 15:25
Many users are using a number of techniques such as drive mapping, or symbolic links to create 'virtual' folders.
They are doing this in order to be able to move media files from one location to another WITHOUT having to rebuild their library.
e.g. Mapping drive M: to music and remapping drive M to the relevant server or folder.
My suggestion is to handle this is a uniform way across all platforms, by creating support for virtual paths in XBMC.
The paths would work like this:
1) A user sets up a virtual path with a name of their choosing e.g. "My Music"
2) The user maps that virtual path to a physical one e.g. "C:\My Media\My Music"
3) Music is added to the library with the "My Music:" path (which is substituted at runtime for the physical path.
This then allows a user to scan all their music from My Music: and later move their media to another location without screwing up their library. They only have to remap My Music: to the new location.
This is NOT to be confused with 'Sources' which are slightly different
They are doing this in order to be able to move media files from one location to another WITHOUT having to rebuild their library.
e.g. Mapping drive M: to music and remapping drive M to the relevant server or folder.
My suggestion is to handle this is a uniform way across all platforms, by creating support for virtual paths in XBMC.
The paths would work like this:
1) A user sets up a virtual path with a name of their choosing e.g. "My Music"
2) The user maps that virtual path to a physical one e.g. "C:\My Media\My Music"
3) Music is added to the library with the "My Music:" path (which is substituted at runtime for the physical path.
This then allows a user to scan all their music from My Music: and later move their media to another location without screwing up their library. They only have to remap My Music: to the new location.
This is NOT to be confused with 'Sources' which are slightly different
