<div dir="ltr">On Sat, Mar 9, 2013 at 3:47 PM, Michael Stucky <span dir="ltr"><<a href="mailto:mike@stucky.us" target="_blank">mike@stucky.us</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr"><div><div class="h5">On Sat, Mar 9, 2013 at 10:11 AM, Michael Stucky <span dir="ltr"><<a href="mailto:mike@stucky.us" target="_blank">mike@stucky.us</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr"><div><div>On Sat, Mar 9, 2013 at 9:09 AM, John Pilkington <span dir="ltr"><<a href="mailto:J.Pilk@tesco.net" target="_blank">J.Pilk@tesco.net</a>></span> wrote:<br></div></div><div class="gmail_extra">
<div class="gmail_quote"><div><div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div><br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
I've put the two files, MythDVBcut.sh and pycut.py, here:<br>
<br>
<a href="http://www.mythtv.org/wiki/__MythDVBcut" target="_blank">http://www.mythtv.org/wiki/__<u></u>MythDVBcut</a><br>
<<a href="http://www.mythtv.org/wiki/MythDVBcut" target="_blank">http://www.mythtv.org/wiki/<u></u>MythDVBcut</a>><br>
<br>
</blockquote></blockquote></blockquote></blockquote></div>
<snip><div><br>
<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
This works well for SD content, I like the improved cutlist creation<br>
logic. But, as with mythcutprojectx, the script fails on HD content<br>
(HDHR tuner). 'mplex' gives about a dozen "++ WARN: [mplex] Stream e0:<br>
data will arrive too late ..." and then "**ERROR: [mplex] Too many<br>
frame<br>
drops -exiting".<br>
<br>
Mike<br>
<br>
</blockquote></blockquote></blockquote></blockquote>
<br></div>
<snip><div><br>
<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Or, of course, it may all be OK apart from remux problems. HD bitrate<br>
too high for the DVD profile.<br>
<br>
</blockquote>
<br></div>
I see something like this:<br>
<br>
INFO: [mplex] rough-guess multiplexed stream data rate : 4333744<br>
INFO: [mplex] target data-rate specified : 10080000<br>
INFO: [mplex] Setting specified specified data rate: 10080000<br>
<br>
man mplex says:<br>
-r|--mux-bitrate num<br>
The total (non VBR) / peak (VBR) bit-rate of the output stream in k Bits/sec. If unspecified and not set by a preset it is automatically calculated from the input<br>
stream.<br>
<br>
... so it could be worth adding --mux-bitrate 20000<br>
<br>
to the mplex command for an HD recording. No promises.<div><div><br>
<br>
John<br><br></div></div></blockquote><div><br></div></div></div><div>I read some of those same suggestions and had tried --mux-bitrate as high as 9600. Will test with higher rates and see if that makes a difference.</div>
<div>
<br></div><div>Mike </div></div></div></div>
</blockquote></div><br></div></div></div><div class="gmail_extra">Success!! I had to increase --mux-bitrate to 50000 (about 5x the rate estimated by mplex) to get a clean run of mplex on 720p mpeg2 HD content from an HDHR tuner. Will test with 1080i content later today.</div>
<div class="gmail_extra"><br></div><div class="gmail_extra">Mike</div></div>
</blockquote></div><br>Further tests indicate that a trial-and-error process is/maybe required for each HD recording (channel??) to get a clean run of mplex. The only way I have been able to get consistent results is to use mythffmpeg to remux into an mkv container.</div>
<div class="gmail_extra"><br></div><div class="gmail_extra">mythffmpeg -fflags +genpts -i $DEMUXPREF.m2v -i $DEMUXAUDIO -vcodec copy -acodec copy "$OUTFILE"<br></div><div class="gmail_extra"><br></div><div class="gmail_extra" style>
Where $OUTFILE is the recording name with an .mkv extension. I move the resulting file to my Video storage group, the file is playable on my MythFEs and all my other media players.</div><div class="gmail_extra" style><br>
</div><div class="gmail_extra" style>Mike</div></div>