Lightworks 11.1.f Public Beta (Windows Only)

Today we are releasing the next Public Beta of Lightworks for Windows (11.1.f)

We now have approximately 3000 users actively testing and reporting feedback on the latest version of Lightworks. This build primarily fixes issues that have been broken between builds. There is still more work to be done with regards to having 11.1 ready for release, so the release date may slip by a week or two into March.

To access the latest Beta build for Windows please visit: lwks.com/beta

The fixes since 11.1.e are:

  • Fixed crash on startup in the 64bit version when MIDI devices are connected
  • Removed obsolete Matrox drivers (5.5/6/6.1/7)
  • Added support for Matrox 9.2 SP1 drivers
  • Added support for Matrox DSXLE3 range
  • Fixed tiles not repositioning automatically in bin after clip is deleted in tile view
  • Ensure that the whole of the viewer/tile is kept onscreen following a change in output video format
  • Fixed performance problems playing back material in the 64bit version primarily XDCAM HD MXFs/AVCHD
  • Fixed import of AVCHD material in the Free version (when using Create Link)
  • Fixed import of MJPEG MOV files in the 32bit version only (64bit will not work with these files)
  • Fixed missing audio on MPEG4 exports
  • Fixed ProRes sample failing to import with video
  • Fixed ability to type the timecode into the labels panel
  • Fixed potential crash recording 1080p 23.98fps using Blackmagic I/O
  • Fixed crash clicking Standby when setup to record Voice over on the record panel
  • Fixed AAF import from AVID showing black clips in the edit
  • Fixed project name not appearing when creating a new room to a project from the project browser screen
  • Fixed ability to remove an EQ effect from an audio clip by right clicking and selecting remove
  • Fixed alpha channel not being removed when applying a 3D DVE to a clip
  • Fixed edit sync warnings not appearing when making a copy of an edit
  • Fixed ability to use non-writable drives if they have a Material/Sound folder on them

All Beta feedback is through the Lightworks Forum under the “Windows Beta Testers” section.

Advertisements

Lightworks 11.1.d Public Beta (Windows Only)

Today we are releasing the next Public Beta of Lightworks for Windows (11.1.d)

Since opening up the Beta program to the public three weeks ago, we have had an enormous amount of feedback, which shows in the list of fixes below. We now have 1100 users actively testing and reporting feedback on the latest version of Lightworks.

To access the latest Beta build for Windows please visit: lwks.com/beta

The fixes since 11.1.c include:

  • Fixed issue with playback stopping on the fullscreen output when moving the mouse
  • Fixed exit icon not appearing on fullscreen playback
  • Fixed Alpha setting not persisting on 4 corner gradient effect
  • Fixed 1 frame timecode discrepancy on BWAV imports
  • Fixed incorrect image on MTS files transcoded to Matrox YUYV
  • Fixed timeline marker not moving during playback after adding an effect and changing a keyframe parameter
  • Fixed inability to record from HDMI on Blackmagic Intensity
  • Fixed audio only recording using Blackmagic I/O
  • Fixed drag and drop behaviour of FX when V tracks are disabled
  • Enhancements and improvements to ALE import: (Pro version required)
    • File location/Name is no longer required under the Filepath heading. The ALE just needs to be in the same folder as the media
    • Related Video and Audio tracks are now automatically synced together upon import to Lightworks
    • ALE must be stored in parent directory of media it is referring to for import to analyse the media
    • Creates auto-grouped audio-only clips. Primarily multichannel BWAVs that have been extracted as separate .MXF files in the AVID MediaFiles folder
    • Included better logging during the import process to indicate why certain files cannot be imported
    • Included better logging during the import process to indicate which folders are being scanned
    • Ignore any subfolders starting with ‘.’ during media scanning
    • Ignore “Mac OSX” subfolders during media scanning
    • Ignore “resource.frk” subfolders during media scanning
    • Show ALE framerate on the import panel
    • Respect Reel IDs when pairing media files
  • Fixed vectorscope output displaying nonsense when using Blackmagic I/O
  • Fixed reading of media locators on AAF import
  • Fixed media locations disappearing when switching between project spaces
  • Added ALE licensing option to the licensing panel
  • Added User definable project/media locations to the licensing panel
  • Added import option to suppress material linking when importing AAFs
  • Added right-mouse click menu on Bin icon to display ‘All Contents’ from a project
  • Changed Lightworks archiving. User now selects whether to include local media or linked to media
  • Fixed playback of audio imported to the system drive in 11.0.3
  • Fixed display of Matrix wipes on FX panel
  • Fixed display of ProRes sample on the import panel (previously black)
  • Fixed reading of Reel ID from file imports
  • Fixed black Renders/Recordings/Exports using 1080i/PAL Blackmagic uncompressed MOV setting
  • Fixed connection settings on the record panel using Blackmagic I/O
  • Fixed Matrox Mpeg422P@HL bit rate setting on the export/render/record panels
  • Fixed 24bit WAV export in the 64bit version
  • Fixed a memory leak related to reading audio-file locators in AAF import
  • Fixed encoding/decoding URL strings in AAF locators with regard to real unicode characters
  • Fixed re-linking to sound files on AAF import (on a material drive) that do not have ‘.WAV’ extensions
  • Fixed AAF import of video file metadata (wrong aspect ratio etc)
  • Fixed failure to transcode 30fps .MP4 sample to MPEG422 AVI
  • Fixed potential crash playing back XDCAM HD MXF files in the 64bit version
  • Fixed potential issue with shared projects not updating correctly when importing files
  • Fixed audio links in .archive not being restored to the Sound folder when restoring the .archive
  • Fixed media appearing offline after using the move function of the media tool
  • Fixed link on Filecard to show all media being linked to
  • Fixed audio playback on AIFF sample
  • Prevent two instances of Lightworks being run at the same time
  • Fixed potential crash clicking the Location field in a bin after moving media using the Manage Media tool
  • Fixed typewriter titling effect progression with overlapping non-coincident effects
  • Fixed archiving progress bar from reporting invalid time (when including linked media)

