[mythtv-users] More Transcode questions

James Pifer jep at obrien-pifer.com
Tue Sep 7 14:52:25 EDT 2004

> Well, manual checks:
> 1) Yes, you'll see transcode in background
> 2) Yes, you'll see beginning transcode and ending transcode in the log.
> 3) Trickier, if it fails different things can happen.  Check in your
> transcoding table in your db for the status code.  If you have a bunch
> of .nuv.tmp files sitting around it'll be a clue too.
> 4) Varies greatly based on compression and CPU
> 5) Yes, assuming you have it set to not keep the old files, it'll
> build a .nuv.tmp then copy it over the old .nuv when it is done. 
> It'll look the same, just smaller.
> ______________________________________________________________________
> _______________________________________________

Well, I do see it in the log now(not sure why I didn't before). I'm
getting the following:

2004-09-07 14:31:05 Transcoding from
/mythtv/recordings/1005_20040823072800_20040823080000.nuv to
Input #0, mpeg, from
  Stream #0.0: Video: mpeg2video, 480x480, 29.97 fps
  Stream #0.1: Audio: mp2, 48000 Hz, stereo, 384 kb/s
strange error flushing buffer ... 
2004-09-07 14:33:05 Transcoding
/mythtv/recordings/1005_20040823072800_20040823080000.nuv failed
2004-09-07 14:33:06 Deleting

Trying to find a solution for "strange error flushing buffer ...".
Possible things so far are, disable ACPI if it available, disable PCI
devices not in use, and upgrade the BIOS if available. Don't know if any
of those were successful before. 

Any other possible solutions?


More information about the mythtv-users mailing list