<div dir="ltr"><div class="gmail_quote">On Mon, Aug 18, 2008 at 6:19 PM, Allen Edwards <span dir="ltr"><<a href="mailto:allen.edwards@oldpaloalto.com">allen.edwards@oldpaloalto.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div class="Ih2E3d">> If you need more help, you will probably have to give more detail. How many<br>> boxes, frontend/backend/both? What motherboards, processors, memory, disks,<br>> operating systems, Mythtv versions, etc.<br>
<br><br></div>OK, this is getting strange. I have discovered that the front end<br>locks up if I try and play any show form Channel 9 (KQED) recorded<br>after 8/15. I can play any channel 9 show before 8/15 and I can play<br>
any show on any other channel. Any show from Channel 9 previews and<br>looks like a gray screen with some attempt at showing the content of<br>the show in little flickering blocks, maybe 1 inch by 1/4 inch. I have<br>been calling that digital noise.</blockquote>
<div> </div>
<div>Sounds like a damaged recording that Myth doesn't handle well. Can you try playing the file with -v playback on the mythfrontend command-line and seeing if there is anything interesting in the logs? The fact that mplayer plays it just means that perhaps it copes better with an error or particular recording feature of the file. Another option would be to force mplayer to use the ffmpeg codec (-vf ffmpeg I think, but check -vf help for details) which should closely resemble MythTV's playback which might also give you more information. Also, does this vary between recordings made on your HDHR vs. Air2PC? If possible, try recording once off of each to see if there is any difference.</div>
<div> </div>
<div>Kevin</div></div></div>