From MythTV Official Wiki
Revision as of 17:21, 8 May 2013 by Lstein (Talk | contribs)

Jump to: navigation, search

Author Lincoln Stein
Description This script maps TV recordings on a local or remote MythTV backend to a human-readable directory structure on the local machine.
Supports Version25.png  Version26.png 


This is a FUSE filesystem for MythTV ( It uses the Myth 0.25 API to mount the TV recordings known to a MythTV master backend onto a virtual filesystem on the client machine for convenient playback with mplayer or other video tools. Because it uses the MythTV network protocol, the recordings do not need to be on a shared NFS-mounted disk, nor does the Myth database need to be accessible from the client.


Run the following commands from within the top-level directory of this distribution:

$  git clone git://
$ cd mythfs-perl
$ ./Build.PL
$ ./Build test
$ sudo ./Build install

If you get messages about missing dependencies, run:

$ ./Build installdeps

and then "sudo ./Build install". See #Fuse Notes if you get Fuse-related errors when attempting to install dependencies.

For best performance, Perl must have been compiled with support for IThreads. In addition, you will need at Fuse version 0.15 to run correctly under Perl versions >= 5.14. Threading will be automatically disabled if not available. See #Fuse Notes for additional information.


To mount the recordings contained on the master backend "MyHost" onto a local filesystem named "/tmp/mythfs" use this command:

$ mkdir /tmp/mythfs
$ MyHost /tmp/mythfs

The script will fork into the background and should be stopped with fusermount. The mounted /tmp/mythfs directory will contain a series of human-readable recordings organized by title (directory) and subtitle (file).

To unmount:

$ fusermount -u /tmp/mythfs

NOTE: Do NOT try to kill the process. This will only cause a hung filesystem that needs to be unmounted with fusermount.

There are a number of options that you can pass to, including the ability to customize the filesystem layout and set the interval that the backend is checked for new and deleted recordings. Call with the -h option for the complete help text.

Local Recordings

The default behavior of this filesystem is to use the Myth API to stream recordings across the network when you attempt to read from them. This is done in an efficient way that fetches just the portion of the file you wish to read. However, if the underlying recording files are directly accessible (either in a regular director or via an NFS mount), you can get better performance by passing the --mountpt option with the path to the directory in which the recordings can be found. The filesystem will then be set up as a set of symbolic links that point from a human readable file name to the recording file.

The main advantage of creating symbolic links is that NFSv4 can be significantly faster than the backend streaming protocol -- about 1.6X in my informal tests. The main limitation is that this mode does not understand storage groups, so all recordings need to be located in a single storage group in a locally-accessible directory. However if a recording file is not found in local directory, then will fall back to the streaming protocol, so the recording is accessible one way or another.

The Default Directory Layout

Recordings that are part of a series usually have a title (the series name) and subtitle (the episode name). Such recordings are displayed using a two-tier directory structure in which the top-level directory is the series name, and the contents are a series of recorded episodes. The corresponding pattern (as described in the next section) is "%T/%S".

For recordings that do not have a subtitle, typically one-off movie showings, the recording is placed at the top level.

In all cases, the time the recorded was started is attached to the filename, along with an extension indicating the recording type (.mpg or .nuv). The file create and modification times correspond to the recording start time. For directories, the times are set to the most recent recording contained within the directgory.

Here is an example directory listing:

% ls -lR  /tmp/mythfs
total 35
-r--r--r-- 1 lstein lstein 21262807708 Jan 11 13:10 007 Licence To Kill.mpg
-r--r--r-- 1 lstein lstein 12298756208 Jan 11 13:10 A Funny Thing Happened on the Way to the Forum.mpg
-r--r--r-- 1 lstein lstein 14172577964 Jan 11 13:10 A Heartland Christmas.mpg
-r--r--r-- 1 lstein lstein 17591877032 Mar 10 14:24 A Knight_s Tale.mpg
dr-xr-xr-x 1 lstein lstein           5 Mar 11 03:41 Alfred Hitchcock Presents
dr-xr-xr-x 1 lstein lstein           8 May  4 01:20 American Dad

/home/lstein/Myth/Alfred Hitchcock Presents:
total 3
-r--r--r-- 1 lstein lstein 647625408 Dec 25 15:30 Back for Christmas.mpg
-r--r--r-- 1 lstein lstein 647090360 Dec  7 00:00 Dead Weight.mpg
-r--r--r-- 1 lstein lstein 660841056 Mar 11 03:00 Rose Garden.mpg
-r--r--r-- 1 lstein lstein 647524452 Dec 25 00:00 Santa Claus and the 10th Ave. Kid.mpg
-r--r--r-- 1 lstein lstein 649819932 Dec 27 00:00 The Contest of Aaron Gold.mpg

/home/lstein/Myth/American Dad:
total 4
-r--r--r-- 1 lstein lstein 3512038152 Apr 24 00:00 Flirting With Disaster.mpg

The size of directories corresponds to the number of recordings (not counting subdirectories) contained within it.The modification time of directories is the start time of the most recent recording contained within it.

Customizing the Directory Listing

You may customize the directory listing by providing a pattern for naming each recording using the -p option. For example:

$ -p '%C/%T:%S (%od-%ob-%oY)' mythbackend ~/Myth

This will create filenames that look like this:

Sitcom/The Simpsons:The Food Wife (13-Nov-2011).mpg

Patterns contain a combination of constant strings plus substitution patterns consisting of the "%" sign plus 1 to three characters. A slash will be interpreted as a directory level: multiple levels are allowed.

Commonly-used substitution patterns are:

   %T   = Title (show name)
   %S   = Subtitle (episode name)
   %C   = Category
   %cn  = Channel: channel number
   %cN  = Channel: channel name
   %y   = Recording start time:  year, 2 digits
   %Y   = Recording start time:  year, 4 digits
   %m   = Recording start time:  month, leading zero
   %b   = Recording start time:  abbreviated month name
   %B   = Recording start time:  full month name
   %d   = Recording start time:  day of month, leading zero
   %h   = Recording start time:  12-hour hour, with leading zero
   %H   = Recording start time:  24-hour hour, with leading zero
   %i   = Recording start time:  minutes
   %s   = Recording start time:  seconds
   %a   = Recording start time:  am/pm
   %A   = Recording start time:  AM/PM

A full list of patterns can be obtained by running " -p help".

Patterns are largely compatible with the excellent ( script, but there are a small number of enhancements, such as the ability to generate the month name. Also, the patterns that generate the month name without a leading zero are not supported.

You may wish to use a delimiter to separate fields of the recording name, for example "%T:%S" to generate "Title:Subtitle". Occasionally a recording field is empty, leading to names like "The Wild Ones:.mpg". To avoid this, pass the --trim option with the delimiter you use, and dangling/extra delimiters will be trimmed:

$ -p '%T:%S' --trim=':' backend /tmp/myth

Fuse Notes

For best performance, you will need to run this filesystem using a version of Perl that supports IThreads. Otherwise it will fall back to non-threaded mode, which will introduce occasional delays during directory listings and have notably slower performance when reading from more than one file simultaneously.

If you are running Perl 5.14 or higher, you *MUST* use at least 0.15 of the Perl Fuse module. At the time this was written, the version of Fuse 0.15 on CPAN was failing its regression tests on many platforms. I have found that the easiest way to get a fully operational Fuse module is to clone and compile a patched version of the source, following this recipe:

$ git clone git://
$ cd perl-fuse
$ perl Makefile.PL
$ make test   (optional)
$ sudo make install


This script has not yet undergone diligent testing. Try running with the -debug flag to see where the problems are occurring and report issues to


Lincoln Stein <> 8 May 2013