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

[greg at nodecam.com]

> greg at nodecam.com wrote:
>>
>> 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")
>>
> I don't think the fact that your files are .nuv is your problem. The error
> message mentions "remote files". Is mythtranscode able to access these
> files
> directly using an NFS share?

Hi Mike,

I have it set up using an NFS share, mounted the same place on all machines.

My understanding of it, from reading up on that error message is that Myth
first tries to find the file locally and if that doesn't work, then it
throws that error.  Since the actual file is not .nuv, it can't find it
locally, and falls back to that error message.

As soon as I changed the extension in the recorded table to .mpg, it
transcoded no problem, since that's what the filename actually was.  I
didn't try to play back any of the affected recordings, because they won't
play back on my frontends (which is why I have to transcode them) but I'm
wondering now if I'd have been able to play them back, or if I would have
gotten an "unable to find file" type message if I'd have tried it.

It feels like maybe there's a hole somewhere in the job processing where
it thought that the file was transcoded successfully, and thus changed the
filename in 'recorded' but in reality the transcode failed because I had
set it up incorrectly.

I can't say for sure, until I poke at the code a bit sometime in the next
few weeks.

Thanks,

Greg