Who Can Upgrade?

Upgrades to Version 4 are available for VoxPro 3.0, 3.1, 3.2 and 3.3 software license holders. Cost of $199.00 US, includes a CD-ROM with our latest version, HASP USB hardware dongle, one year tech support, free software upgrades for one year, and UPS Ground shipping.

Upgrading from v 3.2 and 3.3 requires the return of the original HASP PP dongle sold with the VoxPro software. You have a 30 day window, after installing your upgrade, to return your old version 3x dongle with the provided UPS envelope.

Order Upgrade »

Instructions for upgrading from VoxPro 3.x to 4.x

We’ve made significant changes to VoxPro! The result is that files from VoxPro version 3 (3.x) are not compatible with VoxPro version 4 (4.x).  Nonetheless, there is a migration path.  You may save yourself considerable confusion and aggravation by taking a moment to familiarize yourself with the migration procedure before installing the upgrade.

Uninstall any pre version 4.x of VoxPro before installing version 4.x or higher. Version 4.x uses a different installer package which is incompatible with the installer used in previous versions. The 4.x installer will not overwrite previously installed VoxPro program files, so they must be uninstalled first. This will not affect existing audio files in any way.

Upgrading on the same PC

If you install 4.x in the same location where you have 3.x installed, then 4.x will “see” the 3.x user configuration file VP_Config.vpc and use it to create corresponding user accounts in the new format.  The accounts it creates are only the 3.x accounts that physically reside on the local machine.  When users login for the first time, they are prompted by a popup window with instructions on how to import their 3.x files into the new 4.x format.  The tool that performs this task is called Version Converter, and it is enabled simply by the presence of the 3.x VP_Config.vpc file in the 4.x folder.  Version Converter is discussed more fully below.

Upgrading on a new PC

If you install 4.x in a different location from where 3.x is installed, 4.x will not see the VP_Config.vpc file, and will thus have no knowledge of the legacy 3.x user accounts.  This may or may not be what you want, depending on circumstances.  If you mean to move your user accounts to a different location than where they were in VP3 (for example, you would like to put them on a bigger hard drive), then you’ve done the right thing.  Login as Administrator, go to the Accounts menu and (re-)create your users in the new, preferred location.  Exit VoxPro, find your original 3.x  VP_Config.vpc file (it should still be in the old 3.x folder), and copy it into the new 4.x folder.  When VoxPro is restarted, users will have access to the Version Converter utility.  Files converted to 4.x format will be copied to the new account locations.

Upgrade with remote server

What if your user accounts are on a remote server?  In this case it doesn’t really matter whether you install 4.x in the same location as 3.x, since only local accounts are automatically carried over from 3.x to 4.x.  Login as Administrator and (re-)create the accounts, taking special care to specify the remote server in the path to each user’s account.  (Or you may take this opportunity to move the account, specifying a different location, be it local or remote.)  Copy the VP_Config.vpc file into the 4.x folder if it is not already there, and restart VoxPro.  The Version Converter utility is now available to each user.

Using Version Convertor

Access to the Version Converter file conversion utility is enabled if 4.x finds the 3.x configuration file VP_Config.vpc in its installation folder when it starts up.  Version Converter is launched from the main File menu.

Version Converter may be run automatically, or you may control all of its actions manually.  The choice is up to each user.  Either way, you may cancel its actions at any time and return to VoxPro.  You may then restart Version Converter at a more convenient time and pick up from where you left off.

Version Converter requires two to three minutes (depending on CPU speed) to convert and import an hour’s worth of audio into 4.x.  Be aware, then, that a large file collection comprising, say, 10GB of storage, might take a full hour to convert.  You may use VoxPro during this time, but you might be distracted by Version Converter’s progress notifications.

If you run Version Converter automatically...

  • It empties your 3.x  Deleted Files folder (Recycle Bin in version 3.1).
  • It only converts Edits, not Masters.  If you have Masters that you access frequently, you may want to first run Version Converter manually, to import your Masters, then run it in automatic mode to get your Edits.
  • It deletes your Edits (and corresponding Masters) as they are converted. 
  • It only allows you to convert your own files.  You must be logged into 4.x using the account you want to convert.  So, if you are logged in as Administrator, but you are looking at Joe User’s folders, running Version Converter in automatic mode will convert the Administrator’s files, not Joe User’s. 

If you run Version Converter manually...

  • It does not automatically delete 3.x files as they are converted.  You will probably want to delete old files as you go along, especially if space on your hard disk is limited.
  • It allows you to pick and choose which files you want to convert.
  • It allows you to specify the destination account and folder for converted files. 
  • It allows the Administrator to convert files from any account that existed in your 3.x installation.

* Please note that Hotkeys assigned in 3.x cannot be transferred to 4.x, but will have to be reassigned once again.

Final steps

After you have given users sufficient time to import their files from 3.x, you may reclaim the disk space they occupy by selecting the Delete Version 3 Files command from the main File menu (you must be logged on as Administrator to do this).  This will delete all of the 3.x edit, master and reference files that are located in the same folders as the current 4.x accounts.  3.x files that are located in other areas must be deleted manually.  (So, for example, if you have moved your user accounts from the C: drive to a new D: drive, you’ll have to clean out the old files on C: by hand.)   This action also deletes the 3.x configuration file VP_Config.vpc from the VP4 folder, thus disabling use of Version Converter.