<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
K Stanton wrote:
<blockquote cite="mid468586B2.40401@comcast.net" type="cite">A year ago
I was having problems with 0.19 with recording that changed
resolutions (526x480 vs 704x480):<br>
<a class="moz-txt-link-freetext"
href="http://www.gossamer-threads.com/lists/mythtv/users/188895">http://www.gossamer-threads.com/lists/mythtv/users/188895</a><br>
<br>
I was doing fine with 0.20-fixes
both packaged from Axel and compiled myself under FC4. More recently I
tried FC6 and svn 0.20.1 13460 and 13645 from Axel. Analog tuners were
working, and playback of both digital and analog, but I wasn't able get
my digital tuners working, so I moved on...<br>
<br>
I recently upgraded to svn 0.21-trunk 13726 to get an HD Homerun
working and recording directories. Now I'm experiencing all the
problems from a year ago. Again, this is DVB, and the problems are all
because of Comcast Northwest New Jersey interjecting commercials at
lower resolution than
the main video:<br>
<br>
- mythcommflag time skew after a lower-resolution segment - later
flags skew earlier by the cumulative amount of time of previous
low-resolution segments<br>
- commercial skipping a segment with lower resolution will result
in a frontend seg fault<br>
- skipping forward IN to the lower-resolution portion will
result in a pause then continuing of video<br>
- skipping forward OUT of the lower-resolution portion will
result in a frontend seg fault - rarely it will make it through the
transition, but only with garbled video<br>
<ul>
</ul>
So, would you have any clues as to why my problem is back? I took a
quick scan of the changelog/timeline and didn't see anything obvious.<br>
<br>
Thanks,<br>
Kevin<br>
<br>
</blockquote>
Resolved, for the moment... I changed playback from "Standard" to
"libmpeg2", and that did the trick. I should have thought of that
before! Curious how ffmpeg _used_ to work for this issue, but now not.<br>
<br>
mythcommflag still becomes time-skewed by the cumulative duration of
the lower resolution segments, but at least there are no crashes :)<br>
</body>
</html>