I’m running a trial of Voyager (latest daily build 2.2.13f) and it doesn’t appear to want to connect to a NAS / network location for opening an image. I’m assuming therefore that it won’t allow me to save images to a network location either?
Calling a mapped drive location:
Using a local http web address (192.168.0.x/xxx) also does not work but has a different error message (I can’t show 2 embedded images as a new user).
I generally use NAS for all of my data files, so is this a Voyager issue, or do I need to set something up?
Check your network settings or map your network folder as disk. Voyager uses the OS API to load and save the files, cannot do in anyelse mode. Connect to NAS is not something related to an application but to your OS.
In my NAS(s) I have a root folder ‘Jon’, which I map to - this works for most other applications, which is why I thought it might have been a Voyager thing.
All other folders are in a tree below this.
I cannot see any mapped folders in Voyager for example:
There should also be a list of all mapped drives?
Anyway, this looks like it’s not a Voyager issue, more like the way I have my network setup.
I think problem is Voyager start like administrator, so map network driver with a different credential directly on the browse for folder clicking on the computer node with right click on mouse, choose reconnect with a different user, switch the username with the actual user name you are logged and use the password of this user, close the browse for folder control and reopen , you will found the new sharing
I use a QNAP NAS and have Voyager save to a local drive on my imaging PC, and then the QNAP Qsync application copies it to the NAS (Which means the initial file save in Voyager is faster as it is local) and Qsync also copies the file to my PC in the house from the NAS. I end up with three physically separated copies of each image file within about 30 seconds of the download from the camera. I imagine most NAS manufacturers would have a similar sync application.
Is not an issue … you must use the right user to connect the network drive or change the policies in OS.
Overall isn’t a good idea to use a NAS (or generally a slow disk) like primary storage during Voyager running, you must use the fastest disk you have on the PC.
The latest daily build 2.2.13g2 has fixed the mapped network drives issue on both the ‘demo’ pc and ‘trial’ laptop installations I am testing.
I’ve also installed Qsync, and am testing that - hopefully without issues, as I usually like to be very manual when it comes to backups / syncing etc. as I’ve been caught out before!
