3.7 PAM engine should not have influence. On the other side what is the MI version in you environment. This may have some impact after update from MI is triggered.

Hi Rich, We have tested the spanned AAFs we have from the last time and see no issues with IPWS 3.8 Could you please provide a fresh set of clips that you still experience issues with in 3.8? Thanks

Hi, The issue is described as using the same instance of AMT to write hi-res then proxy resolutions of the same masterclip. The recommendation is to start separate AMT instance for each masterclip. Thanks

Hi Radha, Also I forgot to mention the Avid Media Connector service (AMC) that may actually do what you need and is controllable through REST API. Please contact us at the following page for info and pricing http://www.avid.com/alliance-partner-program/partner-with-avid Thanks, Vadym

Only AAF files can be imported (checked-in) into Interplay. MXF files stay on the Nexis/ISIS workspace. Non-AAF files will be treated as non-Avid assets making them not available to Avid products to process. Nexis workspaces can be mounted using Nexis client as a regular Windows file share. Then you can access files on it as any other files, mind the

Hi, Interplay Production contains assets with metadata only, media typically goes to Nexis/ISIS mov and ts files have to be transcoded into Avid supported format OpAtom MXF and metadata AAF before it could be added into Interplay. Interplay web services do not handle media. It is possible to get media file locations of the assets then retrieve media

Hi Nicolas, You can use Interplay Production Services and Transfer Status application or the similar feature of Interplay Access to monitor transcode queue to see exactly what MediaCentral does in this case. Also IMX belongs to the family of MPEG2 codecs so you'll have to use STPEncode (longGOP export) to render your sequence for playback. Thansk

Jeff, Please test the whole thing with sudo -i or root with default options and see if that works first. Also the instability you're seeing would most likely be caused by demo ISIS and non matching File Gateway hardware

Hi Jeff, Where are all the parameters in your command line are coming from? In my case I simply use mount.cifs //filegw/workspace ./test -o user=test and subsequent commands like touch work just fine for me. If I look into the default parameters used to mount I see the following for deb machine: (rw,relatime,vers=1.0,cache=strict,username=test,domain

Hi Tomerb, First of all Interplay PAM manages metadata separately from media. The check-in operation is to submit asset metadata into PAM database which comes in a form of AAF. AAF metadata is something what AMT can generate as a part of "AMT archive". If you have AMT DLL sample app successfully compiled please take a look at the RAW_TO_AMT