[mythtv-users] "Mythtranscode is currently unable to transcode remote files" on master?

[Niklas Brunlid]

Just thought I'd give transcoding my MPEG-2 to MPEG-4 a try, but just when  
the transcoding job is about to start I get this:

2005-07-25 00:07:24.940 New DB connection, total: 2
2005-07-25 00:07:24.949 Attempted to transcode  
myth://:/2_20050413203000_20050413210000.nuv. Mythtranscode is currently  
unable to transcode remote files.
2005-07-25 00:07:25.051 Deleting  
/myth/tv/2_20050413203000_20050413210000.nuv.tmp
2005-07-25 00:07:25.210 New DB connection, total: 2
2005-07-25 00:07:25.219 Attempted to transcode  
myth://:/2_20050413203000_20050413210000.nuv. Mythtranscode is currently  
unable to transcode remote files.
2005-07-25 00:07:25.225 Deleting  
/myth/tv/2_20050413203000_20050413210000.nuv.tmp
2005-07-25 00:07:25.383 New DB connection, total: 2
2005-07-25 00:07:25.387 Attempted to transcode  
myth://:/2_20050413203000_20050413210000.nuv. Mythtranscode is currently  
unable to transcode remote files.
2005-07-25 00:07:25.393 Deleting  
/myth/tv/2_20050413203000_20050413210000.nuv.tmp
2005-07-25 00:07:25.549 New DB connection, total: 2
2005-07-25 00:07:25.553 Attempted to transcode  
myth://:/2_20050413203000_20050413210000.nuv. Mythtranscode is currently  
unable to transcode remote files.
2005-07-25 00:07:25.559 Deleting  
/myth/tv/2_20050413203000_20050413210000.nuv.tmp

The thing is, I only have one combined backend/frontend and no remote ones  
(not counting my MVP), and all recordings are on a local mount. However,  
the last time I tried transcoding, I think the whole "job queue" stuff  
wasn't there, so I haven't configured that. Is there a setting I'm  
missing? What are the default/sane settings for this to work?

Server is a FC3 box, standard P4, Mythology install, last  
apt-get-updated-upgraded about a week ago. Myth is set to a fixed IP, i.e.  
the internal one on my LAN, and the server acts as a firewall/gateway as  
well, so it has another (external) IP as well. Anyway, can the fact that  
Myth is not set to 127.0.0.1 cause these problems?

/ Niklas