<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">On Apr 21, 2015, at 1:35 PM, Ryan Lavender <<a href="mailto:ryanlavender@comcast.net" class="">ryanlavender@comcast.net</a>> wrote:<br class=""><div><blockquote type="cite" class=""><br class="Apple-interchange-newline"><div class=""><span style="font-family: Calibri, Verdana, Helvetica, Arial; font-size: 15px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">Can someone point me in the right direction for writing a patch to get MythTV to discard fill packets?</span></div></blockquote></div><br class=""><div class="">If Richard’s suggestion doesn’t work for you try queueing a lossless transcode from the recordings display: Menu -> Job Options -> Begin Transcoding -> Default. There’s a myth-setup option that has be be selected but it’s on by default. Besides executing a cut list the process cleans recordings of transport stream artifacts that aren’t needed for playback. Without a cut list it’s essentially a cleaning operation, you’ll know if it worked by the before / after file sizes.</div><div class=""><br class=""></div><div class="">- George</div></body></html>