2005-02-10, 02:38
ok, i guess i could have been clearer in my instructions. for step 1, i meant upload the xbmcmythtv directory and all sub directories to the xbmc/scripts. so the filesystem should look like:
within the scripts directory, you should have a subdirectory called xbmcmythtv and within that you would have the *.py files. under the xbmcmythtv directory, you would have a language directory and a skin directory.
note: you should *never* have to overwrite xbmc files with this installation method. if you find yourself overwriting files that came with xbmc, then you are doing something wrong and you will most likely mess up your xbmc install.
the old way of installing stuff into the xbmc directories made it more difficult to uninstall everything if you don't want to use the scripts.
technically speaking, you do not need to upload the contents of the "test" directory. the files in the directory are only used for emulation testing outside of xbmc. however, it won't hurt if you upload the test directory with everything else.
my current setup that works fine is a feb 3, 2005 build of xbmc, myth tv 0.16, and the latest cvs of xbmcmythtv.
the path prefix should be a string that can be prepended in front of the myth generated recording filenames (e.g. 1014_20040713103000_20040713110000.nuv) to access the files remotely for playback. the live prefix should be the prefix needed to access the dir where myth will generate the ringbuffer files. with my setup, these two directories happen to be the same. if you happen to share the directory using smb, then it should be a smb share path prefix.
if you use the special value '%h' somewhere in the path prefix, then the scripts will replace the '%h' with the hostname stored in the mythdatabase. this is in case you have multiple backends that record shows. this assumes the remote share name is the same on all hosts. if you only have one backend, you don't need to use the '%h' value - you can put in the hostname explicitly. (if your myth database has fully qualified domain names in the recorded.hostname column, then the scripts will strip the domain from the hostname before replacing %h. this was a bug/feature request from someone that had fqdn hostnames in myth but was sharing using netbios/smb and the fqdn was not the same as the netbios hostname.)
i should note that the prefix can begin with "smb://", "xns://", "xbms://" or anything else supported by xbmc. i have only tested with "smb://" but the others should work as well...
Quote:xbmc/
scripts/
xbmcmythtv/
language/
skin/
within the scripts directory, you should have a subdirectory called xbmcmythtv and within that you would have the *.py files. under the xbmcmythtv directory, you would have a language directory and a skin directory.
note: you should *never* have to overwrite xbmc files with this installation method. if you find yourself overwriting files that came with xbmc, then you are doing something wrong and you will most likely mess up your xbmc install.
the old way of installing stuff into the xbmc directories made it more difficult to uninstall everything if you don't want to use the scripts.
technically speaking, you do not need to upload the contents of the "test" directory. the files in the directory are only used for emulation testing outside of xbmc. however, it won't hurt if you upload the test directory with everything else.
my current setup that works fine is a feb 3, 2005 build of xbmc, myth tv 0.16, and the latest cvs of xbmcmythtv.
the path prefix should be a string that can be prepended in front of the myth generated recording filenames (e.g. 1014_20040713103000_20040713110000.nuv) to access the files remotely for playback. the live prefix should be the prefix needed to access the dir where myth will generate the ringbuffer files. with my setup, these two directories happen to be the same. if you happen to share the directory using smb, then it should be a smb share path prefix.
if you use the special value '%h' somewhere in the path prefix, then the scripts will replace the '%h' with the hostname stored in the mythdatabase. this is in case you have multiple backends that record shows. this assumes the remote share name is the same on all hosts. if you only have one backend, you don't need to use the '%h' value - you can put in the hostname explicitly. (if your myth database has fully qualified domain names in the recorded.hostname column, then the scripts will strip the domain from the hostname before replacing %h. this was a bug/feature request from someone that had fqdn hostnames in myth but was sharing using netbios/smb and the fqdn was not the same as the netbios hostname.)
i should note that the prefix can begin with "smb://", "xns://", "xbms://" or anything else supported by xbmc. i have only tested with "smb://" but the others should work as well...