Updates, Backups And Sharing Sounds; Operating System Updates - Kemper Profiler Main Manual

Updates, Backups and Sharing Sounds 281

Updates, Backups and Sharing Sounds
The PROFILER operating system should be updated on a regular basis to receive refinements and new features. All
you need is an internet connection, a PC or Mac and a USB memory stick.

Operating System Updates

Before we lay out the technical steps to perform an update of the PROFILER operating system, let's explain the
concept of how the PROFILER software evolves:
KEMPER is constantly improving the software in terms of new features, enhanced capabilities, and fixes for known
issues. Software updates are available on the KEMPER download page and are free of charge to all users. All you
need is an active user account, to which a PROFILER is registered with its serial number. As soon as you log into
your account, you will have access to any available upgrade packages.
Each new software revision is first tested internally by the developers, and by our team of experienced beta testers.
As soon as it seems to be suitably mature, it will be published as a public beta. A public beta might be followed by
another public beta which will include fixes and enhancements based on initial user feedback. Generally speaking,
public beta software is not recommended for critical environments and productions. However, if you don't mind
taking a bit of a risk and want to check out the latest and greatest innovations, you are invited to test and share your
valuable input and feedback, for example in our user forums.
By the way, if you create a backup before you upgrade, you can always downgrade to our latest release version,
restore your backup, and be on safe ground for your next job. This way, you can completely avoid occasional
downward compatibility issues that can affect data stored under a new operating system. Downgrades follow the
same procedure as upgrades.
After a few iterations, the public beta software normally matures into a stable OS. At this point we elevate its status
from public beta to release software. Not every revision makes the cut to become a release. So, don't be surprised, if
a release 3.3.0 is for example followed by a release 4.0.6.