Hello,

We are interested to know how to access growing file in Avid PAM environment with ISIS storage using web service.

Thanks,

Hi Vijeta,

Please provide more details on the access you're looking into for a growing file. In general there are no restrictions other than requests can be done to available media part only and subclips creation may be limited until file is complete.

You may retrieve Frame Chase Expected/Known Duration attributes for a clip to figure out if the clip is growing and how much media is available.

Thanks.

Here's what the call to GetAttributes() would looke like:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:typ="http://avid.com/interplay/ws/assets/types">

   <soapenv:Header>

      <typ:UserCredentials>

         <typ:Username>user</typ:Username>

         <typ:Password>pass</typ:Password>

      </typ:UserCredentials>

   </soapenv:Header>

   <soapenv:Body>

      <typ:GetAttributes>

         <typ:InterplayURIs>

<typ:InterplayURI>interplay://WGC?mobid=060a2b340101010101010f0013-000000-0000000b223714ee-060e2b347f7f-2a80</typ:InterplayURI>

         </typ:InterplayURIs>

           <typ:Attributes>

            <typ:Attribute Group="USER" Name="Display Name"/>

            <typ:Attribute Group="SYSTEM" Name="Frame Chase Expected Duration"/>  

            <typ:Attribute Group="SYSTEM" Name="Frame Chase Known Duration"/>  

         </typ:Attributes>

      </typ:GetAttributes>

   </soapenv:Body>

</soapenv:Envelope>

Here's the response for a growing file:

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">

   <soap:Body>

      <GetAttributesResponse xmlns="http://avid.com/interplay/ws/assets/types">

         <Results>

            <AssetDescription>

               <InterplayURI>interplay://WGC?mobid=060a2b340101010101010f0013-000000-0000000b223714ee-060e2b347f7f-2a80</InterplayURI>

               <Attributes>

                  <Attribute Name="MOB ID" Group="SYSTEM">060a2b340101010101010f0013-000000-0000000b223714ee-060e2b347f7f-2a80</Attribute>

                  <Attribute Name="Moniker" Group="SYSTEM">1|EF4A65FA-4B30-4319-808D-AE7D316F5DCB|*|17354|*</Attribute>

                  <Attribute Name="Display Name" Group="USER">Trans_20Secs</Attribute>

                  <Attribute Name="Frame Chase Expected Duration" Group="SYSTEM">00:00:20:00</Attribute>

                  <Attribute Name="Frame Chase Known Duration" Group="SYSTEM">00:00:12:05</Attribute>

               </Attributes>

            </AssetDescription>

         </Results>

      </GetAttributesResponse>

   </soap:Body>

</soap:Envelope>

I've discovered that applications which support frame-chasing set the "Record Complete" attribute to "0" while the media is being captured, and "1" when capture is complete. So an easy way to include or exclude growing files from searches is to test the value of this attribute.