[mythtv-users] Updated script for editing recordings

[John Pilkington]

On 09/03/13 08:56, John Pilkington wrote:
> On 09/03/13 00:04, John Pilkington wrote:
>> On 08/03/13 22:26, Michael Stucky wrote:
>>> On Tue, Mar 5, 2013 at 5:02 PM, John Pilkington <J.Pilk at tesco.net
>>> <mailto:J.Pilk at tesco.net>> wrote:
>>>
>>>     On 04/03/13 13:05, John Pilkington wrote:
>>>
>>>         For several years I've been using Mythcutprojectx to process my
>>>         recordings from dvb-t, and I've used Mythpycutter less often for
>>>         recordings from dvb-t2.
>>>
>>>         http://www.mythtv.org/wiki/__Mythcutprojectx
>>>         <http://www.mythtv.org/wiki/Mythcutprojectx>
>>>         http://www.mythtv.org/wiki/__Mythpycutter
>>>         <http://www.mythtv.org/wiki/Mythpycutter>
>>>
>>>         I now have an updated script that works with 0.25-fixes and
>>>         0.26-fixes
>>>         for both dvb-t and dvb-t2.  It provides more info about what it
>>>         has done
>>>         and, although restricted to cutting at keyframes, usually cuts
>>>         where I
>>>         would like it to.  It might well be useful for other formats, at
>>>         least
>>>         for removing pre-and-post run.
>>>
>>>         The user interface is largely unchanged; I use it from the
>>> keyboard.
>>>
>>>         I am minded to remove both the above wiki entries and create
>>>         another. Is
>>>         that in line with current policy?  And if so, where?
>>>
>>>
>>>
>>>     I've put the two files, MythDVBcut.sh and pycut.py, here:
>>>
>>>     http://www.mythtv.org/wiki/__MythDVBcut
>>>     <http://www.mythtv.org/wiki/MythDVBcut>
>>>
>>>     Project-X will usually be needed.  There's a link to the latest
>>> tarball.
>>>
>>>     I hope they'll be useful - perhaps for non-DVB too.
>>>
>>>
>>>     John P
>>>
>>>
>>> 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
>>>
>>
>> Thanks for trying it.
>>
>> I'm afraid I've never seen any HDHR output.  For me HD implies DVB-T2
>> implies h264 implies avoid Project-X.  That's why I wrote Mythpycutter.
>>
>> mplex will only be used if Project-X has been used.
>>
>> The new script ought to work  (apart perhaps from a short audio glitch
>> at cutpoints) if you can set USEPJX to false on detecting HD  - but
>> audio sync will probably move at cutpoints if it's not a robust format
>> like a DVB Transport Stream, which self-corrects.
>
>
> A simple test would be to treat USEPJX as another setting-up variable
> like TESTRUN.  If it's set initially to 'false' Project-X won't be
> needed; you won't get the benefits it can give, but you should still get
> effective cutting - unless there's something unexpected in the seektable
> or a flaw in my use of PXadj$$ instead of PXraw$$ to create bytelist$$.
>
> John
>

Or, of course, it may all be OK apart from remux problems.   HD bitrate 
too high for the DVD profile.

Google throws up lots of really old posts, eg

> 5th November 2004, 21:58
> Hi windtrader,
>
> "Too many frame drop message" is caused by the bitrate being too high. For two ac3 audio tracks (both 6 ch?), a video maximum bitrate of 8900 is appropriate (9350 for one ac3 track).
>
> Best Regards,
> Bob

John