[mythtv-users] Compiling 0.25-fixes mythtranscode against 0.26 library's is it possible?

[Michael Stucky]

On Wed, Jul 3, 2013 at 9:00 AM, John Pilkington <J.Pilk at tesco.net> wrote:

> On 03/07/13 12:57, Anthony Giggins wrote:
>
>>
>>
>> On 7 January 2004 01:14, John Pilkington <J.Pilk at tesco.net
>> <mailto:J.Pilk at tesco.net>> wrote:
>>
>>     On 03/07/13 12:31, Anthony Giggins wrote:
>>
>>
>>
>>         On 3 July 2013 17:35, John Pilkington <J.Pilk at tesco.net
>>         <mailto:J.Pilk at tesco.net>
>>         <mailto:J.Pilk at tesco.net <mailto:J.Pilk at tesco.net>>> wrote:
>>
>>              On 02/07/13 12:15, Anthony Giggins wrote:
>>
>>                  Hi All,
>>
>>                  Along the lines of
>>         http://www.gossamer-threads.__**__com/lists/mythtv/users/**537328
>>
>>         <http://www.gossamer-threads._**_com/lists/mythtv/users/537328
>>         <http://www.gossamer-threads.**com/lists/mythtv/users/537328<http://www.gossamer-threads.com/lists/mythtv/users/537328>
>> >**>
>>
>>                  And http://code.mythtv.org/trac/__**__ticket/11593<http://code.mythtv.org/trac/____ticket/11593>
>>         <http://code.mythtv.org/trac/_**_ticket/11593<http://code.mythtv.org/trac/__ticket/11593>
>> >
>>
>>
>>                  <http://code.mythtv.org/trac/_**_ticket/11593<http://code.mythtv.org/trac/__ticket/11593>
>>         <http://code.mythtv.org/trac/**ticket/11593<http://code.mythtv.org/trac/ticket/11593>
>> >>
>>
>>                  I tried running 0.25-fixes mythtranscode in place of my
>>         0.26-fixes
>>                  mythtranscode but ran into library dependancy hell,
>>                  I'm just thinking our loud here but given the state of
>>         mythtranscode
>>                  should the dev's just up-port 0.25 mythtranscode or is
>>         there
>>                  some other
>>                  reason these bugs are not being addressed? or are
>>         others not
>>                  experiencing these issues?
>>
>>                  the alternative lossless cut options are not nearly as
>>         reliable,
>>
>>         http://www.mythtv.org/wiki/___**_Lossless_Cut<http://www.mythtv.org/wiki/____Lossless_Cut>
>>         <http://www.mythtv.org/wiki/__**Lossless_Cut<http://www.mythtv.org/wiki/__Lossless_Cut>
>> >
>>
>>
>>                  <http://www.mythtv.org/wiki/__**Lossless_Cut<http://www.mythtv.org/wiki/__Lossless_Cut>
>>         <http://www.mythtv.org/wiki/**Lossless_Cut<http://www.mythtv.org/wiki/Lossless_Cut>
>> >>
>>                  due to issues with HDHR recordings also rather I/O
>>         intensive
>>                  works much
>>                  better with ionice -c3
>>
>>         http://www.mythtv.org/wiki/___**_MythDVBcut<http://www.mythtv.org/wiki/____MythDVBcut>
>>         <http://www.mythtv.org/wiki/__**MythDVBcut<http://www.mythtv.org/wiki/__MythDVBcut>
>> >
>>
>>
>>                  <http://www.mythtv.org/wiki/__**MythDVBcut<http://www.mythtv.org/wiki/__MythDVBcut>
>>         <http://www.mythtv.org/wiki/**MythDVBcut<http://www.mythtv.org/wiki/MythDVBcut>
>> >>
>>                  Works great with simple cuts only ie. leading/trailing
>>         only, not
>>                  so good
>>                  with Ad removal
>>
>>
>>              As the perpetrator of this script, let me comment.  It
>>         works well
>>              for me for recordings (DVB-T UK) where the video is
>>         identified by
>>              ffmpeg as 'mpeg2video (Main)', which it cuts using
>>         Project-X.  For
>>              other formats short audio glitches are to be expected at
>>         internal cuts.
>>
>>              John P
>>
>>
>>
>>         Hi John,
>>
>>         And thank you for your script.
>>
>>         yes video is identified the same ie.
>>         [NULL @ 0x72f180] start time is not set in
>> estimate_timings_from_pts
>>         [mpegts @ 0x729100] write_section_data: PID 0x499 CRC error
>>         Input #0, mpegts, from
>>         '/storage3/recordings/4073___**20130703025000.mpg':
>>
>>             Duration: 01:29:58.36, start: 21314.455456, bitrate: 10094
>> kb/s
>>               Stream #0:0[0x431]: Video: mpeg2video (Main), yuv420p,
>>         1440x1080
>>         [SAR 4:3 DAR 16:9], 11000 kb/s, 25 fps, 25 tbr, 90k tbn, 50 tbc
>>               Stream #0:1[0x433](eng): Audio: ac3, 48000 Hz, stereo,
>>         s16, 384 kb/s
>>               Stream #0:2[0x435](eng): Subtitle: dvb_teletext
>>               Stream #0:3[0x499]: Data: dsmcc_b
>>         At least one output file must be specified
>>
>>         I'm is Australia and what I'm finding is simple cuts work great
>> but
>>         anything beyond a few cuts causes parts to be cut out
>>         incorrectly and
>>         creates files ALOT smaller then expected.
>>
>>         -rw-rw-r-- 1 seven  seven     6346752 Jul  3 21:13
>>         /storage3/recordings/4073___**20130703025000.mpg
>>
>>         -rw-r--r-- 1 mythtv mythtv 6811607352 Jul  3 14:20
>>         /storage3/recordings/4073___**20130703025000.mpg.old
>>
>>
>>         Cheers,
>>
>>         Anthony
>>
>>
>>     Hmm. Sorry to hear that.  All my mpeg2 stuff is 720x576 or less and
>>     it works ok.  There's a note on the wiki page about the remuxing
>>     failing at higher bitrates, and an mkv workaround, but I've not used
>>     that myself.
>>
>>     Cheers,
>>
>>     John
>>
>> OK sorry I dont know how I missed that thread or the comment on the wiki,
>>
>> is this ment to go into the existing script?
>>
>> mythffmpeg -fflags +genpts -i $DEMUXPREF.m2v -i $DEMUXAUDIO -vcodec copy
>> -acodec copy "$OUTFILE"
>>
>> or is this a manual work around, It is more than likely a HD issue as
>> the one that work reliably are not HD, perhaps this can be used only on
>> a specific channel or perhaps depending on the resolution, what are your
>> thoughts on automating this?
>>
>> Cheers,
>>
>> Anthony
>>
>>
> That's not really something I want to get into - but mythffmpeg will tell
> you if it's an HD recording and you could set USEPJX=false for those.  The
> script should then work just it does for DVB-T2 HD h264 here in the UK. Not
> perfect, but it might suit better than what you have already.
>
>
> John has updated his script since I provided the HDHR HD workaround, so
the variable names in my snippet are out of date. If you want to try my
workaround you will need to replace:

