[Please adjust your posting technique. The message text you are quoting is indistinguishable from the text you are writing. If you're having difficulty posting through Nabble, try subscribing to the list directly so you can reply using your usual email client.]
Scott Souter wrote: > ...I am using Myth SVN Version 0.21.20071211-1 15258 and elsewhere you said: > Can you tell I'm pretty green? These two statements don't go together well. If you're new at this stuff, it isn't the best idea to be running the SVN version of a project. > I have no hostname for my box and no domain name. > From what I gather this is important for livetv to work. Where did you read that having a host name configured was necessary for the Live TV feature to work? The wiki page for the MythTV Live TV feature: http://mvpmc.wikispaces.com/Live+TV doesn't list that as a prerequisite. You do, however, need to have a database connection, and thus the -y, -u, -p, and possibly -T command line switches. You appear to be supplying these parameters. You can test your database connectivity using a menu found off of the MythTV settings menu in mvpmc. > When I look at /etc/hosts on the server (mythtv) it shows the > following > > 127.0.0.1 mythtv localhost > # generated by drakhosts > > which confuses me because the ip of the nic is 192.168.0.50. You won't normally see the "public" IP address for the local machine get automatically added to /etc/hosts. You can manually add it, but even if you did, it wouldn't help things on the MVP, as it doesn't have access to the /etc/hosts file on the server. (Though I think you're chasing a red herring.) If you really want to have your LAN machines be accessible by name, install Dnsmasq on your Linux box, which provides both DHCP and DNS, and turn off DHCP on your router. > I think I have this right for -b livetv directory and -r for recordings. > correct? > mvpmc -f /etc/helvB14.pcf -o composite -S 600 -s 192.168.0.50 -b > /data/livetv -p mythtv -u mythtv -y 192.168.0.50 -T mythconverg -r /data You have a bunch of switches specified that I've found to be problematic or are redundant with compiled-in defaults. Consult this page: http://mvpmc.wikispaces.com/commandline for more info. Specifically, the -f switch I've found to be problematic. The font_override.xml technique you tried works better, though I agree with the other person who said that you should eliminate these extras until you've gotten the basics working. "-o composite" is redundant with the default. "-S 600" is redundant with the default set in the theme files. "-b /data/livetv" shouldn't be used if you are using MythTV protocol. "-r /data" shouldn't be used if you are using MythTV protocol. "-T mythconverg" is redundant with the default. > I have deleted the "-r /data" and just like that I can see my > recordings. Good. > Is getting livetv to work something simple as well? I'd delete the -b switch. > If this is one option to have the -r removed, am I missing some sort > of advantage? The paths to the ring buffer and video directory were required for MythTV version prior to 0.19. Newer MythTV versions provide the same functionality through the MythTV protocol. I'm not sure the ring buffer is even still accessible in this fashion in current MythTV versions. At best these techniques are deprecated, and at worse they're obsolete. > What is the intension of creating these directories in the mvp? The primary use for mounting network file systems on the mvpmc is to use the Filesystem browser to directly access media, which could be movies, audio, or pictures. -Tom ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Mvpmc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mvpmc-users mvpmc wiki: http://mvpmc.wikispaces.com/