All Beta feedback is through the Lightworks Forum under the “Windows Beta Testers” section.

Lightworks 11.1.c Public Beta

Today we are releasing the next version of Lightworks 11.1 as a Public Beta for Windows (11.1.c) This means any user wishing to test the latest Windows Beta builds can gain access without having to ask. They simply click the link below, fill in some details, and agree to the Terms and Conditions. This will then give them access to all the Windows Beta Builds as they become available.

www.lwks.com/beta

The main new features of 11.1 Beta are:

  • Added support for Blackmagic I/O devices. Drivers 9.5 or higher are required (Pro version required)
  • Added support for Windows 7 64bit with a separate installer (Pro version required)
  • Added outlining support for the native titling effect (Pro version required)
  • Added ability to let the user specify where media directories are stored using the disk manager tool (Pro version required)
  • Added ability to let the user specify where local projects are stored using the Manage project spaces function (Pro version required)
  • Added support for linking to audio rather than copying it locally
  • Allowed MP4/AVCHD (MTS/M2TS) media to be imported into the Free version as transcode only
  • Added support for linking to files through ALE import. The ALE must contain a valid media location
  • Added support for automatic relinking to subclips when importing an AAF
  • Added ability to enable/disable detection of split MXF files
  • Added support for subclips without V tracks on AAF import/export
  • Added ability to automatically flatten multi-level subclips to one level when exporting an AAF to Avid
  • Added ability to read and interpret AVID markers as cue points in AVID AAFs
  • Updated installer to include latest Sentinel RTE (6.51) This allows installation on Windows 8

