Grass Valley Aurora Browse v.6.5 Installation - Manual (Page 12)

12 Aurora Browse Installation and Configuration Guide November 1, 2008
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 consideration when establishing the workflow for your use of
Aurora Browse:
Separation of Browse Proxy and Browse metadata — In Aurora Browse 6.5, there
is a clear separation of proxy and metadata. For example, someone using Aurora Edit
could have a hi-res asset within the MediaFrame database without tying up encoders
for the proxy. This would allow them to search, add metadata, perform other tasks.
mpg
Ingest*
Aurora Edit
High-res Audio/Video
MPEG1 low-res proxy video
The Ingest system can be a K2, M-Series, or stand-alone Profile system.
The Media Storage is a K2 system.
On large systems the Client (formerly called 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
MediaFrame Core communications, such
as between MDIs, ASK, and Resolver.
MediaFrame
Server
Aurora Browse Clients
Advanced
Encoder
SmartBin Encoder****
Archive
AV
mpg
th/sb
Client/FTP (formerly Production) Network***
Corporate LAN (formerly Client) Network
MDI Server
mpg info info info info info
info
info th/sb
mpg th/sb
th/sb
th/sb
AV
AV
AV
Media
Storage**
AV
Proxy
NAS
info
mpg
DSM
(News MDI server)
Aurora Ingest
Ingest
o
Edit
) n)
Browse
e
e
e
Proxy
P
N
MediaFrame
Conform server Aurora FTP server
(archive)
!
!