071-8550-08

Aurora Ingest Version 6.5.2 Release

Notes and Upgrade Instructions
These release notes contain the most recent information and supersede previous
publications, as of 31 August 2009. Check the Grass Valley website at
www.grassvalley.com/docs for an updated version that contains additional important
information.

Copyright © Grass Valley, Inc. All rights reserved. Printed in the United States of America. Portions of software © 2000 – 2009, Microsoft Corporation. All rights reserved. This
document may not be copied in whole or in part, or otherwise reproduced except as specifically permitted under U.S. copyright law, without the prior written consent of Grass
Valley, Inc., P.O. Box 59900, Nevada City, California 95959-7900. This product may be covered by one or more U.S. and foreign patents.
Product options and specifications subject to change without notice. The information in this manual is furnished for informational use only, is subject to change without notice,
and should not be construed as a commitment by Grass Valley, Inc. Grass Valley, Inc. assumes no responsibility or liability for any errors or inaccuracies that may appear in
this publication.
Grass Valley, K2, Aurora, Summit, Dyno, Turbo, M-Series, Profile, Profile XP, NetCentral, NewsBrowse, NewsEdit, NewsQ, NewsShare, NewsQ Pro, and Media Manager are
either registered trademarks or trademarks of Grass Valley, Inc. in the United States and/or other countries. Grass Valley, Inc. products are covered by U.S. and foreign pat-
ents, issued and pending. Additional information regarding Grass Valley, Inc.’s trademarks and other proprietary rights may be found at www.thomsongrassvalley.com. Other
trademarks and logos used in this document are either registered trademarks or trademarks of the manufacturers or vendors of the associated products, such as Microsoft®
Windows® operating system, Windows Media® player, Internet Explorer® internet browser, and SQL Server™. QuickTime and the QuickTime logo are trademarks or regis-
tered trademarks of Apple Computer, Inc., used under license therefrom.
 Contents
Grass Valley Product Support.....................................................................................................3
Release Summary......................................................................................................................5
What's new in version 6.5.2.....................................................................................................5
Fixed in 6.5.2.......................................................................................................................5
Feature limitation in this release..........................................................................................6
Changes and features in previous releases............................................................................6
Version 6.5.1.132.................................................................................................................6
Version 6.5...........................................................................................................................6
Older versions......................................................................................................................8
Version compatibility...................................................................................................................9
System specifications..............................................................................................................9
Compatible Grass Valley products.........................................................................................11
Compatible third party products............................................................................................12
Upgrading Aurora Ingest systems.............................................................................................13
Upgrading Aurora Ingest devices with SiteConfig.................................................................13
About upgrading Aurora Ingest devices with SiteConfig....................................................13
Prepare for upgrade...........................................................................................................13
Prepare SiteConfig for software deployment.....................................................................14
Upgrade K2 systems.........................................................................................................14
Distribute devices into deployment groups........................................................................15
Install High Priority Windows updates (recommended).....................................................15
Manually upgrade systems................................................................................................16
Check all currently installed software on Aurora Ingest devices........................................16
Add software package to deployment group for Aurora Ingest devices.............................17
Setting deployment options................................................................................................18
Upgrade software on Aurora Ingest devices......................................................................21
Upgrade NAS systems......................................................................................................23
Upgrade Browse and MediaFrame systems......................................................................24
Licensing Grass Valley products...............................................................................................25
About software licensing.......................................................................................................25
Requesting a license.............................................................................................................25
Adding a license....................................................................................................................27
Deleting licenses...................................................................................................................27
Archiving licenses..................................................................................................................28
Aurora Ingest licenses...........................................................................................................28
Operation considerations..........................................................................................................29
Additional notes........................................................................................................................32
Installing software .................................................................................................................33
Configuring ScheduALL properties ......................................................................................35
Configuring ScheduALL application .....................................................................................39
Known Issues............................................................................................................................41

2 Aurora Ingest Version 6.5.2 Release Notes and Upgrade Instructions 31 August 2009
 Grass Valley Product Support
To get technical assistance, check on the status of a question, or to report a new issues,
contact Grass Valley Product Support via e-mail, the Web, or by phone or fax.

Web Technical Support

To access support information on the Web, visit the product support Web page on the
Grass Valley Web site. You can download software or find solutions to problems.
World Wide Web: http://www.grassvalley.com/support/
Technical Support E-mail Address: [email protected]

Telephone Support
Use the following information to contact Product Support by phone.

International Support Centers

Our international support centers are available 24 hours a day, 7 days a week.
Support Center Toll free In country

France +800 80 80 20 20 +33 1 48 25 20 20

United States +1 800 547 8949 +1 530 478 4148

Authorized Local Support Representative

A local support representative may be available in your country. To locate a support