The full list of fixes in this version can be seen below. It is worth paying particular attention to the Limitations and Known Issues:

  • Renamed Disk Manager tool to Media Manager tool
  • Enhance Mange project spaces panel on the project browser
  • Fixed audio on 23.98 1080p MXF AVID DNxHD exports importing back in and playing at twice the speed
  • Fixed AVID DNxHD-TR MXF export not working correctly
  • Fixed a number of changes to the way we link to clips when re-importing
  • Prevented any attempts to ‘copy-local’ audio clips on AAF import
  • Fixed errors causing ‘heap corruption’ in a number of AAF functions
  • Fixed erroneous folders being created when creating a new project space
  • Fixed Pref file import when encountering empty lines
  • Fixed audio levels not moving when using ALT S shortcut
  • Fixed solo/mute functions from Mackie to be remembered after a trim
  • Fixed solo/mute functions from Mackie to be remembered when switching focus to another edit/shot
  • Fixed audio linking when using shared projects
  • Fixed Mackie Solo/Mute functions when audio mixer panel is not open
  • Fixed audio drag in fades from incorrectly appearing when inserting from a source that contains fades
  • Prevented import panel showing frame rate or other metadata if we haven’t read it from the file
  • Fixed all channels displaying the same information when linking to multichannel WAV file
  • Fixed audio corruption when transcoding a multichannel WAV file on import
  • Fixed incorrect display message about Matrox DSX Utils on startup
  • Fixed record panel only allowing one audio connection option
  • Fixed crash opening recording panel when using Matrox I/O
  • Fixed audio on transcoded H.264 Mov files
  • Fixed sync issue importing from an ALE
  • Fixed audio replay rate on WAV samples
  • Fixed memory handle leak (handles continuing to increase)
  • Fixed no audio on Blackmagic output when first entering a project
  • Fixed crash opening an edit that contains 32 audio tracks
  • Fixed playback of 24 bit audio masquerading as 16
  • Fixed reading of audio files that have multiple single channel streams
  • Fixed potential crash resizing a viewer during playback
  • Fixed image on SDI output of Blackmagic when set to NTSC
  • Fixed 23.98/29.97fps Quicktime exports showing up as 24/30fps
  • Fixed panels jumping around after a right/left click operation
  • Fixed Rack behaviour when adding bin to a rack within a rack
  • Fixed incorrect audio replay rate for 23.98 .MXF audio samples
  • Fixed incorrect filename showing on BWAV imports
  • Fixed reading of Reel ID from MXF files on import
  • Changed licensing so that the user is not required to activate the free version IF there is an available network Pro-license available

Limitations and Known Problems

  • Potential crash transcoding an .MP3 audio file on import
  • The Vectorscope may show incorrect information. This is under investigation
  • The audio may be distorted playing back at certain output formats using Blackmagic I/O. This is under investigation
  • You will not be able to install the 32bit and 64bit version on the same system
  • There is currently no audio linking for AVCHD with AC3 audio. AC3 audio in AVCHD files will still be copied locally
  • There is currently no audio linking for Quicktime files audio will still be copied locally
  • Some audio files may not import correctly or may not link correctly, please send us any samples you experience issues with
  • Some Quicktime files may import with audio at the incorrect length. This is under investigation
  • Transcoding may be slower than previous Beta versions this is under investigation
  • The ‘Elapsed’ and ‘Total Duration’ fields in the edit label tab of the BITC panel do not show feet and frames (including 16mm & 35mm 3-perf)
  • Video analysis tool appears through the FX configuration panel when configuring a colour correction effect
  • AC3 audio will not import on .MOV wrapped files
  • You will not be able to export a Quicktime Movie from a shot/sequence that contains native H.264 MOV files
  • Potential crash browsing import directories without Quicktime installed
  • Uncompressed Blackmagic SD option will not work correctly for some formats
  • Potential crash importing WMV file
  • You will need to set “Stop record if label break” to “No” for successful recording using a Firewire deck
  • You will need to set “Stop record if label missing” to “No” for successful recording using a Firewire deck
  • DV recordings may have a black frame at the end of the recorded clip
  • Potential memory leak playing very large AVID DNxHD edits
  • Audio monitor delay setting will not be accounted for during export
  • Cannot record HDV through Firewire
  • AVID DNxHD 10bit encode is not possible
  • Make sure any other applications are closed before attempting to install Lightworks
  • Video track can turn red after removing certain FX
  • Performance issues working with H.264 MOV files natively
  • XDCAM EX Quicktime files will not play correctly
  • Error during startup when Matrox MTX utils installed “error copying Matrox DSX driver” Please turn off UAC in Windows
  • Image on viewers and SDI output may look very poor on old ATI graphics card when set to 10-bit precision
  • SHIFT clicking a tile into a viewer has currently been disabled. You can now double left click tiles into existing viewers
  • XDCAM HD files may show pixelation on the viewer when dragging the timeline marker through them quickly
  • PCM Audio on IMX XDCAM samples is pink noise
  • .VOB files appear as “Sound” only on the import panel, but yet import with picture. Performance will be slow
  • Image quality on playback may be poor when project card set to NTSC Fields
  • You will not be able to transcode 1080p 60fps files on import
  • Blu-ray VC1 export does not generate a valid file. It imports back as Sound only
  • Audio on exported AVCHD files cannot be played by Windows Media Player it is just mute
  • Firewire decks MUST be switched off after recording