CMD="ionice -c3  mplex -o "$1" -V -f 9 $TEMPHEAD.m2v $TEMPAUDIO"

With something like this (the "mediainfo" package is required for this to
work):

filename=`mediainfo '--Inform=General;%FileName%' "$1"`

OUTFILE="$filename".mkv

CMD="ionice -c3 mythffmpeg -fflags +genpts -i $TEMPHEAD.m2v -i $TEMPAUDIO
-vcodec copy -acodec copy $OUTFILE "

# tell mythDB about new filename

echo "update recorded set basename='${OUTFILE}' where chanid=$chanid and
starttime='$starttime';" | mysql -N -u${DBUserName} -p${DBPassword}
-h${DBLocalHostName} ${DBName}


You will as need to replace "$1" with "$OUTFILE" in the following lines:

CMD="ionice -c3 mythcommflag -q --rebuild --file $1 "

echo -e "Output file is $1. \n"

echo -e "\nRunning:  mythffmpeg -i "$1" 2>&1 | grep -C 4 Video" | tee -a
log$$

mythffmpeg -i "$1" 2>&1 | grep -C 4 Video | tee -a log$$

CMD="mv ${TEMPHEAD}_log.txt  ${LOGDIR}/$1.PXcut$$.txt"

As I mentioned above, I am using a modified version of John's earlier
script so this is untested. Let me know if this doesn't work.

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