EditShare Avid-Style Sharing - Software updates

EditShare ReadMe 

Storage Version 6.0.5.4 

Ark Version 2.0.5.4 

Flow Version 2.0.5.2 

December 9, 2010 

Always check updates.editshare.com for the latest version of this ReadMe. 

This version of EditShare provides support for EditShare Geevs, includes a new 

Flow release, and fixes several limitations. It is for EditShare systems already 

running earlier versions of 6.0.x. 

If you are already running a version of EditShare v6.x, see the following sections: 

• New in this Version 

• Fixed in this Version 

If you are upgrading from a v5.5.23 system, see the following section: 

• Upgrading from Version 5.5.23 

Also see the following sections: 

• Supported Client Versions 

• Changes in Previous Versions 

• Limitations 

• Technical Support Information 

NOTE: If you purchased the EditShare Ark option or if it was included with your XStream 

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 

NEW IN THIS VERSION 

the EditShare Flow option or if it was included with your XStream server, the software 

update for Flow v2.0.5.2 is included with this update. 

New in this Version 

This version includes the following: 

• Initial support for EditShare Geevs version 5.0. You can now add Geevs to 

your system through the EditShare Role Assistant. 

• EditShare Flow version 2.0.5.2. See "Flow Version 2.0.5.2" on page 2. 

Flow Version 2.0.5.2 

Flow v2.0.5.2 includes the following new features: 

• You can now change the size of the thumbnail display in Flow Logger by 

pressing Ctrl and the plus-sign key (+) or Ctrl and the minus-sign key (-). 

• You can now view clips by dragging them into the Preview window. 

Fixed in this Version 

The following EditShare limitations have been fixed: 

• If your EditShare Storage system included a large number of Media 

Spaces, you might not have been able to add new Media Spaces or add 

users to Media Spaces. This has been fixed. 

• Users of Avid-Style Media Spaces might have experienced occasional 

issues with reading bins and Avid media database PMR files. This has been 

fixed. 

• Users of Avid-Style Media Spaces running Avid on Windows 7 might 

have experienced long delays when beginning video capture. This has 

been fixed. 

• You might have experienced timecode breaks during periods of high CPU 

use or multiple simultaneous captures. This has been fixed. 

• You might not have been able to change the proxy format from the 

default. This has been fixed. 

2


SUPPORTED CLIENT VERSIONS 

• Even with a correct dongle ID, Flow Control might have displayed the 

dongle ID as 0. This has been fixed. 

• If you selected a particular order for Flow Logger template items in the 

Metadata tab of Flow Control, the order might have reverted to 

alphabetical in the Logger itself. This has been fixed. 

• Template item lists in Flow Logger might have displayed the first item in 

the list rather than the item you selected. This has been fixed. 

• If you selected the Thumbnail display in the File Browser, clips might not 

have displayed. This has been fixed. 

• If a clip failed to scan during a Flow Scan job, the entire job might have 

failed to progress. This has been fixed. 

• After you restarted a server, Flow Scan might have failed to start. This has 

been fixed. 

• A sequence created from clips created outside of Flow might not have 

imported into Avid correctly. This has been fixed. 

Supported Client Versions 

This release supports several versions of client operating systems and editing 

applications. See the following sections: 

• "Client Operating Systems" on page 3 

• "Editing Applications" on page 4 

• "Considerations for Using DAVE" on page 4 

Client Operating Systems 

See your editing application documentation for information on operating 

systems supported for your application version. EditShare has qualified its 

software with the following operating systems: 

• Windows 7, Windows Vista, and Windows XP 

• Mac OS X: 

– Version 10.6.4 and earlier (Snow Leopard) 

NOTE: EditShare v6.0 and later includes support for mounting Managed 

and Unmanaged Media Spaces using AFP on OS X 10.6.x. Make sure all 

3


SUPPORTED CLIENT VERSIONS 

users of a given Media Space type mount it using only one protocol. For 

example, do not allow User A to mount a Managed Media Space using AFP 

and User B to mount a Managed Media Space using DAVE. 

– Version 10.5.x (Leopard) and 10.4 (Tiger) 

– For important information about DAVE compatibility with your 

operating system and editing application versions, see 