Windows 7 64bit Limitations and Known Problems

  • The Pro version is required in order to run the 64bit version
  • Blackmagic I/O will NOT work in the 64bit version. This is under investigation. Please use the 32bit version for testing
  • You may recieve a HASP warning about errors in the executable file when closing Lightworks. This is under investigation
  • Potential crash on startup with Mackie audio device connected
  • There is no Quicktime Movie/MPEG4 import/export via Apple SDK
  • Premiere and After Effects plugins are not supported
  • The licensing panel(s) may show incorrect links to the Lightworks Shop
  • Audio content analysis is disabled
  • CDDA ripping is not available

Limitations and Known Issues With Matrox Hardware I/O

  • If your system is not fast enough or does not have enough memory, the captures using MXO2 will stop with a “dropped-frame” message
  • If the drives you are recording to are not fast enough the captures using MXO2 will stop with a “dropped-frame” message

Limitations and Known Issues With Blackmagic Hardware I/O

  • If you are using a Decklink Duo, you will only get I/O from SDI 2 not SDI 1
  • Blackmagic I/O will NOT work in the 64bit version. This is under investigation. Please use the 32bit version for testing
  • Audio monitor level control has no effect on Blackmagic recordings
  • You may experience a crash when stopping record using Blackmagic I/O Please report this to us.
  • The SDI output may become distorted and flicker randomly. This is under investigation
  • You will not be able to view video on the Blackmagic output if Precision is set to 10bit. Change to 8bit
  • You will not be able to view video from Boris Red via the Blackmagic Output when Lightworks is running

All Beta feedback is through the Lightworks Forum under the “Windows Beta Testers” section.

#Lightworks v11.0.3 for Windows is now available at http://lwks.com/downloads

We’ve just released Lightworks v11.0.3 for Windows, with a variety of bugfixes & enhancements. Downloads & more information are available at lwks.com/downloads.

We’re also hard at work on the upcoming beta of Lightworks 11.1 with a number of changes, including Blackmagic I/O support, as discussed over at RedShark, EditShare’s new online magazine for moving image professionals. If you are interested in joining the Lightworks beta program, information on it will be available to registered users on LWKS.com shortly.

As a reminder, we’re aiming to release the initial alpha version of Lightworks for Ubuntu Linux on the 30th of October. A lot of people have been asking about it, and we’re eager to get it to you and see what you start doing with it. 

If you’re just starting out with Lightworks, you may find the Lightworks video tutorials on YouTube useful. They were produced by Peter Bridgman, a long-time professional Lightworks user, and are well worth the time if you’re getting started — or re-familiarized — with Lightworks.

For those curious about the Mac & open source versions, we’re still fully committed to these, but have no updated information at this time. Keep an eye on the Lightworks roadmap for news as it becomes available, and of course our Facebook page and @ESLightworks on Twitter.

At last! Lightworks for Linux will be available starting on October 30th.

 

As EditShare announced at IBC in Amsterdam this month, the Linux version of Lightworks will be ready for public alpha testing on October 30th 2012.

Here’s video of Lightworks running on Ubuntu recorded earlier this year:

The version that we will be releasing in October will be very similar, and also similar to the current Windows version that many people are already using.

What version of Linux is required to run the Lightworks alpha?

Initially it will be Ubuntu 12.04 only, with an aim of supporting other versions at a later date.

Is the Linux version of Lightworks available to download?

We are aiming for the 30th of October, 2012.

Will the Linux version be identical to the Windows version?

Yes, the two will look and feel the same. Some components will not be available in the Linux version, such as Firewire recording. More information will be available shortly.

Will I be able to use my existing license for the Windows version of Lightworks with Lightworks for Linux?

If both systems are connected to the same network, you will be able to detach your license from one system and move it to another. More information on this will be available shortly.

What graphics card will I need?

It will run on ATI systems, but performance will be much better with Nvidia.

 

As always, if you have any questions or comments, please join the conversation at the Lightworks Forum.

Thank for your interest in Lightworks — we cannot wait to see what you do with it!

#Lightworks v11.0.1 for Windows is now available at http://lwks.com/downloads

We’ve just released Lightworks v11.0.1 for Windows, with a variety of bugfixes & enhancements. Downloads & more information is available at lwks.com/downloads.

We also released a series of video tutorials for Lightworks earlier this week. They were produced by Peter Bridgman, a long-time professional Lightworks user, and are well worth the time if you’re getting started — or re-familiarized — with Lightworks.

For those curious about the Mac & Linux versions, and the launch of the open source project, we’re still fully committed to all of these, but have no updated information at this time. Keep an eye on the Lightworks roadmap for news as it becomes available, and of course our Facebook page and @ESLightworks on Twitter.

