| 00:01 | <mdz_> | anybody have a >=9GB ultra2 SCSI disk they would like to give me? |
| 00:09 | <DigDig> | mdz: sure. |
| 00:09 | <DigDig> | Whats it for? |
| 00:12 | <mdz_> | to replace my 4GB one that has been 97% full for the past year :-) |
| 00:13 | <yebyen> | Chutt: is the mythweb writer maintaining it at all? |
| 00:14 | <DigDig> | So, its not like, for a good cause or anyting? :-) |
| 00:14 | <mdz_> | nah, I wasn't serious |
| 00:14 | <DigDig> | Good neither was I. But I do have one I am going to sell. |
| 00:14 | <mdz_> | unless you have a warehouse full of them or something |
| 00:15 | <mdz_> | pricewatch has an IBM 18GB for $74 including shipping |
| 00:15 | <yebyen> | Chutt: i'm thinking about adding some stuff to it, like i'm pretty sure it doesn't have "Record on this channel only" |
| 00:15 | <mdz_> | 10k RPM |
| 00:15 | <DigDig> | SCSI?? wow |
| 00:15 | <yebyen> | Chutt: unless it does in cvs, and it's just because i'm using the debs |
| 00:15 | <mdz_> | yebyen: I think the original author is not around right now, but there are a few people actively working on it |
| 00:15 | <mdz_> | yebyen: quite a bit of changes have gone in since 0.7 |
| 00:15 | <yebyen> | alright |
| 00:16 | <yebyen> | then i will refrain from adding anything, since it's probably already done |
| 00:16 | <yebyen> | heh |
| 00:16 | <mdz_> | nah, just ask first |
| 00:16 | <mdz_> | send mail to the list |
| 00:16 | <mdz_> | or ask lichen, I believe he is one of the people working on it |
| 00:16 | <DigDig> | can you record (archive) what is being watched live? |
| 00:17 | <mdz_> | DigDig: you can watch something that has been scheduled to record, but you can't dump a recorded show from the live tv buffer (yet) |
| 00:18 | <yebyen> | i think i'm going to upgrade my desktop box |
| 00:19 | <DigDig> | So, if you have it scheduled, and it has started recording, you can watch it live with only one capture card? |
| 00:19 | <mdz_> | DigDig: yes |
| 00:19 | <mdz_> | DigDig: and rewind, fast forward, etc. |
| 00:20 | <mdz_> | the only thing it cannot do is, if you are watching something live, and you want to record it (including the part you have already watched which is still in the buffer) |
| 00:20 | <DigDig> | Does mythtv know to read from the capture file and not the ringbuffer in that case? |
| 00:20 | <mdz_> | yes |
| 00:20 | <DigDig> | Cool. |
| 00:20 | <DigDig> | Is that in 0.7? |
| 00:20 | <DigDig> | I guess it doesn't really matter though now that I am running CVS. |
| 00:22 | <mdz_> | yes, that has been possible for a long time |
| 00:23 | -!- | PhoenixUT [] has quit [Read error: 60 (Operation timed out)] |
| 00:27 | <DigDig> | How should I submit my changes to XJ.cpp and other files for Xinerama support and other minor changes to display code? |
| 00:27 | <DigDig> | I'm not quite done yet, but I hope to have something that runs by the end of tonight. |
| 00:28 | <mdz_> | are they against current CVS? |
| 00:28 | <DigDig> | I grabbed a tarball last night. |
| 00:30 | <DigDig> | ..of CVS. |
| 00:32 | <mdz_> | does the tarball have the 'CVS' directories in it? I"ve never used that feature |
| 00:33 | <DigDig> | no, but I could use normal cvs access if there is anonymous access. |
| 00:34 | <mdz_> | there is |
| 00:34 | <mdz_> | I would say do a cvs diff -u against current CVS to submit your changes |
| 00:35 | <mdz_> | and send it as an attachment to the mailing list |
| 00:36 | <mdz_> | Chutt: odd, closeEvent doesn't seem to get called when I press escape |
| 00:38 | <mdz_> | argh, the escape keyevent calls done(), which explicitly does not call close() |
| 00:38 | <mdz_> | it hides it and then deletes it |
| 00:41 | <mdz_> | exec() isn't virtual... |
| 00:41 | <mdz_> | I guess I need to override the key binding, if that's possible |
| 00:46 | -!- | noobie [~chatzilla@12-253-102-163.client.attbi.com] has joined #mythtv |
| 00:47 | <DigDig> | Wierd, I just compared cable directly to the TV to MythTV output of hte same channel and Myth is MUCH more clear. |
| 00:48 | <DigDig> | Although eh colors are less defined through MythTV. |
| 00:49 | <mdz_> | what's your source? |
| 00:49 | <mdz_> | analog cable? |
| 00:49 | <DigDig> | Yea. |
| 00:49 | <mdz_> | odd |
| 00:50 | <mdz_> | maybe the tuner on your TV is not so good |
| 00:50 | <mdz_> | could be your brightness/contrast/etc. settings as well |
| 00:50 | <DigDig> | The only difference is that MythTV doesn't go through a cable box. |
| 00:51 | <DigDig> | Its all grainy when I go through the cable box. |
| 00:51 | <mdz_> | ahh |
| 00:51 | <DigDig> | At least on that channel. I haven't tested other channels. My wife is watching TV right now. |
| 00:52 | <DigDig> | CVS doesn't seem to be very useful right now. I get segfaults left and right. I wonder if I should maintain a copy of 0.7 and CVS on my system. |
| 00:53 | <DigDig> | I'd h ave to backport my changes. |
| 00:53 | <mdz_> | get backtraces from the segfaults and help fix them |
| 00:53 | <DigDig> | Hehe, give me CVS access :-) |
| 00:53 | <mdz_> | that is Chutt's decision |
| 00:54 | <mdz_> | sending him patches would work just as well for getting things fixed |
| 00:55 | <mdz_> | it'd be more worthwhile to work on stabilizing CVS than to backport to 0.7 at this point |
| 00:55 | <DigDig> | As long as get is good about applying them. |
| 00:55 | <mdz_> | in my experience, he is very responsive to patches |
| 00:56 | <DigDig> | Ok. |
| 00:56 | <DigDig> | BTW, how many people have CVS write access (just out of curiosity) |
| 00:56 | <mdz_> | dunno |
| 01:01 | <mdz_> | Chutt: has anyone tested whether the DB settings code in mythcontext actually works? |
| 01:01 | <mdz_> | Chutt: with the dialog changes so that it is saved unconditionally, the 'general settings' stuff will actually be saved to the database now |
| 01:18 | <DigDig> | Should expect a little stuttering when I begin watching live TV. I have plenty of processsor power, but when I start watching live TV it skips a lot of frames for the first 2 seconds or so. |
| 01:18 | <DigDig> | Then it is smooth. |
| 01:37 | <yebyen> | hmm |
| 01:37 | <yebyen> | mythtv doesn't seem to be listening to my increased font size settings in theme.txt |
| 01:37 | <yebyen> | heh |
| 01:38 | <yebyen> | well, epg is |
| 01:42 | <-- nyquiljer | (jer@12.211.16.232) has left #mythtv |
| 01:48 | <yebyen> | now nothing is |
| 01:48 | <yebyen> | what have I done |
| 01:48 | <yebyen> | HEH |
| 01:48 | <DigDig> | Does MythTV default to 640x480 inteernally? No matter what I set the capture resolution to, the windowed playback is always 640x480 (and fullscreen is, of course scalled to fullscreen) |
| 01:56 | <mdz_> | DigDig: that has been known to happen, the stuttering at the start of live TV playback |
| 01:56 | <mdz_> | I've never bothered to look into it myself, as I almost never use that feature |
| 01:56 | <DigDig> | Myth doesn't seem to be honoring the "int Height" setting. |
| 01:56 | <DigDig> | Or Width |
| 01:57 | <Chutt> | cvs doesn't use any of those settings |
| 01:57 | <Chutt> | it's all in the gui |
| 01:57 | <DigDig> | Ah ok. |
| 01:57 | <Chutt> | and, yeah, the lag at the beginning is 'normal' |
| 01:57 | <Chutt> | it's made worse by the new server stuff |
| 01:57 | <DigDig> | The GUI updates the DB? |
| 01:57 | <Chutt> | yup |
| 01:57 | <Chutt> | setup->recordings |
| 01:58 | <DigDig> | Ok, i thought was crazy(er) |
| 01:58 | <yebyen> | whoa, setup does something now? |
| 01:58 | <yebyen> | HEH |
| 01:58 | <yebyen> | or in cvs? |
| 01:58 | <mdz_> | the width/height should default to the width/height of the recording |
| 01:59 | <mdz_> | yebyen: in CVS |
| 01:59 | <Chutt> | right, and those default to 640x480 now |
| 01:59 | <yebyen> | Chutt: think it's worth going to CVS over the debs? (considering that i'll lose the convenience of having the debs) |
| 01:59 | <Chutt> | no |
| 01:59 | <Chutt> | stuff's broken |
| 01:59 | <yebyen> | debs it is |
| 01:59 | <yebyen> | HEH |
| 01:59 | <mdz_> | oh, so they do |
| 01:59 | <mdz_> | I forgot I left that as defaulting to max |
| 01:59 | <Chutt> | heh |
| 01:59 | <mdz_> | probably should change it, huh |
| 01:59 | <Chutt> | eh, doesn't _really_ matter |
| 02:00 | <yebyen> | nvtv any good? i'm still running at 640x480 |
| 02:00 | <yebyen> | heh |
| 02:00 | <yebyen> | to compensate for the big black bars in 800x600 |
| 02:00 | <DigDig> | bars where? |
| 02:00 | <DigDig> | how big? |
| 02:00 | <yebyen> | all around the screen |
| 02:00 | <yebyen> | on each side |
| 02:00 | <yebyen> | using nvidia |
| 02:00 | <DigDig> | Oh, in 640x480, yeah i get that |
| 02:00 | <Chutt> | mdz, should i just grant all on the database to % you think? |
| 02:00 | <Chutt> | for remote access |
| 02:01 | <yebyen> | i get it in 800x600, so I step down to 640x480 and it looks fine |
| 02:01 | <DigDig> | i couldnt' get nvtv to work. It did do anything. |
| 02:01 | <yebyen> | heh |
| 02:01 | <yebyen> | oh |
| 02:01 | <yebyen> | Chutt: is a release far off? |
| 02:01 | <mdz_> | Chutt: I wouldn't :-) |
| 02:01 | <Chutt> | it's not soon |
| 02:01 | <yebyen> | fair enough |
| 02:01 | <yebyen> | it works as it is, that's enough for me |
| 02:01 | <Chutt> | mdz, how to deal with remote access, though? |
| 02:01 | <DigDig> | but nvtv is SUPPOSED to addust the timing so you can fill the whle screen. |
| 02:02 | <Chutt> | nvtv doesn't support all encoder chips, though |
| 02:02 | <mdz_> | the right thing to do is to leave it up to the user (or the packages) to do the grants |
| 02:02 | <mdz_> | but I can understand if you want to avoid a lot of user questions |
| 02:02 | <Chutt> | right |
| 02:02 | <mdz_> | mythtv sux0rzz it sez permishun denide all the tiem |
| 02:02 | <Chutt> | i can write a little script, i suppose |
| 02:03 | <mdz_> | hmm |
| 02:03 | <Chutt> | setup_frontend.sh, to be run on the master server |
| 02:03 | <Chutt> | just tell it the ip to give access to |
| 02:03 | <mdz_> | if the default setup gives the mythtv user enough privileges to grant privileges to other users, it could be set up through the GUI |
| 02:03 | <mdz_> | or a script |
| 02:03 | <Chutt> | or, it could just automatically be given when the frontend connects to the backend |
| 02:03 | <mdz_> | hmm, there's an idea |
| 02:04 | <yebyen> | i'm going to upgrade my mythtv box |
| 02:04 | <yebyen> | so I can encode at 640x480 |
| 02:05 | <DigDig> | I wonder how MythTV should choose an Xinerama screen. Maybe just the screen closest in res. to the width of the video? |
| 02:05 | <DigDig> | Or maybe a settings.txt setting? |
| 02:05 | <Chutt> | i think i'll make it grant perms on a successful connect |
| 02:05 | <Chutt> | digdug, yeah, stick it in the settings file for now |
| 02:06 | <mdz_> | I guess % wouldn't be that bad if there's actually a password |
| 02:06 | <Chutt> | other than 'mythtv'? =) |
| 02:06 | <mdz_> | yep |
| 02:07 | <Chutt> | i need to pass back the sql connection settings to the client anyway |
| 02:07 | <mdz_> | I bet there are about 0 people (besides those using the debs) who have set a real password |
| 02:07 | <Chutt> | i don't think granting perms when it does that would be too bad |
| 02:08 | <Chutt> | i'm going to get rid of the current method of watching what you're recording |
| 02:08 | <Chutt> | well, not current, since that doesn't work in cvs, but =) |
| 02:08 | <Chutt> | make an inprogress table, and add those to the playback list |
| 02:08 | <mdz_> | not much point in having a password, much less host access control, if anyone can get the password just by asking :-) |
| 02:09 | <Chutt> | indicate that they're in progress somehow |
| 02:09 | <mdz_> | hmm |
| 02:09 | <Chutt> | so you can stop recording by deleting the entry |
| 02:09 | <Chutt> | and watch it by playing it back |
| 02:09 | <mdz_> | that'd be neat |
| 02:09 | <Chutt> | i think that'd work better with multiple recordings going on |
| 02:09 | <mdz_> | would you make live tv work the same way? |
| 02:10 | <mdz_> | so multiple clients could watch the same live tv session? |
| 02:10 | <Chutt> | that won't really work |
| 02:10 | <Chutt> | you couldn't change channels and stuff |
| 02:10 | <Chutt> | but it will just use the first available tuner card |
| 02:10 | <Chutt> | regardless of where it is physically |
| 02:11 | <DigDig> | Should I put in "#ifdef HAVE_XINERAMA" statements or just assume people at least hve the libs and headers on their systems when they build? |
| 02:12 | <Chutt> | that's all part of xfree 4.x, right? |
| 02:12 | <Chutt> | probably safe to just require it |
| 02:12 | <DigDig> | Its part of debian's. |
| 02:12 | <Chutt> | if not, and there's mass amounts of complaining, then it can be ifdef'd |
| 02:13 | <Chutt> | but no need for that right off |
| 02:16 | <mdz_> | or, if there's mass amounts of complaining, xfree 4.x could become a requirement :-P |
| 02:16 | <Chutt> | that too |
| 02:16 | <yebyen> | heh |
| 02:16 | <Chutt> | most people should be running something recent enough |
| 02:17 | <Chutt> | ah well |
| 02:17 | <Chutt> | i wonder if i'll write any code tomorrow |
| 02:18 | <mdz_> | anything that's in Debian stable is more than safe enough for a baseline |
| 02:18 | <Chutt> | hah |
| 02:18 | <Chutt> | so, is the 3.2 transition going to happen? |
| 02:19 | <mdz_> | haven't been paying attention |
| 02:19 | <mdz_> | I suppose I'll notice when 'gcc' is suddenly 3.2 and I need to recompile my packages |
| 02:20 | <mdz_> | hmm, looks like this settings table stuff only gets loaded at startup, darn |
| 02:20 | <mdz_> | otherwise, all the globalsettings.h stuff should work now |
| 02:20 | <mdz_> | requires a restart at least though |
| 02:20 | <Chutt> | fixable? |
| 02:21 | <mdz_> | yeah, I was planning to scrap that stuff anyway |
| 02:21 | <mdz_> | and have it load the settings using the classes |
| 02:21 | <mdz_> | but it could also be fixed to do a query whenever a setting is looked up |
| 02:22 | <Chutt> | most settings queries don't happen _that_ often |
| 02:22 | <mdz_> | I just loaded all of my settings.txt stuff into the db |
| 02:22 | <mdz_> | except for ExternalChannelCommand |
| 02:22 | <Chutt> | hrm |
| 02:22 | <mdz_> | we'll see if anything breaks |
| 02:22 | <mdz_> | next time i restart the frontend |
| 02:22 | <Chutt> | some of em do get loaded only on startup of some stuff |
| 02:22 | <Chutt> | have to look into that |
| 02:22 | <Chutt> | i need to make more stuff async, anyway |
| 02:23 | <Chutt> | send some signals around to tell people to reload settings, etc |
| 02:23 | <mdz_> | could have it just refresh after running one of the settings dialogs |
| 02:23 | <mdz_> | since that should be the only time it changes |
| 02:23 | <Chutt> | 'zactly |
| 02:23 | <Chutt> | but i want the playback box to update automatically, for example |
| 02:23 | <Chutt> | so i need some messaging stuff |
| 02:24 | <Chutt> | and i need to send messages from the backend to the running live-tv process if i want the live tv -> recording transition to work |
| 02:24 | <DigDig> | Is the tarball from the CVS browser a realtime snapshot? |
| 02:24 | <Chutt> | yup |
| 02:24 | <Chutt> | there's direct anon cvs access, though |
| 02:24 | <Chutt> | in the howto docs on the website |
| 02:24 | <DigDig> | I should use that. |
| 02:24 | <DigDig> | Ok. |
| 02:24 | <Chutt> | first section, i think |
| 02:24 | <DigDig> | I am familiar with CVS. |
| 02:25 | <Chutt> | and if you can track any bugs down, i'd appreciate it |
| 02:25 | <DigDig> | Like all the segfaults? :) |
| 02:25 | <Chutt> | all? |
| 02:25 | <Chutt> | heh |
| 02:25 | <Chutt> | stuff runs fairly nicely for me |
| 02:25 | <Chutt> | i only get reproduceable segfaults if i'm running the backend while i do a make install |
| 02:26 | <DigDig> | both the backend and frontend segfault fairly regularly for me while watching live TV. |
| 02:26 | <Chutt> | rewriting the library or the binary seems to really mess up the running process |
| 02:26 | <mdz_> | weird, it shouldn't |
| 02:26 | <mdz_> | newly launched processes could get unhappy |
| 02:26 | <Chutt> | heh, moegreen in here's having a similar problem to that, gets some weird socket error |
| 02:26 | <Chutt> | then stuff dies |
| 02:26 | <Chutt> | i can't reproduce it, though |
| 02:27 | <Chutt> | and if i can't see anything obviously wrong, so :( |
| 02:28 | <DigDig> | If I ctl-C out of the frontend, the backend will usually segfault. IT also happens when I switch from LiveTV to None. |
| 02:28 | <Chutt> | that i may have fixed earlier today |
| 02:28 | <Chutt> | double deleteing the sockets when it was cleaning them up =) |
| 02:28 | <Chutt> | killing a running live-tv process will do bad things, though |
| 02:28 | <mdz_> | looks like the only stuff left to guify from settings.txt is PIP and that timeoffset thing |
| 02:29 | <mdz_> | I guess the theme stuff comes next |
| 02:29 | <Chutt> | cool |
| 02:29 | <mdz_> | sure is a lot of stuff in there |
| 02:29 | <Chutt> | most of the theme stuff can stay out |
| 02:29 | <Chutt> | i don't think there's a need for a lot of it |
| 02:29 | <Chutt> | like, font sizes and all that |
| 02:30 | <mdz_> | as in, can go away, or stay in the config file? |
| 02:30 | <Chutt> | stay in the config file |
| 02:30 | <mdz_> | hmm |
| 02:30 | <mdz_> | you want to keep the config file? |
| 02:30 | <Chutt> | hrm, though |
| 02:30 | <Chutt> | i dunno |
| 02:30 | <mdz_> | I guess as long as each setting is only in one place or the other, it'd be ok |
| 02:30 | <Chutt> | maybe most of it can go in the gui |
| 02:30 | <mdz_> | but probably still confusing |
| 02:30 | <Chutt> | there's not as much as i though |
| 02:30 | <mdz_> | it looks easy |
| 02:30 | <Chutt> | got the theme, then the window size |
| 02:30 | <DigDig> | Whats the policy in C++ in regards to defining variable? I see a lot of variables being defined mid function. Where in C I would usually put that all at the very top of the function. |
| 02:31 | <Chutt> | digdug, they can go anywhere, i usually don't define things until i need them |
| 02:31 | <mdz_> | lots of random show this/show that type things |
| 02:31 | <mdz_> | a whole bunch of checkboxes |
| 02:31 | <Chutt> | mdz, yeah |
| 02:31 | <Chutt> | new epg style, old epg style |
| 02:31 | <Chutt> | etc |
| 02:31 | <Chutt> | or alternate |
| 02:31 | <Chutt> | i dunno what i want to call that |
| 02:32 | * yebyen | ponders |
| 02:32 | <Chutt> | only thing is |
| 02:32 | <yebyen> | i wonder what the sanest way to send audio from the notebook to the desktop is |
| 02:32 | <yebyen> | esd? |
| 02:32 | <Chutt> | what about multiple frontend configurations? |
| 02:34 | <Chutt> | yebyen, if you want to use a lot of bandwidth |
| 02:34 | <mdz_> | multiple frontend configurations could just be a hostname column in the table |
| 02:35 | <yebyen> | Chutt: hrm |
| 02:35 | <mdz_> | but personally I think it's probably not worth it |
| 02:35 | <mdz_> | maybe for a couple of things, like the overscan |
| 02:35 | <mdz_> | but most of it I bet would always be the same |
| 02:35 | <yebyen> | Chutt: i'm thinking about going back to my solution of just x-forwarding xmms running on the machine with the speaker |
| 02:35 | <DigDig> | Is there a place I can put the Xinerama detection stuff so that the Qtdialog stuff can the XvOutput stuff can access them? |
| 02:35 | <Chutt> | yeah, maybe |
| 02:35 | <Chutt> | digdug, hum. |
| 02:36 | <Chutt> | i dunno |
| 02:36 | <Chutt> | yebyen, mythmusic will run remotely soon =) |
| 02:36 | <yebyen> | Chutt: woot :) |
| 02:36 | <yebyen> | Chutt: i think X Forwarding xmms is the sanest way |
| 02:36 | <yebyen> | is there a good way to do that without opening up network X listening? |
| 02:36 | <Chutt> | meh |
| 02:36 | <yebyen> | like, through ssh |
| 02:36 | <Chutt> | xmms has a crappy ui, though |
| 02:37 | <yebyen> | i've never figured out how to do it |
| 02:37 | <yebyen> | Chutt: yeah, I am used to it, heh |
| 02:37 | <Chutt> | i never understood why people liked the winamp ui |
| 02:39 | <Chutt> | digdug, you can just stash stuff in libmyth |
| 02:39 | <Chutt> | stick it in util.cpp/.h or something |
| 02:40 | <DigDig> | Can i just stick a regular C function in there? Whats the policy on that? |
| 02:40 | <Chutt> | those are just regular c functions now |
| 02:40 | <Chutt> | though, hmm |
| 02:40 | <Chutt> | you're going to need X headers, aren't you |
| 02:40 | <DigDig> | One. |
| 02:40 | <Chutt> | which? |
| 02:40 | <DigDig> | Xinerama.h |
| 02:41 | <DigDig> | extentions/Xinerama.h |
| 02:41 | <Chutt> | i think you'll need more than that, that looks like it wants Display defined |
| 02:42 | <DigDig> | I guess I will need Xlib stuff. |
| 02:42 | <Chutt> | hmm |
| 02:42 | <DigDig> | why is that a problem? You dont' want the dependency on X? |
| 02:43 | <Chutt> | no, some x headers conflict with qt headers |
| 02:43 | <Chutt> | but i don't think it's going to matter |
| 02:43 | <Chutt> | including qapplication.h looks like it'll pull in a definition for Display |
| 02:43 | <Chutt> | so, ignore me =) |
| 02:44 | <Chutt> | and just stick whatever helper functions you need in those util files |
| 02:44 | <Chutt> | should be the best place for em, i think |
| 02:44 | <DigDig> | So just include Xinerama.h and everything else should be defined? |
| 02:45 | <Chutt> | i think |
| 02:45 | <Chutt> | dunno, of course =) |
| 02:45 | <Chutt> | but, bed time |
| 02:45 | <DigDig> | one sec. |
| 02:47 | <DigDig> | I see you still run 'setGeometry' in many places. You said something about centralizing that or making another Dialog class. |
| 02:58 | <yebyen> | there we go, now a reasonably sane way |
| 02:58 | <yebyen> | everything's on the machine with the stereo, including the mp3s |
| 02:58 | <yebyen> | except the actual xmms gets exported over ssh to the laptop |
| 02:58 | <yebyen> | heh |
| 03:01 | * Soopaman | curses at his $^!$ nforce box |
| 03:01 | <DigDig> | What is nforce anyway? Is that an all nVidia thing? |
| 03:01 | <Soopaman> | yeah |
| 03:02 | <Soopaman> | integrated chipset |
| 03:02 | <DigDig> | Sound, video, PCI, everything? |
| 03:03 | <Soopaman> | yep |
| 03:04 | <DigDig> | Sound like a good idea anyway... |
| 03:10 | <yebyen> | hmm |
| 03:10 | <yebyen> | if i spend $150 upgrading shit, I'll have enough spare parts to build another system entirely |
| 03:11 | <yebyen> | err, $350 |
| 03:28 | -!- | bigguy [bigman@h9.44.102.166.ip.alltel.net] has joined #mythtv |
| 03:32 | -!- | DigDig [] has quit ["[BX] Hey, where's the cream filling?!"] |
| 03:36 | <Soopaman> | hmm.. Chutt, mdz |
| 03:37 | <Soopaman> | what does "Can't call method "do" on an undefined value at -e line6, <> line 1." mean? |
| 03:44 | -!- | ilan [foobar@ip68-6-103-84.sb.sd.cox.net] has joined #mythtv |
| 03:44 | <ilan> | hey |
| 03:50 | <ilan> | will mythtv work on non-x86 platforms? |
| 03:50 | <ilan> | so like sparc or ppc? |
| 03:53 | <bigguy> | it hasn't been run on one yet |
| 03:53 | -!- | gossamer [~chatzilla@h24-78-86-175.vc.shawcable.net] has joined #mythtv |
| 03:53 | <bigguy> | might take some hacking but I'm sure you could get it running on one |
| 03:54 | <ilan> | ill have to find myself a capture / tv card that works first |
| 04:11 | <Soopaman> | anyone awake install mythtv via tv? |
| 04:11 | <Soopaman> | err via debian |
| 04:11 | <Soopaman> | heheh |
| 04:37 | -!- | _bigguy_ [bigman@h9.44.102.166.ip.alltel.net] has joined #mythtv |
| 04:38 | -!- | bigguy [] has quit [Read error: 113 (No route to host)] |
| 04:38 | -!- | _bigguy_ is now known as bigguy |
| 04:48 | -!- | nevertheless [~chris@p50859ADF.dip.t-dialin.net] has joined #mythtv |
| 05:09 | -!- | gossamer [] has quit ["ChatZilla 0.8.11 [Mozilla rv:1.3a/20021212]"] |
| 05:18 | <yebyen> | Soopaman: me |
| 05:28 | <Soopaman> | yebyen, does it work for you?> |
| 05:29 | <yebyen> | yep |
| 05:29 | <Soopaman> | did you encounter any problems? |
| 06:23 | -!- | bigguy [] has quit [Read error: 113 (No route to host)] |
| 06:28 | -!- | bigguy [bigman@h9.44.102.166.ip.alltel.net] has joined #mythtv |
| 07:02 | -!- | bigguy [] has quit ["Off to B-E-D"] |
| 10:08 | -!- | Edgan [edgan@66-214-208-21.rno-cres.charterpipeline.net] has joined #mythtv |
| 10:25 | -!- | liscio [~root@65.39.134.27] has joined #mythtv |
| 11:08 | -!- | Edgan [] has quit [Read error: 110 (Connection timed out)] |
| 11:20 | -!- | Edgan [edgan@66-214-208-21.rno-cres.charterpipeline.net] has joined #mythtv |
| 11:22 | -!- | _shad [] has quit [Read error: 110 (Connection timed out)] |
| 11:24 | -!- | moegreen [~moegreen@pa-steclge-u2-c3c-151.stcgpa.adelphia.net] has joined #mythtv |
| 11:38 | -!- | liscio [] has quit ["BitchX: its what's for lunch"] |
| 12:02 | <mdz_> | Soopaman: it most likely means that you did not answer the configuration questions correctly |
| 12:02 | <mdz_> | Soopaman: the line immediately before it is probably more meaningful, it is just a fallout error |
| 12:13 | -!- | liscio [~root@65.39.134.27] has joined #mythtv |
| 12:29 | <-- Universe | has quit () |
| 12:30 | -!- | Universe [Yeah@6532175hfc29.tampabay.rr.com] has joined #mythtv |
| 12:31 | <Universe> | hey mdz, Chutt.. ya there? |
| 12:32 | -!- | moegreen [] has quit [Read error: 113 (No route to host)] |
| 12:46 | -!- | paperclip [] has quit [Remote closed the connection] |
| 12:47 | -!- | paperclip [~joe@ip68-11-30-173.no.no.cox.net] has joined #mythtv |
| 12:52 | -!- | _shad [shad@CPE00201888d549.cpe.net.cable.rogers.com] has joined #mythtv |
| 12:53 | <_shad> | Gah |
| 12:53 | <_shad> | Stupid internet |
| 12:53 | <_shad> | Chutt: alive? |
| 12:56 | -!- | moegreen [~moegreen@pa-steclge-u2-c3c-151.stcgpa.adelphia.net] has joined #mythtv |
| 13:15 | <Chutt> | now i am |
| 13:34 | <_shad> | hehe |
| 13:34 | <_shad> | I'm dumb |
| 13:34 | <_shad> | I have mythbackend stuck in a D state now |
| 13:34 | <Chutt> | heh |
| 13:34 | <Chutt> | can't kill -9 it? |
| 13:34 | <_shad> | nope |
| 13:34 | <_shad> | hehe |
| 13:34 | <_shad> | I did a mythbackend& |
| 13:34 | <_shad> | then a mythtv |
| 13:34 | <_shad> | it said it connected as a player |
| 13:34 | <_shad> | and did nothing |
| 13:35 | <_shad> | so I killed mythtv |
| 13:35 | <_shad> | and mythbackend wouldn't die |
| 13:35 | <_shad> | :) |
| 13:35 | <Chutt> | weird |
| 13:35 | <_shad> | ya |
| 13:35 | <_shad> | I had it partially working a couple days ago |
| 13:35 | <Chutt> | you did edit the backend_settings.txt file, right? |
| 13:35 | <_shad> | yep |
| 13:35 | <_shad> | I put in 127.0.0.1 |
| 13:35 | <_shad> | maybe that's why |
| 13:35 | <Chutt> | naw, that should be fine |
| 13:35 | <_shad> | hrm |
| 13:35 | <_shad> | I'm gonna do a reboot and try again |
| 13:35 | <_shad> | since I can't restart mythbackend :) |
| 13:36 | <Chutt> | it's just the address it uses to send to any client programs that want to connect back to it |
| 13:36 | <Chutt> | heh, sorry |
| 13:36 | <_shad> | heh |
| 13:36 | <_shad> | it's my tv box |
| 13:36 | <Chutt> | don't background it =) |
| 13:36 | <_shad> | it doesn't do anything |
| 13:36 | <_shad> | heh |
| 13:36 | <_shad> | so I'll have to open another shell to start mythtv? |
| 13:36 | <Chutt> | for now |
| 13:36 | <_shad> | ok |
| 13:36 | <Chutt> | that's probably the best thing to do |
| 13:37 | <_shad> | I can do that |
| 13:37 | <_shad> | Hey. I have a new uptime record with that box. 7 days |
| 13:37 | * _shad | laughs |
| 13:37 | <Chutt> | heh |
| 13:37 | <Chutt> | my dev box has been up for months |
| 13:37 | <_shad> | ya |
| 13:38 | <_shad> | you know how not to crash stuff though |
| 13:38 | <Chutt> | hehe |
| 13:38 | <Chutt> | ok, i'll bbl |
| 13:38 | <_shad> | k |
| 13:45 | <_shad> | Hrm. it segfaults the backend |
| 13:45 | -!- | moegreen [] has quit [Read error: 104 (Connection reset by peer)] |
| 13:51 | <Universe> | damnit |
| 13:51 | <Universe> | missed him again |
| 13:52 | <_shad> | hehe |
| 13:52 | <_shad> | you using CVS rightnow? |
| 13:52 | <Universe> | well... I updated this morning and I can't get it to compile |
| 13:53 | <_shad> | heh |
| 13:53 | <_shad> | do a make clean |
| 13:53 | <_shad> | err |
| 13:53 | <_shad> | distclean |
| 13:53 | <Universe> | I think its a gcc 3.2 thing |
| 13:53 | <_shad> | I think chutt's using 3.2 now though |
| 13:53 | <_shad> | what's the error? |
| 13:53 | <Universe> | one sec |
| 13:57 | -!- | Edgan [] has quit [Read error: 104 (Connection reset by peer)] |
| 13:58 | <Universe> | here... |
| 13:58 | <Universe> | In file included from /usr/qt/3/include/private/qucomextra_p.h:42, |
| 13:58 | <Universe> | from moc_dialogbox.cpp:15: |
| 13:58 | <Universe> | /usr/qt/3/include/private/qucom_p.h:443: ISO C++ forbids declaration of `e' |
| 13:58 | <Universe> | with no type |
| 13:58 | <Universe> | /usr/qt/3/include/private/qucom_p.h:443: parse error before `;' token |
| 13:58 | <Universe> | /usr/qt/3/include/private/qucom_p.h:443: invalid suffix on integer constant |
| 13:59 | <_shad> | heh |
| 13:59 | <_shad> | weird |
| 13:59 | <Universe> | hmm.. |
| 13:59 | <Universe> | it might be the QT version I am running |
| 13:59 | <_shad> | which ver? |
| 13:59 | <Universe> | 3.0.5-r2 |
| 14:00 | <_shad> | *** Opt devel libqt3-mt-de 3.0.5-4 3.0.5-4 Qt Threaded development files |
| 14:00 | <_shad> | is what I'm using |
| 14:00 | <Universe> | well.. |
| 14:00 | <Universe> | ok |
| 14:00 | <Universe> | then I have no clue |
| 14:00 | <_shad> | change you gcc? :) |
| 14:01 | <Universe> | I haven't.. |
| 14:01 | <Universe> | running 3.2-r1 |
| 14:01 | <_shad> | hm. what distro? |
| 14:01 | <Universe> | gentoo |
| 14:02 | <_shad> | ok. can't help you there :) |
| 14:02 | <Universe> | yesterday mornign I updated from cvs and compiled fine |
| 14:02 | <Universe> | I was getting a segmentation fault when closing LiveTV everything tho |
| 14:03 | <Universe> | so I thought I would just update this morning and if that doesn't fix it, bring it to Chutt's attention |
| 14:03 | <_shad> | yes |
| 14:03 | <_shad> | I get a seg fault on opening livetv :) |
| 14:03 | <Universe> | I get it on closing |
| 14:03 | <Universe> | heh |
| 14:03 | <_shad> | how do you compile with debug info? |
| 14:03 | <Universe> | edit settings.pro |
| 14:03 | <_shad> | kk |
| 14:05 | <_shad> | I hate computers |
| 14:05 | <_shad> | hrmmm |
| 14:05 | <_shad> | I have an idea :) |
| 14:06 | <_shad> | I remember chutt saying he's using the latest debian unstable |
| 14:06 | <_shad> | I haven't updated in awhile |
| 14:06 | <Universe> | heh |
| 14:06 | <_shad> | I bet he's using qt 3.1 and stuff |
| 14:06 | <Soopaman> | mdz, what were you saying about my problem? |
| 14:07 | <_shad> | *** Opt devel libqt3-mt-de 3.0.5-4 3.1.0+cvs.2 Qt Threaded development files |
| 14:07 | <_shad> | woo |
| 14:07 | <_shad> | maybe... |
| 14:08 | <Chutt> | universe, where's the error from in mythtv? |
| 14:10 | <Universe> | its just a segmentation fault after changing from WatchingLiveTV to None |
| 14:10 | <Chutt> | no, the compile error |
| 14:10 | <Universe> | oh |
| 14:10 | <_shad> | <Universe> In file included from /usr/qt/3/include/private/qucomextra_p.h:42, |
| 14:10 | <_shad> | <Universe> from moc_dialogbox.cpp:15: |
| 14:10 | <_shad> | <Universe> /usr/qt/3/include/private/qucom_p.h:443: ISO C++ forbids declaration of `e' |
| 14:10 | <_shad> | <Universe> with no type |
| 14:10 | <_shad> | <Universe> /usr/qt/3/include/private/qucom_p.h:443: parse error before `;' token |
| 14:10 | <_shad> | <Universe> /usr/qt/3/include/private/qucom_p.h:443: invalid suffix on integer constant |
| 14:10 | <_shad> | :) |
| 14:11 | <Chutt> | oh, from the dialogbox |
| 14:11 | <Universe> | aye |
| 14:11 | <_shad> | Chutt: I'm recompiling myth with debug info, and doing a debian update. we'll see what's wrong :) |
| 14:11 | <Chutt> | make sure you do a make clean |
| 14:11 | <_shad> | yep |
| 14:11 | <Chutt> | before compiling |
| 14:11 | <_shad> | already did |
| 14:11 | <_shad> | I love ccache also :) |
| 14:12 | <_shad> | going back and recompiling the release ver should take me under a min |
| 14:12 | <Universe> | tried that Chutt |
| 14:12 | <Chutt> | what's line 443 of /usr/qt/3/include/private/qucom_p.h |
| 14:14 | <Universe> | e=;<8n const QUuid TID_QUType_QString; |
| 14:14 | <Soopaman> | Chutt, are there any known problems of database creation with the apt-get mythtv release? |
| 14:15 | <Chutt> | no |
| 14:15 | <Chutt> | universe, err, that's not right :) |
| 14:15 | <Chutt> | universe, e=;<8n? |
| 14:15 | * Universe | shrugs |
| 14:15 | <Chutt> | kinda looks like you've got some file system corruption going on |
| 14:15 | <Universe> | thats what it says |
| 14:15 | <Universe> | DOH! |
| 14:15 | <Chutt> | i'm goin shopping =) |
| 14:15 | <Universe> | ok |
| 14:15 | <Soopaman> | chuytk |
| 14:15 | <Chutt> | hope your harddrive isn't dying |
| 14:15 | <Soopaman> | ws that no to me? |
| 14:16 | <Chutt> | soopaman, yes |
| 14:16 | <Universe> | dont have too much fun Chutt.. |
| 14:16 | <Soopaman> | damn... dpkg-reconfigure mythtv doesn't fix it either |
| 14:16 | <liscio> | Chutt: buying some hardware/ :) |
| 14:17 | <_shad> | chutt |
| 14:17 | <_shad> | I have a bt |
| 14:17 | <_shad> | bt |
| 14:17 | <_shad> | #0 NuppelVideoRecorder::IsRecording (this=0x0) |
| 14:17 | <_shad> | at ../libNuppelVideo/NuppelVideoRecorder.h:70 |
| 14:17 | <_shad> | #1 0x08072320 in TVRec::HandleStateChange (this=0x821fe10) at |
| 14:17 | <_shad> | tv_rec.cpp:350 |
| 14:17 | <_shad> | #2 0x08073d5f in TVRec::RunTV (this=0x821fe10) at tv_rec.cpp:522 |
| 14:17 | <_shad> | #3 0x08073d20 in TVRec::EventThread (param=0x821fe10) at tv_rec.cpp:507 |
| 14:17 | <_shad> | #4 0x406fc06f in pthread_start_thread () from /lib/libpthread.so.0 |
| 14:18 | <_shad> | #5 0x406fc0b5 in pthread_start_thread_event () from /lib/libpthread.so.0 |
| 14:18 | <_shad> | <before updating debian> |
| 14:19 | <_shad> | I'll try again once it's updated |
| 14:23 | <_shad> | Universe: you probably have a bad stick of ram |
| 14:24 | <liscio> | Universe: what FS are you using on your machine, btw? |
| 14:24 | <liscio> | _shad: bad sticks of ram often show much more subtle errors, and far more harsh... |
| 14:25 | <_shad> | well |
| 14:25 | <_shad> | I had a bad stick of ram |
| 14:25 | <_shad> | and it kepts fucking up files |
| 14:25 | <_shad> | that was all :) |
| 14:25 | <_shad> | it'd swap some characters and stuff |
| 14:25 | <_shad> | when I'd go do an update for debian, it'd complain about the formatting of the available file |
| 14:25 | <Universe> | oh crap... liscio... You are probably right... I have a questionable stick in there.. |
| 14:26 | <_shad> | Universe: install memtest86 and run it |
| 14:26 | <_shad> | sr/share/qt/mkspecs/linux-g++ -o tv_play.o tv_play.cpp |
| 14:26 | <_shad> | tv_play.cpp: In method `enum TVState TV::LiveTV()': |
| 14:26 | <_shad> | tv_play.cpp:113: warning: unused variable `int result' |
| 14:26 | <_shad> | hehe |
| 14:26 | <liscio> | Universe: _shad's the one that mentioned the bad stick possibility. :) |
| 14:27 | <liscio> | Universe: try rebooting the machine with a *slow* ram test in the bios and see how that goes. |
| 14:27 | <brtb> | some kinda corruption going on there... i had that once, not good |
| 14:27 | <_shad> | lisco: that doesn't usually catch stuff |
| 14:27 | <_shad> | memtest86 checks almost everything |
| 14:27 | <brtb> | use memtest86. that'll catch it |
| 14:27 | <brtb> | unless it's IO |
| 14:27 | <_shad> | ya |
| 14:27 | <_shad> | heh |
| 14:27 | <liscio> | _shad: never knew about that cmd. will try it one day.... :) |
| 14:27 | <_shad> | actually |
| 14:28 | <_shad> | liscio: it's actually a sep. proggy, you boot to it |
| 14:28 | <liscio> | unfortunately, I only have one stick of 512 in my mythtv box, and if it goes, I'm screwed. |
| 14:28 | <liscio> | _shad: oh...neat. |
| 14:28 | <_shad> | lisco: install the badram patch for linux, and you can take out that part of ram :) |
| 14:28 | <_shad> | memtest86 will give you a command line to show where the bad ram is |
| 14:28 | <_shad> | I have a bad stick of 128 here |
| 14:28 | <_shad> | ran it, and now I can use 96 of it ;) |
| 14:29 | <liscio> | _shad: that's pretty cool. |
| 14:29 | <Universe> | I will brb |
| 14:29 | <_shad> | ya |
| 14:29 | <liscio> | Universe: g'luck... |
| 14:29 | <Universe> | that computer == server |
| 14:29 | <_shad> | if you have a 512 stick of ram with a bad bit, you're in luck |
| 14:29 | <Universe> | k |
| 14:29 | <_shad> | heh |
| 14:29 | <_shad> | hopefully it IS the ram :) |
| 14:29 | <liscio> | _shad: yeah...fortunately nowadays RAM is cheap. :) |
| 14:29 | <_shad> | yep |
| 14:29 | <liscio> | _shad: especially if you stick to pc133 like me. :) |
| 14:29 | <_shad> | if it isn't you have other problems |
| 14:30 | <_shad> | such as your onboard ide dying |
| 14:30 | <_shad> | I have a couple of computers here with that |
| 14:30 | <_shad> | the primary channel is fucked, so I just use the secondary :) |
| 14:30 | <liscio> | wow. what do you guys do to your poor, poor hardware... :) |
| 14:30 | * _shad | works at a computer place, so he gets all the half-broken equipment to play with |
| 14:31 | <liscio> | _shad: you guys don't actually sell to end-users though, right? |
| 14:31 | <_shad> | no |
| 14:31 | <_shad> | it's what we get in and fix |
| 14:31 | <_shad> | I take it home to play with |
| 14:31 | <_shad> | hehe |
| 14:32 | <liscio> | _shad: that's right...i'm hoping at my full-time job there's opportunity for swiping some older hardware...I used to have four fully-functioning machines here that I had to sell a few months ago. :( |
| 14:32 | <liscio> | _shad: dual celeron 400, dual p2-350, p2-300, and a duron 800...those on top of my desktop and myth box... |
| 14:33 | <_shad> | hehe |
| 14:33 | <_shad> | bastard |
| 14:33 | <_shad> | I have like 10 machines |
| 14:33 | <liscio> | _shad: I needed lots of machines to test my BeOS drivers on... :) |
| 14:33 | <_shad> | p3-450 and less |
| 14:33 | <liscio> | _shad: and needed at least two dual-processor machines to try and trigger the more "fun" bugs... |
| 14:33 | <_shad> | hehe |
| 14:34 | <_shad> | I'm too poor to buy a new machine |
| 14:34 | <_shad> | I'll stick with this celeron 300A till it dies |
| 14:34 | <liscio> | _shad: well, they just keep getting cheaper. I can build someone a myth box for around 875 canadian... |
| 14:35 | <liscio> | _shad: unfortunately, you really have to justify that cost by using it for more than just mythtv. :) |
| 14:35 | <_shad> | yep |
| 14:35 | <_shad> | but the box will be using 100% cpu all the time though |
| 14:35 | <_shad> | so it can't really be a server :( |
| 14:35 | <liscio> | _shad: not the way I have mine configured. :) |
| 14:35 | <_shad> | well |
| 14:36 | <liscio> | _shad: 480x480 is watchable for me, and I have about 50% cpu for serving... |
| 14:36 | <_shad> | you have a fast machine |
| 14:36 | <_shad> | :) |
| 14:36 | <liscio> | _shad: and the mythtv boxen I build are 1800+'s vs. my 1700+... |
| 14:36 | <liscio> | so that might shave about 3-5% off.. |
| 14:37 | <liscio> | Besides, if you run mythtv nice'd, it doesn't really matter what else you run on the machine. :) |
| 14:37 | <liscio> | just as long as it's not disk-intensive (for obvious reasons) |
| 14:38 | -!- | Edgan [edgan@66-214-208-21.rno-cres.charterpipeline.net] has joined #mythtv |
| 14:38 | -!- | Universe [] has quit [Read error: 60 (Operation timed out)] |
| 14:38 | <_shad> | yea |
| 14:38 | <_shad> | I'm waiting untill the 6gig machines arive before I buy :) |
| 14:38 | <_shad> | or atleast 5 gig |
| 14:39 | <_shad> | by then I should have a house :) |
| 14:39 | <liscio> | _shad: didn't you read the slashdot article which shows the ceo of intel saying the processors are reaching their limits? :) |
| 14:41 | <_shad> | yes |
| 14:41 | <Soopaman> | i don't know why they are going retarded on processor frequency when the same motherboard bottlenecks exist |
| 14:41 | <_shad> | but that's for silicon :P |
| 14:41 | <Soopaman> | shit fucking damn |
| 14:42 | <Soopaman> | WHAT IS WRONG WITH YOU DEBIAN/MYTHTV/MYSQL#%!#^!$^!$^ |
| 14:42 | <_shad> | nothing |
| 14:42 | <_shad> | heh |
| 14:42 | <_shad> | 0.7? |
| 14:42 | <Soopaman> | it was bad enough i had to fight my way through the nvidia bastard kernel thing |
| 14:42 | <Soopaman> | yeah |
| 14:42 | <_shad> | what errors? |
| 14:42 | <Soopaman> | the apt-get'able release |
| 14:43 | <Soopaman> | all after the setup |
| 14:43 | <Soopaman> | lemme reget them |
| 14:43 | <_shad> | heh |
| 14:44 | <Soopaman> | "DBD::mysql::db: do failed: You have an error in your rSQL syntax near''*' at line 1 at -e line6, <> line 1" |
| 14:44 | <Soopaman> | in addition to 5 lines like that |
| 14:44 | <_shad> | gah |
| 14:44 | <_shad> | weird :) |
| 14:44 | <_shad> | you using unstable? |
| 14:45 | <Soopaman> | nope potato |
| 14:45 | <_shad> | that's probably why :) |
| 14:45 | <Soopaman> | welll kinda potato |
| 14:45 | <_shad> | what version of qt? |
| 14:45 | <Soopaman> | how do i check? |
| 14:45 | <_shad> | dselect? |
| 14:49 | -!- | Edgan [] has quit ["Client Exiting"] |
| 14:51 | <liscio> | how easy is it in debian to move from gcc-2.95 to gcc-3.2? |
| 14:51 | <_shad> | well |
| 14:51 | <_shad> | just wait a couple weeks |
| 14:52 | <_shad> | and debian unstable will be 3.2 |
| 14:52 | <_shad> | :) |
| 14:52 | <liscio> | :) |
| 14:52 | <_shad> | they're undergoing the conversion now.. sorta |
| 14:52 | <liscio> | but ignoring that fact, would I just have to install the 3.2 package, then recompile my kernel and drivers? |
| 14:52 | <_shad> | well |
| 14:53 | <_shad> | hem |
| 14:53 | <_shad> | heh |
| 14:53 | <_shad> | I have 3.2 installed |
| 14:53 | <_shad> | but it's not the default gcc |
| 14:53 | <_shad> | but all debian packages have to be recompiled AFAIK |
| 14:53 | <liscio> | right..was that via a deb package? |
| 14:53 | <_shad> | that's why it's taking so long |
| 14:53 | <_shad> | ya |
| 14:53 | <liscio> | oh. okay. I thought so. |
| 14:53 | <_shad> | *** Std devel gcc-3.2 3.2.2-0pre2 3.2.2-0pre2 The GNU C compiler. |
| 14:53 | <_shad> | *** Std devel gcc-3.2-base 3.2.2-0pre2 3.2.2-0pre2 The GNU Compil |