"Considerations for Using DAVE" on page 4. 

Editing Applications 

EditShare works with many client editing applications and versions. EditShare 

has completed compatibility testing through the following versions: 

• Avid v5.0.3 (NewsCutter v9.0.3) and earlier, with the following proviso: 

– If you use an Avid system from v3.1.3/7.1.3 or later, all the Avid 

systems that you share projects with need to be v3.1.3/7.1.3 or later. 

If you use an Avid system from v3.1.2 or earlier, all the Avid systems 

you share with need to be v3.1.2 and earlier. 

• Final Cut Pro v7.0.2 and earlier 

• Adobe Premiere Pro CS4 and earlier 

Considerations for Using DAVE 

DAVE 8.1 is the version EditShare recommends for all EditShare customers 

running Snow Leopard (10.6.x) 

All Snow Leopard Mac systems need to be running DAVE 8 for compatibility 

with the operating system, and DAVE 8.1 is the most stable DAVE 8 release 

available. 

DAVE 8.1 also supports Leopard (10.5.x) However, if you have Macs running 

Leopard, DAVE 7.1 continues to work and does not necessarily need to be 

upgraded to DAVE 8.1. 

You can download DAVE 8.1 from Thursby's web site at 

http://download.thursby.com/dave/dave81.dmg 

CAUTION: Until further notice, all other versions of DAVE besides 7.1 or 8.1 are no 

supported and do not work properly with EditShare. 

When you use DAVE v7.1 with Avid, you need to enable DAVE Workarounds. 

See “Avid Scan Issues” in the EditShare Version 6.0 Administrator’s Guide. 

4


CHANGES IN PREVIOUS VERSIONS 

NOTE: All users of Avid and non-Avid Project Spaces as well as all Avid Media Spaces 

must use DAVE for mounting. 

Changes in Previous Versions 

The following sections describe changes in previous version: 

• New in Flow Version 2.0.5 

• Upgrading from Version 5.5.23 

• Configuring Your System with the EditShare Role Assistant 

• Fixed in Version 6.0.5.3 

• Fixed in Version 6.0.5.1 

• Documentation Changes 

New in Flow Version 2.0.5 

The following features are new in Flow version 2.0.5: 

• Flow Ingest 

– Preview, scan, and ingest of QuickTime files with multiple audio 

tracks. 

– File ingest on more than one channel at the same time (only one 

ingest per channel). 

– File ingest that proceeds as fast as the network and the CPU can 

support. 

– Preview files in Windows XP. 

– Ingest and preview files larger than 2 GB. 

– Get clipname from device. 

• Flow Browse 

– An NLE tab and an Options tab that let you select several options. 

See "Selecting Flow Browse Options" on page 6. 

– Support for dragging and dropping clips into Lightworks. See the 

EditShare Lightworks User’s Guide. 

5



NOTE: At this time you cannot drag and drop subclips or sequences into 

Lightworks. 

– You can now work with Avid sequences that include more than two 

channels of audio and that have mixed audio channels. 

Selecting Flow Browse Options 

You can select several Flow Browse options. Do the following. 

TASK 

1. Click the Settings button. 

The Settings window opens to the Shortcuts tab (formerly named the 

Shortcut Editor). 

2. Click the NLE tab. 

6



3. Select the editing application you work with the most: 

• Lightworks 

• Media Composer (only MXF clips display) 

• Final Cut Pro (only MOV clips display) 

4. Click the Options tab. 

5. Select options as described in the following table. 

Option 

Start Full Screen 

Set anamorphic flag when 

dragging file to FCP 

Auto refresh searches 

Description 

Starts Flow Browse in full-screen mode the next time you 

open it. 

Lets you specify if SD material should be displayed in Final 

Cut Pro as widescreen by varying the pixel aspect ratio the 

clip displays at. 

Refreshes the search automatically at the interval you select. 

6. Click OK. 

Upgrading from Version 5.5.23 

This software update applies only to systems already running EditShare v6.0.0 

or later. EditShare also offers a paid upgrade path from v5.5.23 to Editshare 6, 

however, which includes a new EditShare operating system as well as many 

other features and improvements. Your data is preserved through the v5-to-v6 