EditShare 6.2.0.1 now available, including urgent Ark 2.2.0.1 update. See http://editshare.com/updates for details.

New EditShare server updates are available. Please see editshare.com/updates for details & downloads.

Please note that these are part of EditShare’s 6.2.x series, with many notable changes & improvements to multiple product lines, including Storage, Flow, and Ark enhancements.

Full information about this update is available in the EditShare v6.2 ReadMe PDF

URGENT NOTICE FOR ARK CUSTOMERS

All EditShare Ark customers who previously updated to Ark 2.2/EditShare 6.2 should immediately update to Ark 2.2.0.1/EditShare 6.2.0.1. Please contact EditShare customer support for further details. It is critical that you update without delay.

If you have not yet updated to Ark 2.2/EditShare 6.2, the update to 6.2.0.1 is not urgent. However, there are many new Flow, Ark and Storage features in the 6.2 series; see the 6.2 release notes for details.

Full information about this update is available in the ReadMeV6_2_0_1.pdf

EditShare Ark (6.2.0.1)

Changes in this version:

  • Fixed Ark Tape bug which caused blank tapes to be formatted incorrectly.

IMPORTANT NOTE REGARDING GEEVS WITH EDITSHARE STORAGE AND FLOW

This update is not compatible with the currently shipping Geevs version, 5.1.3.0. Please do not update your storage, Ark, or Flow servers if you are running Geevs 5.1.3.0 or earlier and using Geevs with Flow.

Geevs 5.2.1.0, which is required for compatibility with Flow 2.2, will be released in Mid-June. As soon as it is released, notification will be posted here. It will then be safe to update all your servers at once to the latest releases.

NOTE FOR AVID USERS UPGRADING FROM EDITSHARE 6.1.3.1 OR EARLIER

If you were previously using EditShare Connect on OS X or Windows under EditShare 6.1.3.1 or earlier, and had configured Avid Style or the Avid Launcher, you must 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 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 6.1.3.2, 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 6.1.3.0 or 6.1.3.1, you should update to 6.1.3.3 but you must contact EditShare Technical Support for assistance remaking the bond before doing so.

If you use ethernet bonding but are upgrading from 6.1.3.2, 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)

Installing EditShare Updates

If your server has a connection to the Internet, you can run Install Updates from the Control Panel on your server’s desktop. Otherwise, you can download the offline updater from editshare.com/updates, copy it to your server, then go back and run Install Updates.

As always, feel free to contact EditShare technical support if you have any questions.

 

EditShare 6.2 update now available, including Flow 2.2 & Ark 2.2. See http://editshare.com/updates for details.

New EditShare server updates are available. Please see editshare.com/updates for details & downloads.

Please note that these are part of EditShare’s 6.2.x series, with many notable changes & improvements to multiple product lines, including Storage, Flow, and Ark enhancements.

Full information about this update is available in the EditShare v6.2 ReadMe PDF

ATTENTION CUSTOMERS USING GEEVS AND FLOW

This update is not compatible with Geevs 5.1.3.0! Please see ‘Important Note’ below for details.

EditShare Storage (6.2)

Changes in this version:

  • Support for SNMP-connected UPS devices.
  • New DAVE locking and caching options in EditShare Connect.
  • Automatic repair of quotas.
  • Removed Netatalk restart when creating new Managed, Unmanaged or Avid Style spaces.
  • Improvements to NFS client.

EditShare Flow (2.2)

This is a major release which includes many new features:

  • Group clip creation on Flow and Geevs ingest for multicam editing in Avid.
  • New clip status icons and timeline colors in Flow Browse that show whether clip is online, offline, or archived.
  • File Deletion from Flow Browse
  • New scan options, and ability to scan from Flow Browse in addition to Flow Control.
  • Partial file restoration from Ark Disk.
  • Creation of Ark restore jobs from projects, folders, clips, and sequences.
  • Many improvements to Search including similar and Boolean searches.
  • Media spaces arranged by type in Flow Browse.
  • Separation of Flow Scan and Proxy creation process, now possible to make proxies on multiple servers at once.
  • Improved metadata layout, and ability to configure custom metadata layouts.
  • Project sharing now available in Flow Projects tab using EditShare Shared Projects Red/Amber/Green lock icon system to indicate ownership.
  • You can now purchase an option to allow Flow to scan existing 3rd party storage locations that present an smb mount.
  • You can now change locked clip metadata if you have permission.
  • Expanded codec support for Scan, File Based Ingest, and SDI Ingest. Additional codecs supported by Flow Scan including Avid JFIF 4:1s and 10:1, and Canon 5D files. See here for details.
  • Drag and drop of Flow Projects or Folders into FCP7 or Adobe Premiere.
  • Other bug fixes, see Fixed in Flow Version 2.2.0.0 in the ReadMe.