center during normal local business hours, refer to the following list. This list is
regularly updated on the website for Grass Valley Product Support
(http://www.grassvalley.com/support/contact/phone/)
After–hours local phone support is also available for warranty and contract customers.
Region County Telephone

Asia China +86 10 5883 7575

Hong Kong, Taiwan, Korea, +852 2531 3058
Macau
Japan +81 3 6848 5561
Southeast Asia - Malaysia +603 7492 3303
Southeast Asia - Singapore +65 6379 1769

31 August 2009 Aurora Ingest Version 6.5.2 Release Notes and Upgrade Instructions 3
Grass Valley Product Support

Region County Telephone

Indian Subcontinent +91 11 515 282 502;

+91 11 515 282 504
Pacific Australia, New Zealand +61 1300 721 495
Central America, All +55 11 5509 3440
South America
North America North America, Mexico, +1 800 547 8949;
Caribbean +1 530 478 4148
Europe UK, Ireland, Israel +44 118 923 0499
Benelux – Netherlands +31 (0) 35 62 38 421
Benelux – Belgium +32 (0) 2 334 90 30
France +800 80 80 20 20;
+33 1 48 25 20 20
Germany, Austria, +49 6150 104 444
Eastern Europe
Belarus, Russia, +7 095 258 09 20;
Tadzhikistan, Ukraine, +33 (0) 2 334 90 30
Uzbekistan
Nordics (Norway, Sweden, +45 40 47 22 37
Finland, Denmark, Iceland)
Southern Europe – Italy +39 02 24 13 16 01;
+39 06 87 20 35 42
Southern Europe – Spain +34 91 512 03 50
Middle East, Near East, Middle East +971 4 299 64 40
Africa
Near East and Africa +800 80 80 20 20;
+33 1 48 25 20 20

4 Aurora Ingest Version 6.5.2 Release Notes and Upgrade Instructions 31 August 2009
 Release Summary

What's new in version 6.5.2

This version of software includes several improvements, in addition to correcting
some problems that were present in earlier releases.

Version 6.5.2

• Scheduling integration with VizuAll, Inc.'s ScheduALL — Enabling events

scheduled on Aurora Ingest Scheduler to appear on ScheduALL and vice versa.
• SiteConfig support — Network configuration and software deployment across
all Aurora products is supported by SiteConfig, Grass Valley's system management
tool.
• Administrator password – The default administrator account on Aurora devices
has credentials as follows:
• Username: administrator
• Password: adminGV!
SiteConfig expects these credentials by default.
• Records survive on Ingest Server close — Users are now able to close the Aurora
Ingest Server while recording is taking place. Records will continue for the
predetermined duration, regardless of whether the server application is launched
again.
• Documentation for this release — The following manuals have been revised or
are new:
• Aurora Ingest System Guide 071-8514-05
• SiteConfig Migration Instructions 071-8705-00
The manuals are on Aurora Ingest Software CD part number 063-8268-09.

Fixed in 6.5.2

Reference Description
number

CR101934 RMI import of trimmed XDCAM HD clip results in corrupted clip in News
database.
CR102312 Scheduler can skip past an event and leave it in "Ready" status.
CR102334 On system with full SQL installed, Ingest installer gives error that SQL
Express is not installed.
CR103947 Event stays as recording when SD K2 had stopped recording.
CR104457 Reordering templates no longer works.

31 August 2009 Aurora Ingest Version 6.5.2 Release Notes and Upgrade Instructions 5
Release Summary

Reference Description
number

CR104465 VTR Controller/VTR Ingest won't launch on Marathon systems.

CR104900 After using Scheduler to record to placeholder on main and backup server,
clip starts on different frame when loaded in main vs. backup Playout.

Feature limitation in this release

• No nested bin support with K2 Summit.

Changes and features in previous releases

The following sections describe changes and features in past releases.

Version 6.5.1.132

• K2 Summit compatible – The Aurora suite of software, including Aurora Ingest,

is compatible with the K2 Summit software.

Version 6.5

Aurora Ingest 6.5 is a major release for Aurora Ingest. Although each application has
new features and functionality, the overarching change is the inclusion of MediaFrame.
A complete, in-depth guide to what’s new is included in a document called What’s
New – Aurora Ingest 6.5.

Aurora Ingest Server

• MediaFrame Integration – New search and metadata tools have been embedded
in numerous areas within the application. MediaFrame server can be configured
within Tools | Options of Aurora Ingest - Server.
NOTE: For MediaFrame connectivity to function between the Scheduler, RMI,
and the VTR Ingest applications that are on a different domain than the
MediaFrame server, there must be a defined one-way trust relationship between
Aurora Ingest and the MediaFrame Server.
• Time of Day Timecode – Users can now select Time of Day timecode for feeds.
• MediaFrame Expiration Date Setting – Users can set expiration date for metadata
that ties into MediaFrame.

Aurora Ingest Scheduler

• MediaFrame Integration – Users can search, preview and mark highlights directly
from the scheduling application.

6 Aurora Ingest Version 6.5.2 Release Notes and Upgrade Instructions 31 August 2009
 Release Summary

• Improved Crash Record Control – Users can name crash records, select router
source, select aspect ratio setting and direct a crash record to a folder location, prior
to hitting record. These actions lead to a faster scheduling operation.
• Quick Schedule – Users can use Quick Schedule mode to the Scheduler grid for
efficient additions of feeds.
• Enhanced Trim and Extend – Users can trim and extend feeds via keyboard.
• X-Keys controller Support – X-Keys controller is supported with Scheduler and
MediaFrame to enhance the ability to log live and previously captured events.
• System Information Utility – The Help->About box now includes a System
Information Utility.
• Link to Placeholder – A currently recording event can be linked to a placeholder.
• Default Colors – A new set of default colors have been configured for Scheduler.
If needed, users can still change those default colors within Tools | Options.

Aurora Ingest RMI

• MediaFrame Integration – When MediaFrame is enabled, metadata can be mapped
from the removable media device to MediaFrame.
• Multiple Clips Merge – Users can merge multiple clips into a single clip on import.
• Preview and Trim – Users can preview and trim clips prior to import.
• Speed Improvement – Speed improvement after the need to transcode on import
had been eliminated.
• Edit During Import – Currently importing feeds are editable by Aurora Edit before
they are complete.
• DV100 Support – Support for DV100 media, via removable media import from
P2.
NOTE: Transfers of DV100 media to the Summit are supported, while transfers
to K2 server are not.
• AVC-Intra Support – Support for AVC-Intra media import.
• XDCAM HD 1080i Support – Support for XDCAM 4:2:2, 1080i, Long GOP
50mbit media import.
NOTE: XDCAM HD 720p import format is not yet supported.
• System Information Utility – The Help->About box now includes a System
Information Utility.
• Default Colors – Default colors have been changed for RMI.

Aurora Ingest VTR Ingest

• MediaFrame Integration – When MediaFrame is enabled, metadata can be added
either on a tape basis or clip by clip basis.
• Keyword Scan – Keyword scan feature automatically records an entire tape and
marks keywords for every timecode break that is found.
• Primary and backup records – Users can now make primary and backup records.
• System Information Utility – The Help->About box now includes a System
Information Utility.

31 August 2009 Aurora Ingest Version 6.5.2 Release Notes and Upgrade Instructions 7
Release Summary

Older versions

For information about older software versions not listed in these release notes, refer
to the release notes for those versions.

8 Aurora Ingest Version 6.5.2 Release Notes and Upgrade Instructions 31 August 2009
 Version compatibility
Versions qualified for compatibility with this release of software are summarized in
the following sections.

System specifications
This section describes the hardware requirements that customers should use when
purchasing equipment for this release. The minimum spec describes the bare minimum
requirement for running Aurora, which may reduce the quality of user experience,
depending on the task. The expected lifespan of minimum spec equipment is also less
than that of recommended spec equipment, since it lacks head room for future growth.
NOTE: Minimum specs for SD configurations are provided only for existing SD
customers upgrading to this release. New customers should use HD configurations.

Aurora Edit HD desktop, Aurora Ingest RMI (HD)

MINIMUM Spec RECOMMENDED Spec

Processor(s) Intel Core 2 Quad Core 2.33 Two Intel Xeon 5410 Quad
GHz Core 2.33 GHz
OR
Two Intel Xeon 5160
Dual Core 3.0 GHz
Memory 3 GB 3 GB
Graphics Discrete graphics with 256 Discrete graphics with 384
MB of dedicated memory MB of dedicated memory
and support for Direct3D 9 and support for Direct3D 9
and Shader Model 3.0 + 10 and Shader Model 4.0
System Drive 80 GB 7200 RPM SATA 80 GB 7200 RPM SATA
Media Drives 2 x 250 GB 7200 RPM 2 x 250 GB 7200 RPM
SATA striped SATA striped
Optical Drive CD/DVD CD/DVD
Network Gigabit Ethernet (2) Gigabit Ethernet (2)
Firewire/1394 As needed As needed
OS Windows XP Pro 32 SP3 Windows XP Pro 32 SP3
Notes A Gigabit Ethernet card and a Firewire/1394 card shall NOT
be installed on the same PCI bus segment (eg. adjacent PCI
slots), since this can cause very poor performance. It is the
customer’s responsibility to ensure that the system has
sufficient number and type of expansion slots to meet the

31 August 2009 Aurora Ingest Version 6.5.2 Release Notes and Upgrade Instructions 9
Version compatibility

MINIMUM Spec RECOMMENDED Spec

intended use. (For example, to accommodate network and/or

FireWire cards.)

Aurora Ingest RMI (SD)

MINIMUM Spec

Processor(s) Intel Core 2 Dual Core 2.33

GHz
OR
Intel Xeon 5140 Dual
Core 2.33 GHz
OR
AMD Opteron 270 Dual
Core 2.0 GHz
Memory 2 GB
Graphics Discrete graphics with 128
MB of dedicated memory
and support for Direct3D 9
and Shader Model 3.0
System Drive 80 GB 7200 RPM SATA
Media Drives 2 x 250 GB 7200 RPM
SATA striped
Optical Drive CD/DVD
Network Gigabit Ethernet (2)
Firewire/1394 As needed
OS Windows XP Pro 32 SP3
Notes A Gigabit Ethernet card and a Firewire/1394 card shall NOT
be installed on the same PCI bus segment (eg. adjacent PCI
slots), since this can cause very poor performance.

Aurora Ingest Server

MINIMUM Spec RECOMMENDED Spec

Model HP xw4600 Dell PowerEdge 2950

Processor Intel Core 2 Dual Core 2.3 Intel Xeon 1.0 GHz
GHz
Memory 1 GB 2 GB

10 Aurora Ingest Version 6.5.2 Release Notes and Upgrade Instructions 31 August 2009
 Version compatibility

MINIMUM Spec RECOMMENDED Spec

Graphics Integrated or discrete Integrated graphics

graphics with 128 MB of
memory and support for
Direct3D 9 and Shader
Model 3.0
System Drive 80 GB 7200 RPM SATA 36 GB 7200 RPM SATA or
SAS
Optical Drive CD/DVD CD/DVD
Network Gigabit Ethernet Gigabit Ethernet
OS Windows XP Pro 32 SP3 Windows Server 2003 R2 32
SP2

Aurora Ingest (VTR Ingest, VTR Controller, Scheduler)

MINIMUM Spec RECOMMENDED Spec

Processor Intel Core 2 Dual Core 2.3 Intel Core 2 Quad Core 2.3
GHz GHz
Memory 1 GB 2 GB
Graphics Integrated or discrete Integrated or discrete
graphics with 128 MB of graphics with 128 MB of
memory and support for memory and support for
Direct3D 9 and Shader Direct3D 9 and Shader
Model 3.0 Model 3.0
System Drive 80 GB 7200 RPM SATA 80 GB 7200 RPM SATA
Optical Drive CD/DVD CD/DVD
Network Gigabit Ethernet Gigabit Ethernet
OS Windows XP Pro 32 SP3 Windows XP Pro 32 SP3
Notes It is the customer’s responsibility to ensure that the system
has sufficient number and type of expansion slots to meet
the intended use. AURORA_IN_BASE and
AURORA_IN_LOGGER requires one free PCI slot for video
capture board and one free PCI slot for Comtrol 422 board.

Compatible Grass Valley products

Grass Valley products are compatible with this release of software as follows:
Product Version Comments

Aurora Browse client 6.5.2.8 —

31 August 2009 Aurora Ingest Version 6.5.2 Release Notes and Upgrade Instructions 11
Version compatibility

Product Version Comments

Aurora Browse MediaFrame 6.5.2.19 With compatible version of

Server SQL
Aurora Browse Proxy 6.5.2.12 —
Encoder
Aurora Edit 6.5.2.745 With compatible version of
SQL
Aurora Playout 6.5.2.80 With compatible version of
SQL
Generic iSCSI Installer 3.3.0.1141 or 7.0.11.1081 or —
7.0.12.1151
GVG_MLib Installer 3.3.0.1141 or 7.0.11.1081 or —
7.0.12.1151
K2 system software 3.3.0.1141 or 7.0.11.1081 or With compatible version of
7.0.12.1151 SNFS
M-Series system software 2.0.13.567 —
RMI Core 6.5.2.745 For RMI Installation
SiteConfig application 1.1.0.433 or higher —

Compatible third party products

Products by manufacturers other than Grass Valley are compatible with this release
of software as follows:
Product Version Comments

DeckLink 6.4
ENPS 5.00.0123 or 6.00.0009 For use with Scheduled
Events
Hauppauge 5.9F
Microsoft Windows XP with Service Pack 3 Windows Vista is NOT
currently supported
Microsoft Windows Server Win2003 Server R2 For Ingest Server
Component only
Panasonic P2 Driver 2.03.0002 Contact Panasonic for driver
SNFS 3.1.2.RC25225.6138 For RMI Installation within
K2 SAN
Sony XDCAM FAM Driver 2.04 Contact Sony for driver

12 Aurora Ingest Version 6.5.2 Release Notes and Upgrade Instructions 31 August 2009
 Upgrading Aurora Ingest systems
This section contains the tasks necessary for the upgrade to this release of software.

Upgrading Aurora Ingest devices with SiteConfig

This section contains the tasks for using SiteConfig to upgrade to this release of
software. Work through the tasks sequentially to complete the upgrade.
NOTE: These upgrade instructions assume that current software is at version 6.5.0
or higher. If you have a lower version of software, contact Grass Valley Support
before upgrading.

About upgrading Aurora Ingest devices with SiteConfig

These upgrade instructions apply to Aurora Ingest devices as follows:

• Aurora Ingest workstation
• IEP
With these upgrade instructions, you use SiteConfig from a network connected control
point PC and remotely upgrade software simultaneously on one or more devices. This
is the recommended process for software upgrades.
Before you upgrade software using SiteConfig, each Aurora Ingest device must be
migrated to become a SiteConfig managed device. This includes installing SiteConfig
support on the device and qualifying the device for communication with SiteConfig.
Refer to SiteConfig Migration Instructions. Also refer to the SiteConfig User Manual
or SiteConfig Help Topics.
NOTE: Do not attempt to upgrade software incrementally across the devices of a
K2 SAN while media access is underway. Online software upgrading is not supported.
To upgrade software using SiteConfig, you must first have SiteConfig set up for system
management and software deployment in your facility. These upgrade instructions
assume that you have already done that for your K2 SAN. Then you add your Aurora
Ingest devices to the SiteConfig system description that you are using for your K2
SAN.
The following installation tasks provide information specifically for the upgrade to
this version of software. Read the information in these sections carefully before
attempting any upgrade to software.

Prepare for upgrade

Before upgrading, do the following:

• Procure the software installation files for this release via the appropriate distibution
method, such as download, CD-ROM, network drive, or external drive.

31 August 2009 Aurora Ingest Version 6.5.2 Release Notes and Upgrade Instructions 13
Upgrading Aurora Ingest systems

• Start up the devices you are upgrading, if they are not already started.
• Stop all media access on the devices you are upgrading.
• Shut down all applications on the devices you are upgrading.

Prepare SiteConfig for software deployment

Do the following to prepare SiteConfig for the software upgrade.

1. Make the following files accessible to the SiteConfig control point PC:
• File for all Aurora Ingest devices:
• Aurora Ingest software installation (*.cab) file
• Additional files for Aurora Ingest RMI devices:
• AuroraSuite software installation (*.cab) file
• GenericISCI software installation (*.cab) file
• GVGMLib software installation (*.cab) file

2. If a newer version of SiteConfig is available for upgrade and you have not yet
upgraded SiteConfig, do the following:
a) From Windows Add/Remove programs, uninstall the current version of
SiteConfig from the control point PC.
b) Install the new version of SiteConfig on the control point PC.
3. If not already present in the SiteConfig system description, configure deployment
groups as follows:
• A deployment group that contains your Aurora Ingest devices

