[mythtv-users] Updated script for editing recordings

[Michael Stucky]

On Sat, Mar 9, 2013 at 9:09 AM, John Pilkington <J.Pilk at tesco.net> wrote:

>
>      I've put the two files, MythDVBcut.sh and pycut.py, here:
>>>>>
>>>>>     http://www.mythtv.org/wiki/__**MythDVBcut<http://www.mythtv.org/wiki/__MythDVBcut>
>>>>>     <http://www.mythtv.org/wiki/**MythDVBcut<http://www.mythtv.org/wiki/MythDVBcut>
>>>>> >
>>>>>
>>>>>  <snip>
>
>
>  This works well for SD content, I like the improved cutlist creation
>>>>> logic. But, as with mythcutprojectx, the script fails on HD content
>>>>> (HDHR tuner). 'mplex' gives about a dozen  "++ WARN: [mplex] Stream e0:
>>>>> data will arrive too late ..." and then "**ERROR: [mplex] Too many
>>>>> frame
>>>>> drops -exiting".
>>>>>
>>>>> Mike
>>>>>
>>>>>
> <snip>
>
>
>  Or, of course, it may all be OK apart from remux problems.   HD bitrate
>> too high for the DVD profile.
>>
>>
> I see something like this:
>
> INFO: [mplex] rough-guess multiplexed stream data rate    : 4333744
>    INFO: [mplex] target data-rate specified               : 10080000
>    INFO: [mplex] Setting specified specified data rate: 10080000
>
> man mplex says:
>     -r|--mux-bitrate num
>               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
>               stream.
>
> ... so it could be worth adding --mux-bitrate 20000
>
> to the mplex command for an HD recording.  No promises.
>
>
> John
>
>
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.

Mike
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mythtv.org/pipermail/mythtv-users/attachments/20130309/05012c5d/attachment.html>