Feature request: mapping/rewrite rules for file location

[fvdpol]

Reported on Media Monkey forum by Teknojnky on Mon Oct 22, 2018 4:53 am

link: http://www.mediamonkey.com/forum/viewtopic.php?f=2&t=31680&sid=4c4111f5c9aba2c4fc277304e5064733&start=105#p450930

Ok for the feature request, I would like to suggest an option to modify the path (or more specifically, the drive) of the exported files.

for example, mediamonkey and itunes runs on windows, and the music files are on a network server.

the paths in both are \sauron\media\audio\ and so on

<key>Location</key><string>file://localhost//sauron/media/audio/MP3/B/Bad%20Religion/1990%20-%20Against%20the%20Grain%20%5BMP3%5D/13%20-%20Bad%20Religion%20-%2021st%20Century%20(Digital%20Boy).mp3</string>

plex however runs on that network server itself, so the path is local

<key>Location</key><string>file://localhost/data/media/audio/MP3/B/Bad%20Religion/1990%20-%20Against%20the%20Grain%20%5BMP3%5D/13%20-%20Bad%20Religion%20-%2021st%20Century%20(Digital%20Boy).mp3</string>

while it's not difficult to do a find/replace, its an additional step I have to stop and do any time I want to update the xml for plex.

I have to replace the //sauron with /data

I would think this could be easy to do, since MM stores the drive and path separately.

I could probably go in the script and hardcode it, but I figure this might be useful for other users who have network stored music, which makes the path different from what itunes/mediamonkey see.

[fvdpol]

Thinking a bit on how to this could be made generic/flexible, as the the replacements/substitutions will greatly depend on the way a user is using various storage locations for the files...

Possible idea is to have a table with a number of substitution (find-replace) rules ordered by priority: first try if 1st rule matches, if not try 2nd etc.

Rule would try to match locations starting with file://localhost<FindString>, and if this matches replace this with file://localhost<ChangeToString>

for the original requestor's use-case this would the lead to a configuration of:
FindString: //sauron
ChangeToString: /data

quick draft mock-up of user interface:

names of the fields need some more thought, as this is probably not intuitive