Upgrade K2 systems

Prerequisites for this task are as follows:

• If upgrading a K2 SAN, all SAN clients must be offline (all media access stopped)
or shut down. Depending on your system design, this could include devices such
as K2 clients, K2 appliances, Aurora Proxy (Advanced) Encoders, MDI server,
Aurora Edit clients, Aurora Ingest clients, Aurora Playout clients, and generic
clients.
Upgrade your K2 systems to the compatible version of K2 system software. This
includes K2 SAN systems and stand-alone K2 Media Client and K2 Summit
Production Client systems. Refer to K2 Release Notes for procedures.

14 Aurora Ingest Version 6.5.2 Release Notes and Upgrade Instructions 31 August 2009
 Upgrading Aurora Ingest systems

Distribute devices into deployment groups

You can gather devices of different types into a SiteConfig deployment group. This
allows you to deploy software to all the devices in the deployment group at the same
time, as part of the same deployment session. Based on the roles you have assigned
to the devices, SiteConfig deploys the proper software to each device. This increases
the efficiency of your software deployment with SiteConfig.
If you have not already done so, configure your deployment groups. The recommended
deployment group distribution is as follows. Depending on your system design, your
system might not have all the device types listed.
• In a deployment group named "Aurora_Edit_Ingest_Playout", place the following
devices:
• Aurora Edit workstation of any storage options: Shared storage, NAS storage,
and stand-alone.
• Aurora Edit LD
• DSM
• Conform Server
• SmartBin Server
• FTP Server
• Aurora Ingest Platform
• IEP
• Aurora Playout Platform
• In a deployment group named "Aurora_Browse_MediaFrame", place the following
devices:
• MediaFrame server
• MDI server
• Aurora Proxy Encoder
• K2 Basecamp Express
• If you have a K2 Nearline SAN (NAS), in a deployment group named for the SAN
system, place the following devices:
• The Nearline SAN's K2 Media Servers.

