Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[mattkhan]

This has been raised a few times over the years, seems a simple thing and would be useful to get it fixed. I'm raising it here as it affects the windows build as well.

A windows client and playback files directly if it has access to it via the same path as the server, i.e. has the same drives mounted with the same drive letter. This breaks on other platforms (and is somewhat inflexible on windows). It would be preferred if each client could set a path prefix for locations instead.

For example perhaps you could specify a list of path variables like

FILMS=W:
MUSIC=X:

anywhere it sees W: then it replaces internally with $FILMS

another client could then set

FILMS=/media/films
MUSIC=/media/music

and everything would just work

[Cryph]

I second this -- I just upgraded my Master License and this is literally the only shortcoming I currently experience.
I wind up maintaining two completely separate but identical libraries, one out in the cloud and one locally at home due to linux pathing.

[Peter_T]

+1 - this would make my life so much easier as well...