A new version of MythFS. Besides a lot of code improvements, this version supports the deletion of recordings. The recordings will be deleted by communicating with the native protocol to the MythTV backend. Therefore, MythFS now speaks the native protocol.

Everybody familiar with MythTV will know, that this protocol changes for each version of MythTV and that protocol versions are incompatible. MythFS currently speaks protocol version 40 and 44. In case you want to use MythFS with a MythTV version that speaks another version of the protocol, please install the most recent version of MythFS, run mythfsdump > mythfsdump.out and email me the output saved in mythfsdump.out. The output contains enough information for me to reverse engineer your version of the MythTV protocol and to release an update.

As always, the most recent release of MythFS is found on Sourceforge.

This little tool can be used to make MythTV recordings easily accessible to
programs without implementing any interface towards MythTV, because each
recording is just a file. After mounting the filesystem, a virtual directory
structure is created with 3 top entries: Programs, Dates and Channels. All
recordings appear as directories and files in this tree. Currently, the only
operations supported are:

• browsing the directory tree
• reading individual recordings
• deleting recordings (for protocol versions 40 and 44)

History

I wrote MythFS, because I really like the MythTV backend and Mythweb, but I am
not too enthousiastic about the MythTV frontend. I am using XBMC
(http://www.xbmc.org/) on an Apple TV to view the recordings and somehow none
of the offered interfaces towards Myth suit my needs: the native XBMC interface
(myth://mythtv:mythtv@192.168.1.1) crashes my backend, the Python script
mythbox (http://mythbox.googlecode.com/) and finaly the UPNP interface (which
functioned really well in XBMC on my Xbox) does not allow seeking in
recordings.

After the initial struggles to get Xen working properly on my Asus P5B based server, I added my Hauppauge PVR-500 TV card in the equation. One of the main objectives of the Xen project was to be able to isolate my MythTV setup from my webserver and mailserver.
Badly enough, this is what happened when I tried to load the module in the kernel:

Linux video capture interface: v1.00
PCI: Enabling device 0000:00:00.0 (0000 -> 0002)
PCI: Setting latency timer of device 0000:00:00.0 to 64
ivtv: ==================== START INIT IVTV ====================
ivtv: version 0.6.6 (tagged release) loading
ivtv: Linux version: 2.6.16.42-xen SMP gcc-4.1
ivtv: In case of problems please include the debug info between
ivtv: the START INIT IVTV and END INIT IVTV lines, along with
ivtv: any module options, when mailing the ivtv-users mailinglist.
ivtv0: Autodetected Hauppauge WinTV PVR-150 card (cx23416 based)
PCI: Enabling device 0000:00:01.0 (0000 -> 0002)
tveeprom 0-0050: Hauppauge model 23559, rev D591, serial# 8228113
tveeprom 0-0050: tuner model is Philips FQ1216AME MK4 (idx 91, type 56)