EditShare Avid-Style Sharing - Software updates
EditShare Avid-Style Sharing - Software updates
EditShare Avid-Style Sharing - Software updates
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
<strong>EditShare</strong> ReadMe<br />
Storage Version 6.0.5.4<br />
Ark Version 2.0.5.4<br />
Flow Version 2.0.5.2<br />
December 9, 2010<br />
Always check <strong>updates</strong>.editshare.com for the latest version of this ReadMe.<br />
This version of <strong>EditShare</strong> provides support for <strong>EditShare</strong> Geevs, includes a new<br />
Flow release, and fixes several limitations. It is for <strong>EditShare</strong> systems already<br />
running earlier versions of 6.0.x.<br />
If you are already running a version of <strong>EditShare</strong> v6.x, see the following sections:<br />
• New in this Version<br />
• Fixed in this Version<br />
If you are upgrading from a v5.5.23 system, see the following section:<br />
• Upgrading from Version 5.5.23<br />
Also see the following sections:<br />
• Supported Client Versions<br />
• Changes in Previous Versions<br />
• Limitations<br />
• Technical Support Information<br />
NOTE: If you purchased the <strong>EditShare</strong> Ark option or if it was included with your XStream<br />
server, the software update for Ark v2.0.5.4 is included with this update. If you purchased
EDITSHARE README STORAGE VERSION 6.0.5.4 ARK VERSION 2.0.5.4 FLOW VERSION 2.0.5.2<br />
NEW IN THIS VERSION<br />
the <strong>EditShare</strong> Flow option or if it was included with your XStream server, the software<br />
update for Flow v2.0.5.2 is included with this update.<br />
New in this Version<br />
This version includes the following:<br />
• Initial support for <strong>EditShare</strong> Geevs version 5.0. You can now add Geevs to<br />
your system through the <strong>EditShare</strong> Role Assistant.<br />
• <strong>EditShare</strong> Flow version 2.0.5.2. See "Flow Version 2.0.5.2" on page 2.<br />
Flow Version 2.0.5.2<br />
Flow v2.0.5.2 includes the following new features:<br />
• You can now change the size of the thumbnail display in Flow Logger by<br />
pressing Ctrl and the plus-sign key (+) or Ctrl and the minus-sign key (-).<br />
• You can now view clips by dragging them into the Preview window.<br />
Fixed in this Version<br />
The following <strong>EditShare</strong> limitations have been fixed:<br />
• If your <strong>EditShare</strong> Storage system included a large number of Media<br />
Spaces, you might not have been able to add new Media Spaces or add<br />
users to Media Spaces. This has been fixed.<br />
• Users of <strong>Avid</strong>-<strong>Style</strong> Media Spaces might have experienced occasional<br />
issues with reading bins and <strong>Avid</strong> media database PMR files. This has been<br />
fixed.<br />
• Users of <strong>Avid</strong>-<strong>Style</strong> Media Spaces running <strong>Avid</strong> on Windows 7 might<br />
have experienced long delays when beginning video capture. This has<br />
been fixed.<br />
• You might have experienced timecode breaks during periods of high CPU<br />
use or multiple simultaneous captures. This has been fixed.<br />
• You might not have been able to change the proxy format from the<br />
default. This has been fixed.<br />
2
EDITSHARE README STORAGE VERSION 6.0.5.4 ARK VERSION 2.0.5.4 FLOW VERSION 2.0.5.2<br />
SUPPORTED CLIENT VERSIONS<br />
• Even with a correct dongle ID, Flow Control might have displayed the<br />
dongle ID as 0. This has been fixed.<br />
• If you selected a particular order for Flow Logger template items in the<br />
Metadata tab of Flow Control, the order might have reverted to<br />
alphabetical in the Logger itself. This has been fixed.<br />
• Template item lists in Flow Logger might have displayed the first item in<br />
the list rather than the item you selected. This has been fixed.<br />
• If you selected the Thumbnail display in the File Browser, clips might not<br />
have displayed. This has been fixed.<br />
• If a clip failed to scan during a Flow Scan job, the entire job might have<br />
failed to progress. This has been fixed.<br />
• After you restarted a server, Flow Scan might have failed to start. This has<br />
been fixed.<br />
• A sequence created from clips created outside of Flow might not have<br />
imported into <strong>Avid</strong> correctly. This has been fixed.<br />
Supported Client Versions<br />
This release supports several versions of client operating systems and editing<br />
applications. See the following sections:<br />
• "Client Operating Systems" on page 3<br />
• "Editing Applications" on page 4<br />
• "Considerations for Using DAVE" on page 4<br />
Client Operating Systems<br />
See your editing application documentation for information on operating<br />
systems supported for your application version. <strong>EditShare</strong> has qualified its<br />
software with the following operating systems:<br />
• Windows 7, Windows Vista, and Windows XP<br />
• Mac OS X:<br />
– Version 10.6.4 and earlier (Snow Leopard)<br />
NOTE: <strong>EditShare</strong> v6.0 and later includes support for mounting Managed<br />
and Unmanaged Media Spaces using AFP on OS X 10.6.x. Make sure all<br />
3
EDITSHARE README STORAGE VERSION 6.0.5.4 ARK VERSION 2.0.5.4 FLOW VERSION 2.0.5.2<br />
SUPPORTED CLIENT VERSIONS<br />
users of a given Media Space type mount it using only one protocol. For<br />
example, do not allow User A to mount a Managed Media Space using AFP<br />
and User B to mount a Managed Media Space using DAVE.<br />
– Version 10.5.x (Leopard) and 10.4 (Tiger)<br />
– For important information about DAVE compatibility with your<br />
operating system and editing application versions, see<br />
"Considerations for Using DAVE" on page 4.<br />
Editing Applications<br />
<strong>EditShare</strong> works with many client editing applications and versions. <strong>EditShare</strong><br />
has completed compatibility testing through the following versions:<br />
• <strong>Avid</strong> v5.0.3 (NewsCutter v9.0.3) and earlier, with the following proviso:<br />
– If you use an <strong>Avid</strong> system from v3.1.3/7.1.3 or later, all the <strong>Avid</strong><br />
systems that you share projects with need to be v3.1.3/7.1.3 or later.<br />
If you use an <strong>Avid</strong> system from v3.1.2 or earlier, all the <strong>Avid</strong> systems<br />
you share with need to be v3.1.2 and earlier.<br />
• Final Cut Pro v7.0.2 and earlier<br />
• Adobe Premiere Pro CS4 and earlier<br />
Considerations for Using DAVE<br />
DAVE 8.1 is the version <strong>EditShare</strong> recommends for all <strong>EditShare</strong> customers<br />
running Snow Leopard (10.6.x)<br />
All Snow Leopard Mac systems need to be running DAVE 8 for compatibility<br />
with the operating system, and DAVE 8.1 is the most stable DAVE 8 release<br />
available.<br />
DAVE 8.1 also supports Leopard (10.5.x) However, if you have Macs running<br />
Leopard, DAVE 7.1 continues to work and does not necessarily need to be<br />
upgraded to DAVE 8.1.<br />
You can download DAVE 8.1 from Thursby's web site at<br />
http://download.thursby.com/dave/dave81.dmg<br />
CAUTION: Until further notice, all other versions of DAVE besides 7.1 or 8.1 are no<br />
supported and do not work properly with <strong>EditShare</strong>.<br />
When you use DAVE v7.1 with <strong>Avid</strong>, you need to enable DAVE Workarounds.<br />
See “<strong>Avid</strong> Scan Issues” in the <strong>EditShare</strong> Version 6.0 Administrator’s Guide.<br />
4
EDITSHARE README STORAGE VERSION 6.0.5.4 ARK VERSION 2.0.5.4 FLOW VERSION 2.0.5.2<br />
CHANGES IN PREVIOUS VERSIONS<br />
NOTE: All users of <strong>Avid</strong> and non-<strong>Avid</strong> Project Spaces as well as all <strong>Avid</strong> Media Spaces<br />
must use DAVE for mounting.<br />
Changes in Previous Versions<br />
The following sections describe changes in previous version:<br />
• New in Flow Version 2.0.5<br />
• Upgrading from Version 5.5.23<br />
• Configuring Your System with the <strong>EditShare</strong> Role Assistant<br />
• Fixed in Version 6.0.5.3<br />
• Fixed in Version 6.0.5.1<br />
• Documentation Changes<br />
New in Flow Version 2.0.5<br />
The following features are new in Flow version 2.0.5:<br />
• Flow Ingest<br />
– Preview, scan, and ingest of QuickTime files with multiple audio<br />
tracks.<br />
– File ingest on more than one channel at the same time (only one<br />
ingest per channel).<br />
– File ingest that proceeds as fast as the network and the CPU can<br />
support.<br />
– Preview files in Windows XP.<br />
– Ingest and preview files larger than 2 GB.<br />
– Get clipname from device.<br />
• Flow Browse<br />
– An NLE tab and an Options tab that let you select several options.<br />
See "Selecting Flow Browse Options" on page 6.<br />
– Support for dragging and dropping clips into Lightworks. See the<br />
<strong>EditShare</strong> Lightworks User’s Guide.<br />
5
EDITSHARE README STORAGE VERSION 6.0.5.4 ARK VERSION 2.0.5.4 FLOW VERSION 2.0.5.2<br />
CHANGES IN PREVIOUS VERSIONS<br />
NOTE: At this time you cannot drag and drop subclips or sequences into<br />
Lightworks.<br />
– You can now work with <strong>Avid</strong> sequences that include more than two<br />
channels of audio and that have mixed audio channels.<br />
Selecting Flow Browse Options<br />
You can select several Flow Browse options. Do the following.<br />
TASK<br />
1. Click the Settings button.<br />
The Settings window opens to the Shortcuts tab (formerly named the<br />
Shortcut Editor).<br />
2. Click the NLE tab.<br />
6
EDITSHARE README STORAGE VERSION 6.0.5.4 ARK VERSION 2.0.5.4 FLOW VERSION 2.0.5.2<br />
CHANGES IN PREVIOUS VERSIONS<br />
3. Select the editing application you work with the most:<br />
• Lightworks<br />
• Media Composer (only MXF clips display)<br />
• Final Cut Pro (only MOV clips display)<br />
4. Click the Options tab.<br />
5. Select options as described in the following table.<br />
Option<br />
Start Full Screen<br />
Set anamorphic flag when<br />
dragging file to FCP<br />
Auto refresh searches<br />
Description<br />
Starts Flow Browse in full-screen mode the next time you<br />
open it.<br />
Lets you specify if SD material should be displayed in Final<br />
Cut Pro as widescreen by varying the pixel aspect ratio the<br />
clip displays at.<br />
Refreshes the search automatically at the interval you select.<br />
6. Click OK.<br />
Upgrading from Version 5.5.23<br />
This software update applies only to systems already running <strong>EditShare</strong> v6.0.0<br />
or later. <strong>EditShare</strong> also offers a paid upgrade path from v5.5.23 to Editshare 6,<br />
however, which includes a new <strong>EditShare</strong> operating system as well as many<br />
other features and improvements. Your data is preserved through the v5-to-v6<br />
update process.<br />
7
EDITSHARE README STORAGE VERSION 6.0.5.4 ARK VERSION 2.0.5.4 FLOW VERSION 2.0.5.2<br />
CHANGES IN PREVIOUS VERSIONS<br />
The upgrade procedure from a v5.5.23 system is described in the <strong>EditShare</strong><br />
Version 5.5.23 to Version 6 Upgrade Guide, which you receive when you<br />
purchase the upgrade. Contact your dealer or <strong>EditShare</strong> Sales for pricing and<br />
availability.<br />
For additional information about the v6.0.x release, see the following topics:<br />
• "Your Version 6.0.5.x System" on page 8<br />
• "New in Storage Version 6" on page 8<br />
• "New in Flow Version 2.0.4" on page 12<br />
• "New in Ark Version 2.0.5.0" on page 15<br />
• "Fixed in Version 6.0.5.0" on page 15<br />
Your Version 6.0.5.x System<br />
Consider the following about this release:<br />
• The <strong>EditShare</strong> Role Assistant includes the ESA Assistant and the Ark<br />
Assistant (if you purchased the Ark option). In most cases, you need to<br />
run the Role Assistant to make sure that your components are configured<br />
correctly. See "Configuring Your System with the <strong>EditShare</strong> Role<br />
Assistant" on page 15.<br />
• With the introduction of <strong>EditShare</strong> 6, the file format and extension has<br />
changed for dongle <strong>updates</strong> and downloaded offline <strong>updates</strong>. Update files<br />
now end in .es6, for example, ES6Update_101234_flowV2.es6. You<br />
cannot use a .es6 updater with a v5.5.x system, and you cannot use a .esu<br />
updater with a v6.0.x.x system.<br />
New in Storage Version 6<br />
<strong>EditShare</strong> v6 provides important advantages over the last major release,<br />
<strong>EditShare</strong> v5. A new, more powerful operating system has been implemented.<br />
The enhanced Linux OS provides a significant improvement in performance,<br />
resulting in higher stream counts. <strong>EditShare</strong> Manager services also start and<br />
restart faster than previously. The overall look of the application has also been<br />
updated for a unified appearance with other <strong>EditShare</strong> products, which includes<br />
most <strong>EditShare</strong> systems shipped in the last few years. Contact <strong>EditShare</strong> Sales to<br />
find out if your server can be upgraded.<br />
NOTE: Version 6 is supported only on 64-bit systems.<br />
8
EDITSHARE README STORAGE VERSION 6.0.5.4 ARK VERSION 2.0.5.4 FLOW VERSION 2.0.5.2<br />
CHANGES IN PREVIOUS VERSIONS<br />
In addition to the operating system and user interface changes, the following<br />
features are new in this version and are described in the <strong>EditShare</strong> Version 6.0<br />
Administrator’s Guide:<br />
• User groups. You can save time by organizing users into groups, and then<br />
adding and removing groups from Spaces rather than adding and<br />
removing individuals. See “Adding Users to Groups,” “Removing Users<br />
from Groups,” and “Removing Users or Groups from Media Spaces.”<br />
• <strong>Avid</strong>-style <strong>Sharing</strong>. <strong>EditShare</strong> now offers a second way to share <strong>Avid</strong><br />
media and projects if you are accustomed to working with <strong>Avid</strong> Unity and<br />
you want to continue to work in that way. This feature is currently enabled<br />
only for Windows systems. See"<strong>Avid</strong>-<strong>Style</strong> <strong>Sharing</strong>" on page 11 in this<br />
ReadMe and “<strong>Avid</strong>-<strong>Style</strong> Media Space.”<br />
• DPX optimization. This version provides multiple levels of optimizations<br />
for working with the DPX format, including the following:<br />
– Speeding up the creation and opening of long sequences of DPX<br />
files.<br />
– Laying down sequences of DPX files close to one another on<br />
<strong>EditShare</strong> storage volumes in real time, which prevents<br />
fragmentation and unnecessary disk seeks.<br />
– Allowing simultaneous writing and reading of 2K DPX files on the<br />
same 16-drive volume.<br />
See “Adjusting DPX Options.”<br />
• Renaming Media Spaces. If you make a mistake naming a Space or decide<br />
you want to change the name, it is now easy to change the name. See<br />
“Renaming Media Spaces.”<br />
• Changing a Managed Media Space to Unmanaged. This is useful when the<br />
permissions and ownership rules of Managed Spaces are too restrictive for<br />
a particular workflow. See “Converting Managed Media Spaces to<br />
Unmanaged.”<br />
• Changing the <strong>EditShare</strong> Administrator password in <strong>EditShare</strong> Manager.<br />
See “Changing Your Administrator Password.”<br />
• Status web page that gives you access to client installers, manuals, and<br />
server status. See “Viewing <strong>EditShare</strong> Status in a Web Browser.”<br />
• How you connect to the server remotely. You now use RealVNC on<br />
Windows and Mac to connect remotely. The installers are in your SMB<br />
File Exchange area. See “Preparing the Administrator’s Workstation.”<br />
NOTE: TightVNC and Chicken of the VNC are no longer supported.<br />
9
EDITSHARE README STORAGE VERSION 6.0.5.4 ARK VERSION 2.0.5.4 FLOW VERSION 2.0.5.2<br />
CHANGES IN PREVIOUS VERSIONS<br />
• Several optimizations for Windows Vista, Windows 7, and OS X that<br />
affect operation generally and can also particularly improve performance<br />
when you work with uncompressed HD. See “Setting up Editors<br />
Workstations.”<br />
• Enhanced support for OS X workstations that connect to <strong>EditShare</strong><br />
storage via Apple Filesharing Protocol (AFP). <strong>EditShare</strong> now includes a<br />
new version of Netatalk, the Linux/Unix service that allows OS X<br />
workstations to connect via AFP. Netatalk now offers full support for the<br />
extended attributes that are now part of OS X 10.6 filesystems, ensuring<br />
that OS X users do not encounter problems when connecting via AFP.<br />
• Automatic <strong>updates</strong>. Your <strong>EditShare</strong> server now delivers <strong>updates</strong> and<br />
reports when they are available, and queries whether you want to install<br />
them. See “<strong>EditShare</strong> Updates.”<br />
If your server is on the Internet, when you click Install Updates and there<br />
are <strong>updates</strong> available, a browser window opens with a version of the<br />
ReadMe for that update.<br />
NOTE: If you have systems that are not connected to the Internet, <strong>EditShare</strong> also<br />
offers two standalone offline updaters that you can download from<br />
<strong>updates</strong>.editshare.com. If your unconnected system is running Flow, download and<br />
run the version of the <strong>EditShare</strong> v6.0.5.0 updater that includes Flow. A different<br />
version not containing Flow packages is available for all other unconnected<br />
systems, which saves you time when you update.<br />
• Improvements to the Role Assistant and the ESA Assistant. See<br />
"Configuring Your System with the <strong>EditShare</strong> Role Assistant" on page 15<br />
in this ReadMe, “<strong>EditShare</strong> Updates,” and “Setting up Multiple Severs<br />
with ESA Assistant.”<br />
The following new features are described in the <strong>EditShare</strong> Version 6.0 Editor’s<br />
Guide:<br />
• You can now reset your login count in <strong>EditShare</strong> Connect. See “Resetting<br />
Your Login Count.”<br />
• The <strong>Avid</strong> Launcher has several UI changes and now allows you to choose<br />
to work with <strong>Avid</strong>-<strong>Style</strong> sharing or with <strong>Avid</strong> Unity. See “Method Two:<br />
<strong>Avid</strong> Launcher.”<br />
Also new is the way <strong>EditShare</strong> numbers its releases. See "Release Numbering and<br />
<strong>EditShare</strong> Connect Client Updates" on page 11.<br />
10
EDITSHARE README STORAGE VERSION 6.0.5.4 ARK VERSION 2.0.5.4 FLOW VERSION 2.0.5.2<br />
CHANGES IN PREVIOUS VERSIONS<br />
<strong>Avid</strong>-<strong>Style</strong> <strong>Sharing</strong><br />
While <strong>EditShare</strong> pioneered the first non-<strong>Avid</strong> system for sharing bins,<br />
sequences and media, we now offer a second way for collaborating with these<br />
assets. Called <strong>Avid</strong>-<strong>Style</strong> <strong>Sharing</strong>, the new system provides bin-locking and<br />
media sharing that works the same way it does with <strong>Avid</strong>'s Unity storage.<br />
Each approach has its advantages. For example, the original <strong>EditShare</strong> way of<br />
sharing bins via User folders is probably much more secure for schools and big<br />
organizations where editors want some guarantee that their bins and sequences<br />
cannot be modified by others. Similarly, deleting files and rebuilding media<br />
databases is both safer and easier with <strong>EditShare</strong>'s <strong>Avid</strong> MXF spaces.<br />
However, for <strong>Avid</strong> editors who are accustomed to the way Unity works, now<br />
there is no need to learn a new way of doing things. With <strong>EditShare</strong>'s <strong>Avid</strong>-<strong>Style</strong><br />
<strong>Sharing</strong>, you get both <strong>Avid</strong>-<strong>Style</strong> bin-locking and the <strong>Avid</strong> way of associating<br />
media files with the workstation that created them. In addition, with <strong>Avid</strong>-<strong>Style</strong><br />
Spaces, you get a small performance boost on Windows workstations that can<br />
be important when ingesting or outputting sequences with six or more audio<br />
tracks.<br />
Release Numbering and <strong>EditShare</strong> Connect Client Updates<br />
With this release, <strong>EditShare</strong> is implementing a new release-numbering scheme<br />
that might save you time and effort.<br />
If your facility has a large number of client workstations, it can be<br />
time-consuming to update client software. <strong>EditShare</strong> occasionally releases new<br />
storage software that includes new features and fixes to prior limitations, but<br />
that does not require a new version of <strong>EditShare</strong> Connect. In this case, you do<br />
not need to spend the time to unnecessarily update the client software.<br />
<strong>EditShare</strong> releases now have an additional number slot, for a total of 4. For<br />
example, the current release is numbered 6.0.5.0, rather than 6.0.5. The way to<br />
tell if you need an <strong>EditShare</strong> Connect update is as follows:<br />
• Storage versions that do not require updating <strong>EditShare</strong> Connect clients<br />
include a change only in the final number slot.<br />
For example, in the future, if you were running 6.0.6.3 and a v6.0.6.4<br />
release became available, you would not need to update your <strong>EditShare</strong><br />
Connect client software.<br />
11
EDITSHARE README STORAGE VERSION 6.0.5.4 ARK VERSION 2.0.5.4 FLOW VERSION 2.0.5.2<br />
CHANGES IN PREVIOUS VERSIONS<br />
• Storage versions that require updating <strong>EditShare</strong> Connect clients include<br />
a change in the third number slot.<br />
For example, in the future, if you were running 6.0.6.3 and a v6.0.7.0<br />
release became available, you would need to update your <strong>EditShare</strong><br />
Connect client software.<br />
New in Flow Version 2.0.4<br />
The following features are new in this version and are described in the <strong>EditShare</strong><br />
Flow Version 2.0 Setup and User’s Guide:<br />
• Ark-Flow integration. See "About Ark-Flow Integration" on page 13 and<br />
“Using <strong>EditShare</strong> Ark with Flow” (also see the <strong>EditShare</strong> Ark Version 2.0<br />
Setup and User’s Guide).<br />
• Edit While Capture. The ability to edit material that is still being captured.<br />
See "About Edit While Capture" on page 13 and “Ingesting with Edit<br />
While Capture.”<br />
• File-based ingest support. The ability to ingest XDCAM and P2 clips<br />
directly from a workstation running Flow Browse. The ability to keep clips<br />
in their native codec or transcode to other resolutions without any<br />
reencoding, called Rewrapping. See "About File-Based Ingest" on page 14<br />
and “Ingesting from Files,” as well as “Improvements in Flow Control” in<br />
this list.<br />
• Sequence drag-and-drop. The ability to select a sequence icon and drag<br />
the entire sequence into an editing application without having to select all<br />
the clips in the sequence. See “Working with Sequences.”<br />
• Ganged capture. The ability to start and stop ingest of multiple sources<br />
simultaneously, using the same codec and metadata settings from each<br />
channel in the group. You select the codec and destination only once, and<br />
the metadata stays the same for each channel, except that the clip name<br />
gets appended with chl1 chl2, and so on. See “Ingesting Material.”<br />
• Captures View. Shows you a tree view in the File browser of the<br />
components of a capture. See “Viewing Media Space Contents and Search<br />
Results.”<br />
• Clip status. Shows you status such as Online or Offline, Capturing,<br />
Archived, and so on. See “Viewing Clip Status.”<br />
• Capture status. Clips in process of being captured appear in the File<br />
browser with a red border and a file size of “Recording.” Clips lists are<br />
automatically refreshed during a capture.<br />
12
EDITSHARE README STORAGE VERSION 6.0.5.4 ARK VERSION 2.0.5.4 FLOW VERSION 2.0.5.2<br />
CHANGES IN PREVIOUS VERSIONS<br />
• Schedule repeat. The ability to schedule the repeat of a scheduled job. See<br />
“Creating an Ingest Schedule.”<br />
• Search improvements. You can search by creation date, and the search<br />
includes deleted and archived files.<br />
• Improvements in Flow Control, including the following:<br />
– Informational field in the Users tab, and the ability to assign<br />
permissions for reading and writing metadata and restoring<br />
from Ark<br />
– Status information in the Networks tab<br />
– Ability to control the ingest rate for file ingest, so your facility is not<br />
overwhelmed by numerous ingests at the same time<br />
– Ability to specify a Scan server’s IP address in Manual mode<br />
– Ability to control proxy creation during scanning<br />
• Flow client software now available from the status web page. See “Viewing<br />
<strong>EditShare</strong> Status in a Web Browser” in the <strong>EditShare</strong><br />
Administrator’s Guide.<br />
About Ark-Flow Integration<br />
If you have Flow and Ark systems at your facility, you can now configure these<br />
two products to be used together seamlessly. For each clip you back up or<br />
archive onto an Ark Tape or Ark Disk device, Flow keeps a record in its database<br />
indicating the clip has been archived. Flow also makes sure the clip has a<br />
corresponding proxy file that you can later search for or play in Flow Browse.<br />
At any time after you have deleted high-resolution clips from your <strong>EditShare</strong><br />
storage, you can use Flow Browse to find the clips you want to restore. Flow<br />
retrieves the media files you selected from Ark and restores them to an<br />
<strong>EditShare</strong> Media Space. You can then use them for editing. You can tell Ark<br />
which clips you want to restore, where you want to restore them to, and when<br />
you want to run the restore job.<br />
About Edit While Capture<br />
In addition to chunking, the Edit While Capture feature provides a second way<br />
to start editing video material while you are still capturing it.<br />
With Edit While Capture, you can specify a longer duration of time – for<br />
example, 1 hour or 2 hours – and within a few seconds of when you begin<br />
recording, you can drag the clip into your editing application and begin working<br />
13
EDITSHARE README STORAGE VERSION 6.0.5.4 ARK VERSION 2.0.5.4 FLOW VERSION 2.0.5.2<br />
CHANGES IN PREVIOUS VERSIONS<br />
with it. When viewed in your editing application, the clip appears to have<br />
whatever duration you set. When you scroll into the part of the clip that has not<br />
yet been recorded, instead of seeing a video image, you see a slate that says<br />
“Media Not Yet Recorded.” Over time, the unrecorded part of the clip is<br />
replaced by real video and audio data.<br />
With Edit While Capture, you don't need to have multiple clips to begin editing<br />
the material you have just captured. If your event goes past the time limit you<br />
specified, a new Edit While Capture clip is automatically created that is seamless<br />
with the previous clip – so you don't miss even a split second of the event you<br />
are recording. You do not need to manually start a new capture.<br />
Another unique aspect of Flow's Edit While Capture feature is that it allows you<br />
to create “Universal Edit While Capture” clips. That is, if you are capturing in a<br />
codec that is common to both <strong>Avid</strong> and QuickTime – for example, DV 50 or<br />
DVCPro HD – the video and audio data needs to be only stored once on your<br />
<strong>EditShare</strong> Server. <strong>Avid</strong> sees the Edit While Capture clips as native <strong>Avid</strong> MXF<br />
files and Final Cut Pro sees the same clips as native QuickTime files.<br />
About File-Based Ingest<br />
Flow supports ingest of file-based media from XDCAM-EX cards, P2 cards, and<br />
even from virtual XCDAM-EX and P2 directories located on USB, FireWire, or<br />
local storage devices. If you connect an XDCAM-EX or P2 device to an Express<br />
card or PC-card slot to a workstation running Flow Browse, you can browse the<br />
contents of that card or disk in the File browser Device tab.<br />
NOTE: If your media is stored on Sony XDCAM-EX cards or Panasonic P2 cards, you<br />
must install the appropriate drivers so your workstation recognizes the cards.<br />
Flow offers a number of ways to ingest your file-based media. One option is to<br />
rewrap the clips, which keeps them in their native codec without any<br />
reencoding. For example, if you want to ingest <strong>Avid</strong> files, you select the <strong>Avid</strong><br />
Rewrap codec, and if you want to ingest QuickTime files for Final Cut Pro, you<br />
select the FCP Rewrap codec. In either case, the files are not reencoded even if<br />
the file extension (wrapper) changes. You can also choose to transcode your<br />
file-based media to many other <strong>Avid</strong> and FCP codecs.<br />
Unlike when you ingest from videotapes, which generally run in real time,<br />
file-based ingest has the potential to transfer data as fast as it can come off the<br />
device. To prevent file-based ingest activities from overwhelming the network<br />
or storage system, Flow allows administrators to limit the bandwidth available<br />
to file-based ingest activities. This limit does not apply to real-time SDI video<br />
ingest activities. The bandwidth is shared equally among all workstations that<br />
are currently doing file-based ingest.<br />
14
EDITSHARE README STORAGE VERSION 6.0.5.4 ARK VERSION 2.0.5.4 FLOW VERSION 2.0.5.2<br />
CHANGES IN PREVIOUS VERSIONS<br />
New in Ark Version 2.0.5.0<br />
The following features and changes are new in this version and are described in<br />
the <strong>EditShare</strong> Ark Version 2.0 Setup and User’s Guide:<br />
• Ark v2 is supported in the <strong>EditShare</strong> version 6 operating system. The<br />
<strong>EditShare</strong> v6.0.5.0 <strong>updates</strong> includes an update to Ark v2.0.5.0.<br />
• Ark now supports integration with Flow. See "About Ark-Flow<br />
Integration" on page 13 and “Using <strong>EditShare</strong> Ark with Flow” in the<br />
<strong>EditShare</strong> Flow Version 2.0 Setup and User’s Guide.<br />
• Individual file restore (requires Flow). See “Restoring Individual Files.”<br />
• Backup of Universal Media Spaces. See “Adding a Backup Job.”<br />
• You are now notified if you are trying to restore items from a tape that is<br />
not in the autoloader.<br />
Fixed in Version 6.0.5.0<br />
The following limitations were fixed:<br />
• Previous versions might have sent spurious e-mails to the <strong>EditShare</strong><br />
Administrator email account. This has been fixed.<br />
• Remote help might have failed to connect if you initiated it from a local<br />
VGA connection instead of from VNC. This has been fixed.<br />
• RAIDs might not have mounted after a cold boot. This has been fixed.<br />
• You might have seen screen artifacts the first time you started the Ark<br />
application. This has been fixed.<br />
• Several selection options might have been difficult to distinguish in the<br />
v6.0 user interface. This has been fixed.<br />
• You might have experienced connectivity problems with Switch mode in<br />
the IP Configurator. This has been fixed.<br />
• You might have had trouble emptying the trash in Managed, Unmanaged<br />
or <strong>Avid</strong> <strong>Style</strong> Media Spaces. This has been fixed.<br />
Configuring Your System with the <strong>EditShare</strong> Role Assistant<br />
The <strong>EditShare</strong> Role Assistant makes sure your system is configured correctly. In<br />
general, you must run the Role Assistant as part of a first-time setup. The only<br />
15
EDITSHARE README STORAGE VERSION 6.0.5.4 ARK VERSION 2.0.5.4 FLOW VERSION 2.0.5.2<br />
CHANGES IN PREVIOUS VERSIONS<br />
exception is if you have a standalone <strong>EditShare</strong> server with no ESA groups and<br />
no Flow or Ark applications.<br />
As of v6, if you want to configure an ESA group, you run the ESA Assistant from<br />
the Role Assistant, and if you want to configure an Ark system, you can run the<br />
Ark Assistant from the Role Assistant or from the Control Panel.<br />
If you add Flow roles to a server using the Role Assistant, required Flow<br />
packages are downloaded automatically if you have Internet access on that<br />
server. If you don’t, you need to download the offline updater with Flow and<br />
install it on the server, and then rerun the Role Assistant to add the appropriate<br />
Flow roles.<br />
If you were already running Flow under version 6.0.x, you must reboot and then<br />
reboot again after the Role Assistant completes. If you do not run the Role<br />
Assistant after updating, you might not get the Flow clients installed in the<br />
correct place on the ESA master.<br />
For additional details abut setting up your system, see “Using the <strong>EditShare</strong> Role<br />
Assistant” in the <strong>EditShare</strong> Version 6.0 Administrator’s Guide.<br />
Fixed in Version 6.0.5.3<br />
The following limitations have been fixed:<br />
• If you have Ark at your site, your <strong>EditShare</strong> Storage system might have<br />
become unresponsive because too many Ark log notifications were being<br />
retained. This has been fixed.<br />
• After updating to v6.0.5.1, you might not have been able to connect to AFP<br />
shares. This has been fixed.<br />
Fixed in Version 6.0.5.1<br />
The following limitations have been fixed:<br />
• With <strong>Avid</strong>-<strong>Style</strong> sharing, if you opened an <strong>Avid</strong> bin that held content, the<br />
bin might have appeared empty. This has been fixed.<br />
• <strong>EditShare</strong> now supports <strong>Avid</strong> Pro Tools on Windows systems without<br />
iSCSI.<br />
• You might have had trouble updating your email preferences. This has<br />
been fixed.<br />
16
EDITSHARE README STORAGE VERSION 6.0.5.4 ARK VERSION 2.0.5.4 FLOW VERSION 2.0.5.2<br />
LIMITATIONS<br />
• You might have had problems importing jpeg files into an <strong>Avid</strong> editing<br />
application and then creating media on an <strong>EditShare</strong> Media Space. This<br />
has been fixed.<br />
• An unallocated tape is now removed from the Available list in Ark if the<br />
tape is not in the autoloader.<br />
• You might not have been able to write to your SMB File Exchange area.<br />
This has been fixed.<br />
• You might have been receiving spurious “has not completed a verification<br />
in more than 7 days” messages about your RAID controllers. You are now<br />
correctly notified of verifications.<br />
• You might not have been receiving email status messages from your<br />
expansion server. This has been fixed.<br />
Documentation Changes<br />
The <strong>EditShare</strong> Administrator’s Guide and the <strong>EditShare</strong> Editor’s Guide were<br />
updated for v6.0. The <strong>EditShare</strong> Ark Setup and User’s Guide and the Ark Help<br />
were updated for v2, and the <strong>EditShare</strong> Flow Setup and User’s Guide was<br />
updated for v2.0.<br />
Limitations<br />
You might experience the following limitations in this version:<br />
• "General Limitations" on page 17<br />
• "Flow Limitations" on page 19<br />
• "Ark Limitations" on page 19<br />
General Limitations<br />
• If you configured the <strong>Avid</strong> Launcher in <strong>EditShare</strong> Connect, before you<br />
upgrade your <strong>Avid</strong> software, you must remove your <strong>Avid</strong> application<br />
from the <strong>EditShare</strong> Connect <strong>Avid</strong> Management tab by selecting it and<br />
then clicking the Remove <strong>Avid</strong> Application button.<br />
17
EDITSHARE README STORAGE VERSION 6.0.5.4 ARK VERSION 2.0.5.4 FLOW VERSION 2.0.5.2<br />
LIMITATIONS<br />
• If you use AFP on OS X 10.6.x, and you capture clips that exceed 2 GB in<br />
size with DV25, DV50, or DVCPro HD codecs, you might lose tape name<br />
and timecode information.<br />
Workaround: Use DAVE if you plan to capture large clips with DV25,<br />
DV50, or DVCPro HD codecs. All other codecs are unaffected by this<br />
issue and should be safe for you to use to capture and edit with AFP.<br />
• When you connect to the RAID Manager on a remote server, you might<br />
see a This Connection is Untrusted message box. This does not indicate an<br />
actual error.<br />
Workaround: Click the “I Understand the Risks” button and then click<br />
the “Add Exception” button. An Add Security Exception dialog box<br />
opens. Click the “Confirm Security Exception” button.<br />
• If you start your <strong>Avid</strong> application by double-clicking the desktop icon,<br />
then look at a bin from an <strong>Avid</strong>-<strong>Style</strong> Media Space, you might not see the<br />
locking icons that indicate that <strong>Avid</strong>-<strong>Style</strong> sharing is working.<br />
Workaround: Close the <strong>Avid</strong> application, and click the Launch <strong>Avid</strong><br />
Application button in <strong>EditShare</strong> Connect to restart the <strong>Avid</strong> application.<br />
• If you try to use the <strong>Avid</strong> Launcher from <strong>EditShare</strong> Connect on a<br />
Windows Vista 32-bit system, the <strong>Avid</strong> editing application might not start<br />
successfully.<br />
• Each workstation that connects to your <strong>EditShare</strong> server must have a<br />
unique name. <strong>EditShare</strong> recommends that the boot drive on each<br />
workstation also have a unique name. See “Naming Workstations” and<br />
“Naming Boot Drives” in the <strong>EditShare</strong> Administrator’s Guide.<br />
• If you create a user on an <strong>EditShare</strong> server and then add that server to an<br />
ESA group as an expansion server, the user is not available in the new ESA<br />
group.<br />
Workaround: Create the ESA group before you create users on any of the<br />
intended expansion servers.<br />
• You cannot use Traditional Media Spaces under AFP in this version at this<br />
time.<br />
• In <strong>Avid</strong> MXF and Universal Media Spaces with many users, if you try to<br />
assign all users read-only status at once, you might experience<br />
system slowdown.<br />
• You might experience difficulty if you try to add users with names longer<br />
than 16 characters.<br />
Workaround: Restrict usernames to 16 characters or fewer.<br />
18
EDITSHARE README STORAGE VERSION 6.0.5.4 ARK VERSION 2.0.5.4 FLOW VERSION 2.0.5.2<br />
LIMITATIONS<br />
• In the <strong>EditShare</strong> Connect Project browser on a Mac, if you have a Finder<br />
window open while you are moving bins or folders or refreshing the<br />
browser, you might hear the Mac system noise for deleting a folder even<br />
though you aren’t deleting one. This is because <strong>EditShare</strong> is creating and<br />
then deleting a folder to refresh the Finder. You can ignore the noise.<br />
• AFP is not supported in this version of <strong>EditShare</strong> Connect on Macintosh<br />
OS X version 10.4.x.<br />
NOTE: You can use AFP on OS X v10.4.x if you are running <strong>EditShare</strong> v5.1<br />
and earlier.<br />
Flow Limitations<br />
• For file-based ingest, if you select one of the rewrap codecs (<strong>Avid</strong>wrap or<br />
FCPwrap), and then ingest only part of a file from an XDCAM-EX card,<br />
the first two frames might be corrupted. For example, if you trim the IN<br />
point on a clip (that is, if you don't start a file-ingest on the first frame of<br />
video from the original clip), the beginning of the resulting clip that gets<br />
transferred to the <strong>EditShare</strong> Storage Server is slightly corrupted with some<br />
blockiness in the first two frames. To compensate, Flow takes a few extra<br />
frames to ensure that the first frame you actually wanted to ingest is good.<br />
The two blocky frames come from just slightly outside the place where you<br />
marked the IN point.<br />
Workaround: When you are editing, do not include the blocky frames in<br />
your sequence.<br />
Ark Limitations<br />
• CAUTION: In Ark Assistant, select First-time Setup only for configuring new<br />
Ark systems. First-time Setup removes all backed-up files.<br />
• Ark activation is not supported in version 6.0.5.3.<br />
• In the Ark Assistant Configuration area, you might not see a server you<br />
want to select.<br />
Workaround: In the list of servers, select the option, and then<br />
type the IP address of the server you want.<br />
19
EDITSHARE README STORAGE VERSION 6.0.5.4 ARK VERSION 2.0.5.4 FLOW VERSION 2.0.5.2<br />
TECHNICAL SUPPORT INFORMATION<br />
• In an Ark backup job, if you create an item including a Media Space from<br />
a Master server and another Media Space from an expansion chassis, the<br />
backup does not run and an error message appears in the Log window.<br />
Workaround: Make sure all Media Spaces in a single backup item are<br />
from the same server. Create a separate item for Media Spaces you want to<br />
back up from an expansion chassis.<br />
• For Ark Tape, only Media Space users included in the most recent backup<br />
are included in the Restore.<br />
For Ark Disk, all users who have been part of a Media Space during any<br />
previous backup are included in the restore, even if they have now been<br />
removed from the Media Space or from <strong>EditShare</strong> Manager. Users added<br />
to a Media Space after the most recent backup job has run are not included<br />
in the restore, however.<br />
Technical Support Information<br />
For assistance beyond this ReadMe and that provided in your <strong>EditShare</strong><br />
documentation, contact <strong>EditShare</strong> Technical Support at<br />
support@editshare.com.<br />
You can also call one of the following telephone numbers:<br />
• <strong>EditShare</strong> Americas: 617-782-0479<br />
• <strong>EditShare</strong> Europe, Middle East & Africa:44 (0) 20 7183 2255<br />
• <strong>EditShare</strong> Asia-Pacific: 61 7 3112 5220<br />
<strong>EditShare</strong> strongly recommends that you purchase a support agreement; if you<br />
do not have a support agreement, a per-incident rate is available for problems<br />
not covered by warranty.<br />
Copyright and Disclaimer<br />
Copyright © 2010 by <strong>EditShare</strong><br />
This manual, as well as any software described in it, is furnished under either a<br />
license or a confidentiality agreement, is confidential to <strong>EditShare</strong>, and may be<br />
used or copied only in accordance with the above mentioned agreements. The<br />
information in this manual is furnished for your use only and is subject to<br />
20
EDITSHARE README STORAGE VERSION 6.0.5.4 ARK VERSION 2.0.5.4 FLOW VERSION 2.0.5.2<br />
COPYRIGHT AND DISCLAIMER<br />
change without notice. <strong>EditShare</strong> assumes no responsibility or liability for any<br />
errors or inaccuracies that might appear in this manual.<br />
This Documentation is the property of <strong>EditShare</strong> and is provided in accordance<br />
with an <strong>EditShare</strong> license agreement. Copying, modifying, or distributing this<br />
Documentation in violation of the license agreement, United States Copyright<br />
Laws, or the Copyright Laws of any applicable foreign jurisdiction is<br />
expressly prohibited.<br />
<strong>EditShare</strong> is a registered trademark of <strong>EditShare</strong> in the United States and other<br />
countries.<br />
<strong>Avid</strong> is a registered trademark of <strong>Avid</strong> Technology, Inc. DAVE is a registered<br />
trademark of Thursby <strong>Software</strong> Systems, Inc. Final Cut Pro, Leopard,<br />
Macintosh, and Macintosh OS are registered trademarks of Apple, Inc. in the<br />
United States and other countries. Premiere is a registered trademark of Adobe,<br />
Inc. Windows is a registered trademark of Microsoft Corporation in the United<br />
States and other countries. All other brand and product names are trademarks<br />
or registered trademarks of their respective companies and are hereby<br />
acknowledged.<br />
Notice: To the best of our knowledge, the information in this document is<br />
accurate; however, <strong>EditShare</strong> assumes no responsibility or liability for the<br />
accuracy or completeness of this information. Mention of trade names or<br />
commercial products does not constitute endorsement by <strong>EditShare</strong> except<br />
where explicitly stated.<br />
<strong>EditShare</strong>, 119 Braintree Street, Suite 705, Boston, MA 02134<br />
Tel: 617-782-0479 Fax: 617-782-1071 http://www.editshare.com<br />
Part #: ESRM-V6_0_5_4.<br />
December 9, 2010<br />
21
EDITSHARE README STORAGE VERSION 6.0.5.4 ARK VERSION 2.0.5.4 FLOW VERSION 2.0.5.2<br />
COPYRIGHT AND DISCLAIMER<br />
22