<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Fri, Dec 28, 2012 at 10:10 AM, Doug Vaughan <span dir="ltr"><<a href="mailto:r.d.vaughan@rogers.com" target="_blank">r.d.vaughan@rogers.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">Eric,<br>
Which device made the recordings? If it is an HDHomerun then recordings from that device is mentioned in the Lossless Cut wiki as being problematic. If you are not using a HDHomerun then create a bugreport. Seeinstructions on the wiki page:<br>
<a href="http://www.mythtv.org/wiki/Lossless_Cut#Bug_Reporting" target="_blank">http://www.mythtv.org/wiki/<u></u>Lossless_Cut#Bug_Reporting</a><br>
<br>
Please use the "-B" option which will include a 25Mg sample of the problem video file. The accuracy of Lossless Cut is totally bound to the ability of the mkvmerge utility to properly read the recorded video file and the accuracy of the MythTV keyframes in the recordedmarkup table. The cut pointsare a calculation of their location in the formula:<br>
keyframe * Framesper second = HH:MM:SS.nnnnnnnnn (down to the nano second)<br>
<br>
If the recorded file cannot have its cut points calculated that way (e.g. some HDHomerun recordings) then the mkvmerge's cuts will not be inaccurate.<br>
<br>
Doug<br></blockquote><div><br></div>Thanks Doug,<div>The recordings were made from an hdhomerun prime. Are all of the hdhomeruns included in this bucket of problematic devices? </div></div><br></div></div>