We ran into an issue with package when installed on a clean system. It seems that one of the DLLS included with latest VC14 release of media processors is dependant on the VS 2013 c++ lib support. According to a dependancy walker - FTF.DLL (dated 2016-10-13) is dependant on MSVCR120.DLL and MSVCP120.DLL. When installing on a clean system, this library

So... I was able to reverse engineer the issue with the AMT2 making proxy (mpeg1/layer 2) audio for audio only clips. As a recap - I was seeing the file start offset in the AMT2 generated file (file mob) being offset from the actual clip master mob start offset (values in audio samples). All rates were not correct EXCEPT for 29.97 DF and 59.94 DF. I

Hello, I am attempting to use AMT2 to add proxy audio tracks to existing clips with PCM (24 bit WAB) MXF files. The problem that I am encountering is that in the created proxy audio files - the start offset for the source mob is incorrect for all rates that are NOT 29.97 or 59.94 drop frame. These two rates work correctly. If I attempt NDF (with properties

Hi all, Looks like the mxf files have multiple ID blocks that I wasn't extracting fully with the generic dump. Here is the full list of ID blocks. Looks like Media Processor created these XDCAM-EX 35 files. AMT2 throws an access violation with them when calling OpenMxfFile. [ K = MXFIdentification ( 000000000001e9c7 ) 06.0e.2b.34.02.53.01.01.0d

This is a feature request for AMT3/Media Processor: AMT3 provides for adding user attributes to newly created clips via the AAF created. Would it be possible to add support for shot locators as well to be attached an imported with the same AAF file? (with locator text and color support). As we migrate from AMT2 and the open source AAF toolkit to AMT3

Hi all, Hoping that there can be some feedback on this issue - it seems that some Avid products create MXF in some formats that can't be opened with AMT2 - latest SDK. Not looking for AMT2 to be fixed - just to have the missing??? metadata (likely dark metadata) added that is causing this. In this case it is XDCAM media. More on this issue - another

Hello, I am trying to locate the most recent avid-acs-proxybal-net package? We are using currently: avid-acs-proxybal-net.2.5.1-build-0013-g4c233a3 Thanks in advance! Rich

Just an FYI for the developer team... I am seeing output to the console when the VC14 media processor 4.4.22.10044 - unloads at program exit. Just before console closes - I see: "log4cplus: ERROR Derived Appender did not call destructorImpl()" Same application with the VC12 version of the libraries does not show this output. Doesn't seem

More details on this issue... The customer provided us with some XDCAM50 clips (25 fps interlace) created with the same process - Interplay MAM 4.9.5.10037. These work with NO issues with our AMT2 product. An MXF dump of the XDCAM 50 video file shows metadata that is not present in the other formats mentioned (e.g. coding equations). Based on previous

More details on this issue... The customer provided us with some XDCAM50 clips (25 fps interlace) created with the same process - Interplay MAM 4.9.5.10037. These work with NO issues with AMT2 product. An MXF dump of the XDCAM 50 video file shows metadata that is not present in the other formats mentioned (e.g. coding equations). Based on previous experience