<div dir="ltr"><div class="gmail_quote">On Wed, Oct 8, 2008 at 3:18 PM, Brad DerManouelian <span dir="ltr"><<a href="mailto:myth@dermanouelian.com">myth@dermanouelian.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div style=""><div class="Ih2E3d"><div><div>On Oct 8, 2008, at 3:10 PM, Scott Kidder wrote:</div><br><blockquote type="cite"><div dir="ltr"><br><div class="gmail_quote">On Wed, Oct 1, 2008 at 11:40 AM, 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="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <div dir="ltr">I took a couple of screen shots to show the problem more clearly. I paused the input source (an SD DirecTiVo), then ran either "v4l2-ctl -b cc" or "v4l2-ctl -b off" to turn closed captioning on or off, and then captured a frame using xine. If you flip back and forth between the two images, it's clear that the first several lines are being cropped and everything shifted up when cc is enabled. It's also interesting that even with the uncropped picture, the VBI stuff has apparently already been removed. If I had to guess, I would say that VBI removal is being done twice when cc is on. (I would prefer that VBI were not removed at all, so that MythTV overscan or whatever could be applied consistently to all inputs.)<br>
<br>cc on: <a href="http://www.flickr.com/photos/37377999@N00/2905480460/sizes/o/" target="_blank">http://www.flickr.com/photos/37377999@N00/2905480460/sizes/o/</a><br>cc off: <a href="http://www.flickr.com/photos/37377999@N00/2905480878/sizes/o/" target="_blank">http://www.flickr.com/photos/37377999@N00/2905480878/sizes/o/</a><br>
<br></div></blockquote></div><br>I have an identical problem with recordings made on my PVR-150 through the composite inputs. Mine matches the 'CC On' image. I'd basically given up on this problem until I saw your message! For what it's worth, here's the IVTV output for my PVR-150 card:</div>
</blockquote><br></div></div><div>Have you tried asking on the ivtv mailing list? This is clearly an ivtv issue and they would be much more knowledgeable about why this is happening. It looks intentional to me, but I don't know why.</div>
<div></div></div></blockquote><div><br>Being new to MythTV, I only recently learned the relationship between mythtv and ivtv. I'll find the ivtv list and pursue it there. Thanks for the pointer.<br><br>Jim <br></div>
</div></div>