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

November 1, 2008 Aurora Browse Installation and Configuration Guide 13
Legacy systems
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
SmartBin—or configure Aurora Browse rules—to automatically create proxy for
this material, so you can use Aurora Browse to evaluate and select material for
further editing.
• Workspace — This is the location in which you store material undergoing the
editing process. Do not configure any Aurora Browse rules to create proxy for this
material. This saves encoding resources.
• Outbox — This is the location in which you place material that has been edited and
is usable in its current state. You might have one outbox for on-air material and one
outbox for review material. Configure Aurora Browse rules to create proxy for this
material, so you can use Aurora Browse to select and use this material.
Legacy systems
This manual documents Browse systems using K2 systems for media storage.
Existing systems, such as those using Profile XP/Open SAN for media storage, do not
match the systems documented in this manual.
You can find some information about earlier systems in Appendix C, Legacy systems
on page 121. If you need the entire overview and task flow for working on a legacy
system, you should refer to the version of this manual that corresponds to the software
version around which your system was originally built.