Reference table showing supported formats and codecs in Flow 2.2.

EditShare Ark (2.2)

Changes in this version:

  • Ark Watch Groups created on expansion servers will now work properly.
  • Quicker display of large numbers of tape pools and backup runs.
  • Improved sorting of tape pool names.
  • Improved accuracy of estimated time for backup and restore.
  • Ark restore jobs will now continue even if there is an error on restoring a particular file.
  • Swapping of tapes will be optimized when running simultaneous backups.

IMPORTANT NOTE REGARDING GEEVS WITH EDITSHARE STORAGE AND FLOW

This update is not compatible with the currently shipping Geevs version, 5.1.3.0. Please do not update your storage, Ark, or Flow servers if you are running Geevs 5.1.3.0 or earlier and using Geevs with Flow.

Geevs 5.2.1.0, which is required for compatibility with Flow 2.2, will be released in Mid-June. As soon as it is released, notification will be posted here. It will then be safe to update all your servers at once to the latest releases.

NOTE FOR AVID USERS UPGRADING FROM EDITSHARE 6.1.3.1 OR EARLIER

If you were previously using EditShare Connect on OS X or Windows under EditShare 6.1.3.1 or earlier, and had configured Avid Style or the Avid Launcher, you must 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 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 6.1.3.2, 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 6.1.3.0 or 6.1.3.1, you should update to 6.1.3.3 but you must contact EditShare Technical Support for assistance remaking the bond before doing so.

If you use ethernet bonding but are upgrading from 6.1.3.2, 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)

Installing EditShare Updates

If your server has a connection to the Internet, you can run Install Updates from the Control Panel on your server’s desktop. Otherwise, you can download the offline updater from editshare.com/updates, copy it to your server, then go back and run Install Updates.

As always, feel free to contact EditShare technical support if you have any questions.

EditShare 6.1.3.4 update now available, including Ark 2.1.3.4. See http://editshare.com/updates for details.

New EditShare server updates are available. Please see editshare.com/updates for details & downloads.

Please note that these are part of EditShare’s 6.1.x series, with many notable changes & improvements to multiple product lines. The 6.1.3.4 update focuses exclusively on Ark enhancements.

EditShare Ark (2.1.3.4) – Changes in this version:

  • Previously, Ark set the “block size” for LTO drives with each Ark Tape server boot up or each restart of the Ark Tape service. Now the block size is set each time a tape is loaded. This should fix reported issues with tape labels sometimes not being written or read properly, and with backups and restorations sometimes failing without a restart of Ark.
  • On Ark tape servers where the DNS address was slow to respond, certain Ark processes could timeout. This has been fixed.
  • Improved Unicode Compatibility. Until this release, the Ark User Interface might have occasionally failed to show the details for some running and completed jobs because of “unicode incompatibilties”. This has been resolved.
  • In previous Ark releases, if you scheduled an Ark job more than once per day – for example, every hour or ever 20 minutes – the list of queued jobs might have failed to display properly. This has been resolved.
  • Backups and restorations might have previously failed on Ark servers that were configured with multiple IP Addresses. This has been resolved.

Full information about this update is available in the ReadMeV6_1_3_4.pdf

Note for Avid users upgrading from EditShare 6.1.3.1 or earlier

If you were previously using EditShare Connect on OS X or Windows under EditShare 6.1.3.1 or earlier, and had configured Avid Style or the Avid Launcher, you must 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 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 6.1.3.2, 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 6.1.3.0 or 6.1.3.1, you should update to 6.1.3.3 but you must contact EditShare Technical Support for assistance remaking the bond before doing so.

If you use ethernet bonding but are upgrading from 6.1.3.2, you can upgrade normally without assistance.

Note on Thursby 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)

Installing EditShare 6.1.3.4

If your server has a connection to the Internet, you can run Install Updates from the Control Panel on your server’s desktop. Otherwise, you can download the offline updater from editshare.com/updates, copy it to your server, then go back and run Install Updates.

As always, feel free to contact EditShare technical support if you have any questions.