GRASS VALLEY AURORA INGEST - RELEASE NOTES AND UPGRADE INSTRUCTIONS V7.1, Aurora Ingest 7.1 Upgrade Instructions

Copyright © Grass Valley, Inc. All rights reserved. Printed in the United States of America. Portions of software © 2000 – 2010, 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, Solo, Dyno, Turbo, 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.grassvalley.com. Other trade­marks and logos used in this document are either registered trademarks or trademarks of the manufacturers or vendors of the associated products, such as Microsoft® Win­dows® operating system, Windows Media® player, Internet Explorer® internet browser, and SQL Server™. QuickTime and the QuickTime logo are trademarks or registered
trademarks of Apple Computer, Inc., used under license therefrom.

071-8550-12

Aurora Ingest Version 7.1 Release Notes
and 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 th at contains additional important

information.

Contents

Grass Valley Product Support.....................................................................................................4

Release note revisions for this release.......................................................................................6

Release Summary......................................................................................................................7

What's new in version 7.1.0.....................................................................................................7

Version 7.1.0........................................................................................................................7

Fixed in 7.1.0.......................................................................................................................7

Feature limitation in this release..........................................................................................8

Changes and features in previous releases............................................................................8

Version compatibility.................................................................................................................13

System specifications............................................................................................................13

Compatible Grass Valley products.........................................................................................15

Compatible third party products............................................................................................16

Upgrading Aurora Ingest systems.............................................................................................18

Upgrading Aurora Ingest devices with SiteConfig.................................................................18

About upgrading Aurora Ingest devices with SiteConfig....................................................18

Prepare for upgrade...........................................................................................................19

Prepare SiteConfig for software deployment.....................................................................19

Install prerequisite files on the control point PC.................................................................20

Upgrade K2 systems.........................................................................................................20

Distribute devices into deployment groups........................................................................20

Install High Priority Windows updates (recommended).....................................................21

Manually upgrade systems................................................................................................21

Check all currently installed software on Aurora Ingest devices........................................22

Add software package to deployment group for Aurora Ingest devices.............................23

Setting deployment options................................................................................................24

Upgrade software on Aurora Ingest devices......................................................................28

Upgrade NAS systems......................................................................................................31

Upgrade Browse and MediaFrame systems......................................................................31

Licensing Grass Valley products...............................................................................................33

About software licensing.......................................................................................................33

Requesting a license.............................................................................................................33

Adding a license....................................................................................................................35

Deleting licenses...................................................................................................................35

Archiving licenses..................................................................................................................36

Aurora Ingest licenses...........................................................................................................36

Operation considerations..........................................................................................................37

New topics................................................................................................................................40

Disabling User Account Control on Windows 7 clients..........................................................40

Setting SQL password on a DSM..........................................................................................40

Use configured web proxy settings........................................................................................43

Multi-tiered bin support for K2 Summit..................................................................................44

Set Timecode per channel.....................................................................................................44

Standalone RMI.....................................................................................................................45

RMI import to K2 Summit......................................................................................................46

Adding clips to groups...........................................................................................................47

Previewing clips.....................................................................................................................47

2 Aurora Ingest Version 7.1.0 Release Notes and Upgrade Instructions 18 October 2010

Option to not create keywords on Merge Import...................................................................48

Support for trimmed clips in groups.......................................................................................48

Scheduling events with ENPS...............................................................................................49

Drag and drop scheduled items............................................................................................53

Additional notes........................................................................................................................55

Installing Ingest software manually........................................................................................55

Configuring ScheduALL properties ......................................................................................57

Configuring ScheduALL application .....................................................................................62

Known Issues............................................................................................................................64

18 October 2010 Aurora Ingest Version 7.1.0 Release Notes and Upgrade Instructions 3

Grass Valley Product Support

Grass Valley Product Support

To get technical assistance, check on the status of a question, or to report a new issue,
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: [e-mail]

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.

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.

In countryToll freeSupport Center

[phone][phone]France

[phone][phone]United States

TelephoneCountryRegion

[phone]ChinaAsia

4 Aurora Ingest Version 7.1.0 Release Notes and Upgrade Instructions 18 October 2010

[phone]Hong Kong, Taiwan, Korea,

Macau

[phone]Japan

[phone]Southeast Asia - Malaysia

South America

Grass Valley Product Support

TelephoneCountryRegion

[phone]Southeast Asia - Singapore

[phone]India

1 300 721 495AustraliaPacific

0800 846 676New Zealand

[phone]For callers outside Australia

or New Zealand

[phone]AllCentral America,

North America

Africa

North America, Mexico,
Caribbean

France

Eastern Europe

Tadzhikistan, Ukraine,
Uzbekistan

Near East and Africa

[phone];
[phone]

[phone]UK, Ireland, IsraelEurope

[phone]Benelux – Netherlands

[phone]Benelux – Belgium

[phone];
[phone]

[phone]Germany, Austria,

[phone]Belarus, Russia,

[phone]Northern Europe

[phone]Southern Europe – Italy

[phone]Southern Europe – Spain

[phone]Middle EastMiddle East, Near East,

[phone];
[phone]

18 October 2010 Aurora Ingest Version 7.1.0 Release Notes and Upgrade Instructions 5

Release note revisions for this release

Release note revisions for this release

This release of software has multiple versions of release notes, as follows:

DescriptionPart

number

Initial release notes for Aurora Ingest 7.1 software071-8550-11

Topics added/modified, with the following changes:071-8550-12

• SNFS and Generic iSCSI cab files are no longer bundled together.
Check the Compatible Grass Valley products on page 15 to
determine the version compatible with your system.

6 Aurora Ingest Version 7.1.0 Release Notes and Upgrade Instructions 18 October 2010

Release Summary

What's new in version 7.1.0

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

Version 7.1.0

• Windows 7 support — Aurora Ingest clients support the Windows 7 operating
system for 32-bit and 64-bit versions.

• Installing or updating SNFS and Generic iSCSI — SNFS and Generic iSCSI
cab files are no longer bundled together. Check the Compatible Grass Valley

products on page 15 to determine the version compatible with your system.

• Documentation for this release — In addition to these release notes, use the
following document for this release of Aurora Ingest software:

• Aurora Ingest System Guide v7.0 — 071-8514-06 — April, 2010

The document is on Aurora Ingest 7.0 Software CD with part number 063-8268-10
or you can also search for the document at http://www.grassvalley.com/docs.

Fixed in 7.1.0

number

PR25036

PR25138

CR112471

CR112610

CR113183

DescriptionReference

Ingest installation run via SiteConfig stalls if SQL Server service is not
running.

After inserting a P2 card and selecting the import destination, the destination
reverts back to the default location.

Modifying recurrence end date does not take effect.PR25199

Support login to database using Windows authentication mode.CR112271

Ingest Server process fails to shutdown when exiting the Ingest Server
application.

Unable to resize event and use Quick Schedule on Scheduler's timeline.CR112472

