Launching Client takes over a minute after adding a download area in Local Settings
CompletedHi Norman
New install with latest v5 release.
Clients on all PCs (3of) ran instantly from fresh install.
In client local settings i have added a mapped network drive where the client holds exported footage. When we click apply after adding the drive it took a while to apply (at one point client was unresponsive and the windows pop up box came up saying close program or wait to respond).
Once applied and client reloaded it takes over a minute for the client to launch.
Environment - Windows 11 Pro Workstations, QNAP NAS Storage share folder mapped as Z Drive.
This happens across all 3 workstations, there are no network issues on any workstation/QNAP
Thanks
aaron
-
Hi Aaron ONeill,
I'm fairly confident, that the delay is caused by the mapped network drive, or more specific the amount of files and their volume which cause the delay.
What happens, is that each time, you open the client, all content of the mapped drive has to be initialized, and the higher the volume, the long it takes to load.
You can confirm this, by starting the client through the command line or command prompt with the parameter --skip-media-folder-scan If there are no other issues, the client should start within seconds.
0 -
Hi Norman
I have done this by adding the paramters to the shortcut icon and the first window opens rapidly as expected. however the next two windows still open slower than expected albiet not as slow as normal, the end user has 3 instances of the client running across three monitors using the save windows config option.
Is there a way (batch file maybe) to run all instances with the parameter exceptions? Or does v6 overcome this issue with mapped drives?
thanks
0 -
Hi Aaron ONeill,
If you create a batch script with the following code, the client will start three times, and skips the scan of the media folder for each instance:
@echo off
start "" "c:\Program Files\Network Optix\Nx Witness\Client\6.0.0.39503\HD Witness.exe" --skip-media-folder-scan --no-single-application
start "" "c:\Program Files\Network Optix\Nx Witness\Client\6.0.0.39503\HD Witness.exe" --skip-media-folder-scan --no-single-application
start "" "c:\Program Files\Network Optix\Nx Witness\Client\6.0.0.39503\HD Witness.exe" --skip-media-folder-scan --no-single-applicationObviously, if you use another version of Nx Witness, than 6.0.0.39503, you use the applicable path to the correct version.
You also can remove the media folder from the Local Settings menu, tab General, by clicking on the folder you want to remove, and select Remove...This way, the media folder won't be scanned again, and you can remove the --skip-media-folder-scan parameter from the batch script.
To be clear, there is no issue, if the volume of media folder is significant, it takes a significant amount of time to initialize it.
0 -
Thank you.
Understood regarding no issue. The client has historic footage files (lots of) which they have to keep. As an alternative for other people facing the same issue i could map a seperate folder that is empty if neccasery but overtime i suppose the load time of the client will lengthen.
Thanks for your support
0 -
Hi Aaron ONeill,
They can have as much historic data as they want, but instead of indexing it everytime they open the Desktop client, they also can open the files if needed, through the Main Menu > Open > Files and open the desired file. This way, they can play the file in the desktop client, but the Desktop client doesn't initialize the media folder each time.
0
Post is closed for comments.
Comments
5 comments