User manual GRASS VALLEY AURORA BROWSE RELEASE NOTES AND UPGRADE INSTRUCTIONS V7.1

[. . . ] 071-8639-10 Aurora Browse Release Notes Version 7. 1 Release Notes & Upgrade Instructions These release notes contain the most recent information and supersede previous publications, as of October 18, 2010. Check the Grass Valley website at www. grassvalley. com/docs for an updated version that contains additional important information. These release notes contain information for the following: · Aurora Browse client · MediaFrame server · MDI server · K2 BaseCamp Express · Aurora Proxy Encoder · SmartBins Encoder Copyright © Grass Valley, Inc. This document may not be copied in whole or in part, or otherwise reproduced except as specifically permitted under U. S. [. . . ] This last restart is required, regardless of whether the Details column does or does not display "Restart required". Install Browse client PC application If upgrading to Aurora Browse 7. 1, the previous version must be uninstalled first. If the Aurora Browse client application is already installed, any upgraded software on the MediaFrame server is automatically detected and a message box prompts you to upgrade your Aurora Browse client application. If you do not upgrade software as prompted, the automatic prompt is disabled for future upgrades. To enable the automatic prompt you must re-install the Aurora Browse client application. If the Aurora Browse user has administrator privileges you can use setup. exe to install the Aurora Browse application on the client PC. The executable file installs the prerequisites and the Aurora Browse application. If the Aurora Browse user does not have administrator privileges, an administrator needs to install all the prerequisites for the user. The user then can install the Aurora Browse application by using the AuroraBrowse. application installer. Use the following steps to install the Aurora Browse client application. See the Aurora Browse Installation and Configuration Guide for specific instructions on roles and licensing. Navigate to the location of the Browse installation file on the MediaFrame server share. Once you have installed the Browse client software, you will need to enter the name of the MediaFrame server. Logging in to the Aurora Browse client PC 1. To log in to Aurora Browse, select Programs | Grass Valley Aurora Browse | Aurora Browse. Aurora Browse will check your settings before the user interface displays. 18October 2010 Aurora Browse Version 7. 1. 0 Release Notes and Upgrade Instructions 25 Upgrading Aurora Browse and MediaFrame systems 2. If this is the first time you have accessed Aurora Browse, a dialog box displays asking you for the name of the Aurora Browse server. If you need to change this name later, select File | Connect to server. For information on using the Aurora Browse client application, see the Aurora Browse User Guide or the Help menu of the Aurora Browse client application. 26 Aurora Browse Version 7. 1. 0 Release Notes and Upgrade Instructions 18October 2010 Licensing Grass Valley products The following sections contain instructions for managing Grass Valley product licenses. About software licensing Licenses are requested through the License Wizard and managed through the SabreTooth License Manager, which is installed on the Grass Valley product with the Grass Valley software. The License Wizard and SabreTooth License Manager must be located on the Grass Valley product. License information is stored in text files that you can manage just like any other file on your system. Licenses are unique to the system for which they are requested and cannot be used on any other machine. You should back up the license text files to a separate drive or as part of a recovery image. Licenses are based on your system's unique identifier, which is partially derived from your system's Media Access Control (MAC) address. [. . . ] Periodically, the Smart Bin Encoder should be monitored and these windows closed. If you transfer a single asset to an archive that already has an asset of that name, a dialog box appears asking if you want to rename the asset. If you transfer a batch of archives without enabling auto-rename, no dialog box prompts you to rename the assets; instead Browse returns an error message. Specify auto-rename before archiving the batch of assets. CR75426 Description: Workaround: CR58258 Description: Workaround: CR57788 Description: Workaround: CR59288 Description: Workaround: CR58568 Description: Workaround: CR92283 Description: Workaround: 40 Aurora Browse Version 7. 1. 0 Release Notes and Upgrade Instructions 18October 2010 Known Issues CR86742 Description: Workaround: When archiving to SGL 6, the status page does not show transfer updates. [. . . ]