Install High Priority Windows updates (recommended)

• Windows “High Priority” updates are recommended, but not required. While you
have devices in an offline state to upgrade software, you should check to see if
there are any new updates that you need to install. Use standard Windows
procedures.
CAUTION: Only “High Priority Updates” should be installed. Do not
install other Windows or driver updates.

31 August 2009 Aurora Ingest Version 6.5.2 Release Notes and Upgrade Instructions 15
Upgrading Aurora Ingest systems

Manually upgrade systems

Some tasks that might be required with the upgrade to this release are not supported
for SiteConfig management and/or software deployment. For these tasks you must
manually upgrade and/or configure the device before using SiteConfig to upgrade
software. Refer to the tasks in this section as appropriate for your system.

Upgrade Microsoft SQL Server 2005 Standard Edition

Microsoft SQL Server 2005 Standard Edition is installed on devices as follows:

• Aurora DSM – SQL Server 2005 Standard Edition is required.
• Ingest Server – Either Microsoft SQL Express 2005 or Microsoft SQL Server 2005
Standard Edition is required.
Use the following steps to manage upgrades to Microsoft SQL Server 2005 Standard
Edition.
1. Determine if you have Microsoft SQL Server 2005 Standard Edition installed on
one or more of your system devices, If installed, continue with next steps.
2. Check version compatibility information in these release notes and determine if
this release of software requires an upgrade to Microsoft SQL Server 2005 Standard
Edition.
3. If an upgrade is required, go to the local device and upgrade Microsoft SQL Server
2005 Standard Edition.

Check all currently installed software on Aurora Ingest devices

Prerequisites for this task are as follow:

• The device is assigned in the SiteConfig system description and network
connectivity is present.
• SiteConfig is able to log in to the device using the username/password credentials
assigned to the device.
• The SiteConfig control point PC does not have a network drive mapped to an
administrative share (such as C$) on a device on which you are checking software.
• If this is the first time deploying software to Aurora devices using SiteConfig, on
those Aurora devices previous versions of Aurora software and SiteConfig software,
such as the Network Configuration Kit and/or Discovery Agent, have been manually
uninstalled. For more information refer to SiteConfig Migration Instructions.
Do the following steps on the devices that you are upgrading.
1. In the Software Deployment | Deployment Groups tree view, right-click the top-most
node for the group or any individual device and select Check Software.
NOTE: If you have access problems, verify that the adminstrator account on
the device has credentials as currently configured in SiteConfig. By default
credentials on the device should be administrator/adminGV! for Aurora devices
and Administrator/adminK2 for K2 devices.

16 Aurora Ingest Version 6.5.2 Release Notes and Upgrade Instructions 31 August 2009
 Upgrading Aurora Ingest systems

The Check Software dialog box appears. SiteConfig searches for software on
the selected device or devices and gathers information. Progress is reported.
2. When the check is complete for the selected device or devices, close the Check
Software dialog box.
An updated list of all currently installed software is displayed in the Software
Deployment | Devices | Installed Software list view. If software is a SiteConfig managed
software package, information is displayed in the Managed Package and Deployment
Group columns.

Add software package to deployment group for Aurora Ingest devices

Prerequisites for this task are as follows:

• You can access the software package file from the SiteConfig control point PC.
• The Aurora Ingest devices to which you are deploying software are in a deployment
group.
Use the following procedure to add one or more software packages to the deployment
group that contains your Aurora Ingest devices. For this release of software, identify
and add software installation files as follows:
Software File name

Aurora Ingest software – For all Aurora AuroraIngest_6.5.2.xxxx.cab

Ingest devices
Aurora Suite – For Aurora Ingest RMI AuroraSuite_6.5.2.xxxx.cab
device only

For Aurora Ingest RMI devices, you must also add the following software packages
to the deployment group. Depending on the K2 software version of your K2 SAN,
also add software package installation files as follows:
NOTE: Add files for either 3.x OR 7.x. Do not add files for both 3.x AND 7.x.
• If your devices access storage on a K2 software version 3.x K2 SAN, add software
package installation files as follows:
Software compatible with 3.x K2 SAN File name

Generic iSCSI client GenericISCI_x86_3.x.x.cab

GVG MLib software GVG_MLib_3.x.x.cab

• If your devices access storage on a K2 software version 7.x K2 SAN, add software
package installation files as follows:
Software compatible with 7.x K2 SAN File name

Generic iSCSI client GenericISCI_x86_7.x.x.cab

GVG MLib software GVG_MLib_7.x.x.cab

31 August 2009 Aurora Ingest Version 6.5.2 Release Notes and Upgrade Instructions 17
Upgrading Aurora Ingest systems

SNFS is bundled with the Generic iSCSI cab file.

1. In the Software Deployment | Deployment Groups tree view, select a deployment
group.
2. Click the Add button.
The Add Package(s) dialog box opens.
3. Do one of the following to select the software package:
• Select from the list of packages then click OK.
• Click Browse, browse to and select the package, then click Open.

4. If one or more EULAs are displayed, accept them to proceed. If you do not accept
a EULA, the associated software is not assigned to the deployment group.
SiteConfig adds the package to the deployment group.
The package appears in the Managed Packages list for the selected deployment group.
SiteConfig creates new software deployment tasks for the package and displays them
in the Tasks list view.

Setting deployment options

Pre-requisites for this procedure are as follows:

