Latest post Fri, Jul 13 2018 9:10 PM by jkalbfleisch. 3 replies.
Page 1 of 1 (4 items)
Sort Posts: Previous Next
  • Wed, Jul 11 2018 9:05 PM

    setting Duration using ipws.setAttributes

    Is there a way to set Duration of a masterclip using ipws?


    SYSTEM are readonly and if I put the full string its longer than 30 which ipws does not like?


    #attribute_name = "com.avid.workgroup.Property.System.Duration"

    attribute_name = "Property.System.Duration"

    attribute_value = "00:31:26:18"


    ipws_attributes = []

    value_collection = collections.OrderedDict()

    value_collection["@Group"] = "USER"

    value_collection["@Name"] = attribute_name

    value_collection["#text"] = attribute_value



    The propblem being if I dont set it cloudUX does not like that.


  • Thu, Jul 12 2018 1:56 PM In reply to

    Re: setting Duration using ipws.setAttributes

    I am wondering if maybe I just need to login using credentials that have admin privledges and just set Duration for group System.


    It seems to me there must be a way to set variables that are required by interplay/CloudUX, I am just missing what it is.

  • Fri, Jul 13 2018 8:44 PM In reply to

    • Vadym
    • Not Ranked
    • Joined on Thu, Apr 17 2014
    • Posts 196
    • Points 2,445
    • Avid Developer Moderator
      Avid Employee

    Re: setting Duration using ipws.setAttributes

    Hi Jeff,

    There is no possibility to set duration as well as other system attributes through IPWS as you've correctly mentioned.

    Masterclip duration (and start time) is set on ingest for the media present.

    Sequence duration comprises of the lenght of all the cuts it contains.

    Could you provide more details on the issue with the error message above?


  • Fri, Jul 13 2018 9:10 PM In reply to

    Re: setting Duration using ipws.setAttributes

    I think that means we have to set duration in the aaf and check that in. The error comes up when you try to load the logging pane in cloudUX. Which seems to be saying Duration must be set for certain functionality in interplay and cloudUX to work right. I am also thinking there will be some testing to recheck in aafs over and over until we have figured out all of the SYSTEM variables that must be set in the aaf in order for cloudUX/interplay to be happy with the master clip. If you had a list of all of the SYSTEM properties that "must" be set we could start with that.


    I think the issue may be comming up due to we are not using an ingest servicewe are dropping files onto NEXIS and checking in the aaf. So that process of setting stuff during ingest wont be happening.

Page 1 of 1 (4 items)

© Copyright 2011 Avid Technology, Inc.  Terms of Use |  Privacy Policy |  Site Map |  Find a Reseller