...I'll have to change all the filenames in JRiver MC too.
Yes, not a very attractive solution. Hopefully, there's an easy fix—surely being able to scan a network share is a fairly common requirement.
So I guess I'll have to restart PVD for now unless another solution appears.
Just curious—are you unable to even select the network path in the dialog when it's run manually? I suppose the problem is the dialog itself is not being equipped to handle network drives.
Here's a question for you that's sort of related to this (and, no doubt, caused me to think of the
subst command). My primary means of transferring data from my old computer to the new one will by via a USB drive (much of the video data resides only there anyway). I'm thinking the best way to do that is...
1. Copy all the data (from several partitions) on the USB drive to directories of the HDD of the new computer.
2. Map each directory (that was a partition) to the same drive letter on the new computer.
3. Install PVD and MC with the same database/library and, to the extent possible, configuration data. Hopefully, both applications will find all media files exactly where they are expected to be, and PvdImport will also be unaffected.
4. Use MC to move all data to new locations on the HDD (generally, to consolidate multiple locations into fewer; the USB drive will no longer be used for media). Scan the new locations to update the paths in PVD. Then run PvdImport mass update to ensure all the pathnames match.
Do you see any problems with this approach? Is there an easier way? It's tempting to think there must be if the two computers were networked (something I'm not planning on doing because the old computer is to be retired). But that doesn't seem to offer any easier means of migrating files while keeping them in sync with the MC library and PVD database.