• A software package has been assigned to the deployment group and applicable
deployment tasks are now displayed in the Tasks area.
1. In the Software Deployment | Deployment Groups tree view, select a deployment
group.
2. In the Tasks list view, view tasks and determine if you must set deployment options.
Tasks that need to have deployment options set display in the Details column a
message stating "Deployment options required."
If you select a task that needs to have its deployment options set, the Start
Deployment button is disabled and the message is displayed next to the button.
3. Do one of the following to set deployment options:
• Double-click the task.
• Select the task and click the Options button.
A wizard opens.
4. Work through wizards and set deployment options as follows:
Software Deployment options

Aurora
Ingest

18 Aurora Ingest Version 6.5.2 Release Notes and Upgrade Instructions 31 August 2009
 Upgrading Aurora Ingest systems

Software Deployment options

Select the SQL Server configuration that will be used by Aurora Ingest
Server. If you choose SQL Server 2005, select the server instance from
the dropdown list. If your system has SQL Server already installed
(e.g. if the system houses the Aurora Edit database), choose to use the
existing SQL Server instance; if not, choose SQL Express.

31 August 2009 Aurora Ingest Version 6.5.2 Release Notes and Upgrade Instructions 1
Upgrading Aurora Ingest systems

Software Deployment options

Enter the name of the Aurora Ingest Server.

5. If your system has Aurora Ingest RMI devices, also configure deployment options
as follows:
Software Deployment options

GVG_MLib Enter the name(s) of the K2 Media Server(s) with role of file system
server (FSMs)
Aurora
Suite

Enter Database server(DSM), Shared AV Files, Shared AV Drives.

20 Aurora Ingest Version 6.5.2 Release Notes and Upgrade Instructions 31 August 2009
 Upgrading Aurora Ingest systems

Software Deployment options

Enter Local AV Files, Cache Files.

6. If you have multiple devices of the same type, you can enter deployment options
for one of them using the wizard. Then, when you bring up the same wizard on
every device, you can choose the Use options from radio button and select the first
device for which you set options.
SiteConfig copies the options you set for the first device and fills in the blanks
on the wizard.

Upgrade software on Aurora Ingest devices

Prerequisites for this task are as follows:

• The devices that you are upgrading are in a deployment group.
• For the software you are upgrading, you have added a newer version of that managed
software package to the deployment group.
• You have recently done the SiteConfig "Check Software" operation on the devices
you are upgrading.
When you upgrade software, SiteConfig enforces an uninstall of the current version
of software before installing the upgrade version. SiteConfig can do the uninstall/install
in a single deployment session. If you are upgrading multiple software components,
SiteConfig enforces any dependencies by sequencing deployment tasks. SiteConfig
provides uninstall deployment tasks and install deployment tasks to indicate the
taskflow.
1. In the Software Deployment | Deployment Groups tree view, select the device or the
group of devices for which you are upgrading software.

31 August 2009 Aurora Ingest Version 6.5.2 Release Notes and Upgrade Instructions 21
Upgrading Aurora Ingest systems

The corresponding software deployment tasks are displayed in the Tasks list
view.
2. For the software you are uninstalling, select the Deploy check box in the row for
the uninstall task.
3. For the software you are installing, select the Deploy check box in the row for the
install task.
For upgrading all Aurora Ingest devices to this release, deploy the following
tasks:
Deploy Managed Package Action

AuroraIngest xxxx.xxxx Uninstall

AuroraIngest 6.5.2.xxxx Install

IngestServerPrerequisites Uninstall
xxxx.xxxx
IngestServerPrerequisites Install
6.5.2.xxxx

For Aurora Ingest RMI devices, also deploy the following tasks:
Deploy Managed Package Action

AuroraSuite xxxx.xxxx Uninstall

AuroraSuite 6.5.2.xxxx Install

GenericISCI x86 xxxx.xxxx Uninstall

GenericISCI x86 xxxx.xxxx Install

(version must be compatible with
K2 SAN)
GVGMLib xxxx.xxxx Uninstall

GVGMLib xxxx.xxxx (version Install

must be compatible with K2 SAN)

If a message instructs you to upgrade the Discovery Agent, on the control point
PC go to the directory to which SiteConfig is installed and in the Discovery
Agent Setup directory find the DiscoveryAgent_x.x.x.x.cab file. Add it to
the deployment group and deploy the Discovery Agent software as well.
NOTE: If there are dependencies, SiteConfig can enforce that some tasks be
deployed together.

4. Click the Start Deployment button.

22 Aurora Ingest Version 6.5.2 Release Notes and Upgrade Instructions 31 August 2009
 Upgrading Aurora Ingest systems

Deployment tasks run and software is uninstalled. Progress is reported and next
steps are indicated in both the Status and Details columns.
5. When the Status or Details columns indicate next steps, proceed as follows:
• When Details displays a Restart required link, click the link and when prompted
"...are you sure...", click Yes.
The device restarts. This restart is required by the Aurora Ingest software
uninstall.
Deployment tasks run and software is installed. Progress is reported and next
steps are indicated in both the Status and Details columns.
6. When the Status or Details columns indicate next steps, proceed as follows:
• When Details displays a Restart required link, click the link and when prompted
"...are you sure...", click Yes.
The device restarts.
7. Monitor progress as indicated by both the Status and Details column. When finished,
the Status column indicates complete.

Upgrade NAS systems

Prerequisites for this task are as follows:

• K2 systems are upgraded to the compatible version of K2 system software.
• Aurora Edit, Ingest, and Playout systems are upgraded to the compatible versions
of software.
Upgrade the MediaFrame Proxy NAS (K2 Nearline SAN) to the compatible version
of K2 software. Use SiteConfig and deploy software, using steps similar to those
for other systems.
a) Check software on the Nearline SAN's K2 Media Servers.
b) Add software *.cab file to the deployment group that contains the K2 Media
Servers.
c) Upgrade software on K2 Media Servers via a SiteConfig deployment session.

31 August 2009 Aurora Ingest Version 6.5.2 Release Notes and Upgrade Instructions 23
Upgrading Aurora Ingest systems

Upgrade Browse and MediaFrame systems

Prerequisites for this task are as follows:

• K2 systems are upgraded to the compatible version of K2 system software.
• Aurora Edit, Ingest, and Playout systems are upgraded to the compatible versions
of software.
• K2 Nearline SAN (NAS) systems are upgraded to the compatible version of K2
system software.
Upgrade your Browse and MediaFrame systems to the compatible versions of
software. Refer to Aurora Browse Release Notes for procedures.

24 Aurora Ingest Version 6.5.2 Release Notes and Upgrade Instructions 31 August 2009
 Licensing Grass Valley products
The following sections contain instructions for managing Grass Valley product licenses.

About software licensing

Once the Aurora Ingest software is installed, you are provided with a 30-day temporary
license. You need to get a software license number from Grass Valley in order to
install the permanent license. Obtaining the software license number is important
because you cannot launch channels or configure Aurora Ingest after your 30-day
temporary license has expired.
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. If you change your system’s
MAC address by performing operations such as changing the System Processor card,
you must obtain a new license based on the new MAC address.

Requesting a license
Software licenses are unique to the system for which they are purchased. They cannot
be used on any other system. This requires that you provide a generated unique ID for
the desired system to Grass Valley, which is then used to create your unique license.
1. Log on to the device that you want to license.
You must log in as a Windows administrator with a local account, not a domain
account.
2. Open the License Request Wizard.
Find the License Request Wizard shortcut on the Windows desktop.

