Was the (tcrequant) ratio that it gave in the log output reasonable? About 1.3 would mean that the calculation of the ratio was wrong (you put extra video files in /myth/tmp). About 1.03 would mean that the calculation of the ratio was right, but the file got truncated before burning.
The most likely thing is that you have some video files in /myth/tmp that are not owned by (the user) mythtv. This means that they cannot be deleted by the pre-burn clean up and mytharchive thinks they will become part of the DVD.
The second most likely thing and the reason I am posting today is that your mplex process may have barfed most of the way through your file leaving you a partial output file. Play the short DVD and see if the ending is there. If you find
Quote:
Too many frame drops
in /myth/tmp/logs/mythburn.log then this is what happened.
I found a solution to this. Search
Quote:
Failed while running dvdauthor
in the forum to see. I will post this by April 3, 2010
If you have put anything in /myth/tmp I would remove it. If you don't know what I am talking about then you have probably not done anything like this, so don't worry about it.
Failed or aborted burns leave junk behind. That junk should be cleared out by the next burn in most cases. Sometimes stuck processes get left, but that should not cause your particular issue either and the stuck processes go away at next reboot. You could delete everything in /myth/tmp/work and /myth/tmp/logs and reboot and try again.
In R5.5, the code that does the burn is /usr/share/mythtv/mytharchive/scripts/mythburn.py The line that calculates the ratio looks like:
Code:
scalepercentage=totalvideosize/dvdrsize
You could monkey with that in semi-obvoius ways, to get one burn to go right, but that won't fix the real problem.
I am not around here on a regular basis, but I try to help when I am. It has been months since I came here last.
Please reply to this post if this helped or not.
Cliff