update process. 

7



The upgrade procedure from a v5.5.23 system is described in the EditShare 

Version 5.5.23 to Version 6 Upgrade Guide, which you receive when you 

purchase the upgrade. Contact your dealer or EditShare Sales for pricing and 

availability. 

For additional information about the v6.0.x release, see the following topics: 

• "Your Version 6.0.5.x System" on page 8 

• "New in Storage Version 6" on page 8 

• "New in Flow Version 2.0.4" on page 12 

• "New in Ark Version 2.0.5.0" on page 15 

• "Fixed in Version 6.0.5.0" on page 15 

Your Version 6.0.5.x System 

Consider the following about this release: 

• The EditShare Role Assistant includes the ESA Assistant and the Ark 

Assistant (if you purchased the Ark option). In most cases, you need to 

run the Role Assistant to make sure that your components are configured 

correctly. See "Configuring Your System with the EditShare Role 

Assistant" on page 15. 

• With the introduction of EditShare 6, the file format and extension has 

changed for dongle updates and downloaded offline updates. Update files 

now end in .es6, for example, ES6Update_101234_flowV2.es6. You 

cannot use a .es6 updater with a v5.5.x system, and you cannot use a .esu 

updater with a v6.0.x.x system. 

New in Storage Version 6 

EditShare v6 provides important advantages over the last major release, 

EditShare v5. A new, more powerful operating system has been implemented. 

The enhanced Linux OS provides a significant improvement in performance, 

resulting in higher stream counts. EditShare Manager services also start and 

restart faster than previously. The overall look of the application has also been 

updated for a unified appearance with other EditShare products, which includes 

most EditShare systems shipped in the last few years. Contact EditShare Sales to 

find out if your server can be upgraded. 

NOTE: Version 6 is supported only on 64-bit systems. 

8



In addition to the operating system and user interface changes, the following 

features are new in this version and are described in the EditShare Version 6.0 

Administrator’s Guide: 

• User groups. You can save time by organizing users into groups, and then 

adding and removing groups from Spaces rather than adding and 

removing individuals. See “Adding Users to Groups,” “Removing Users 

from Groups,” and “Removing Users or Groups from Media Spaces.” 

• Avid-style Sharing. EditShare now offers a second way to share Avid 

media and projects if you are accustomed to working with Avid Unity and 

you want to continue to work in that way. This feature is currently enabled 

only for Windows systems. See"Avid-Style Sharing" on page 11 in this 

ReadMe and “Avid-Style Media Space.” 

• DPX optimization. This version provides multiple levels of optimizations 

for working with the DPX format, including the following: 

– Speeding up the creation and opening of long sequences of DPX 

files. 

– Laying down sequences of DPX files close to one another on 

EditShare storage volumes in real time, which prevents 

fragmentation and unnecessary disk seeks. 

– Allowing simultaneous writing and reading of 2K DPX files on the 

same 16-drive volume. 

See “Adjusting DPX Options.” 

• Renaming Media Spaces. If you make a mistake naming a Space or decide 

you want to change the name, it is now easy to change the name. See 

“Renaming Media Spaces.” 

• Changing a Managed Media Space to Unmanaged. This is useful when the 

permissions and ownership rules of Managed Spaces are too restrictive for 

a particular workflow. See “Converting Managed Media Spaces to 

Unmanaged.” 

• Changing the EditShare Administrator password in EditShare Manager. 

See “Changing Your Administrator Password.” 

• Status web page that gives you access to client installers, manuals, and 

server status. See “Viewing EditShare Status in a Web Browser.” 

• How you connect to the server remotely. You now use RealVNC on 

Windows and Mac to connect remotely. The installers are in your SMB 

File Exchange area. See “Preparing the Administrator’s Workstation.” 

NOTE: TightVNC and Chicken of the VNC are no longer supported. 

9



• Several optimizations for Windows Vista, Windows 7, and OS X that 

affect operation generally and can also particularly improve performance 

when you work with uncompressed HD. See “Setting up Editors 

Workstations.” 

• Enhanced support for OS X workstations that connect to EditShare 

storage via Apple Filesharing Protocol (AFP). EditShare now includes a 

new version of Netatalk, the Linux/Unix service that allows OS X 