RMI crashes when there's a SonyEX directory structure within P2 or Infinity
disc.

Scheduler shows 'Failed to update database' error when modifying whole
recurring series.

Unable to record a feed with duration of more than 24 hours.CR113371

18 October 2010 Aurora Ingest Version 7.1.0 Release Notes and Upgrade Instructions 7

Release Summary

Feature limitation in this release

Changes and features in previous releases

• For Aurora Ingest to work with Windows 7, you need to disable the User Account
Control in your machine. Refer to Disabling User Account Control on Windows 7

clients on page 40 for more information in these release notes.

• When installing the Aurora Ingest Server on the DSM (IEP configuration), different
password requirements cause the database installation of the Aurora Ingest Server
to fail. Refer to Setting SQL password on a DSM on page 40 for more information
in these release notes.

• RMI does not support importing directly into a K2 HD/SD Media Server.

• RMI that imports directly into K2 Summit can only import to either shared K2

Summit storage or a single standalone K2 Summit.

NOTE: RMI cannot be setup to import to a combination of shared and standalone
K2 Summits or a combination of multiple standalone K2 Summits.

The following sections describe changes and features in past releases.

Version 7.0.0

• New Look — The look and feel of the Aurora Ingest has been changed to match
the rest of the Grass Valley product lines.

• New terminology — The MediaFrame server will now be referred to as K2
BaseCamp. (The scaled-down version of the Aurora Browse/MediaFrame system
is still referred to as K2 BaseCamp Express.)

• Use Configured Web Proxy Settings — You can set MediaFrame to use proxy
settings configured in your web browser to communicate with MediaFrame services.
For example, the proxy configured in Internet Explorer under Tools > Options >
Connections > LAN Settings > Proxy Server. Refer to Use configured web proxy

settings on page 43 for more information in these release notes.

• Multi-Tiered Bins in K2 Summit — Aurora Ingest supports the ability to configure
records into K2 Summit's multi-level bin hierarchy feature. The configuration needs
to be set up within the Aurora Ingest Server. Refer to Multi-tiered bin support for

K2 Summit on page 44 for more information in these release notes.

• Set Timecode per Channel — The setup is within the Channel Configuration part
of the Aurora Ingest Server. Refer to Set Timecode per channel on page 44 for
more information in these release notes.

• Standalone RMI — This is the latest addition of RMI operating mode, which
doesn't require Aurora Ingest Server to import clips from removable media devices.
Standalone RMI requires a local database only to recognize previously imported
clips and disks. The option to run Standalone RMI is during RMI installation. Refer
to Standalone RMI on page 45 for more information in these release notes.

• RMI import into K2 Summit — RMI allows importing clips directly into K2
Summit. Imports either can be saved into shared K2 Summit storage or into a single

8 Aurora Ingest Version 7.1.0 Release Notes and Upgrade Instructions 18 October 2010

Release Summary

standalone K2 Summit. RMI cannot be setup to import to a combination of shared
and standalone K2 Summits or a combination of multiple standalone K2 Summits.
Refer to RMI import to K2 Summit on page 46 for more information in these release
notes.

• Merge groups in RMI — This feature gives the ability to create multiple merge
import groups that can be imported at the same time. This allows operators to create
a number of groups of clips, name them, and then import them into the system
without having to stand by and repeat multiple merge imports separately. Refer to

Adding clips to groups on page 47 for more information in these release notes.

• View as Tape in RMI — RMI offers the option to preview clips when multiple
clips are selected within the RMI import list. This loads the preview tool with a
'View as Tape'-like preview within the regular bin trimmer view. This allows
operators to load clips into the viewer, play them and easily decide what to import.
Refer to Previewing clips on page 47 for more information in these release notes.

• Option to not create keywords on Merge Import — RMI offers the flexibility
to create keywords automatically or not create keywords on Merge Import. Refer
to Option to not create keywords on Merge Import on page 48 for more information
in these release notes.

• Support for Trimmed Clips in Groups — RMI supports the ability to trim clips
and import them within merged import groups while still preserving the edited
marks. Previously, trimmed clips could only be imported individually in order to
recognize the mark in and out attributes. Refer to Support for trimmed clips in

groups on page 48 for more information in these release notes.

• Multi-Select Rename in RMI — Multiple clips can now be selected and renamed
at the same time. This can be found in the right-click menu of RMI. When a group
of clips are renamed, they will each increment from the base clip name (e.g. <clip
name>(n+1).

• XDCAM EX Support — XDCAM EX is now part of the supported XDCAM
series from Sony. JVC also has the ability to encode in the XDCAM EX format.
These files are supported in both RMI and Aurora Edit.

NOTE: 'View as Tape' will not mix and match XDCAM and XDCAM EX media.
They are treated as separate formats, even if the characteristics of the file format
are similar.

• XDCAM 720p Support— 720p is now part of the supported file formats for
XDCAM.

• Enhanced MOS Workflow — With this workflow, ingested assets will be
embedded with MOS Object IDs and seen as MOS objects throughout ENPS. Feeds
that are scheduled either through Aurora Ingest Scheduler or the ENPS Assignment
Grid will automatically create MOS Object IDs within the system. The workflow
is enabled by selecting the Generate MOS Objects for Feeds option within Aurora
Ingest Server and XMOS Server. Refer to Scheduling events with ENPS on page
49 for more information in these release notes.

• Link to Placeholders in RMI — Prior to import, operators may link individual
clips, as well as groups of clips to placeholders in RMI. When imported into
appropriate folders, these assets may then be searched within ENPS and dragged
below the black line with scripts for use in Aurora Edit.

• Drag and Drop Scheduled Items — As an additional method of modifying feeds
within Aurora Ingest Scheduler, selected items can be dragged around the channel

18 October 2010 Aurora Ingest Version 7.1.0 Release Notes and Upgrade Instructions 9

Release Summary

and dropped in new locations or timeframes. Refer to Drag and drop scheduled

items on page 53 for more information in these release notes.

• Assign ETA Events from ENPS — ETA event is a channel reservation via ENPS.
Operators can assign ETA event on the ENPS assignment grid and block other
events from taking the slot on Scheduler. ETA event then allows operators to crash
record over it if the ETA start time has passed.

• Multi-Select Items in Scheduler for Deletion — Scheduler supports standard
selection techniques such as CTL + Select and Shift + Select in order to
highlight a number of feeds for deletion. This also includes recurring events.

• Goto Date Calendar Picker — The Goto Today, Goto Yesterday, and Goto

Tomorrow buttons have been consolidated into a single calendar picker, which

allows users to easily do all of the above while also selecting an exact date that is
more than one day away. This button is accessible within the timeline toolbar.

• Keyboard Scroll within combo boxes — Drop-downs for router sources, feed
channels, folder locations, etc. have been modified to accept typed characters for
quick auto-pick capabilities. When a combo box is selected, type a character and
the list will jump to the first item with that letter or number. If you continue typing
within 1 second of the first character, the search will become more granular.

• Recurring Date Extension Modifier — In order to account for anomalies with
various equipment or workflows that don't accept certain characters in file names,
we've added the option to alter the base extension modifier for recurring events.
Within the Tools|Options|Feed tab of the Aurora Ingest Server tool, there is a new
Recurring Date Format combo box with several options. The date format (e.g.
MM_DD_YYYY) will be determined through the regional settings of the Windows
OS. So, if the system is configured to see DD_MM_YYYY, then the combo box
options will reflect this setting.

• Maximize Channel View of VTR Ingest — As VTR Ingest allows for 8
simultaneous channels to be recording batch sessions at one time, the user interface
is challenged to present a single channel view that may be large enough to provide
enough list detail to the end user. Therefore, a new button has been added to each
channel of VTR Ingest which then allows for maximizing a window. Once selected,
the window expands to cover each of the other channels. Their functions, however,
will remain untouched, so recording in other channels will not be affected.

• Timecode Break and Keyword Scan from Middle of Tape — VTR Ingest offers
the option of starting record sessions from places other than the start of the tape.
When the buttons for timecode break scan and keyword scan are selected, the user
will be asked if they'd like to start the session from the current position of the tape.
A yes response will do so while a no response will rewind to the beginning of the
tape prior to starting the process.

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:

10 Aurora Ingest Version 7.1.0 Release Notes and Upgrade Instructions 18 October 2010

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.

Version 6.5.1.132

• K2 Summit compatible – The Aurora suite of software, including Aurora Ingest,
is compatible with the K2 Summit software.

Release Summary

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

• 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

Aurora Ingest Scheduler

• MediaFrame Integration – Users can search, preview and mark highlights directly

• Improved Crash Record Control – Users can name crash records, select router

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.

that ties into MediaFrame.

from the scheduling application.

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.

18 October 2010 Aurora Ingest Version 7.1.0 Release Notes and Upgrade Instructions 11

Release Summary

• 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.

Older versions

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

12 Aurora Ingest Version 7.1.0 Release Notes and Upgrade Instructions 18 October 2010

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)

