EditShare Storage (188.8.131.52) – Changes in this version:
- Previously, you might have gotten erroneous warnings in the Daily Health Report about RAID Verification not having occurred in the last week on various hardware RAIDs, when in fact verification had been occurring. This has been fixed.
- New preference in EditShare Connect to hide Mac resource fork folders on Windows machines, which resolves some issues sharing Avid projects between Mac and PC Avid systems.
- Fix for Avid users receiving Segmentation Fault errors while using Avid Style media spaces, especially when switching from Avid to other applications or to the desktop.
- EditShare Connect is designed to warn you and not proceed with mounting spaces if Avid is already running when EditShare Connect is launched. However, in previous versions of EditShare Connect, the check for whether or not Avid was already running was too sensitive. Even if only the AvidBinIndexer was running and not the Avid application itself, EditShare Connect would say that “Your Avid application is already running”. This has been resolved.
- A new version of the EditShare network configurator ensures that proper network performance parameters are getting set according to the type of network card in the server – 1 Gigabit or 10 Gigabit – and according to whether bonding and/or bridging is enabled.
EditShare Ark (184.108.40.206) – Changes in this version:
- Flow proxy and database files can now be backed up to Ark (Please contact EditShare Technical Support for configuration details, automatic configuration to follow in a future version).
- Ark will now properly run multiple backup or restore jobs simultaneously (assuming they don’t require tapes from the same pool).
- Fixes to Ark Check Jobs – When running Ark Check Jobs, you will no longer see a progress bar that looks as if the job is running, nor will you get emails for each Media Space that was checked. You will only see a pop up box and receive an email – both providing a summary of the results of the Check Job.
- Ark no longer allows you to back up a media space in Maintenance or Unshare Mode, which ensures that correct information is reported to the flow database.
EditShare Flow (220.127.116.11) – Changes in this version:
- In Flow Browse, if you browsed to a mounted Media Space in the Local tab, duplicate clip entries might have appeared in the database. The new v18.104.22.168 Flow clients fix this problem.
NOTE FOR AVID USERS UPGRADING FROM EDITSHARE 22.214.171.124 OR EARLIER
If you were previously using EditShare Connect on Mac OS X or Windows under EditShare 126.96.36.199 or earlier, and had configured Avid Style or the Avid Launcher, you must first un-configure these features in the old version of EditShare Connect.
Next, if you are a Windows user, you must uninstall the old version of EditShare Connect.
Finally, both Mac OS X and Windows users must update to the new version of EditShare Connect and reenable Avid Style and/or the Avid Launcher.
If you are upgrading from EditShare 188.8.131.52, you can simply install the new EditShare Connect clients over the old ones. You may need to re-target your Avid application in Windows EditShare Connect and/or re-enable the Avid Style option on Windows or os x.
NOTE ON ETHERNET BONDING:
If you have previously configured an ethernet bond under 184.108.40.206 or 220.127.116.11, you should update to 18.104.22.168 but you must contact EditShare Technical Support for assistance remaking the bond before doing so.
If you use ethernet bonding but are upgrading from 22.214.171.124, you can upgrade normally without assistance.
NOTE ON DAVE:
Please visit the updated DAVE compatibility page for new information on the latest EditShare approved DAVE build, 9.0.2-1450. (Updated 30 April 2012)