workstations to connect via AFP. Netatalk now offers full support for the 

extended attributes that are now part of OS X 10.6 filesystems, ensuring 

that OS X users do not encounter problems when connecting via AFP. 

• Automatic updates. Your EditShare server now delivers updates and 

reports when they are available, and queries whether you want to install 

them. See “EditShare Updates.” 

If your server is on the Internet, when you click Install Updates and there 

are updates available, a browser window opens with a version of the 

ReadMe for that update. 

NOTE: If you have systems that are not connected to the Internet, EditShare also 

offers two standalone offline updaters that you can download from 

updates.editshare.com. If your unconnected system is running Flow, download and 

run the version of the EditShare v6.0.5.0 updater that includes Flow. A different 

version not containing Flow packages is available for all other unconnected 

systems, which saves you time when you update. 

• Improvements to the Role Assistant and the ESA Assistant. See 

"Configuring Your System with the EditShare Role Assistant" on page 15 

in this ReadMe, “EditShare Updates,” and “Setting up Multiple Severs 

with ESA Assistant.” 

The following new features are described in the EditShare Version 6.0 Editor’s 

Guide: 

• You can now reset your login count in EditShare Connect. See “Resetting 

Your Login Count.” 

• The Avid Launcher has several UI changes and now allows you to choose 

to work with Avid-Style sharing or with Avid Unity. See “Method Two: 

Avid Launcher.” 

Also new is the way EditShare numbers its releases. See "Release Numbering and 

EditShare Connect Client Updates" on page 11. 

10



Avid-Style Sharing 

While EditShare pioneered the first non-Avid system for sharing bins, 

sequences and media, we now offer a second way for collaborating with these 

assets. Called Avid-Style Sharing, the new system provides bin-locking and 

media sharing that works the same way it does with Avid's Unity storage. 

Each approach has its advantages. For example, the original EditShare way of 

sharing bins via User folders is probably much more secure for schools and big 

organizations where editors want some guarantee that their bins and sequences 

cannot be modified by others. Similarly, deleting files and rebuilding media 

databases is both safer and easier with EditShare's Avid MXF spaces. 

However, for Avid editors who are accustomed to the way Unity works, now 

there is no need to learn a new way of doing things. With EditShare's Avid-Style 

Sharing, you get both Avid-Style bin-locking and the Avid way of associating 

media files with the workstation that created them. In addition, with Avid-Style 

Spaces, you get a small performance boost on Windows workstations that can 

be important when ingesting or outputting sequences with six or more audio 

tracks. 

Release Numbering and EditShare Connect Client Updates 

With this release, EditShare is implementing a new release-numbering scheme 

that might save you time and effort. 

If your facility has a large number of client workstations, it can be 

time-consuming to update client software. EditShare occasionally releases new 

storage software that includes new features and fixes to prior limitations, but 

that does not require a new version of EditShare Connect. In this case, you do 

not need to spend the time to unnecessarily update the client software. 

EditShare releases now have an additional number slot, for a total of 4. For 

example, the current release is numbered 6.0.5.0, rather than 6.0.5. The way to 

tell if you need an EditShare Connect update is as follows: 

• Storage versions that do not require updating EditShare Connect clients 

include a change only in the final number slot. 

For example, in the future, if you were running 6.0.6.3 and a v6.0.6.4 

release became available, you would not need to update your EditShare 

Connect client software. 

11



• Storage versions that require updating EditShare Connect clients include 

a change in the third number slot. 

For example, in the future, if you were running 6.0.6.3 and a v6.0.7.0 

release became available, you would need to update your EditShare 

Connect client software. 

New in Flow Version 2.0.4 

The following features are new in this version and are described in the EditShare 

Flow Version 2.0 Setup and User’s Guide: 

• Ark-Flow integration. See "About Ark-Flow Integration" on page 13 and 

“Using EditShare Ark with Flow” (also see the EditShare Ark Version 2.0 

Setup and User’s Guide). 

• Edit While Capture. The ability to edit material that is still being captured. 

See "About Edit While Capture" on page 13 and “Ingesting with Edit 

While Capture.” 

• File-based ingest support. The ability to ingest XDCAM and P2 clips 

