Ho ho ho. The most noticeable fix today is client’s were sometimes not getting notified when a new drive set was made available. We’re also continuing to improve reporting and error handling as we transition more background services to SignalR.
The largest change in v4.3.0 is a full automatic update system which allows us to push updates without having to manually remote into every system. Any pending update will be installed once all the maintenance tasks are completed, which by default runs at 1am. You can change the maintenance window if you wish to. Automatic updates will be enabled by default, please contact us if you want them disabled for your site.
v4.1.0 introduces audit logging, where we record what users complete what actions and at what time. E.g. UserA gave UserB read access to DriveC at time X. For now it’s just recorded in the database, and we’ll be adding a way to view this information in the future. We can access the data directly in the database for now if you need to know anything.
2.16.4 brings another bunch of bug fixes. We’ve much improved dealing with long file paths when deleting a drive, and also fixed a YSOD when editing a users last name. Performance of backing up large files to Backblaze has also been improved.
Introducing cloud backup of Avid project files. We’ve partnered with Backblaze to securely and safely backup Avid bins on a regular basis. There are also a full set of restore tools available. Read the full announcement for further details.
Mostly bug fixes today. We’ve included the ability to delete computers from the list of edit suites so you can keep that list tidy. Sometimes on a Mac the operating system can timeout when trying to mount a drive. The timeout duration has been reduced to 5 seconds so it doesn’t appear like everything is locked.
Under the System/Edit Suites menu you can see a list of every computer which has DIVA Client installed. This includes the version of Avid which the suite is running to make it easier to keep track of who needs updates or not. We’ve also recored their IP address to give an overview of your post network.
Despite appearances, our developers haven’t created an amazing new middle out compression algorithm and quartered the size of all your media. No, instead they just can’t add. So we’ve fixed the bug where suddenly your drives look they have a lot less used space on them.
With today’s release of Avid Media Composer 8.6.1, Avid have finally moved away from the use of .avs files for managing each project’s settings, and have fully committed to the .xml file format. Part of our project detection and sharing system relied on this .avs file existing within the project folder. We’ve modified the system so it will now work with either a .xml or a .avs.
Some of you may have noticed that you’re getting alert emails twice? Or you just ignore them anyway? Either way, we’ve stopped that annoying habit, so you’ll only get a zillion instead of a bajillion emails every day now.
Avid have recently made a change to Media Composer where to open a project, the user must have full write access to the project files. As a result, we’ve decided to remove the read permission for Avid Project drives, and convert any existing read permissions to write.
DIVA v2.13.0 introduces External Drives - this allows you to add remote network shares and FTP servers as DIVA Drives, which your editors can then easily mount in the suite. They can even be added to favourites! We’ve added to the help documentation how to add an external drive, as well as a walkthrough video.
Introducing DIVA Focus, our new cloud central monitoring platform. As all the system monitoring until now has been performed within the local system, if DIVA Server went down for any reason, we wouldn’t know about it until someone called us. Now we can monitor the health of DIVA externally, and immediately be informed if anything is wrong.
Now that OS X 10.11 El Capitan is out, as well as DAVE 13, there’s been some changes in the way that OS X mounts drives. Please note that Avid Media Composer DOES NOT officially support OS X 10.11 yet!
A tiny fix for the Windows client. With 2.10.3 we converted the client config from an ini file to the registry. At one site, some suites didn’t correctly copy over the configured server address, so crashed when trying to connect to nothing. We’ve added an extra check to make sure the config value exists, and if not, show the user the configuration screen so they can set it.
We recently discovered that sub-folders within a users folder in a project did not have the correct permissions applied, and other users could save those bins. We’ve added some background processing to ensure that doesn’t happen, as well as some other small fixes around detecting new projects.
A couple of sites have noticed problems with mounting drive favourties on Windows. This relates to the list of available drive letters not being ready by the time the user has clicked mount on the favourite. v2.9.2 resolves this problem, as well as a couple of all small tweaks.
We’ve improved the message display and handling on Client, primarily for Windows. Only important messages will be queued for when a user next connects, otherwise if they’re not online when the message is generated the message will be discarded.
There is now a number of different states for a drive, which is reflected in the Client. For example if a Node goes offline, then the drive will display as ‘Node Offline’ in the Client, and prevent a user from attempted to mount it.
Today we’re releasing DIVA v2.5.5 which contains a number of behind the scenes optimisations, mostly focused around ensuring project permissions are correct when moving bins between users and unprotected.
Features media: Can now move media from one user to another on Avid Media drives from the permissions page. client: Display drive used space on details pane. fusion: Changed layout to use a fluid width. Display drive space used and free. server: Improved error handling to nodes.