RECOMMENDED SpecMINIMUM Spec

Processor(s)

Graphics

Media Drives

OS

Intel Core 2 Quad Core 2.33
GHz

OR

Two Intel Xeon 5160
Dual Core 3.0 GHz

Discrete graphics with 256
MB of dedicated memory
and support for Direct3D 9
and Shader Model 3.0

2 x 250 GB 7200 RPM
SATA striped

Windows XP Pro 32 SP3 or
Windows 7

Two Intel Xeon 5410 Quad
Core 2.33 GHz

4 GB4 GBMemory

Discrete graphics with 384
MB of dedicated memory
and support for Direct3D 9
+ 10 and Shader Model 4.0

80 GB 7200 RPM SATA80 GB 7200 RPM SATASystem Drive

2 x 250 GB 7200 RPM
SATA striped

CD/DVDCD/DVDOptical Drive

Gigabit Ethernet (2)Gigabit Ethernet (2)Network

As neededAs neededFirewire/1394

Windows XP Pro 32 SP3 or
Windows 7

Notes

18 October 2010 Aurora Ingest Version 7.1.0 Release Notes and Upgrade Instructions 13

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

Version compatibility

RECOMMENDED SpecMINIMUM Spec

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

Aurora Ingest RMI (SD)

MINIMUM Spec

Processor(s)

Graphics

Media Drives

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

2 GBMemory

Discrete graphics with 128
MB of dedicated memory
and support for Direct3D 9
and Shader Model 3.0

80 GB 7200 RPM SATASystem Drive

2 x 250 GB 7200 RPM
SATA striped

CD/DVDOptical Drive

Gigabit Ethernet (2)Network

OS

Notes

Aurora Ingest Server

Processor

14 Aurora Ingest Version 7.1.0 Release Notes and Upgrade Instructions 18 October 2010

As neededFirewire/1394

Windows XP Pro 32 SP3 or
Windows 7

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.

RECOMMENDED SpecMINIMUM Spec

Dell PowerEdge 610HP xw4600Model

Intel Xeon 1.0 GHzIntel Core 2 Dual Core 2.3

GHz

4 GB4 GBMemory

Version compatibility

RECOMMENDED SpecMINIMUM Spec

Graphics

graphics with 128 MB of
memory and support for
Direct3D 9 and Shader
Model 3.0

80 GB 7200 RPM SATASystem Drive

Windows XP Pro 32 SP3OS

Aurora Ingest (VTR Ingest, VTR Controller, Scheduler)

Processor

Graphics

Intel Core 2 Dual Core 2.3
GHz

Integrated or discrete
graphics with 128 MB of

Direct3D 9 and Shader
Model 3.0

Integrated graphicsIntegrated or discrete

36 GB 7200 RPM SATA or
SAS

CD/DVDCD/DVDOptical Drive

Gigabit EthernetGigabit EthernetNetwork

Windows Server 2003 R2 32
SP2

RECOMMENDED SpecMINIMUM Spec

Intel Core 2 Quad Core 2.3
GHz

2 GB1 GBMemory

Integrated or discrete
graphics with 128 MB of
memory and support formemory and support for
Direct3D 9 and Shader
Model 3.0

OS

Notes

Windows XP Pro 32 SP3 or
Windows 7

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:

80 GB 7200 RPM SATA80 GB 7200 RPM SATASystem Drive

CD/DVDCD/DVDOptical Drive

Gigabit EthernetGigabit EthernetNetwork

Windows XP Pro 32 SP3 or
Windows 7

CommentsVersionProduct

—7.1.0.8Aurora Browse client

18 October 2010 Aurora Ingest Version 7.1.0 Release Notes and Upgrade Instructions 15

Version compatibility

CommentsVersionProduct

Server

K2 system software

(SNFS)

7.1.0.18Aurora Browse MediaFrame

7.1.0.273Aurora Edit

7.1.0.39Aurora Playout

3.3.2.1401 or 7.2.7.1397Generic iSCSI Installer

3.3.2.1401 or 7.2.7.1397GVG_MLib Installer

3.3.2.1401 for K2 Media
Client

7.2.7.1397 for K2 Summit
Production Client

3.5.2.1b15620StorNext File System

With Windows Server 2003

SQL Server 2005 SP3

—7.1.0.15Aurora Proxy Encoder

With compatible version of
SQL

With compatible version of
SQL

Required for RMI when
importing to a K2 SAN

Required for Ingest Server
and RMI Installation

With compatible version of
SNFS

Required for RMI when
importing to a K2 SAN

Compatible with K2
version 3.3.2.1401 and K2
Summit version

7.2.7.1397

7.1.0.273RMI Core

1.0.0Grass Valley prerequisite

files

Compatible third party products

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

6.4DeckLink

6.00.0042ENPS

—2.0.13.567M-Series system software

Required for RMI
Installation

—1.4.0.451SiteConfig application

