[00:20] any satellite users (US) here? [00:24] not me [00:24] although its best to just post your question [00:25] I'd like to know if US satellite users will just have a poorer experience with mythtv compared to cable folks [00:26] i prefer cable. But thats cause I like HD :) [00:28] two questions: there appears to be a second or so lag between when I press the arrow key and when it registers on screen- how do I fix this? [00:28] also, why does it say pre-scaling theme images every time? [00:29] pre-scaling should be quick the second time it does it [00:29] it is [00:30] ok, i think thats cause its checking it [00:30] as to the delay, sec [00:31] in i believe ~/.lircrc there should be a delay amount. You should be able to reduce this to get better response [00:32] or [00:32] it could be you dont have the proprietary drivers installed for you vid card [00:32] or it could be your computer isn't beefy enough [01:44] how do i restart the myth backend once i've quit out of it to get back to the xfce desktop? [01:44] rebooting doesn't restart it (maybe the session is getting saved at logout?) [01:44] it's driving me nuts! [01:45] depends on your distro. in (*)buntu: [01:45] it's mythbuntu gutsy [01:45] cmd: sudo /etc/init.d/mythtvbackend restart [01:45] buntu = goodness. [01:45] gawd!! i probably could have figured that out, if i'd thought about it... [01:45] let's see if it works! [01:45] ;) [01:46] typo there, you need a hyphen. [01:46] sudo /etc/init.d/mythtv-backend restart [01:48] oh, good... it wasn't working... [01:48] brb [01:50] I'm getting about 1/2 an hour per Gig of storage with SDTV. Is that about right, or can I optimize it down pretty good? [01:50] you're one step further than me. i just got stdef working tonight but no audio so far. [01:51] bluec_: What sound card you got? [01:51] adventurous, hvr-950. [01:51] got HD to work, but don't have the horsepower to play it back. working on ntsc/cable now. [01:52] bluec_: I thought you said you had stdef working? [01:52] got video, don't have audio. [01:53] appears to be a common problem on the hvr-950 [01:53] ok, this is infuriating... [01:53] ? [01:53] why is it that suddenly i can no longer connect to the backend?! [01:53] it's happened more than once.... [01:54] the /etc/init.d/mythtv-backend restart indicated it IS running.... [01:54] bluec_: lemme log back into a IRC client that supports copy and paste, and I can give you a link to the best sound guide I've found for Ubuntu, it just covers all the basics well. [01:54] but i get that $%$&# message about not being able to connect to it... [01:54] it was working 20 minutes ago!! [01:54] ps -eaf | grep -i back [01:55] bluec_: http://ubuntuforums.org/showthread.php?t=205449&highlight=comprehensive+sound [01:55] Actually, this link is a little less annoying: http://ubuntuforums.org/showthread.php?t=205449 [01:55] Doesn't have the highlighting for the search phrase [01:56] i'll take a look. audio is working otherwise (cd's), but so far no audio off /dev/dsp1 when tuned to a TV channel [01:56] What about 1/2 hour per GB of storage, is that a good ratio, or can I optimize it down pretty good if I research it. [01:56] and if I "can't connect" to backend...why can I watch videos? [01:57] bluec_: You've checked your alsa mixer? The channel that has TV sound could just be muted. [01:57] what's happening to make "Watch TV" fail like that....?? [01:57] wilberfan: I've seen that for "Watch TV" when I didn't have my tuner card (aka capture card) configured correctly. [01:58] wilberfan: I had it decoding video with the wrong codec in the setup. [01:58] this has happened 3 or 4 times today... I even re-installed TWICE cuz I got so frustrated!! [01:58] levander: what would make the config suddenly CHANGE?! [01:58] levander: it was working fine... [01:58] wilberfan: No idea, apparently though, reinstall isn't gonna cut it. You need to find what the problem was. [01:59] i'm hip to that now!! [01:59] :| [01:59] Have you been searching the mailing list for answers? http://www.gossamer-threads.com/lists/mythtv/users/ [01:59] is there something i'm supposed to run AFTER i change settings? [02:00] Search on the error message, not your description of the problem. [02:00] wilberfan: Make sure you go all the way to the end of the dialogs where you can change stuff. E.g., keep clicking "Next" till you get to a "Finish". You've been doing that? [02:01] wilberfan: Those dialogs (screens) are like wizards that you have to complete all the way through. [02:01] yes... (where there IS a finish). I meant am I supposed to run mythfilldatabase (or whatever it is) each time, or...? [02:01] wilberfan: ummm, i'd only run mythfilldatabase if you've changed something that affects the channel lineup [02:02] I've been playing with Setup quite a bit (just got up and running myself) and I've never run mythfilldatabase afterwards. [02:02] now none of the config dialog's "take" because it says it can't connect to the backend... [02:02] but i'm trying to connect through the frontend... [02:02] wilberfan: If you've been playing with MythTV Setup, the configuration probably didn't change on its own to stop "Watch TV" from working... [02:03] wilberfan: What do you mean "take"? [02:03] i go through all the screens, and when I select 'finish' it says it can't connect... [02:03] wilberfan: is mythbackend running? [02:03] another big headache is that the display is only on the tv-out--which is in the next room!!! [02:04] levander: the last time i ran 'restart' it said it was... [02:04] wilberfan: In mythfronted, you have to configure it to tell the frontend where the backend is. Like the backend's IP address. [02:04] 127.0.0.1, right? i=t [02:04] lavender - is mythtvbackend listening on tcp ports? example: [02:04] wilberfan: 'ps -ef | grep myth' - see if there's a mythbackend in there [02:04] it's all on one machine.... [02:04] sudo netstat -tanp | grep myth [02:04] tcp 0 0 0.0.0.0:6543 0.0.0.0:* LISTEN 8421/mythbackend [02:04] tcp 0 0 0.0.0.0:6544 0.0.0.0:* LISTEN 8421/mythbackend [02:04] wilberfan: yes for 127.0.0.1, if the frontend and backend are running on the same machine [02:04] levander: i have to drag the mouse and keyboard into the next room to do that...! [02:04] wilberfan: 127.0.0.1 just means localhost [02:04] it's SO annoying... [02:05] no ssh for you? [02:05] is 'localhost' the exact equiv of 127....? can it be one or the other? [02:05] wilberfan: 'sudo apt-get openssh-server' and you can just ssh into it [02:05] if mythbackend isn't running, checkout /var/log/mythtv/mythbackend.log [02:05] it is most indicative of what you did that broke things [02:05] the most common cause is permissions [02:05] levander: openssh into what? [02:05] on the recordings directory [02:05] wilberfan: well, localhost is the name, and 127.0.0.1 is the IP address. But, localhost maps to 127.0.0.1 via DNS and vice versa. [02:06] wilberfan: Into your box in the other room. [02:06] wilberfan: 'sudo apt-get install openssh-server' on the machine that doesn't have full-time mouse and keyboard [02:07] levander: no, here's the setup... The box and it's monitor is in the kitchen. I have an s-video cable running from the Geforce 5200 into the next room where the TV is... [02:07] lol @ s-video cable running into the kitchen [02:07] the display for mythtv ONLY shows up on the TV (in the next room), so to perform ANY functions, i have to drag the mouse and keyboard in there... [02:07] wilberfan: So, i that's the setup, why does the box in the kitchen have no mouse and keyboard? [02:07] it DOES [02:08] wilberfan: No, you can ssh into the box in the kitchen from the computer you are looking at now. [02:08] but the only working DISPLAY is in the next room [02:08] wilberfan: Or, you can install mythfrontend on the computer you're in now [02:08] levander: i'm not sure you're getting it yet.... [02:09] wilberfan: you know what a command prompt is, yes? [02:09] the computer in the kitchen is the computer that mythtv is running on... [02:09] it's only the display that's in the next room... [02:09] wilberfan: if you ssh (secure shell) into a box, you get a command prompt running on a remote machine that shows up on your local machine [02:09] the remote and local machine are the same! [02:09] wilberfan: Understand? [02:09] yes i do...but i don't think you do yet.... [02:10] wilberfan: What computer are you using now? ssh from the machien you are on now, into this machien that has it's monitor in the kitchen [02:10] ok. let's start over. [02:10] imagine the computer you're typing on now had it's monitor in the next room.... [02:11] THAT's what i'm dealing with here.... [02:11] wilberfan: well then, how do you see what I'm typing? [02:11] wilberfan: Do you have binoculars? [02:11] No...i have to take the keyboard and mouse into the next room! [02:11] wilberfan: you do that to see what I'm typing? [02:11] why not just keep the mouse and keyboard into the next room? [02:12] right now i'm irc'ing on a DIFFERENT computer.... [02:12] wilberfan: exactly! [02:12] lol [02:12] wilberfan: ssh from the DIFFERENT computer into the computer that has it's monitor in the kitchen [02:12] rofl [02:12] more detail: [02:13] i have two computers [02:13] they're BOTH in the kitchen. [02:13] wilberfan: then, you get a command prompt on the DIFFERENT computer that is running on the kitchen monitor computer [02:13] they share ONE keyboard and mouse. [02:13] wilberfan: who's on first? [02:13] one of those computers has mythtv front and backend on it [02:13] and the other has IRC on it? [02:13] when the mythtv computer boots up--it's display doesn't show on the monitor--it shows in the TV in the next room... [02:14] wilberfan: yeah, so? [02:14] wilberfan: I just said to check if mythbackend is running, you can do that via ssh. [02:14] so..........i have to take the keyboard and mouse into the next room to do any configuring.... [02:14] and you're saying ssh from machine 1 to machine 2.... [02:14] whew [02:14] wilberfan: just ssh from 1 to 2 to see if mythbackend is running [02:14] wilberfan: not to configure Myth [02:15] wilberfan: to configure Myth, stopping running around with the keyboard and mouse [02:15] wilberfan: bring the kitchen monitor into the room you are in now [02:15] wilberfan: you will never get it working otherwise [02:15] ok. let's move on. [02:16] what's the best way to check if the backend is running? [02:16] wilberfan: 'ps -ef | grep myth' - see if mythbackend is in the output [02:16] wilberfan: you can ssh into the remote box to run that command [02:16] how, exactly, do i do that? [02:17] i don't remember the command [02:17] wilberfan: on the remote machine 'sudo apt-get install openssh-server' on the local machine, 'ssh ' [02:17] wilberfan: you have to run around with the keyboard/mouse to run 'sudo apt-get install openssh-server' [02:18] But, after you do that, you can 'sudo apt-get ' to your heart's content remotely. [02:19] actually isn't ssh installed by the default install? [02:19] i thought i had enabled it for that [02:19] superm1: no [02:19] o [02:19] oh yeah samba is [02:19] ssh isnt [02:19] openssh-server is already installed.... [02:19] superm1: no open ports by default, security policy [02:19] levander, well mythbuntu is a bit different [02:19] superm1: ssh is installed by default [02:19] I have a question about a HDTV qam tuner supported [02:19] superm1: i stand corrected [02:19] levander, yeah i thought i had activated that for install [02:20] :) [02:20] levander, that is the default security policy for ubuntu however [02:20] you are correct there [02:20] host key verification failed... [02:20] superm1: I could see making exceptions to that security policy for Mythbuntu, but I wouldn't overdo the exceptions... [02:20] Hauppage 1800 MCE kit qam/atsc/ntsc? is it support or will 8.04 support it? [02:21] wilberfan: just say yes to that 'host key verification' message [02:21] wilberfan: that happens the 1st time you ssh into a box [02:21] it's not giving me a yes or no options [02:21] MythbuntuGuest05, i'm not too sure on that hardware [02:21] wilberfan: it just means the ssh client doesn't know the remote machine, yet [02:21] wilberfan, have you tried to ssh into a previous install? [02:21] wilberfan: it gets to know it the 1st time you ssh into it [02:21] it just failed and gave me a prompt back... [02:21] if so then rm ~/.ssh/known_hosts [02:21] on your remote machine [02:21] not showing it on the list its a new card [02:21] MythbuntuGuest05, check out linuxtv.org [02:21] and see if its listed there at all [02:21] can't i delete the known_hosts and start over? [02:22] wilberfan, that's what i said :) [02:22] lol [02:22] i see that now.... [02:22] MythbuntuGuest05, or even better, try it and let everyone know if it worked for you :) [02:23] $ ps -ef | grep myth [02:23] 1000 5373 5342 0 17:41 ? 00:00:00 /usr/bin/ssh-agent /usr/bin/dbus-launch --exit-with-session /usr/share/mythbuntu/session.sh [02:23] 1000 5376 1 0 17:41 ? 00:00:00 /usr/bin/dbus-launch --exit-with-session /usr/share/mythbuntu/session.sh [02:23] 1000 5702 5685 0 18:23 pts/1 00:00:00 grep myth [02:23] what is that telling us? [02:23] wilberfan, so the backend isn't running [02:23] like i said before look at your log file [02:23] [sigh] it's NOT? [02:24] if mythbackend isn't running, checkout /var/log/mythtv/mythbackend.log [02:24] it is most indicative of what you did that broke things [02:24] the most common cause is permissions [02:24] where, exactly does it indicate it's not running? [02:24] you would have had an entry like this: [02:24] mythtv 22816 1 4 18:47 ? 00:04:27 /usr/bin/mythbackend --daemon --logfile /var/log/mythtv/mythbackend.log --pidfile /var/run/mythtv/mythbackend.pid --noupnp [02:24] if it was [02:25] permissions... maybe 'wilberfan' changed 'mythtv' settings?? [02:25] permissions usually meaning the recordings directory [02:25] if you changed where it is at [02:25] i probably did.... [02:25] and it can't be written to by the daemon user, 'mythtv' [02:25] like i said [02:25] look at that log [02:25] which log? [02:25] it tells you *exactly* why the backend couldn't launch [02:25] if mythbackend isn't running, checkout /var/log/mythtv/mythbackend.log [02:26] "permission denied" [02:26] look at it with sudo then [02:28] superm1: yeah, you're permissions are weird, you should be able to read (not write) mythbackend.log by default [02:28] sudo: /var/log/mythtv/mythbackend.log: command not found [02:28] levander, yeah you are able to [02:28] if you are in the mythtv group [02:28] wilberfan, you need to use an editor or line reader [02:28] wilberfan: just 'less /var/log/mythtv/mythbackend.log' [02:28] such as nano or cat [02:28] wilberfan: 'less' is a file reader, you view text files in it [02:29] anyone have a remote recommendation? I need to control mythtv, receiver, and and TV. better to use one programmable/lerning remote or irblaster setup? [02:30] ok...there's hundreds of lines of text here...what am i looking for? [02:30] wilberfan: type a '>' to go to the end of the file [02:30] levandar, does http://pastebin.ubuntu.com/ work so he could paste the log there? [02:31] wilberfan: at the end of the file, it says anything about an error [02:31] /media/sdb1//nfslockfile.lock: Permission denied [02:31] Unable to open lockfile! [02:31] Be sure that '/media/sdb1/' exists and that both [02:31] the directory and that file are writeable by this user. [02:31] :| [02:31] like i said [02:31] permissions [02:31] superm1: could the lock file be left open by a previous run of mythbackend? maybe he should just delete the lock file? [02:31] its not just the lock file [02:32] its that it can't be modified [02:32] you need to make sure that the owner of /media/sdb1 is mythtv:mythtv [02:32] sudo chown mythtv:mythtv -R /media/sdb1 [02:32] superm1: okay, i had to ask you because i'm not sure how that lock file works [02:32] if you want to use that for your recordings directory [02:32] sdb1 is an NTFS partition--will that make a difference?? [02:32] * superm1 shrugs [02:32] well you sure like to complicate things here [02:32] no, i DON'T actually! [02:33] :) [02:33] :| [02:33] Gutsy was supposed to ship with good NTFS file system handling, I'd guess no. [02:33] does it have to be ntfs? [02:33] no, it doesn't..... [02:33] But, in the past, yes, NTFS would definitely have made a difference. [02:33] i was thinking of reformatting it ext3, btw... [02:33] I haven't tried it in Gutsy though. [02:33] well the thing is that gutsy ships good ntfs file system support, only when you are using it for user level stuff [02:33] shall i pick another partition...see if that makes a diff?? [02:33] because permissions are more irrelevant [02:33] could you make it something a little more unix permissions friendly [02:33] like xfs [02:33] or jfs [02:34] or pick another partition? [02:34] I'm getting 1/2 hour per GB of storage with SDTV. Is that pretty good, or can I optimize it down quite a bit? [02:34] hi [02:34] levander, that's pretty good [02:34] superm1: i can definitely pick another partition.... [02:34] whatever you end up doing, the most important thing is that the owner is mythtv:mythtv [02:34] so if you continue to use ntfs, you have to mount it as the mythtv user [02:34] superm1: Damn, that means I need a new hard disk. An 80 GB isn't going to cut it. [02:35] I'm trying to diagnose my channels listing but I get unreadable text in my channels.conf: [02:35] cat /home/andrew/.azap/channels.conf [02:35] WUTV-HD�:473028615:8VSB:49:52:3 [02:35] how should i proceed from here? [02:35] what's the first thing I should do? [02:35] (other than go strangle something) [02:35] wilberfan, well that's up to you. if you are going to wipe this partition [02:35] then open up a partition editor such as gparted [02:35] wipe it [02:35] and format it xfs [02:35] and then chown it and continue [02:35] no, i'd rather pick another partition... just to see if that makes a diff... [02:35] well it will as long as its friendly to unix permissions [02:36] and lets you set the owner of it to be mythtv [02:36] wilberfan: gparted, format the new partition, then make sure the new partition is mounted with correct permissions [02:36] superm1: ext3 isn't friendly to unix permissions? [02:36] levander, yes but not to mythtv recordings [02:36] i don't want to use sdb1 for right now...; i'd rather try one of the existing ext3's... [02:36] superm1: You do some detailed stuff with permissions in Myth? [02:36] because deleting large files with ext3 blocks the cpu [02:37] wilberfan: Do you have other stuff on these existing ext3's? [02:37] levander: yes... [02:37] levander, well just the daemon user, mythtv needs to have the permissions to write to the directory [02:37] nothing fancy [02:37] superm1: Ah, what's the best filesystem then for the recordings directory? [02:37] xfs [02:37] is what i recommend [02:37] some people like to push jfs [02:38] but just stay away from reiser and ext3 if you can [02:38] superm1: You know, I said that on the Ars forums, XFS. Then like 5 people jumped on me and said I was stupid. Idiots. [02:38] what did they say? [02:38] superm1: Do you just run XFS for MythTV recordings, or for everything? Like, even '/'? [02:38] how do i exit from 'less', btw? [02:38] wilberfan: 'q' [02:38] levander, i only use it for recordings and media [02:38] levander, for my root filesystem i stick with ext3 [02:39] wilberfan: Since you don't know 'less' already, maybe you're better off disconnecting from the remote machine, 'ssh -X @' and then on the remote machine type 'xtoolwait gedit'. [02:40] wilberfan: That gives you a GUI editor, running on the remote machine, with direct access to the files on the remote machine. [02:40] superm1: Is there a technical reason for sticking with ext3, or is it just laziness? [02:41] levander, well journaling is a good idea to have [02:41] levander, on more important things like a root file system [02:41] superm1: Oh, I thought XFS had journaling. [02:41] levander, it does, but it also doesn't cleanly handle recovering that journal [02:41] in the event of a bad shut down [02:41] superm1: This, I didn't not know. Thanks. [02:42] levander, i've lost things in the past on a root xfs file system [02:42] levander, and mythtv recordings are of a lower priority [02:42] superm1: I bet you learned quick at that point that you can't recover from an XFS journal. [02:42] levander, well there are "supposed" to be ways to recover [02:42] levander, but i had piss poor luck with it [02:43] so i've kept ext3 for all root filesystems since then [02:43] superm1: Plus, the journal probably eats a lot of room for something like Myth recordings... [02:43] superm1: You know, I've never had to go to my journal to recover anything. [02:43] well i dont know how much the journal really takes up space wise [02:43] i've never had to investigate that [02:43] superm1: And, I don't have my PC hooked up to a UPS, and I have brown-outs. [02:43] superm1: Yeah, I'm just guessing, I don't know. [02:44] wilberfan: How you coming with gedit? [02:45] i just dragged the keyboard and mouse into the next room to change the recording partition [02:45] that didn't seem to help [02:45] wilberfan: you could have changed the permissions via ssh [02:45] wilberfan, make sure the new one has the correct permissions too [02:45] what's that command again? [02:46] wilberfan: 'ssh -X @' [02:46] no, i got that one... [02:46] the chown one... [02:46] wilberfan: can you search backwards in your IRC client? [02:47] this is just what superm1 typed above: 'sudo chown mythtv:mythtv -R /media/sdb1' [02:48] does the "R" take care of all the sub-folders? [02:48] "recursive"? [02:48] Yes [02:48] recursive, yes [02:48] might as well change the entire partition, right? [02:49] superm1: I have no idea, you know? [02:49] no prob there? [02:49] superm1: From the command, I'd guess yes wilberfan. [02:49] well it depends if you are using anythign else on there [02:49] superm1: what do you mean? [02:49] from the way you described things, it sounded like you were using the partition just for recordings [02:49] i already have videos there i'd like to watch, too... [02:50] well you should make subdirectories then [02:50] one for recordings [02:50] and one for videos [02:50] because....? [02:50] videos should be permissions of whatever user you use to put them there [02:50] recordings should be the mythtv user [02:50] ah... [02:52] ok, i now have a /media/sdb5/recording with mythtv as the owner... now i can try changing the mythtv config, yes? [02:53] (i really appreciate your help with this stuff, guys... i've been at this all day...and I'm kinda frazzled!) [02:54] yes [02:55] wilberfan: You're diving into Linux head first, good for you. [02:55] it's telling me that directory is "not writable"! [02:56] yeah, head first--without a helmet!! [02:56] "it's"= the backend setup screens [02:56] is it possible to pass audio over HDMI in linux? [02:57] did this command not make it writable?: sudo chown mythtv:mythtv -R /media/sdb5/recording [02:58] wilberfan, no big deal [02:58] ignore the warning right there [02:58] (easy for HIM to say!) [02:58] as long as you really changed the permissions it won't matter [02:58] so i select the "No, i know what i am doing" option? [02:58] lol [02:58] KLIMAUDIO, depends on the vendor of the hdmi output that you have [02:58] wilberfan, yeah [02:58] (even though i don't!) [02:58] lol [02:58] wilberfan, that is something we should take care of though (that warning) [02:59] HOLY CRAPSICLES!!! MY LIVETV IS WORKING AGAIN!!! [03:00] :) [03:00] permissions permissions permissions [03:00] those problems never seem to go away :) [03:00] So, the lesson here... is to make sure the recording directory is owned by--specifically--mythtv?! [03:01] yes. [03:01] it is SUCH a relief to get that fixed... i'd worked myself into quite a GeekSnit [03:01]