pre-roll opcity error and pre roll time

[artboy]

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?

 

[Diego Marchente]

Hi,

I advise you to use HAP files for better performance on files with large resolutions... I don't understand all this passion for H264 files since it has several defects and questionable performance if you don't use a dedicated coprocessor like for Watchpax.

Best regards.

Diego

[artboy]

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.

[RBeddig]

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.

[jfk]

5 hours ago, RBeddig said:

There are many ways to encode H.264 wrongly for use with WATCHOUT. E.g., you should not use any B-frames! …

I want to amplify that statement. Incorrect parameters in h.264 / mp4 / mp2 files will result in random crashes. It would be better if those crashes would occur the first time it is played, but that is never the case. The improper parameters in a file will appear to be ok. The crash will eventually occur at an unpredictable amount of time. So it is crucial that the various parameters be correct or you are likely adding a time bomb. That said, there are users who have achieved reliable success with h.264 / mp4 / mp2 by correctly encoding the files. This requires an intimate understanding of your encoding tools and encoding parameters. aka encoding voodoo

It is important to note that the default h.264, mp4, mp2 encoding parameters of just about any encoding tool out there are the wrong parameters. You must tune h.264, mp4, mp2 encoding settings for WATCHOUT.

There are no such issues with HAP. About the only parameter is chunks, get it wrong and large dimension video may not run smoothly, but it will not crash the system.