<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=gb2312"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:ËÎÌå;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"\@ËÎÌå";
panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoNormal>Hi LIVE555 Streaming Media<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>We just met a problem about calculating fps when open <i>timing_info_present_flag </i>in H265 case<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>In our case, we set <i>timing_info_present_flag</i> to 1 and fill <i>vui_num_units_in_tick</i> and <i>vui_time_scale</i>, in order to help LIVE555 to calculate frame per second. But we set <i>frame_field_info_present_flag</i> to zero, so according to the SPEC of H265, the number of <i>DeltaToDivisor</i> should be one(shown in the following picture)<o:p></o:p></p><p class=MsoNormal><img width=899 height=132 id="ͼƬ_x0020_1" src="cid:image001.png@01D55130.E0C27CA0"><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>In our code now, the <i>DeltaToDivisor</i> is set to two by default in the constructed function of class H264or5VideoStreamParser, and it will be updated in the function analyze_sei_payload if set <i>frame_field_info_present_flag </i>to one. So if we close the <i>frame_field_info_present_flag</i> flag, the number of <i>DeltaToDivisor</i> will not be changed. When calculate the fps, the equation is time_scale/(DeltaTfiDivisor*num_units_in_tick), we get a wrong fps number because <i>DeltaToDivisor</i> is two not one. The wrong value is exactly half of the expected value. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>About this problem, do you have any official patch to solve it?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Thanks<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>