The prerequisite file must be
installed on the SiteConfig
control point PC.

CommentsVersionProduct

For use with Scheduled
Events

16 Aurora Ingest Version 7.1.0 Release Notes and Upgrade Instructions 18 October 2010

Version compatibility

CommentsVersionProduct

5.9FHauppauge

Microsoft Windows

XP with Service Pack 3,
Windows 7

Windows Server 2003Microsoft Windows Server

Windows 7 supported on
Ingest clients

For Ingest Server
Component only

Contact Panasonic for driver2.03.0002Panasonic P2 Driver

Contact Sony for driver2.04Sony XDCAM FAM Driver

18 October 2010 Aurora Ingest Version 7.1.0 Release Notes and Upgrade Instructions 17

Upgrading Aurora Ingest systems

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

With the upgrade instructions in this document, you use SiteConfig from a network
connected control point PC and remotely upgrade software simultaneously on your
Aurora product devices. This is the recommended process for software upgrades.

NOTE: Do not use the upgrade instructions in this document if upgrading with
SiteConfig for the first time.

If SiteConfig was not used for your previous software upgrade, do not use the upgrade
instructions in these release notes. Instead, use the SiteConfig Migration Instructions.
Before you upgrade software using SiteConfig, each of your Aurora product devices
must be migrated to become a SiteConfig managed device. This includes installing
SiteConfig support on the device, manually uninstalling any and all Aurora components,
and qualifying the device for communication with SiteConfig. These instructions are
in the SiteConfig Migration Instructions. Also refer to the SiteConfig User Manual or
SiteConfig Help Topics.

The upgrade instructions in this document apply to the following devices:

• Aurora Ingest Platform

• IEP

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
product devices to the SiteConfig system description that you are using for your K2
SAN.

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.

18 Aurora Ingest Version 7.1.0 Release Notes and Upgrade Instructions 18 October 2010

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.

• 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:

Upgrading Aurora Ingest systems

• File for all Aurora Ingest devices:

• Aurora Ingest software installation (*.cab) file

• GVGMLib software installation (*.cab) file

• Additional files for Aurora Ingest RMI devices:

• AuroraSuite software installation (*.cab) file

• GenericISCI software installation (*.cab) files

(GenericiSCSI_x86<versionnumber>.cab for the 32-bit and
GenericiSCSI_x64<versionnumber>.cab for the 64-bit.)

• SNFS software installation *.cab file
(SNFS_nonK2_x86<versionnumber>.cab for the 32-bit and
SNFS_nonK2_x64<versionnumber>.cab for the 64-bit.)

• PCmonitoring 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 adding a new 64-bit Windows 7 device in SiteConfig, make sure to select x64
as the platform type. This will enable the 64 bit versions of iSCSI and SNFS to be
installed instead of the default 32-bit.

4. If not already present in the SiteConfig system description, configure deployment
groups as follows:

18 October 2010 Aurora Ingest Version 7.1.0 Release Notes and Upgrade Instructions 19

Upgrading Aurora Ingest systems

A deployment group that contains your Aurora Ingest devices•

Install prerequisite files on the control point PC

Some software components, such as those for Aurora products, share common
prerequisite software. You must install a prerequisite software package on the control
point PC to make the prerequisite software available for software deployment to
devices.

1. Check release notes for the required version of prerequisite files, if any.

2. On the SiteConfig control point PC, open Windows Add/Remove programs and
look for Grass Valley Prerequisite Files, then proceed as follows:

• If the required version of prerequisite files is installed, do not proceed with this

task.

• If prerequisite files are not installed or are not at the required version, proceed

with this task.

3. Procure the required prerequisite software installation file. The file name is

Prerequisite Files.msi.

4. On the SiteConfig control point PC, run the installation file. The installation program
copies prerequisite files to C:\Program Files\Grass Valley\Prerequisite

Files.

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.

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.

20 Aurora Ingest Version 7.1.0 Release Notes and Upgrade Instructions 18 October 2010

Upgrading Aurora Ingest systems

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 computer

• 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 unless specifically directed by
product documentation or by Grass Valley Support.

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

18 October 2010 Aurora Ingest Version 7.1.0 Release Notes and Upgrade Instructions 21

Upgrading Aurora Ingest systems

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 Aurora product software at a version lower than 6.5.2 is currently installed, it
must be manually uninstalled. For more information refer to SiteConfig Migration
Instructions.

• If upgrading from Aurora Ingest 6.5.2, add the GVG MLib role to Aurora Ingest
Server device as the previously added device does not have the GVG MLib role.

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.

The Check Software dialog box appears. SiteConfig searches for software on
the selected device or devices and gathers information. Progress is reported.

22 Aurora Ingest Version 7.1.0 Release Notes and Upgrade Instructions 18 October 2010

Upgrading Aurora Ingest systems

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:

File nameSoftware

AuroraIngest_7.1.0.xxxx.cabAurora Ingest software – For all Aurora

Ingest devices

GVG MLib software – For Aurora Ingest
Server and RMI

device only

agent

NOTE: You need to reinstall RMI if you upgrade GVG MLib software in future.

GVG_MLib_3.3.2.1401.cab or
GVG_MLib_7.2.7.1397.cab

AuroraSuite_7.1.0.xxx.cabAurora Suite – For Aurora Ingest RMI

PCMonitoring_x.x.x.xx.cabGrass Valley Windows Monitoring SNMP

For Aurora Ingest RMI device, you must also add the following software package 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:

File nameSoftware compatible with 3.x K2 SAN

GenericISCI_x86_3.3.x.cabGeneric iSCSI client for 32 bit systems

GenericISCI_x64_3.3.x.cabGeneric iSCSI client for 64-bit systems

SNFS for 32 bit systems

18 October 2010 Aurora Ingest Version 7.1.0 Release Notes and Upgrade Instructions 23

GVG_MLib_3.3.x.cabGVG MLib

SNFS_nonK2_x86_x.x.x.xxx.cab (Use

version compatible with your K2 software)

Upgrading Aurora Ingest systems

File nameSoftware compatible with 3.x K2 SAN

SNFS for 64 bit systems

SNFS_nonK2_x64_x.x.x.xxx.cab (Use

version compatible with your K2 software)

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

File nameSoftware compatible with 7.x K2 SAN

GenericISCI_x86_7.2.x.cabGeneric iSCSI client for 32 bit systems

GenericISCI_x64_7.2.x.cabGeneric iSCSI client for 64 bit systems

GVG_MLib_7.2.x.cabGVG MLib

SNFS for 32 bit systems

SNFS for 64 bit systems

SNFS_nonK2_x86_x.x.x.xxx.cab (Use

version compatible with your K2 software)

SNFS_nonK2_x64_x.x.x.xxx.cab (Use

version compatible with your K2 software)

You can add files for both 32 bit and 64 bit systems because when SiteConfig deploys
software it automatically deploys the 32 bit or 64 bit software appropriate for the target
device. SNFS is no longer 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.

