[mythtv-users] Why does Myth think I have a nuv? I swear it's an mpg.

[greg at nodecam.com]

I recently bought a new beefy machine to help with transcoding (among
other things.)  I fired up Mythbuntu, and had it up and running far too
quickly :)

Anyway, I forgot to mount the recording directories before the backend
started up, and the first few recordings that it tried to transcode
failed, because it couldn't access the files.

Once I resolved that situation, I was still unable to transcode those
shows, because the 'recorded' table had a basename with a .nuv extension,
even though the files are still .mpg files.

I just updated the basename behind the scenes, and it's happily
transcoding now, but it struck me as strange.

The exact error message was:
2009-04-29 12:49:27.254 Attempted to transcode
myth://192.168.0.3:6543/1308_20090428190100.nuv. Mythtranscode is
currently unable to transcode remote files.
2009-04-29 12:49:27.314 JobQueue: Transcode Errored: Fringe "Midnight":
Medium Quality (exit status 242, job status was "Starting")

The file was actually 1308_20090428190100.mpg, and when I updated the
database to reflect this, it seems to have resolved things.

Any idea how this could have happened?

Thanks,

Greg