<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Sun, Dec 8, 2013 at 2:30 PM, Tom Dexter <span dir="ltr"><<a href="mailto:digitalaudiorock@gmail.com" target="_blank">digitalaudiorock@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div><div>On Sun, Dec 8, 2013 at 2:11 PM, Jim Stichnoth <<a href="mailto:stichnot@gmail.com" target="_blank">stichnot@gmail.com</a>> wrote:<br>
> On Sun, Dec 8, 2013 at 9:58 AM, Tom Dexter <<a href="mailto:digitalaudiorock@gmail.com" target="_blank">digitalaudiorock@gmail.com</a>><br>
> wrote:<br>
>><br>
>> On Sat, Dec 7, 2013 at 12:48 PM, Jim Stichnoth <<a href="mailto:stichnot@gmail.com" target="_blank">stichnot@gmail.com</a>> wrote:<br>
>><br>
>> > It would be enlightening if you could dump the recording markup with<br>
>> > "mythutil --getmarkup markup.xml --chanid <chanid> --starttime<br>
>> > <starttime>"<br>
>> > and post/attach the resulting markup.xml file.<br>
>> ><br>
>> > Jim<br>
>><br>
>> I sent that as an attachment. Apparently it's awaiting list moderator<br>
>> approval because of the size of the attachment.<br>
><br>
><br>
> Pretty sure there is no moderation. :) Try a <a href="http://pastebin.com" target="_blank">pastebin.com</a> link, or feel<br>
> free to email me directly.<br>
><br>
> Jim<br>
<br>
</div></div>Ah....ok. Here it is.<br>
<br>
<a href="http://pastebin.com/x6CiDUhH" target="_blank">http://pastebin.com/x6CiDUhH</a><br>
<div><div></div></div></blockquote></div><br></div><div class="gmail_extra">Offhand I don't see any problems with the markup/seektable. Here are some interesting bits:</div><div class="gmail_extra">
<br></div><div class="gmail_extra"><div class="gmail_extra"> <mark frame="0" type="33" data="3539156"/></div><div class="gmail_extra">The recording is 3539.156 seconds long, i.e. 59 minutes.</div>
<div class="gmail_extra"><br></div><div class="gmail_extra"> <mark frame="0" type="34" data="89908"/></div><div class="gmail_extra">The recording contains 89908 frames.</div><div class="gmail_extra">
<br></div><div class="gmail_extra"> <mark frame="1" type="12"/></div><div class="gmail_extra">The recording is identified as 16:9 aspect ratio.</div><div class="gmail_extra"><br></div><div class="gmail_extra">
<mark frame="1" type="30" data="1920"/></div><div class="gmail_extra"> <mark frame="1" type="31" data="1080"/></div><div class="gmail_extra">
<mark frame="1" type="32" data="29970"/></div><div class="gmail_extra">The recording is identified as 1920x1080@29.97, i.e. 1080i.</div><div class="gmail_extra"><br></div><div class="gmail_extra">
The interesting bit is that frames/framerate = 89908/29.97 = 3000s = 50 minute length, which is what 0.25 incorrectly reports.</div><div class="gmail_extra"><br></div><div class="gmail_extra">The bulk of the file is seektable data, e.g.:</div>
<div class="gmail_extra"><div class="gmail_extra"> <seek frame="15" type="9" data="1050920"/></div><div class="gmail_extra"> <seek frame="15" type="33" data="501"/></div>
<div class="gmail_extra">This says that frame 15 is a keyframe (only keyframes are listed here) and that it is 1050920 bytes and 501ms from the start of the file.</div><div class="gmail_extra"><br></div><div class="gmail_extra">
Looking at the differences from one seektable entry to the next, it seems that the framerate is quickly and mostly randomly bouncing between 24fps and 30fps. This is most likely due to insertion of the repeat_pict flag which tells the player to show the frame for an extra half frame interval.</div>
<div class="gmail_extra"><br></div><div class="gmail_extra">All in all, it looks in order and is exactly what the 0.27 recorder and player (including mythcommflag --rebuild) changes were designed to handle.</div><div class="gmail_extra">
<br></div><div class="gmail_extra">In rereading the thread, it seems that at this point you're saying that with this rebuilt seektable, during playback it always shows a length of 52 minutes, right? I have no explanation for that. It would be very helpful to get a copy of the 6GB recording file to try to reproduce the issue. (Given your gmail account, you could probably upload it using Google Drive and share it as you like, if you have the time/capacity/patience.)</div>
<div class="gmail_extra"><br></div><div class="gmail_extra">Jim</div></div></div></div>