﻿id	summary	reporter	owner	description	type	status	priority	milestone	component	version	severity	resolution	keywords	cc	mlocked
9801	mythtranscode produces unusable output when transcoding mpeg4->mpeg4 with cutlists	mythtv@…	beirdo	"I am having the following problem with the latest 0.24-fixes version of mythtranscode:
1. Transcoding mpeg2 to mpeg4 with or without cutlist works fine
2. (Re)Transcoding mpeg4 to mpeg4 WITHOUT cutlist works fine
3. (Re)Transcoding mpeg4 to mpeg4 WITH cutlist terminates (without relevant error message) after a few seconds with an output file of about 100-150KB independent of the actual cutlist. If mythfrontend is used then this useless, truncated recording replaces and TRASHES the original recording.

This seems to occur regardless of the actual mpeg4->mpeg4 recording profile parameters and occurs even when doing a 'lossless' version (note in all cases I use mp3 for audio).

Here is an example running mythtranscode from the CLI:

#mythtranscode --chanid 1021 --starttime 20101120163000 --outfile 1021_20101120 163000.nuv-OUT2 --honorcutlist --profile 3

(where profile 3 = High Quality mpeg4/mp3)

Gives the following output:

      2011-05-23 21:52:57.355 Using runtime prefix = /usr

      2011-05-23 21:52:57.355 Using configuration directory = /home/use/.mythtv

      2011-05-23 21:52:57.372 Empty LocalHostName.

      2011-05-23 21:52:57.426 New DB connection, total: 1

      2011-05-23 21:52:57.447 Closing DB connection named 'DBManager0'

      2011-05-23 21:52:57.495 Enabled verbose msgs: important

      2011-05-23 21:52:57.787 Found video height of 1088.  This is unusual and more than likely the video is actually 1080 so mythtranscode will treat it as such.

      2011-05-23 21:52:57.788 New DB connection, total: 2

      2011-05-23 21:52:57.816 New DB connection, total: 3

      2011-05-23 21:52:57.849 Using protocol version 63

      Error in my_thread_global_end(): 1 threads didn't exit


Note that the last error line is a MySQL error that at least in other past reported mythtv contexts may be benign and I don't believe it has anything to do with this bug report.

The full verbose output from adding '-v all' is too long to post so I have posted it to pastebin.com:
     http://pastebin.com/5F9qPR3i

"	Bug Report - General	closed	minor		MythTV - Mythtranscode	0.24-fixes	medium	fixed	mythtranscode cutlist		0
