System diagram - k2 storage, Chapter 1 system overview, Ingest edit browse – Grass Valley Aurora Browse v.6.0b Installation User Manual

Page 12

Aurora Browse Installation and Configuration Guide

September 22, 2006

Chapter 1 System Overview

System diagram - K2 storage

This diagram illustrates an example architecture for a system that uses Aurora Ingest
for ingest and that accesses high-resolution media on K2 storage.

The system illustrated here demonstrates the full range of hardware platform types.
Smaller systems might not include all types of hardware platforms. Consult the
system design for your specific system to determine the hardware platforms you must
install.

Design considerations - Aurora Browse with Aurora Edit

Take the following into considerations when establishing the workflow for your use
of Aurora Browse:

Minimize proxy creation for short-lived material

— The editing process generates

multiple pieces of transitional media, but there is no need to create proxy
representations of this transitional media. To do so creates an unnecessary load on the
system and affects performance.

To avoid this, create at least three designated locations in which material resides to
match your workflow, as follows:

• Inbox — This is the location in which newly acquired material arrives. Use a

mpg

Ingest
Media
Server*

Aurora Edit

High-res Audio/Video

MPEG1 low-res proxy video

The Ingest Media Server can be a K2 system or an M-Series system.

The Media Storage is a K2 system.

On large systems the Production Network can be separated into two
networks: one for media and one for control.

The SmartBin Encoder also bridges between the Edit and
the Browse Proxy systems.

***

****

Thumbnail, storyboard

Web application html pages

MediaFrame Core communications, such
as between MDIs, ASK, and Resolver.

MediaFrame
Server

Aurora Browse Clients

Advanced
Encoder

SmartBin Encoder****