[mythtv-users] Samba share of mythfs.py filesystem not working

[Raymond Wagner]

On 1/26/2011 17:37, John Reid wrote:
>
>
> On 26/01/11 20:29, Raymond Wagner wrote:
>>
>> If you have one central backend, mythlink.pl is the preferred 
>> solution.  Hitting the filesystem directly is much less expensive 
>> than routing your traffic through FuseFS and the python bindings.  
>> Mythfs.py is to allow you to use it on systems with multiple 
>> backends, and no shared NFS mounts.
>>
> That's good to know. Have you any opinion on mythtvfs? Is that 
> comparable to mythfs.py or mythlink in efficiency?

Mythtvfs is going to be more efficient because it's compiled, rather 
than written in python.  However, it is not intended for human 
consumption.  It uses a static format intended to put lots of 
information in the filename, such that it could be used with a plugin 
for some media player called Galleon, instead of making Galleon speak 
myth protocol directly.  Besides that, it does not support myth protocol 
file transfers, instead requiring all content be available on the local 
filesystem, and has no advantage over just using mythlink.pl.

Mythfs.py isn't bad, but the socket code is a bit of a mess.  It's fine 
for local files, and streaming recordings for viewing works well enough, 
but at least on my backend (1.8GHz Ath X2), I get about 25MB/s transfer 
through the bindings before I get limited by the overhead.