The License Request Wizard displays.

3. Read the on-screen instructions, then click Next.

The Customer dialog box displays.

31 August 2009 Aurora Ingest Version 6.5.2 Release Notes and Upgrade Instructions 25
Licensing Grass Valley products

4. Enter the information requested on this page then click Next.

You must provide a valid email address to receive your license file.

The Sales Number dialog box displays.

5. Enter the Sales Order Number in the field then click Next.
Typically the Sales Order Number is found on the Software License sheet that
you received with your Grass Valley product.

The Summary dialog box displays.

6. Review the License Request information and click Finish.

A License Request text file, License_Request_<SalesNumber>.txt, is generated

and saved to the Windows Desktop.
NOTE: If you are requesting licenses for more than one application, be sure
to modify the name of the first License Request text file before saving it to
your desktop. (In Notepad, use the Save As command.) Otherwise, the second
License Request text file will overwrite it.

7. Do one of the following:

• Attach this text file to an email.
• Paste the text directly into an email message.

You might want to keep a copy of the message for your records.
8. Send the email as instructed by the License Request Wizard.

An email will be sent from Grass Valley to the return email address you specified;
your SabreTooth software license will be provided as a text file.
9. Save this email in case you ever need to re-image this machine.
Next add the license to the SabreTooth License Manager.

If you encounter difficulties when requesting a license

If you encounter difficulties running the License wizard, try this alternate method:
1. Generate a unique ID of the device where you will install software, as follows:
a) Click on the License Manager icon on the Windows Desktop.
The SabreTooth License Manager opens.
b) Choose File | Generate Unique Id the License Manager.
c) Click Copy to clipboard to copy the generated ID, and OK to exit.
2. Prepare an email that includes the following information:

26 Aurora Ingest Version 6.5.2 Release Notes and Upgrade Instructions 31 August 2009
 Licensing Grass Valley products

• Customer Name
• Customer Email
• Sales Order Number
• Unique ID of the device where you will install software.

3. Send the email to [email protected].

The SabreTooth license number will be emailed to the email address you specified.

Adding a license
Your software license, Licenses_<SalesNumber>.txt, is provided as a text file. Use
the License Manager to add this file to your system and enable the desired feature.
1. Click on the License Manager icon on the Windows Desktop. The SabreTooth
License Manager opens.
The SabreTooth License Manager opens.
2. Do one of the following:
• Choose File | Import License and navigate to the file location to open the text
file.
• Drag and drop the text file onto the License Manager.

You will now see the permanent license in SabreTooth, as well as any other
licenses, permanent or temporary, that have been installed on this machine.
Once you have added the permanent license, you can delete the temporary license. If
the temporary license is still in SabreTooth you will continue to get temporary license
notifications, even with the permanent license installed, unless you delete the temporary
license.
You should save the permanent license to a backup system.

Deleting licenses
Deleting a license disables the feature that it enabled. You might want to delete a
temporary license prior to its expiry if you have decided not to purchase the feature.
You can delete a temporary license after the permanent license has been installed
without disabling the licensed product.
1. Select the license in the SabreTooth License Manager.
2. Use the Delete key on your keyboard or right click with your mouse and select
Delete.

31 August 2009 Aurora Ingest Version 6.5.2 Release Notes and Upgrade Instructions 27
Licensing Grass Valley products

Archiving licenses
You can archive your licenses to a secure external location. This allows you to quickly
re-install a license should it be deleted or should you have to downgrade and then the
licensed software. You can archive multiple licenses at the same time.
NOTE: If you downgrade to an earlier version of the licensed software, make sure to archive
the licenses first.

1. In the SabreTooth License Manager, select the license or licenses.

2. Choose File | Export License to open the Save As dialog box.
3. Assign a meaningful name to the file, and save it to the desired location. Grass
Valley recommends saving the license file to a USB drive or other external location.

Aurora Ingest licenses

The Grass Valley licenses available at the time of this writing that can be installed on
Aurora Ingest are as follows. Contact your Grass Valley representative for more
information about licenses.

Aurora Ingest licenses

License License type

Aurora-Ingest-Number of channels SabreTooth

Aurora-Ingest-RMI SabreTooth
Aurora-Ingest-Scheduler SabreTooth
Aurora-Ingest-VTR Ingest SabreTooth
Aurora-Ingest-VTR Logging SabreTooth
Aurora-Ingest-ScheduALL SabreTooth

28 Aurora Ingest Version 6.5.2 Release Notes and Upgrade Instructions 31 August 2009
 Operation considerations

The following sections contain additional information about operating your product
systems.

Aurora Ingest Server

• The remote clients should be slaved to the time of day of the Aurora Ingest Server.
If an offset is present, scheduled events will be started according to the time of the
server component rather than the apparent time of the remote scheduler client.
• Each K2/Summit channel should be connected to either Aurora Ingest or Aurora
Playout only. Connecting to both applications at the same time will cause channel
conflicts.
• For setting up an Encore router, limiting names of Sources, Destinations, Levels,
Salvos, Areas, control panels and other names intended for display on Encore
hardware panels to 7 or 8 characters is strongly recommended. Names longer than
8 characters will be truncated and the extra characters will not appear to the panel
operator. Names with 8 characters will also have its last character overwritten if a
Breakaway condition exists.

Aurora Ingest Scheduler

• Aurora Ingest is designed to run with a screen resolution of 1280x1024 for standard
configurations. Some Aurora Ingest windows will not display properly if Windows
is configured to use large fonts.
• Prior to installing Aurora Ingest onto a clean system that will support video overlay
(Scheduler or VTR Ingest), install the Hauppauge WinTVGo Video Capture Card
or Blackmagic Design DeckLink Video Capture Card along with their drivers
included on the installation CD.
• The time of day format within the Scheduler is directly related to the current time
of day format for the individual client machine. To change this, go to Start | Control
Panel | Regional and Language Options and launch the Customize tool. Once in the
customize tool, enter the Time tab and set your time format accordingly.
NOTE: Changes to the Scheduler’s time format will only be seen after a relaunch
of the Scheduler application.
• Scheduled records must be separated by at least 10 seconds between the end of the
outgoing feed and the start of the incoming feed. To account for this, the default
duration of feeds has been set to 59 minutes and 50 seconds in Tools | Options |
General. It is recommended that any edits to the default duration reflect the 10
second minimum separation.
• The Scheduler will hold onto past events history for three weeks.
• Recurring events can be added for up to three years in advance. These events can
be modified later in order to extend the duration of the recurring item.
• For scheduled recurring events, removing a channel from Aurora Ingest Server
will reassign those recurring events to other available channels at start time. For
non-recurring events, those events will be erased rather than reassigned to other
channels.
NOTE: Re-introducing the once removed channel may result in incorrect
scheduling for that channel as the database may hold on to events not seen in

31 August 2009 Aurora Ingest Version 6.5.2 Release Notes and Upgrade Instructions 29
Operation considerations

the user interface of the scheduler. It is recommended that scheduled events get
moved from the channel prior to the channel’s removal.

Aurora Ingest Scheduler with ENPS Assignment Grid

