Jump to content

opcity error and pre roll time


Recommended Posts

Hi, I'm using two 4K h.264 contents. 

Each content is h.264 due to high bandwidth, but the file size is large.

Both contents have the same resolution and the same stage position. 

Wait for the show at the timeline position of 30 seconds. 

If the content plays from 25 seconds through an external time code, the opacity changes from 30 seconds to 1 second. 

I gave 5 seconds of preole time for B content to play properly. 

However, sometimes the opcity conversion is not applied and the content is converted to the cut. 

Currently, it is controlled through production.

 

What could be the problem? 

Does increasing pre-roll time not work in this situation? 

Isn't the pre-roll of content that doesn't appear on the screen applied?

 

timeline.png.86fe13aa7900d7a20d6f9edb7db6ea2e.png

Link to comment
Share on other sites

  • 3 weeks later...
  • Dataton Partner
12 hours ago, artboy said:

Thank you diego.

For now, we have solved it using HAP. 

However, I have a question that H.264 at 4K resolution cannot handle tweens. 

HAP is quite stable, but the problem is always file size.

There are many ways to encode H.264 wrongly for use with WATCHOUT. E.g., you should not use any B-frames! Also, H.264 puts quite some load on the cpu while HAP uses almost no performance of the cpu.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...