<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Wed, Jan 16, 2013 at 7:05 PM, Jim Stichnoth <span dir="ltr"><<a href="mailto:stichnot@gmail.com" target="_blank">stichnot@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Wed, Jan 16, 2013 at 1:53 PM, Jim Stichnoth <<a href="mailto:stichnot@gmail.com">stichnot@gmail.com</a>> wrote:<br>
> On Wed, Jan 16, 2013 at 11:47 AM, Larry T <<a href="mailto:larryt@gmail.com">larryt@gmail.com</a>> wrote:<br>
>> | 1036 | 2013-01-14 05:00:00 | 0 | 33 | 319496 |<br>
><br>
> There it is. The recordedmarkup table thinks the recording length is 319.496s.<br>
><br>
> You can see the meaning for the various values of the "type" column at<br>
> <a href="https://github.com/MythTV/mythtv/blob/master/mythtv/libs/libmyth/programtypes.h#L52" target="_blank">https://github.com/MythTV/mythtv/blob/master/mythtv/libs/libmyth/programtypes.h#L52</a><br>
> .<br>
><br>
> Something very strange is happening to the recording at frame 5819 -<br>
> resolution is reported to have changed from 480x480 to 3819x2242.<br>
> Then at frame 6210 it switches to 3719x896@25Hz, and at frame 6224 it<br>
> finally settles at 480x480@29.97Hz. I don't know if it is at all<br>
> related to the incorrect duration.<br>
><br>
> What does the recordedmarkup table for that recording look like after<br>
> running "mythcommflag --rebuild --chanid <mychanid> --starttime<br>
> <mystarttime>" ?<br>
<br>
</div>Never mind. I'm pretty sure this has to do with mythcommflag. In<br>
0.26, there are several ways that the duration stored in the database<br>
is determined. After a recording finishes, the duration is written as<br>
the number of seconds between the start time and end time of the<br>
recording. Mythcommflag separately calculates the duration as the sum<br>
of the individual frame intervals processed during the final pass over<br>
the recording. "Mythcommflag --rebuild" and "mythtranscode<br>
--buildindex" simulate playing all frames and similarly sum up the<br>
frame intervals. I suspect that when mythcommflag runs, the final<br>
pass is not looking at every frame, but instead doing an optimization<br>
where it samples every nth frame.<br>
<br>
Can you tell me what your mythcommflag settings are? Go to Settings ><br>
Video > General > Page 3 (Jobs). What is the setting for "Commercial<br>
detection method", and which checkboxes are checked ("Enable<br>
experimental speedup of commercial detection" and "Strict commercial<br>
detection")? My system has "All available methods", experimental<br>
speedup unchecked, strict commercial detection checked. I've never<br>
seen such duration problems on my system.<br>
<div class="HOEnZb"><div class="h5"><br>
Jim<br>
_______________________________________________<br>
mythtv-users mailing list<br>
<a href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a><br>
<a href="http://www.mythtv.org/mailman/listinfo/mythtv-users" target="_blank">http://www.mythtv.org/mailman/listinfo/mythtv-users</a><br>
</div></div></blockquote></div><br></div><div class="gmail_extra">My settings mirror yours on one frontend that I checked. I have 2 frontends but neither is on the system that has the PVR-150. The PVR-150 is headless and is configured through mythbuntu to not have the frontend installed. I am not sure if these settings are universal across all or machine specific... As always, let me know if there is some other way I should check for the settings on the specific server in question. <br>
</div></div>