directly from a workstation running Flow Browse. The ability to keep clips 

in their native codec or transcode to other resolutions without any 

reencoding, called Rewrapping. See "About File-Based Ingest" on page 14 

and “Ingesting from Files,” as well as “Improvements in Flow Control” in 

this list. 

• Sequence drag-and-drop. The ability to select a sequence icon and drag 

the entire sequence into an editing application without having to select all 

the clips in the sequence. See “Working with Sequences.” 

• Ganged capture. The ability to start and stop ingest of multiple sources 

simultaneously, using the same codec and metadata settings from each 

channel in the group. You select the codec and destination only once, and 

the metadata stays the same for each channel, except that the clip name 

gets appended with chl1 chl2, and so on. See “Ingesting Material.” 

• Captures View. Shows you a tree view in the File browser of the 

components of a capture. See “Viewing Media Space Contents and Search 

Results.” 

• Clip status. Shows you status such as Online or Offline, Capturing, 

Archived, and so on. See “Viewing Clip Status.” 

• Capture status. Clips in process of being captured appear in the File 

browser with a red border and a file size of “Recording.” Clips lists are 

automatically refreshed during a capture. 

12



• Schedule repeat. The ability to schedule the repeat of a scheduled job. See 

“Creating an Ingest Schedule.” 

• Search improvements. You can search by creation date, and the search 

includes deleted and archived files. 

• Improvements in Flow Control, including the following: 

– Informational field in the Users tab, and the ability to assign 

permissions for reading and writing metadata and restoring 

from Ark 

– Status information in the Networks tab 

– Ability to control the ingest rate for file ingest, so your facility is not 

overwhelmed by numerous ingests at the same time 

– Ability to specify a Scan server’s IP address in Manual mode 

– Ability to control proxy creation during scanning 

• Flow client software now available from the status web page. See “Viewing 

EditShare Status in a Web Browser” in the EditShare 

Administrator’s Guide. 

About Ark-Flow Integration 

If you have Flow and Ark systems at your facility, you can now configure these 

two products to be used together seamlessly. For each clip you back up or 

archive onto an Ark Tape or Ark Disk device, Flow keeps a record in its database 

indicating the clip has been archived. Flow also makes sure the clip has a 

corresponding proxy file that you can later search for or play in Flow Browse. 

At any time after you have deleted high-resolution clips from your EditShare 

storage, you can use Flow Browse to find the clips you want to restore. Flow 

retrieves the media files you selected from Ark and restores them to an 

EditShare Media Space. You can then use them for editing. You can tell Ark 

which clips you want to restore, where you want to restore them to, and when 

you want to run the restore job. 

About Edit While Capture 

In addition to chunking, the Edit While Capture feature provides a second way 

to start editing video material while you are still capturing it. 

With Edit While Capture, you can specify a longer duration of time – for 

example, 1 hour or 2 hours – and within a few seconds of when you begin 

recording, you can drag the clip into your editing application and begin working 

13



with it. When viewed in your editing application, the clip appears to have 

whatever duration you set. When you scroll into the part of the clip that has not 

yet been recorded, instead of seeing a video image, you see a slate that says 

“Media Not Yet Recorded.” Over time, the unrecorded part of the clip is 

replaced by real video and audio data. 

With Edit While Capture, you don't need to have multiple clips to begin editing 

the material you have just captured. If your event goes past the time limit you 

specified, a new Edit While Capture clip is automatically created that is seamless 

with the previous clip – so you don't miss even a split second of the event you 

are recording. You do not need to manually start a new capture. 

Another unique aspect of Flow's Edit While Capture feature is that it allows you 

to create “Universal Edit While Capture” clips. That is, if you are capturing in a 

codec that is common to both Avid and QuickTime – for example, DV 50 or 

DVCPro HD – the video and audio data needs to be only stored once on your 

EditShare Server. Avid sees the Edit While Capture clips as native Avid MXF 

files and Final Cut Pro sees the same clips as native QuickTime files. 

About File-Based Ingest 

Flow supports ingest of file-based media from XDCAM-EX cards, P2 cards, and 

even from virtual XCDAM-EX and P2 directories located on USB, FireWire, or 

