Transferring Volocity Configurations Between Workstations or Users

If you have purchased a new workstation or need to standardize settings across multiple user accounts on a single workstation, Volocity configurations can be transferred. Follow the steps below to safely transfer both user-level settings and system-level configurations.

On Windows Workstations

1. Export User-Level Settings

• Path:
  The user-level settings for Volocity are stored in the following registry key:
  HKEY_CURRENT_USER > Software > Improvision > Volocity
  These settings include lightpaths, import preferences, and other user-specific configurations.

• Steps to Export:

  1. Log in using an Admin account.
  2. Go to the Start menu, search for regedit, and open the Registry Editor.
  3. Navigate to the path:
     HKEY_CURRENT_USER > Software > Improvision > Volocity.
  4. Right-click on the Volocity key and select Export.
  5. Save the exported file as a .reg file in a safe location.

• Steps to Import:

  1. Log into the desired user account.
  2. Double-click the exported .reg file to import the settings into the registry.

2. Export System-Level Settings

• Path:
  System-level configurations for Volocity (e.g., serial port setup, objective calibrations) are stored in the following registry key:
  HKEY_LOCAL_MACHINE > Software > Improvision > Volocity.

• Steps to Export:

  1. In the Registry Editor, navigate to:
     HKEY_LOCAL_MACHINE > Software > Improvision > Volocity.
  2. Right-click on the Volocity key and select Export.
  3. Save the file as a .reg file.

• Steps to Import:

  1. Double-click the exported .reg file on the target workstation to import the system configurations.

3. Important Notes for Windows:

• If transferring both user-level and system-level settings, you must export and import both .reg files.
• Caution: Only export the specific Volocity keys. Accidentally exporting and importing the entire registry (e.g., all keys under HKEY_LOCAL_MACHINE) can severely disrupt the system, potentially requiring a complete OS reinstallation.
• Lightpath Settings Issue:
  • After transferring configurations to a new workstation, lightpaths may appear missing because the camera ID in the registry has changed.
  • For DCAM cameras (e.g., Hamamatsu), you may need to update the DCAM IDs in the registry to restore lightpaths. See detailed instructions here.

On Macintosh Workstations (version 6.3 and older)

1. Export User-Level Settings

• Path:
  User-level settings are stored in:
  Hard Disk > Users > Home Directory (House Icon) > Library > Preferences > Volocity Preferences.

• Steps to Export:

  1. Navigate to the path above.
  2. Copy the Volocity Preferences folder to a safe location.

• Steps to Import:

  1. Move the Volocity Preferences folder to the same path in the target user account’s home directory.

2. Export System-Level Settings

• Path:
  System-level settings are stored in:
  Hard Disk > Library > Preferences > Volocity Preferences.

• Steps to Export:

  1. Navigate to the path above.
  2. Copy the Volocity Preferences folder to a safe location.

• Steps to Import:

  1. Copy the folder into the same path on the target workstation.

3. Important Notes for macOS:

• Avoid Mixing Files: Both the user-level and system-level folders have the same name ("Volocity Preferences"). To avoid confusion, create parent folders (e.g., "User Settings" and "System Settings") before exporting.
• Ensure the files are placed in the exact corresponding paths on the target workstation.

Final Notes on Configuration Transfers

• Lightpath and Camera Settings:

  • On Windows systems, lightpath settings tied to specific cameras may not transfer correctly due to changes in camera IDs. For Hamamatsu DCAM cameras, you can manually adjust the DCAM IDs in the registry to restore these settings.

• Backup and Test:

  • Always create backups of the original settings before making changes.
  • After transferring settings, test Volocity to ensure all configurations have been successfully applied.

By following these steps, you can efficiently transfer Volocity configurations across workstations or user accounts while minimizing potential issues.