24 Aurora Ingest Version 7.1.0 Release Notes and Upgrade Instructions 18 October 2010

Upgrading Aurora Ingest systems

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

Aurora
Ingest

Deployment options

18 October 2010 Aurora Ingest Version 7.1.0 Release Notes and Upgrade Instructions 25

Select the SQL Server configuration that will be used by Aurora Ingest
Server. If you choose SQL Server 2005, select the server instance from

Upgrading Aurora Ingest systems

Software

Deployment options

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.

Enter the name of the Aurora Ingest Server.

GVG_MLib

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

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

Software

Ingest

Deployment options

Select the RMI operating mode, either Standalone RMI or RMI Client.Aurora

26 Aurora Ingest Version 7.1.0 Release Notes and Upgrade Instructions 18 October 2010

Upgrading Aurora Ingest systems

Software

GVG_MLib

Aurora
Suite

Deployment options

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

18 October 2010 Aurora Ingest Version 7.1.0 Release Notes and Upgrade Instructions 27

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

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.

• Prerequisite files are installed on the control point PC.

• You have recently done the SiteConfig "Check Software" operation on the devices

you are upgrading.

If you are upgrading multiple software components for which there is a required
sequence, you must check and uncheck tasks and run multiple deployment sessions
to control the sequence. For some software components, SiteConfig aids you by
enforcing dependencies. For each individual software component, SiteConfig enforces
an uninstall of the current version of software before installing the upgrade version.
SiteConfig provides uninstall deployment tasks and install deployment tasks to indicate
the taskflow. SiteConfig can do the uninstall/install in a single deployment session.

28 Aurora Ingest Version 7.1.0 Release Notes and Upgrade Instructions 18 October 2010

Upgrading Aurora Ingest systems

1. In the Software Deployment | Deployment Groups tree view, select the device or the
group of devices to which you are deploying software.

The corresponding software deployment tasks are displayed in the Tasks list
view.

2. For the software you are deploying, select the Deploy check box in the row for the
uninstall task.

NOTE: If you manually uninstalled or installed software, the uninstall task
might not appear or it might appear with a different package name.

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:

Managed PackageDeploy

xxxx.xxxx

7.1.0.xxxx

must be compatible with K2 SAN)

Action

UninstallAuroraIngest xxxx.xxxx

InstallAuroraIngest 7.1.0.xxxx

UninstallIngestServerPrerequisites

InstallIngestServerPrerequisites

UninstallGVGMLib xxxx.xxxx

InstallGVGMLib xxxx.xxxx (version

InstallPCmonitoring x.x.x.xx

For Aurora Ingest RMI devices, also deploy the following tasks:

Managed PackageDeploy

Action

UninstallAuroraSuite xxxx.xxxx

InstallAuroraSuite 7.1.0.xxx

18 October 2010 Aurora Ingest Version 7.1.0 Release Notes and Upgrade Instructions 29

GenericISCI x86 xxxx.xxxx

GenericISCI x86 xxxx.xxxx
(version must be compatible with
K2 SAN)

GenericISCI x64 xxxx.xxxx

GenericISCI x64 xxxx.xxxx
(version must be compatible with
K2 SAN)

Uninstall

Install

Uninstall

Install

Upgrading Aurora Ingest systems

Also, you must upgrade SNFS with this release, so deploy the following tasks
at the same time:

Managed PackageDeploy

SNFS nonK2 x86 xxxxxx

SNFS nonK2 x86 xxxxxx

SNFS nonK2 x64 xxxxxx

SNFS nonK2 x64 xxxxxx

Action

Uninstall

Install

Uninstall

Install

When using SiteConfig for upgrades, the SNFS upgrade is required even if you
are already at version 3.5.2.1b15620. The upgrade resets SNFS version
information for SiteConfig.

NOTE: If there are dependencies, SiteConfig can enforce that some tasks be
deployed together.

4. Check the area next to the Start Deployment button for a message.

If a message instructs you to upgrade the Discovery Agent, on the control point
PC go to the directory to which SiteConfig is installed, find the

DiscoveryAgent_x.x.x.x.cab file, add it to the deployment group, and deploy

the Discovery Agent software as well.

5. Click the Start Deployment button.

Deployment tasks run and software is uninstalled. Progress is reported and next
steps are indicated in both the Status and Details columns. If an error appears
regarding prerequisite software, install the prerequisite files on the control point
PC and then repeat this step.

30 Aurora Ingest Version 7.1.0 Release Notes and Upgrade Instructions 18 October 2010

Upgrading Aurora Ingest systems

6. When the Status or Details columns indicate next steps, identify the software in
the row, then do one of the following:

• For K2 software, 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.

7. When the Status or Details columns indicate next steps, identify the software in
the row, then do one of the following:

• For K2 software, when Details displays a Restart required link, click the link

and when prompted "...are you sure...", click Yes.

The device restarts.

8. 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.

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.

18 October 2010 Aurora Ingest Version 7.1.0 Release Notes and Upgrade Instructions 31

Upgrading Aurora Ingest systems

Upgrade your Browse and MediaFrame systems to the compatible versions of
software. Refer to Aurora Browse Release Notes for procedures.

32 Aurora Ingest Version 7.1.0 Release Notes and Upgrade Instructions 18 October 2010

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

This topic applies to Grass Valley Sabretooth licenses. 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.

18 October 2010 Aurora Ingest Version 7.1.0 Release Notes and Upgrade Instructions 33

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. If you have K2 Summit Production Client or K2 Solo Media Server and if the write
filter is currently enabled, be aware that files on the desktop are lost on restart.
Therefore do one of the following:

• Save the License Request text file(s) to a different location.

• Keep the K2 system running (do not restart) until after you have requested the

license(s).

8. Do one of the following:

• Attach the License Request 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.

9. 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.

10. 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, or the License wizard is not
available, try this alternate method:

34 Aurora Ingest Version 7.1.0 Release Notes and Upgrade Instructions 18 October 2010

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:

• Customer Name

• Customer Email

• Sales Order Number

• Unique ID of the device where you will install software.

3. Send the email to [e-mail].

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

Adding a license

Licensing Grass Valley products

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.

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.

18 October 2010 Aurora Ingest Version 7.1.0 Release Notes and Upgrade Instructions 35

Licensing Grass Valley products

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.

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
re-license the 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 typeLicense

SabreToothAurora-Ingest-Number of channels

SabreToothAurora-Ingest-RMI

SabreToothAurora-Ingest-Scheduler

SabreToothAurora-Ingest-VTR Ingest

SabreToothAurora-Ingest-VTR Logging

SabreToothAurora-Ingest-ScheduALL

36 Aurora Ingest Version 7.1.0 Release Notes and Upgrade Instructions 18 October 2010

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 WinTV-HVR-1150 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

18 October 2010 Aurora Ingest Version 7.1.0 Release Notes and Upgrade Instructions 37

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 7.1 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 and Windows 7 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.

To disable XDCAM pop-up in Windows 7, follow the steps below:

38 Aurora Ingest Version 7.1.0 Release Notes and Upgrade Instructions 18 October 2010

Operation considerations

1. Go to Start | Control Panel | Hardware and Sound | Auto Play.

2. Scroll down to Devices to get to Sony XDCAM.

3. Select Take no action from the drop-down list.

4. Click Save.

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.

18 October 2010 Aurora Ingest Version 7.1.0 Release Notes and Upgrade Instructions 39

New topics

New topics

Disabling User Account Control on Windows 7 clients

This section contains new or modified topics associated with this release of software.

You need to disable the User Account Control on Windows 7 in order to use Aurora
Ingest.

1. Go to Start | Control Panel | User Accounts.

2. Click on the Change User Account Control settings link.

3. Drag the slider bar to the lowest value that shows Never notify.

4. Click OK.

5. Restart your computer for the change to take effect.

Setting SQL password on a DSM

Aurora Ingest Server in this release requires an SQL SA password. However, the
database that is shipped on a DSM or IEP system has an SA account with no password
associated with it.

In release 7.0 password requirements are as follows:

• The Aurora Ingest Server requires an SQL SA password of "triton".

• The DSM does not require an SQL SA password. Therefore the password is left

blank.

When installing the Aurora Ingest Server on the DSM (IEP configuration) these
different password requirements cause the database installation of the Aurora Ingest
Server to fail.

To fix the problem, before installing the Aurora Ingest Server software, change the
SQL SA password to "triton".

1. Log in to the DSM as an Administrator.

2. Click Start | Programs | Microsoft SQL Server | SQL Server Management Studio to
start SQL Server Management Studio (SSMS).

3. In the Object Explorer pane on the left of SSMS, do the following:

a) Right-click on the server icon and choose Properties.
b) Select the Security page.