local storage devices. If you connect an XDCAM-EX or P2 device to an Express 

card or PC-card slot to a workstation running Flow Browse, you can browse the 

contents of that card or disk in the File browser Device tab. 

NOTE: If your media is stored on Sony XDCAM-EX cards or Panasonic P2 cards, you 

must install the appropriate drivers so your workstation recognizes the cards. 

Flow offers a number of ways to ingest your file-based media. One option is to 

rewrap the clips, which keeps them in their native codec without any 

reencoding. For example, if you want to ingest Avid files, you select the Avid 

Rewrap codec, and if you want to ingest QuickTime files for Final Cut Pro, you 

select the FCP Rewrap codec. In either case, the files are not reencoded even if 

the file extension (wrapper) changes. You can also choose to transcode your 

file-based media to many other Avid and FCP codecs. 

Unlike when you ingest from videotapes, which generally run in real time, 

file-based ingest has the potential to transfer data as fast as it can come off the 

device. To prevent file-based ingest activities from overwhelming the network 

or storage system, Flow allows administrators to limit the bandwidth available 

to file-based ingest activities. This limit does not apply to real-time SDI video 

ingest activities. The bandwidth is shared equally among all workstations that 

are currently doing file-based ingest. 

14



New in Ark Version 2.0.5.0 

The following features and changes are new in this version and are described in 

the EditShare Ark Version 2.0 Setup and User’s Guide: 

• Ark v2 is supported in the EditShare version 6 operating system. The 

EditShare v6.0.5.0 updates includes an update to Ark v2.0.5.0. 

• Ark now supports integration with Flow. See "About Ark-Flow 

Integration" on page 13 and “Using EditShare Ark with Flow” in the 

EditShare Flow Version 2.0 Setup and User’s Guide. 

• Individual file restore (requires Flow). See “Restoring Individual Files.” 

• Backup of Universal Media Spaces. See “Adding a Backup Job.” 

• You are now notified if you are trying to restore items from a tape that is 

not in the autoloader. 

Fixed in Version 6.0.5.0 

The following limitations were fixed: 

• Previous versions might have sent spurious e-mails to the EditShare 

Administrator email account. This has been fixed. 

• Remote help might have failed to connect if you initiated it from a local 

VGA connection instead of from VNC. This has been fixed. 

• RAIDs might not have mounted after a cold boot. This has been fixed. 

• You might have seen screen artifacts the first time you started the Ark 

application. This has been fixed. 

• Several selection options might have been difficult to distinguish in the 

v6.0 user interface. This has been fixed. 

• You might have experienced connectivity problems with Switch mode in 

the IP Configurator. This has been fixed. 

• You might have had trouble emptying the trash in Managed, Unmanaged 

or Avid Style Media Spaces. This has been fixed. 

Configuring Your System with the EditShare Role Assistant 

The EditShare Role Assistant makes sure your system is configured correctly. In 

general, you must run the Role Assistant as part of a first-time setup. The only 

15



exception is if you have a standalone EditShare server with no ESA groups and 

no Flow or Ark applications. 

As of v6, if you want to configure an ESA group, you run the ESA Assistant from 

the Role Assistant, and if you want to configure an Ark system, you can run the 

Ark Assistant from the Role Assistant or from the Control Panel. 

If you add Flow roles to a server using the Role Assistant, required Flow 

packages are downloaded automatically if you have Internet access on that 

server. If you don’t, you need to download the offline updater with Flow and 

install it on the server, and then rerun the Role Assistant to add the appropriate 

Flow roles. 

If you were already running Flow under version 6.0.x, you must reboot and then 

reboot again after the Role Assistant completes. If you do not run the Role 

Assistant after updating, you might not get the Flow clients installed in the 

correct place on the ESA master. 

For additional details abut setting up your system, see “Using the EditShare Role 

Assistant” in the EditShare Version 6.0 Administrator’s Guide. 


The following limitations have been fixed: 

• If you have Ark at your site, your EditShare Storage system might have 

become unresponsive because too many Ark log notifications were being 

retained. This has been fixed. 

• After updating to v6.0.5.1, you might not have been able to connect to AFP 

shares. This has been fixed. 


