Disclaimer: This error code may encompass a few different issues that are included in your IMF's CPL. We have highlighted two of the most prevalent issues that tend to impact our partners. Should you encounter a different IMF_CPL_ERROR and require support, please SUBMIT A REQUEST via the Partner Help Center.

Error Code:

IMF_CPL_ERROR

Error Message(s):

  1. CPL Id [filename] can't be merged with Reference CPL Id [filename], since the video virtual tracks do not seem to represent the same timeline. 

  2. EssenceDescriptor with Id XXXXXX in the CPL's EssenceDescriptorList doesn't match any EssenceDescriptors within the IMFTrackFile resource that references it.

Definition(s):

  1. CPL Id [filename] can't be merged with Reference CPL Id [filename]

    This error messaging indicates that your supplemental/version composition cannot relate back to your primary composition due to a discrepancy in how these two CPLs reference one or more resources. If a delivery partner attempts to upload a new supplemental/version IMF but does not reference the most recent composition that was successfully delivered to Netflix, then you will likely encounter this error.  We can see an example of this illustrated below, where there is an
     inconsistency in how the MainImageSequence is being referred to in the CPL of the failed request(s). 

    Delivery #1:
    Here is how the MainImageSequence is being referred to in the CPL: 

    <SegmentList>
        <Segment>
          <Id>urn:uuid:XXXXXXXXXXX</Id>
          <SequenceList>
            <cc:MainImageSequence xmlns:cc="http://www.smpte-ra.org/schemas/2067-2/2016">
              <Id>urn:uuid:XXXXXXXXXX</Id>
              <TrackId>urn:uuid:XXXXXXXXXX</TrackId>
              <ResourceList>
                <Resource xsi:type="TrackFileResourceType">
                  <Id>urn:uuid:35a94143-fcb1-4690-8870-42aea2919dfe</Id>
                  <Annotation>FILENAME.mxf</Annotation>
                  <EditRate>24000 1001</EditRate>
                  <IntrinsicDuration>43863</IntrinsicDuration>
                  <EntryPoint>0</EntryPoint>
                  <SourceDuration>43863</SourceDuration>
                  <SourceEncoding>urn:uuid:XXXXXXXXXX</SourceEncoding>
                  <TrackFileId>urn:uuid:35a94143-fcb1-4690-8870-42aea2919dfe</TrackFileId>
                  <Hash>XXXXXXXXXXX</Hash>
                </Resource>
              </ResourceList>
            </cc:MainImageSequence>

    Delivery #2:
    Note how the following CPL does not reference resource: 35a94143-fcb1-4690-8870-42aea2919dfe anywhere. Thus, we are unable to match the new resources from the second CPL delivery with the MainImageSequence from the first CPL delivery due to these inconsistencies.

     <SegmentList>
        <Segment>
          <Id>urn:uuid:XXXXXXXXXXX</Id>
          <SequenceList>
            <cc:MainImageSequence xmlns:cc="http://www.smpte-ra.org/schemas/2067-2/2016">
              <Id>urn:uuid:XXXXXXXXXX</Id>
              <TrackId>urn:uuid:XXXXXXXXXX</TrackId>
              <ResourceList>
               <Resource xsi:type="TrackFileResourceType">
                  <Id>urn:uuid:XXXXXXXXXXX</Id>
                  <Annotation>FILENAME.mxf</Annotation>
                  <EditRate>24000 1001</EditRate>
                  <IntrinsicDuration>44</IntrinsicDuration>
                  <EntryPoint>0</EntryPoint>
                  <SourceDuration>44</SourceDuration>
                  <SourceEncoding>urn:uuid:XXXXXXXXXX</SourceEncoding>
                  <TrackFileId>urn:uuid:f86f7521-809a-48c3-932c-52cdd2f0d905</TrackFileId>
                  <Hash>XXXXXXXXXX</Hash>
                </Resource>
              <Resource xsi:type="TrackFileResourceType">
                  <Id>urn:uuid:XXXXXXXXXX</Id>
                  <Annotation>FILENAME.mxf</Annotation>
                  <EditRate>24000 1001</EditRate>
                  <IntrinsicDuration>62</IntrinsicDuration>
                  <EntryPoint>0</EntryPoint>
                  <SourceDuration>62</SourceDuration>
                  <SourceEncoding>urn:uuid:XXXXXXXXXX</SourceEncoding>
                  <TrackFileId>urn:uuid:a05abf53-3677-4c78-9d16-52e018128600</TrackFileId>
                  <Hash>XXXXXXXXXX</Hash>
                </Resource>



  2. Essence Descriptor mismatch (CPL - TrackFile Resource)

    There is a mismatch between an MXF TrackFile and its corresponding EssenceDescriptor information provided in the CPL.  


Solution(s):

  1. CPL Id [filename] can't be merged with Reference CPL Id [filename]

    If multiple supplemental/version packages are needed, you will need to ensure you are always implementing your fixes in the most recent supplemental/version package so the CPL reflects all changes made since the creation of the original delivery. Supplemental packages must account for every change in the evolution of the content.  Neglecting to reference the latest composition when generating supplemental/version packages will result in certain failures, as we will be unable to match new assets with previously delivered content. IMF packages are intended to build off one another in a linear fashion. These types of errors can be prevented by keeping a clear record of your IMF delivery history so that you can easily identify the latest composition and generate new supplemental/version packages accordingly. 

  2. Essence Descriptor mismatch (CPL - TrackFile Resource)

    Review the MXF track file metadata against the CPL's EssecenceDescriptorList, look for discrepancies, and make the appropriate changes. To catch this issue prior to delivery, we recommend downloading the full version of Photon from GitHub.  While https://photon.netflix.com/validate and the Photon service provided in our delivery UI performs reliable validations at the XML level, the Github version of Photon performs equivalency checks between your CPL and the MXF TrackFiles in addition to the standard XML validations. This makes the GitHub version an excellent resource for validating discrepancies between IMFTrackFile resources and how they are referenced in the CPL's EssenceDescriptorList. 
Was this article helpful?
1 out of 1 found this helpful