40 Aurora Ingest Version 7.1.0 Release Notes and Upgrade Instructions 18 October 2010

New topics

c) If not already selected, select SQL Server and Windows Authentication mode.
d) Click OK.

4. If you made a change in the previous step do the following:

a) Restart the server.
b) Log in to the DSM as an Administrator.
c) Click Start | Programs | Microsoft SQL Server | SQL Server Management Studio

to start SQL Server Management Studio (SSMS).

5. In the Object Explorer pane on the left of SSMS, do the following:

a) Navigate to Security | Logins.
b) Right-click on the sa login and select Properties.
c) Select the General page in the left pane of the dialog.

18 October 2010 Aurora Ingest Version 7.1.0 Release Notes and Upgrade Instructions 41

New topics

d) In the Password and Confirm Password fields change the sa user's password to

the following: triton

e) Click OK.

6. In the Properties dialog do the following:

a) Select the Status page.

42 Aurora Ingest Version 7.1.0 Release Notes and Upgrade Instructions 18 October 2010

New topics

b) Under Settings, if not already selected, select Grant.
c) Under Login, if not already selected, select Enabled.
d) Click OK.

7. Verify that Aurora Ingest can connect to the database during installation.

Use configured web proxy settings

A new setting to bypass the configured web proxy has been added to each application
within the Aurora Suite. This checkbox pertains to environments that have MediaFrame
enabled.

For Aurora Ingest, the checkbox is found in Tools|Options|System of the Ingest Server
and will become active only with MediaFrame turned on.

• When checked, the application will continue to go through the configured Web
Proxy settings in order to communicate with MediaFrame services.

18 October 2010 Aurora Ingest Version 7.1.0 Release Notes and Upgrade Instructions 43

New topics

When deselected, web calls through MediaFrame services will bypass the configured
settings.

Multi-tiered bin support for K2 Summit

To account for K2 Summit's multiple level bin hierarchy feature, Aurora Ingest now
provides the ability to configure record destinations to locations other than root
directories. This must be set up within the Aurora Ingest Server component.

From the Tools|Options|Media Server tab of the Ingest Server, clicking Add|Modify
within the record locations dialog will lead to a new selection interface. From this
tool, you may select the proper server, which will present an explorer interface.
Expanding the + symbol will expose additional directories, which may then be selected
for new record locations.

Set Timecode per channel

In past versions, the entire Ingest application had a certain timecode source for feed
capture.

With 7.0 however, each channel within the system can have their own timecode source.
This allows operators to select proper channels for particular timecode sources.

The setup is within the Channel Configuration part of the Aurora Ingest Server.

44 Aurora Ingest Version 7.1.0 Release Notes and Upgrade Instructions 18 October 2010

Standalone RMI

In the past, RMI had to have the Aurora Ingest Server in order to function even at a
base import level. This tether is removed in 7.0, which makes RMI much more flexible
and opens it up to practical operation in the field.

New topics

With the standalone RMI, the Aurora Core is still a requirement as is the iSCSI
connectivity of the system.

Standalone RMI will require a local database, which get installed as part of the Aurora
Core. This is so that RMI can recognize previously imported clips and disks.

The following screenshot shows the configuration for both the client (current) and
standalone methods of running RMI. You'll see that selecting standalone enables
configuration for both the MediaFrame server and the Aurora Playout components.

18 October 2010 Aurora Ingest Version 7.1.0 Release Notes and Upgrade Instructions 45

New topics

RMI import to K2 Summit

In the past, RMI only imported as .vmf and inserted media into the NewsShare DSM.
This is changed with 7.0 as RMI can now operate in a non-DSM environment and
import directly into the K2 Summit while writing .cmf files.

This is configured via Tools|Options in RMI where the operator can choose to have a
database type that is either News or K2.

Once K2 is selected, the operator will be able to direct the import to a specific K2
Summit, much like configuring a SmartBin. This is made available by the inclusion
of the Mlib software on the RMI system.

46 Aurora Ingest Version 7.1.0 Release Notes and Upgrade Instructions 18 October 2010

Adding clips to groups

If needed, you can create groups and add clips into a group before importing in RMI.
This allows operators to create a number of groups of clips, name them, and then
import them into the system without having to stand by and repeat multiple merge
imports separately. Trimmed clips can also be merged into a group and the edited
marks will still be preserved.

1. Select a clip or multiple clips that you want to merge into a group.

2. Right-click and select Add to Group. You can create a new group name or use
existing group names.

New topics

3. Enter the group name if you choose to create a new group.

The group name that you selected will appear in the Merge Group column of that clip.
Then, the group name will become the name of the imported clip once in the system.

You can also remove clips from the group by selecting Remove from Group in the
right-click menu. The Highlight Group option will go ahead and select all clips that
have the same group name.

Previewing clips

When multiple clips are selected within the RMI import list, the operator now has the
option to Preview Clips. This allows users to easily select, deselect and decide what
to import from the list.

1. Verify that the removable media device is plugged in and media is attached or
inserted.

2. Select Programs | Grass Valley | Aurora | RMI.

3. Enter the Tape ID when the dialog box is displayed on screen.

The detachable media option (Rev, P2, XD) is seen automatically.