The following limitations have been fixed: 

• With Avid-Style sharing, if you opened an Avid bin that held content, the 

bin might have appeared empty. This has been fixed. 

• EditShare now supports Avid Pro Tools on Windows systems without 

iSCSI. 

• You might have had trouble updating your email preferences. This has 

been fixed. 

16


LIMITATIONS 

• You might have had problems importing jpeg files into an Avid editing 

application and then creating media on an EditShare Media Space. This 

has been fixed. 

• An unallocated tape is now removed from the Available list in Ark if the 

tape is not in the autoloader. 

• You might not have been able to write to your SMB File Exchange area. 

This has been fixed. 

• You might have been receiving spurious “has not completed a verification 

in more than 7 days” messages about your RAID controllers. You are now 

correctly notified of verifications. 

• You might not have been receiving email status messages from your 

expansion server. This has been fixed. 

Documentation Changes 

The EditShare Administrator’s Guide and the EditShare Editor’s Guide were 

updated for v6.0. The EditShare Ark Setup and User’s Guide and the Ark Help 

were updated for v2, and the EditShare Flow Setup and User’s Guide was 

updated for v2.0. 

Limitations 

You might experience the following limitations in this version: 

• "General Limitations" on page 17 

• "Flow Limitations" on page 19 

• "Ark Limitations" on page 19 

General Limitations 

• If you configured the Avid Launcher in EditShare Connect, before you 

upgrade your Avid software, you must remove your Avid application 

from the EditShare Connect Avid Management tab by selecting it and 

then clicking the Remove Avid Application button. 

17


LIMITATIONS 

• If you use AFP on OS X 10.6.x, and you capture clips that exceed 2 GB in 

size with DV25, DV50, or DVCPro HD codecs, you might lose tape name 

and timecode information. 

Workaround: Use DAVE if you plan to capture large clips with DV25, 

DV50, or DVCPro HD codecs. All other codecs are unaffected by this 

issue and should be safe for you to use to capture and edit with AFP. 

• When you connect to the RAID Manager on a remote server, you might 

see a This Connection is Untrusted message box. This does not indicate an 

actual error. 

Workaround: Click the “I Understand the Risks” button and then click 

the “Add Exception” button. An Add Security Exception dialog box 

opens. Click the “Confirm Security Exception” button. 

• If you start your Avid application by double-clicking the desktop icon, 

then look at a bin from an Avid-Style Media Space, you might not see the 

locking icons that indicate that Avid-Style sharing is working. 

Workaround: Close the Avid application, and click the Launch Avid 

Application button in EditShare Connect to restart the Avid application. 

• If you try to use the Avid Launcher from EditShare Connect on a 

Windows Vista 32-bit system, the Avid editing application might not start 

successfully. 

• Each workstation that connects to your EditShare server must have a 

unique name. EditShare recommends that the boot drive on each 

workstation also have a unique name. See “Naming Workstations” and 

“Naming Boot Drives” in the EditShare Administrator’s Guide. 

• If you create a user on an EditShare server and then add that server to an 

ESA group as an expansion server, the user is not available in the new ESA 

group. 

Workaround: Create the ESA group before you create users on any of the 

intended expansion servers. 

• You cannot use Traditional Media Spaces under AFP in this version at this 

time. 

• In Avid MXF and Universal Media Spaces with many users, if you try to 

assign all users read-only status at once, you might experience 

system slowdown. 

• You might experience difficulty if you try to add users with names longer 

than 16 characters. 

Workaround: Restrict usernames to 16 characters or fewer. 

18


LIMITATIONS 

• In the EditShare Connect Project browser on a Mac, if you have a Finder 

window open while you are moving bins or folders or refreshing the 

browser, you might hear the Mac system noise for deleting a folder even 

though you aren’t deleting one. This is because EditShare is creating and 

then deleting a folder to refresh the Finder. You can ignore the noise. 

• AFP is not supported in this version of EditShare Connect on Macintosh 

OS X version 10.4.x. 

NOTE: You can use AFP on OS X v10.4.x if you are running EditShare v5.1 

and earlier. 

Flow Limitations 

• For file-based ingest, if you select one of the rewrap codecs (Avidwrap or 

FCPwrap), and then ingest only part of a file from an XDCAM-EX card, 

