Dear all, especially Avid interplay transfer users and Avid engineering,
This post consists of 2 parts. 1. A question regarding a possible bug with the transfer manager engine. 2. If as a product, Avid is managing/developing/marketing the transfer manager to the extend they should.
But first the bug I see.
On a HP z400 workstation with Windows 7 64bit Sp1, MC 5.5.3.6, adrenaline with DNxHD expansion. Installing the latest version on the transfer manager client and engine (standalone setup) corrupts several dll's in the C;\Program files x86\Common files\Avid\ folder. This results in MC crashing and not recognizing the adrenaline anymore (lavaflow errors).
It could very well be that, because this version is compatible with MC 6/6.5 that it is not supposed to be used with MC 5.5.3 but the documentation does not mention MC version requirements. And here part 2 of this posts starts. (Rant possibility warning).
I'm looking into several media management solutions available in the market that can "integrate" or sit aside, with Avid MC. Avid has of course Interplay which includes the options interplay transcode, pre-encode etc... also the transfer manager is part of this. But interplay is primarily directed at broadcasters and it's price is accordingly.The transfer manager is the only part of interplay that Avid includes in the MC package and for good reasons if you ask me. But why is the documentation so horribly incomplete?
The standalone setup described with an airspeed classic simply does not work! Not only does the manual instruct the user to remove the FTP option during install, which creates the transfer engine to crash, the setup that actually works is nowhere to be found.
Alternative products I'm looking into are, Marquis project parking, Marquis sequence parking (with its medway engine) and Root6technology's Content agent. While these products are actually very different they also have many things in common.
Now Avid announced in MC7 we will now be able to do background Transcoding/consolidation (not render??? Grrr) in MC, Something the standalone transfer manager could already do more or less. Now, while many of us will be happy with this feature (asked for it for how long???) I suddenly wondered...:
AVID, in light of "opening up", using 3rd party I/O, having 3rd parties integrate AMA plug ins inside MC,.. How about opening up the transfer engine to 3rd parties like Root6 and Marquis to access it to perform media transfer/transcodes/encodes/imports/exports etc... etc... and ALL of these as background processes and with the same integration already in existence? You have never cared to build media management for post production houses, similar to never building a 2 to 4TB shared storage solution for small setups with 2 to 4 clients.
If you really believe in opening up isn't this a mayor opportunity to actually take MC's capabilities a step forward?