4. To preview clips, select multiple clips and click the Preview Clips button.

5. The Preview window is launched and you can preview clips by clicking control
buttons on the window.

18 October 2010 Aurora Ingest Version 7.1.0 Release Notes and Upgrade Instructions 47

New topics

NOTE: This feature is only for multiple clips preview. When playing through
clips, the RMI import list will display the currently playing clip in blue.
Therefore, users can easily select what to import on the RMI list. Trimming
is not supported when multiple clips are loaded for preview.

Option to not create keywords on Merge Import

Although many sites like the idea of having automatic keywords generated for merge
imports from RMI, not all of them find this to be a benefit for their workflow.

Some like to import merged clips as a single asset and then allow operators to log the
material after importing. The pre-generated keywords tend to get in the way of this
workflow.

To account for this, Tools|Options|Settings now has a checkbox that allows customers
to disable the creation of keywords on import. This is set to off by default.

Support for trimmed clips in groups

In 6.5, trimmed clips could only be imported individually in order to recognize the
mark in and out attributes. With 7.0, however, operators can trim clips and import
them within merged import groups while still preserving the edited marks.

48 Aurora Ingest Version 7.1.0 Release Notes and Upgrade Instructions 18 October 2010

With the additional option to link to placeholder on import, this makes it possible to
edit simple VOs, Bumps, Teases, etc. directly from RMI. Simply trim the clips, order
as needed, and then group the clips into a merged asset that is tagged with a Placeholder
ID. Import this into a folder that is being monitored by Aurora Playout and the story
will be ready for air.

NOTE: Long GOP material from XDCAM and EX will come in with a bit of extra
material on either end of the trimmed media. This is due to the fact that we have to
import on I-Frame boundaries if we are to avoid a transcoding step. It is not
recommended that Long GOP merges go directly to air as the end result may be
different than the original trimmed marks. However, keywords for Long GOP merge
imports will reflect the expected in and out marks created within RMI.

Scheduling events with ENPS

You can schedule events on the Scheduler via ENPS by creating a newsgathering grid.

Prior to creating a newsgathering in ENPS, take note of the MOS ID of your XMOS
Server (by clicking Tools | Options) and ensure that the NCS ID is configured to ENPS.

New topics

If your workflow requires embedded MOS Object IDs with each scheduled event,
ensure that the Generate MOS Objects for Feeds checkbox is selected in XMOS Server
and Aurora Ingest Server.

Channel availability depends on channel group and user logon that had been setup
within Aurora Ingest Server.

18 October 2010 Aurora Ingest Version 7.1.0 Release Notes and Upgrade Instructions 49

New topics

Make sure there is at least 10 seconds of space between scheduled feeds.

1. From the NEWS folder, select New | Newsgathering and the following window will
be displayed:

2. Select GV Assignments template and configure the newsgathering:
The program name will also be GV assignments by default; you can change the
program name to suit your broadcast operation.

a) Enable the MOS Control Active field by clicking on it.

A check sign will be displayed.

b) Click on MOS Story Send and select your MOS ID from the list.

You can also select ETA Assignments template if you want to assign an ETA
event. The ETA event is a channel reservation through ENPS interface for an
event that has tentative start time. As the ETA event reserves a specific channel
on the Scheduler, you cannot assign another event on it. You can crash record
the ETA event after the scheduled time has lapsed.

3. Click Go.

The above window will be displayed.

If you selected ETA Assignments template, the below window will be displayed:

50 Aurora Ingest Version 7.1.0 Release Notes and Upgrade Instructions 18 October 2010

New topics

4. To create a story or newsgathering item, right-click on AM Assignments or PM
Assignments and select Insert row or press CTRL-I for the hotkey.

5. Enter the name of the story and click on each column on the selected line of the
assignment grid to fill out other information of the event you are scheduling:

• Object Autocreate—Select the MOS ID that you use for MOS Story Send. If

the Generate MOS Objects for Feeds option is selected in Aurora Ingest Server
and XMOS Server, a MOS Object ID will be created within the system and
assigned to that story. Then, the feed event will be recognized as a MOS Object
and it can be searched within ENPS.

NOTE: The ObjectAutoCreate column is the trigger mechanism that adds the
MOS Object into the system.

• ETA—Click the field in the column to assign the story as an ETA event.

A check sign will be displayed in the ETA column.

• Feed Source—Select the feed source from the drop-down list. If a router is

configured within Aurora Ingest - Server, router sources are available within
the drop-down.

• Channel—Select the name of the channel for the recording. Available channels

depend on channel group and user logon setup within Aurora Ingest - Server.
A channel will be auto-assigned, if no channel is entered for this setting.

NOTE: If there aren't any channels available on the Scheduler, ENPS doesn't
have any way of alerting the user.

• Location—Select the record location of the event from the drop-down list.

• Start Time—Enter the start time of the event. The time format is HH:MM.

• End Time—Enter the end time of the event. The time format is HH:MM.

• MOS Status—The status changes to Standby and the event shows up in Aurora

Ingest Scheduler.

• Feed Notes—Enter the description or any extra information of the event.

6. Create more stories if you want to schedule more events via ENPS.
Details of the scheduling can easily be changed and viewed on the assignment
grid.

18 October 2010 Aurora Ingest Version 7.1.0 Release Notes and Upgrade Instructions 51

New topics

7. Double-click on the Script icon if you want to write scripts for the story.

8. You can also click within the script window to edit details of the scheduling.

9. Open your Scheduler main window to see events scheduled via ENPS. Those events
are distinguished from other events by green borders.

52 Aurora Ingest Version 7.1.0 Release Notes and Upgrade Instructions 18 October 2010

New topics

Even an ETA event has a green border because it is scheduled via ENPS.
However, the event has a black background which is similar to a channel
reservation event on the Scheduler. While, a regular ENPS event has the same
background color as other events on the Scheduler.

10. You can also change the border color of ENPS events in the color tab within Tools

| Options of the Scheduler.

Status colors of ENPS events are the same as other events setup on the Scheduler.
As can be seen below, the ENPS event displays in yellow as the event is cueing.

11. The MOS Status change is updated on the assignment grid of ENPS in this sequence:

• Standby

• Cueing/Cued

• Recording

• Done

12. To delete an event, you need to delete it from the assignment grid in ENPS.
You cannot delete an ENPS event in Aurora Ingest Scheduler.

Drag and drop scheduled items

In Scheduler, you can drag and drop scheduled items around other channels or
timeframes.

1. Select an item and make sure that the blue selection moniker is around the item.

2. Click and hold the mouse while dragging the item left, right, up, or down.

18 October 2010 Aurora Ingest Version 7.1.0 Release Notes and Upgrade Instructions 53

New topics

3. You will be prompted Yes or No at the time of dropping the feed.

NOTE: The same rule for dragging and dropping across channel groups still
applies to this method of changing time and channels.

54 Aurora Ingest Version 7.1.0 Release Notes and Upgrade Instructions 18 October 2010

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.

