<br><br><div class="gmail_quote">On Thu, Nov 15, 2012 at 9:52 PM, HP-mini <span dir="ltr"><<a href="mailto:blm-ubunet@slingshot.co.nz" target="_blank">blm-ubunet@slingshot.co.nz</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, 2012-11-14 at 14:55 -0500, Doug Vaughan wrote:<br>
> Brett,<br>
> As tosuggestion #3. Lossless Cut always, even when there was noskip or<br>
> cut list, starts the first segment on the first non-zero keyframe as<br>
> identified in the seek table. That was done to avoid the video<br>
> corruption which displaysat the very beginning of the recorded file<br>
> prior to thefirst keyframe. Basically I tried to account for the issues<br>
> you are describing before the first keyframe.<br>
><br>
</div>I was trying to describe an inconsistency between mythtv playback &<br>
cut-list editor..They show different picture at the same frame index..<br>
The behaviour before the first keyframe is a clue maybe not the cause.<br>
I was trying to explain how ffmpeg decoder could influence this..<br>
This offset error would apply at any point in recording.<br>
<br>
I have "start on sequence header" selected, I see no corruption in start<br>
of playback, just the odd cut-list editor navigation..<br>
<div class="HOEnZb"><div class="h5"><br><br></div></div></blockquote><div><br>Just a question about this thread in general, how do you tell from mythtv's editor whether the frame you are on is a keyframe or not? Is it guesswork from scene transitions? Or is it theme dependent ( I tried arclight and blue abstract and couldn't see any info on this). <br>
</div></div><br>