• You can refer to the Aurora Ingest System Guide for instructions on configuring
ENPS for scheduling events and setting up the ENPS Assignment Grid. If this
guide is not yet in your possession, please contact customer support for download
information.
• When using ENPS to schedule events, it is important to note that error notifications
typically handled within the Aurora Ingest Scheduler will not be as readily available
within the ENPS Assignment Grid. For instance, naming conflicts, channel conflicts,
elapsed events, etc. will not always be flagged within the ENPS grid. It is important
to also monitor the Aurora Ingest Scheduler interface in order to get a more accurate
representation of the current activity.

Aurora Ingest RMI

• RMI requires either the Panasonic P2 or Sony XDCAM FAM driver for proper
interaction with these types of removable media devices.
• RMI requires the RMI Core 6.5 installation for proper functionality. In addition,
RMI should be added into the overall stream count of the shared system as it will
be writing directly to the shared storage.
• RMI and Aurora Edit should be installed on separate machines if possible. However,
if it's necessary to install them on the same machine, follow the steps below:
1. Uninstall any previous version of Aurora Edit and Aurora Ingest RMI.
2. Run the Aurora Suite installer, choosing to install the Aurora Edit and RMI
Core components.
3. Run the Aurora Ingest installer, choosing to install the RMI component.
• RMI should only be installed on Windows XP Operating Systems.
• RMI requires a relaunch after the news DSM is rebooted. The application will not
prompt for this, but subsequent import attempts will fail.
• If changing drive volumes for importing clips, the Destination AV Path within
Tools | Options must be directed to the VibrintAVFiles folder within the desired
volume.
• After Sony XDCAM is plugged in and attached to RMI application, XDCAM
pop-up will be displayed. To disable XDCAM pop-up in Windows 2000 and
Windows XP operating systems, follow the steps below:
1. Go to Start | Run and type in gpedit.msc.
2. Once in, go to Administrative Templates.
3. Then click on System.
4. Once in System, look at the right hand pane and search for Turn off AutoPlay.
5. Open Turn off AutoPlay.
6. Select the Enable option.
7. Select CD-ROM drives in the dropdown and click OK.

30 Aurora Ingest Version 6.5.2 Release Notes and Upgrade Instructions 31 August 2009
 Operation considerations

Aurora Ingest VTR Ingest

• If multiple clients are pointed to the same VTR, each client will report a successful
connection. When operating the VTRs, however, the multiple clients may interfere
with each other. It is important to allocate VTRs properly so collisions of this nature
do not occur.
• Records have a frame accuracy recording window of +/- 3 frames for the VTR
Ingest with K2.
• When controlling a VTR that is in 720p mode, transport commands, such as single
frame and ten frame advances may not be frame accurate.

31 August 2009 Aurora Ingest Version 6.5.2 Release Notes and Upgrade Instructions 31
Additional notes

Additional notes

The following sections contain additional information to ensure smooth operation of

Aurora Ingest with other systems.

Setting up AMP control on a K2 Client

With Aurora Ingest Server, K2 Media Clients and K2 Summit Production Clients are
controlled via AMP Protocol over Ethernet.
To set up AMP control of a K2 Client:
1. On AppCenter of the client, click the Options button for the desired panel.
2. Set the Control setting to either Remote Only or Remote and Local and the Protocol
setting to AMP. Repeat this step for each panel that will be controlled remotely by Aurora
Ingest.
3. In the Ingest Server application, go to Tools | Options | Media Server and add the name
of the client.
4. In the Ingest Server application, go to Tools | Options | Channel and add each channel
that will be controlled on the K2 or Summit. In the Channel dropdown list, “VTR1”
corresponds to the “R1” panel on the K2 or Summit, “VTR2” corresponds to the “R2”
panel, etc.
NOTE: Refer to the “Installing and Configuring Aurora Ingest” section of the Aurora
Ingest System Guide for more detailed information about configuring media servers and
channels.

System Imaging Software

Aurora systems use Acronis imaging software, version 3647, which allows you to
back up your system. When the system boots using Acronis Imaging software, select
either Safe Version, Full Version, or boot into Windows.
Safe version should normally be used to restore or create the C:\ partition from the
backup partition, drive F:\.
Full version loads additional USB drivers, which allows a user to backup or restore
with a USB drive. However, the boot process hangs unless the following parameters
are entered prior to selecting Full Version:
1. Press F11.
2. Change the boot parameters from quiet to quiet acpi=off noapic.
3. Click OK.
4. Select the Full Version to load True Image.
NOTE: Acronis imaging software recognizes Rev Pro drives.

32 Aurora Ingest Version 6.5.2 Release Notes and Upgrade Instructions 31 August 2009
 Additional notes

Installing software
The software for Aurora Ingest components can be installed on any PC which meets
the system requirements for that component.

If you don't have SiteConfig within your operation, you can install or upgrade Aurora
Ingest with the procedure below.
To install the Aurora Ingest software on your computer, insert the Aurora Ingest
CD-ROM into the machine’s CD-ROM drive and follow these instructions:

On this screen... Do this...

Welcome Click Next.

License Agreement Select I accept... and click Next.
Select Features Specify the Aurora Ingest applications to install: Server,
Scheduler, VTR Controller, VTR Ingest, or RMI. With Server
component, Microsoft .NET Framework 2.0 and Microsoft
SQL Express will also be installed by default. If your system
has SQL Server already installed (e.g. if the system houses
the Aurora Edit database), choose to use the existing SQL
Server instance; if not, choose SQL Express.
Specify Server Enter the host name of Aurora Ingest Server that will be used
Configuration by Aurora Ingest components. Select the SQL Server
configuration that will be used by Aurora Ingest Server. If
you choose SQL Server 2005, select the server instance from
the dropdown list.
Start Installation Click Next.
Installation Complete Click Finish.

Installing ScheduALL for Aurora Ingest integration

In order to use VizuAll, Inc.'s ScheduALL with Aurora Ingest, you need to install the
ScheduALL application. For a smooth scheduling integration, extra steps need to be
adhered to during the installation process. If technical assistance is needed, you can
contact ScheduALL product support at 1-954-334-5409 option 1.

These applications are the pre-requisites and must be installed on your machine before
proceeding to install ScheduALL.
• Microsoft SQL Server 2005 (For ScheduALL)
• Microsoft SQL Express 2005 (For Ingest)
• Aurora Ingest Server installed and configured
• Visual studio 2005 redistribute SP1 for SchedIngestAPI web service (to be installed
automatically by SchedIngestAPI installer)

31 August 2009 Aurora Ingest Version 6.5.2 Release Notes and Upgrade Instructions 33
Additional notes

The following list contains the minimum ScheduALL components required for
integration with Aurora Ingest.
1. ScheduALL for Windows v4.73.22 (4.74) or greater.
2. ScheduALL Authentication Server.
3. ScheduALL Ingest API license point.
4. Enabled ScheduALL Web Service APIs:
• WorkOrder Query
• WorkOrder Delete
• WorkOrder Modify
• Work Order Request Create
• Event Create
• Event Delete
• Event Details
• Event Modify
• Resource Booking Query
• Resource Query
• WorkOrder Details
• Client Query
5. Modules:
• Scheduling
• Developer's Toolkit
• Client/Server
• WebServiceAPI
• Ingest Web Service API