Installing Ingest software manually

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:

Do this...On this screen...

Click Next.Welcome

Select I accept... and click Next.License Agreement

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.

18 October 2010 Aurora Ingest Version 7.1.0 Release Notes and Upgrade Instructions 55

Additional notes

Do this...On this screen...

Specify Aurora Ingest RMI
Configuration (if RMI
component is selected in
the Select Features screen)

Specify Aurora Ingest
Server Configuration

Application

Select the RMI mode for your operation; whether Standalone
or Client. Standalone means that RMI will run as a standalone
application without needing to connect to an Ingest Server.
If RMI will be connected to an Ingest Server, choose Client.

Enter the host name of Aurora Ingest Server that will be used
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.

Click Next.Ready to Install the

Click Finish.Installation Complete

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)

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

56 Aurora Ingest Version 7.1.0 Release Notes and Upgrade Instructions 18 October 2010

Additional notes

• 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.

Configuring ScheduALL properties

ScheduALL properties can be configured in the System tab when you select Tools |

Options within Aurora Ingest Server.

18 October 2010 Aurora Ingest Version 7.1.0 Release Notes and Upgrade Instructions 57

Additional notes

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

The ScheduALL Properties dialog box is displayed.

58 Aurora Ingest Version 7.1.0 Release Notes and Upgrade Instructions 18 October 2010

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.

18 October 2010 Aurora Ingest Version 7.1.0 Release Notes and Upgrade Instructions 59

Additional notes

3. Configuration details can be entered as below:

DescriptionOption

Default Ingest
Server Address

Channel
Assignment

Add New
Channel

Enter the host name or IP address of the default Ingest Server. The
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.

Shows channel name and host name of the Ingest Server if you
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 the channel name and host name of the Ingest Server other
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.

60 Aurora Ingest Version 7.1.0 Release Notes and Upgrade Instructions 18 October 2010

Additional notes

4. To edit channel and router resources 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,
each channnel on those Ingest Servers must be configured with unique names
to avoid scheduling conflicts with ScheduALL.

18 October 2010 Aurora Ingest Version 7.1.0 Release Notes and Upgrade Instructions 61

Additional notes

Configuring ScheduALL application

7. Click OK after you have finished configuring ScheduALL properties.

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.

62 Aurora Ingest Version 7.1.0 Release Notes and Upgrade Instructions 18 October 2010

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.

Additional notes

7. Click OK to save the setting.

18 October 2010 Aurora Ingest Version 7.1.0 Release Notes and Upgrade Instructions 63

Known Issues

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

Description:CR80235

Workaround:

Description:CR86146

Workaround:

Description:PR20458

Workaround:

The extra “_b” appended to backup feed clip name could break
conformance from remote system.

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

With more than 100 hours of storage space remaining on K2,
Ingest misreports storage.

Aurora Ingest will begin to properly report storage once the
capacity has fallen below 100 hours.

When installing Aurora on Windows 7 clients, a pending
SiteConfig dialog can be missed.

When a dialog is pending, a blinking icon displays on the
Windows 7 task bar. Clicking on this indicator brings up the
dialog that takes you to the isolated session. If you are logged
in via remote desktop, the interactive services detection service
sends a notification about the pending dialog. If the notification
has been missed, go into Windows Services and stop and
restart the Interactive Services Detection Service. This causes
the service to send an immediate notification about the pending
dialog.

Aurora Ingest - Scheduler

Description:CR78916

Workaround:

Description:CR87061

Workaround:

Description:CR89491

64 Aurora Ingest Version 7.1.0 Release Notes and Upgrade Instructions 18 October 2010

Crash record of gang-roll events could fail if the default clip
name consists of more than 32 characters.

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.

Having completed recurring events in Scheduler prevents the
ability to create a series with the same name going forward.

Delete the event from today that already finished recording.
Now Scheduler will let you add a new series with that name.

When custom metadata fields are reordered in Aurora Browse,
they do not get reordered in Ingest.

Known Issues

Workaround:

Workaround:

Description:CR94791

Workaround:

Description:CR99287

Workaround:

Description:CR99410

Workaround:

Close and relaunch Schedule client in order to see the updated
order of custom fields.

Thumbnails don't appear for keywords marked using X-keys.Description:CR94269

Marking keywords manually through the MediaFrame plug-in
window will create a keyword if proxy media exists.

If crash record default bin doesn't exist on media server,
Scheduler shows "Error obtaining clip duration from the media
server".

It is highly recommended that record directories exist on the
media client prior to attempting records or sends.

On clean install with no MediaFrame configuration, Scheduler
default UI has big blank Search window.

This window is harmless. Close the dialog and subsequent
relaunches of the Scheduler will not present the window.

X-keys generic Keyword button adds keyword with blank
name, rather than default name.

When adding a keyword button for X-Keys, opt to add a name
for the keyword.

ScheduALL status light is red while functionality is OK.Description:CR104168

Description:CR104930

Workaround:

Aurora Ingest - RMI

Description:CR98692

None.Workaround:

Non-recurring events get a Creation Date time stamp on the
day they're scheduled, not the day they're recorded.

Use MediaFrame's Metadata Mapping feature to create a
custom metadata field.

1. In MediaFrame/Aurora Browse, create a custom metadata

field whose type is “Date”. You could name the field
“Scheduler Start Time” or something similar.

2. On the MediaFrame Server, go to MediaFrame Config’s
Metadata Mapping tab and map it to show that Scheduler’ s
“EventStartDateTime” field is mapped to your custom
Date field (e.g. "Scheduler Start Time").

3. In Aurora Browse, go to Choose Columns and display your
custom Date field. Now you can sort by the time that events
actually recorded.

If logged in as user without "Modify" rights to
V:\VibrintXDCAMFiles, canceling RMI cache prevents it
from caching again.

18 October 2010 Aurora Ingest Version 7.1.0 Release Notes and Upgrade Instructions 65

Known Issues

Workaround:

Description:CR98929

Description:CR108671

Workaround:

Description:CR110044

Workaround:

Description:CR110610

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.

Clips that were part of a merged import don't show "Exists"
status after relaunching RMI.

No workaround at this time.Workaround:

Panasonic P2 thumbnails that show up under RMI Admin
account don't appear under User account.

1. Login using an administrator account.

2. Give group 'Users' full permission to 'VibrintRMIFiles'
folder.

RMI that imports directly into K2 Summit can only import to
either shared K2 Summit storage or a single standalone K2
Summit.

RMI cannot be setup to import to a combination of shared and
standalone K2 Summits or a combination of multiple
standalone K2 Summits.

RMI needs MetadataProxy.dll & MetadataSrvAdmin.dll copied
to the RMI folder after installation of GVG_MLib.

Workaround:

If GVG-MLib is upgraded, RMI needs to be reinstalled in
order to grab above files.

66 Aurora Ingest Version 7.1.0 Release Notes and Upgrade Instructions 18 October 2010