the first two frames might be corrupted. For example, if you trim the IN 

point on a clip (that is, if you don't start a file-ingest on the first frame of 

video from the original clip), the beginning of the resulting clip that gets 

transferred to the EditShare Storage Server is slightly corrupted with some 

blockiness in the first two frames. To compensate, Flow takes a few extra 

frames to ensure that the first frame you actually wanted to ingest is good. 

The two blocky frames come from just slightly outside the place where you 

marked the IN point. 

Workaround: When you are editing, do not include the blocky frames in 

your sequence. 

Ark Limitations 

• CAUTION: In Ark Assistant, select First-time Setup only for configuring new 

Ark systems. First-time Setup removes all backed-up files. 

• Ark activation is not supported in version 6.0.5.3. 

• In the Ark Assistant Configuration area, you might not see a server you 

want to select. 

Workaround: In the list of servers, select the option, and then 

type the IP address of the server you want. 

19


TECHNICAL SUPPORT INFORMATION 

• In an Ark backup job, if you create an item including a Media Space from 

a Master server and another Media Space from an expansion chassis, the 

backup does not run and an error message appears in the Log window. 

Workaround: Make sure all Media Spaces in a single backup item are 

from the same server. Create a separate item for Media Spaces you want to 

back up from an expansion chassis. 

• For Ark Tape, only Media Space users included in the most recent backup 

are included in the Restore. 

For Ark Disk, all users who have been part of a Media Space during any 

previous backup are included in the restore, even if they have now been 

removed from the Media Space or from EditShare Manager. Users added 

to a Media Space after the most recent backup job has run are not included 

in the restore, however. 

Technical Support Information 

For assistance beyond this ReadMe and that provided in your EditShare 

documentation, contact EditShare Technical Support at 

support@editshare.com. 

You can also call one of the following telephone numbers: 

• EditShare Americas: 617-782-0479 

• EditShare Europe, Middle East & Africa:44 (0) 20 7183 2255 

• EditShare Asia-Pacific: 61 7 3112 5220 

EditShare strongly recommends that you purchase a support agreement; if you 

do not have a support agreement, a per-incident rate is available for problems 

not covered by warranty. 

Copyright and Disclaimer 

Copyright © 2010 by EditShare 

This manual, as well as any software described in it, is furnished under either a 

license or a confidentiality agreement, is confidential to EditShare, and may be 

used or copied only in accordance with the above mentioned agreements. The 

information in this manual is furnished for your use only and is subject to 

20


COPYRIGHT AND DISCLAIMER 

change without notice. EditShare assumes no responsibility or liability for any 

errors or inaccuracies that might appear in this manual. 

This Documentation is the property of EditShare and is provided in accordance 

with an EditShare license agreement. Copying, modifying, or distributing this 

Documentation in violation of the license agreement, United States Copyright 

Laws, or the Copyright Laws of any applicable foreign jurisdiction is 

expressly prohibited. 

EditShare is a registered trademark of EditShare in the United States and other 

countries. 

Avid is a registered trademark of Avid Technology, Inc. DAVE is a registered 

trademark of Thursby Software Systems, Inc. Final Cut Pro, Leopard, 

Macintosh, and Macintosh OS are registered trademarks of Apple, Inc. in the 

United States and other countries. Premiere is a registered trademark of Adobe, 

Inc. Windows is a registered trademark of Microsoft Corporation in the United 

States and other countries. All other brand and product names are trademarks 

or registered trademarks of their respective companies and are hereby 

acknowledged. 

Notice: To the best of our knowledge, the information in this document is 

accurate; however, EditShare assumes no responsibility or liability for the 

accuracy or completeness of this information. Mention of trade names or 

commercial products does not constitute endorsement by EditShare except 

where explicitly stated. 

EditShare, 119 Braintree Street, Suite 705, Boston, MA 02134 

Tel: 617-782-0479 Fax: 617-782-1071 http://www.editshare.com 

Part #: ESRM-V6_0_5_4. 

December 9, 2010 

21


COPYRIGHT AND DISCLAIMER 

22

EditShare Avid-Style Sharing - Software updates

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?