Stephen, I don’t know if you’ve worked out any of these things with PG yet, but for the shortcut issue, I think the only thing that’s going to work is to replace the shortcut with a symbolic link. I’ve tried it with the Wavelab presets folders to network and local targets and it works fine, read and write.
There are built-in commands to create symbolic links in Windows and Mac, they’re a little clunky to make by command line, but they work where shortcuts don’t.
To do this, make a folder called WavelabNetworkPresets on a share on the server. Then from an elevated command prompt (run as admin), right-click-paste the following command at the command cursor (after substituting your info for User1, Server1, and Share1):
mklink /d “\Users\User1\AppData\Roaming\Steinberg\WaveLab 8.5\Presets\Workspace\Layout\AudioMontage\NetworkPresets” “\Server1\Share1\WavelabNetworkPresets”
then press Enter. It will tell you it made a Symbolic Link named NetworkPresets in the local AudioMontage folder. The link will act just like a local folder. Subfolders can be made and used. But Wavelab will need to be restarted to see new presets just added by someone else on the network. And separate folders should probably be made on the server for each different type of preset.
I’ve used symlinks before with other programs that don’t “understand shortcuts” (as Wikipedia puts it), to move the location of a large database that a program wanted to see in a certain place to an external drive. I think it’s quite common as I’ve seen it used for various similar things for iTunes, Gmail, Logic and Dropbox, where shortcuts could not be used.
So I guess the other question for PG is whether Wavelab can be made to “understand shortcuts”, if that’s really something that can be done, as Wikipedia implies. I’m not sure many programs can do that.
Hope you and PG can sort this, and the other things out. I’m interested in doing it myself and didn’t know about the other built-in options for networking in Wavelab that you’ve pointed out.
btw, I normally use a simple program from cnet to make symlinks, but it would require installing on every client machine, which you probably wouldn’t want to do. Also btw, symlinks can’t be easily copied (normal copies don’t work), they should be created on each client machine. And targets can’t be moved or renamed without re-creating the links.
But I also wondered, is there a reason why each user can’t have their own complete settings folder on the server, and just load those when they go from room to room? It seems like Wavelab could be better customized to handle a scenario like that (like choose a settings folder on startup, rather than going to Options, changing the folder, and restarting), but I’m not sure I won’t be trying that way first.