1. Install Sched4.exe which will install ScheduALL. Select the Network Client option.
The default login username is SUPERVISOR with a blank password.
2. Install SchedAuth.exe, which is the Authentication Server for ScheduALL web
services.
3. Install SchedWebAPI.exe, which is the ScheduALL web service.
4. Install SchedIngestAPI (setup.exe), which is the Ingest integration web service.
You can now launch ScheduALL and continue with below steps:
1. At the login screen, enter SUPERVISOR and a blank password.
2. Deselect the "Use Sample Data" option.
3. When prompted to update the database, select "Yes".
4. Keep selecting "Yes" and "OK" for permission enquiries.
After completing above steps, ScheduALL should now be operational with Aurora
Ingest.

34 Aurora Ingest Version 6.5.2 Release Notes and Upgrade Instructions 31 August 2009
 Additional notes

Configuring ScheduALL properties

ScheduALL properties can be configured in the System tab when you select Tools |
Options within Aurora Ingest Server.

1. Click the Configure button, beside the ScheduAll Server setting.

The ScheduAll Properties dialog box is displayed.

31 August 2009 Aurora Ingest Version 6.5.2 Release Notes and Upgrade Instructions 35
Additional notes

2. The Complete Web Service URL and SchedIngestAPI Web Service Config URL
are automatically populated once you set the ScheduALL Server within the System
tab.
Click the Launch button to launch the SchedIngest API configuration page.

36 Aurora Ingest Version 6.5.2 Release Notes and Upgrade Instructions 31 August 2009
 Additional notes

3. Configuration details can be entered as below:

Option Description
Default Ingest Enter the host name or IP address of the default Ingest Server. The
Server Address default Ingest Server should be the server that is majorly used for
scheduling with ScheduALL. By default, all channels on the default
Ingest Server can be used with ScheduALL and do not need to be
assigned within the Channel Assignment section.
Channel Shows channel name and host name of the Ingest Server if you
Assignment have multiple Ingest Servers connected to your system. You can
assign specific channels from multiple Ingest Servers that will be
used with ScheduALL. You can also edit or delete channel from
this section if needed.
Add New Add the channel name and host name of the Ingest Server other
Channel than the default Ingest Server, if you have multiple Ingest Servers
connected to your system. The channel will be displayed in the
Channel Assignment section.

31 August 2009 Aurora Ingest Version 6.5.2 Release Notes and Upgrade Instructions 37
Additional notes

4. To edit channel and router resorces of ScheduALL, you need to select the Edit
Resources checkbox within the ScheduAll Properties window.

You have to wait for the query to ScheduALL to complete, as this may take a
few minutes. Once it's done, the dialog status bar will show 'Ready'.
5. All channels and router sources that had been set up on your Ingest Server will be
displayed. You need to map your existing channels and router sources on Ingest
Server to existing channels and router sources on ScheduALL.
6. Select your particular channel or router source for Ingest Server, double-click on
the ScheduALL resource item and select an item that you want to map with in the
dropdown list.
Channel names and router sources should match respectively for both
applications. If you have multiple Aurora Ingest Servers within your operation,

38 Aurora Ingest Version 6.5.2 Release Notes and Upgrade Instructions 31 August 2009
 Additional notes

each channnel on those Ingest Servers must be configured with unique names
to avoid scheduling conflicts with ScheduALL.
7. Click OK after you have finished configuring ScheduALL properties.

Configuring ScheduALL application

ScheduALL application needs to be set up to include Aurora Ingest Room and the
URL of SchedIngestAPI Web Service for the scheduling integration to be successful.

1. Launch the ScheduALL application.

2. Select File | Supervisor Options | System Preferences | General .
3. Click on the System Options tab and scroll down to the Request Room Options.

4. Select the Aurora Ingest Room.

5. Then, scroll down to Ingest options.

31 August 2009 Aurora Ingest Version 6.5.2 Release Notes and Upgrade Instructions 39
Additional notes

6. Enter the URL of the SchedIngestAPI Web Service.

The default URL is http://localhost/SchedIngestAPI/SchedIngestAPI.asmx. If
the web service had been installed on another machine, edit the URL to include
the hostname or IP address of that machine.
7. Click OK to save the setting.

40 Aurora Ingest Version 6.5.2 Release Notes and Upgrade Instructions 31 August 2009
 Known Issues

The following limitations are present in this release of software. If you wish to obtain
more information about these limitations, please mention the reference numbers.

Aurora Ingest - Server

CR80235 Description: The extra “_b” appended to backup feed clip name could break
conformance from remote system.
Workaround: Change the following value in the Windows registry from 1
to 0: HKEY_LOCAL_MACHINE\SOFTWARE\Grass
Valley\Aurora Ingest\Server\Feed\Use Backup Clip Name
CR86146 Description: With more than 100 hours of storage space remaining on K2,
Ingest misreports storage.
Workaround: Aurora Ingest will begin to properly report storage once the
capacity has fallen below 100 hours.

Aurora Ingest - Scheduler

CR78916 Description: Crash record of gang-roll events could fail if the default clip
name consists of more than 32 characters.
Workaround: As the current limit to a default clip name is 26 characters,
ensure that router source name (which gets added to default
clip name for gang roll events) consists of less than 6
characters. Hence, the default clip name would not consist of
more than 32 characters.
CR87061 Description: Having completed recurring events in Scheduler prevents the
ability to create a series with the same name going forward.
Workaround: Delete the event from today that already finished recording.
Now Scheduler will let you add a new series with that name.
CR89491 Description: When custom metadata fields are reordered in Aurora Browse,
they do not get reordered in Ingest.
Workaround: Close and relaunch Schedule client in order to see the updated
order of custom fields.
CR94269 Description: Thumbnails don't appear for keywords marked using X-keys.
Workaround: Marking keywords manually through the MediaFrame plug-in
window will create a keyword if proxy media exists.
CR94791 Description: If crash record default bin doesn't exist on media server,
Scheduler shows "Error obtaining clip duration from the media
server".
Workaround: It is highly recommended that record directories exist on the
media client prior to attempting records or sends.

31 August 2009 Aurora Ingest Version 6.5.2 Release Notes and Upgrade Instructions 41
Known Issues

CR99287 Description: On clean install with no MediaFrame configuration, Scheduler

default UI has big blank Search window.
Workaround: This window is harmless. Close the dialog and subsequent
relaunches of the Scheduler will not present the window.
CR99410 Description: X-keys generic Keyword button adds keyword with blank
name, rather than default name.
Workaround: When adding a keyword button for X-Keys, opt to add a name
for the keyword.
CR104168 Description: ScheduALL status light is red while functionality is OK.
Workaround: None.
CR105606 Description: For events added through Scheduler, ScheduALL doesn't send
update to Scheduler after modifying channel, router, or
location.
Workaround: After modifying the channel, router or location on ScheduALL,
users need to manually change the channel, router or location
of the same event on Scheduler.

Aurora Ingest - RMI

CR98692 Description: If logged in as user without "Modify" rights to

V:\VibrintXDCAMFiles, canceling RMI cache prevents it
from caching again.
Workaround: You need to turn on Modify access for the
V:\VibrintXDCAMFiles folder if using RMI as a
non-administrator in an environment where Security is enabled.
CR98929 Description: Clips that were part of a merged import don't show "Exists"
status after relaunching RMI.
Workaround: No workaround at this time.

42 Aurora Ingest Version 6.5.2 Release Notes and Upgrade Instructions 31 August 2009