Forum Post

CM_Analyze - Warnings
Hello, I'm relatively new to using Dolby Vision, and I've been experimenting with cm_analyze using a 422HQ Master I exported from Davinci's free version. I have a pretty good grasp when it comes to figuring out the right commands. But there's an issue I've been seeing pop up whenever I'm generating the xml file. It's possible these are a nonissue, and I'm freaking out over nothing. But with how new I am to this, I figured I vet it first before moving on. The errors are as follows:

WARNING skipping empty shot
WARNING contiguous shots have same source (AX), maybe it's a dissolve?
WARNING contiguous shots have same source (BL), maybe it's a dissolve?
WARNING non contiguous shots, not sure why, so filling space with another shot

For additional context, I exported an EDL from Davinci to use for the shot list. And I did include several dissolves in this edit. But that's as far as I know in terms of errors. Any help is appreciated.

  • SylarM (Dolby Labs)

    Hi,

    Thanks for reaching out to us.

    Did you complete the analyzing process with the warning messages? If so did you try to valide the XML out of the analysis? Accoring to you messages, there is possibility that you can still manage to complete the analysis with the warning message. The warning messages are there to provide a reminder and may still generate a valid Dolby Vision XML file, for example, skipping empty shot - do you have a gap or black shot on your timeline? This is a reminder that the algo will treat the gap/black as a black shot.

    Let us know we can help to investigate futher.


    Best
    Sylar Ma
    Expand Post
  • Hello,

    Yes, I was able to complete the analyzing process. And I also validated the XML with metafier. You are correct in assuming that the 'skipping empty shot' warning was for a gap/black shot in my timeline. And the contiguous shot warnings were dissolves in the timeline. Based on your answer, I assume that means the warning messages are not something to worry about? I also wanted to note that metafier left this note at the end of the process:

    04/09/2026/09:48:07.879262500 Metadata: WARNING List of WARNINGS:
    =========================
    WARNING: No L8 Trims found
    =========================
    04/09/2026/09:48:07.1380253834 metafier: INFO No issues found in the Metadata

    Should I be concerned about the warning? Because otherwise, I'm content moving forward with this metadata for my edit if everything else is fine.
    Expand Post
    • SylarM (Dolby Labs)

      Hi.

      Yes you are right. Dolby Vision metadata XML with warning messages is still techinial valid. It will not triger QC fail as long as the warnings are allied with your video essence on the timeline.
      The metafier warning mearns you did not create trim metadta, which is still valid.

      If you want to learn more about Dolby Vision content creation workflow. We have free of charge online learning course. Check it out here:
      learning.dolby.com.


      Best
      Sylar Ma
      Expand Post
  • The only thing I'm having issue now is frame mismatch. I'm running a test from five minutes of my Master. The total frame count of the metadata is 7182 when I convert the xml to an RPU bin. But my Master is 7200. What could be causing this discrepancy?
    • I discovered why the frame count is smaller. It's skipping the first 18 frames when analyzing my Master. How do I stop this from happening. And also how do I stop it in general from skipping not including frames?