Back to Home / #mythtv / 2003 / 02 / Prev Day | Next Day
#mythtv IRC Logs for 2003-02-04

00:30-!-bigguy [bigman@h16.44.102.166.ip.alltel.net] has joined #mythtv
00:44-!-paperclip [] has quit [Read error: 113 (No route to host)]
00:50-!-paperclip [~joe@ip68-11-30-173.no.no.cox.net] has joined #mythtv
00:53-!-paperclip [] has quit [Remote closed the connection]
00:53-!-paperclip [~joe@ip68-11-30-173.no.no.cox.net] has joined #mythtv
03:04-!-DeeKs [~drew@mcp.albatross.co.nz] has joined #mythtv
03:13-!-rcaskey [] has quit [Read error: 60 (Operation timed out)]
03:27-!-journey [~journey@adsl-64-169-134-25.dsl.sktn01.pacbell.net] has joined #mythtv
03:28<journey>anyone have a g400 doing tvout through the framebuffer? i have 2.4.18, with all the matrox stuff compiled in, but matroxset comes back with ioctl failed, and i cant figure out what tod o
03:28<journey>do i have to do modules instead, or something?
03:31<-- journey(~journey@adsl-64-169-134-25.dsl.sktn01.pacbell.net) has left #mythtv
03:37-!-jrh has changed the topic to:
03:38-!-jrh [] has quit ["Client Exiting"]
03:51-!-nevertheless [~neverthel@pD952CF46.dip.t-dialin.net] has joined #mythtv
03:55-!-journey [~journey@adsl-64-169-135-12.dsl.sktn01.pacbell.net] has joined #mythtv
03:55<-- journey(~journey@adsl-64-169-135-12.dsl.sktn01.pacbell.net) has left #mythtv
03:55-!-journey [~journey@adsl-64-169-135-12.dsl.sktn01.pacbell.net] has joined #mythtv
03:58-!-nevertheless [] has quit [Remote closed the connection]
04:02-!-DeeKs [] has quit ["[BX] Eat, drink and be merry...for tomorrow we die"]
04:03-!-nevertheless [~neverthel@pD952CF46.dip.t-dialin.net] has joined #mythtv
04:48-!-nevertheless [] has quit [Remote closed the connection]
04:57-!-journey [] has quit [Read error: 60 (Operation timed out)]
05:41-!-nevertheless [~neverthel@pD952CF46.dip.t-dialin.net] has joined #mythtv
08:48-!-mdz [] has quit ["Client Exiting"]
09:55-!-Chutt [] has quit [Remote closed the connection]
10:52-!-Tuscany [~username@66.54.186.1] has joined #mythtv
11:17<hurdel>is mythweather timing out for anyone else here?
11:29<rkulagow>i had a problem when the shuttle disaster happened. are you getting blank pages displayed?
11:31<Viddy>it does for me sometimes getting pages
11:31<Viddy>but otherwise i have no problem
11:32<rkulagow>try hitting "m" to get it to refresh
11:41<Viddy>i seem to have a problem with mythtv, when i go to change channels, it hands
11:41<Viddy>eeh
11:41<Viddy>hangs
11:42<Viddy>it pauses fine, the osd comes up fine, the program display comes up fine
11:43<Viddy>not entirely sure why, but ive just finished a 13hr shift, so im off to bed
11:44<Viddy>err.. sure about the problem with mythtv, not why i did the shift ;)
11:51<hurdel>Viddy : with mythweather, i get the initial screen, then Connection Attempt #1...#20 etc..
11:51<moegreen>I'll have time tonight to rewrite the connection section of mythweather. I've been meaning to do it to make it more reliable.
11:53<moegreen>On that note though, it usually connects immediately for me - however occasionally it misses the first connection attempt, then works on the 2nd
11:54-!-bigguy [] has quit ["later"]
11:59<hurdel>thanks moegreen
12:00<hurdel>mythweather is sweet to just have on if you are not using myth as a pvr
12:00<hurdel>turn on tv, instant weather
12:00<hurdel>too bad it is -30C here today with -41C windchill
12:00<hurdel>even mythweather can't help that
12:02<moegreen>hurdel: well I don't know, you could always convert it to Fahrenheit :)
12:07<hurdel>DOH
12:07<hurdel>well, -40C is -40F so it is COLLLLD
12:17-!-Chutt [~ijr@dsl093-011-148.cle1.dsl.speakeasy.net] has joined #mythtv
12:32<rkulagow>chutt, did you see this?
12:32<rkulagow>> Subject: [mythtv] Your email is originating from yahoo.com. Due to the
12:32<rkulagow>> highvolume of spam coming from thi
12:32<rkulagow>>
12:32<rkulagow>>
12:32<rkulagow>> Your email is originating from yahoo.com. Due to the high
12:32<rkulagow>> volume of spam coming from this domain, you email has been
12:32<rkulagow>> moved removed and will be deleted. If you need to contact
12:32<rkulagow>> me, please do so from a different address.
12:32<Chutt>yeah, i just unsubscribed the dumbass
12:34<moegreen>it'd be nice if my email client wouldn't send two copies of everything to the mailing list.
12:35<rkulagow>chutt, i'm going to re-work the sound/mute patch to use the mixer associated with /dev/dsp rather than hard-coding /dev/mixer. i guess it's possible that someone may not be using their primary soundcard as their output device. i don't see that it needs to be selectable in setup though, do you?
12:35<Chutt>it should be
12:35<Chutt>just the same as /dev/dsp is selectable in setup
12:36<Chutt>well, settings
12:36<Chutt>in playback
12:36<Chutt>and yeah, once that's done, i'll accept the patch
12:36<rkulagow>ah, ok, then in that case i'll add it as the next field. means adding a column to the database though...
12:37<Chutt>it's just a normal setting
12:37<rkulagow>(next field in setup, with a default of /dev/mixer)
12:37<rkulagow>right.
12:37<rkulagow>thanks.
12:44<rkulagow>moegreen, are you here?
12:44<moegreen>i am
12:46<rkulagow>the latest commit to mythprogfind fixed the segfault issue. now i'm seeing that the sort for the program times seems to mix things up. for example, friends (wife likes it) is on multiple channels on multiple days. in the program time field though, the various times are showing up interspersed. so rather than 2/3, 2/4, 2/5, etc, i've got 2/4, 2/8, 2/12, 2/7, 2/3, etc, etc.
12:47<moegreen>yeah, I've been meaning to fix that as well. I'll get around to that as well tonight.
12:47<rkulagow>ok, just wanted to see if you knew about it. thanks.
12:48<moegreen>I guess it should go strictly by date, then by low->high channel number within each date?
12:48<moegreen>(and time)
12:50<rkulagow>that sounds about right. that way, if i'm looking to record friends on thursdays on NBC, i know that i can just go to thursday (if I know what date thursday will be) and start looking. Would 3 letter day abbreviations fit / be useful?
12:50<poptix>hrm
12:50<poptix>i wonder if mythtv is ipv6 aware
12:50<rkulagow>so instead of 2/8, it'll say Sat 2/8
12:51<poptix>if not, i should submit a patch for it.
12:51<moegreen>it says the three letter day now
12:52<rkulagow><duncecap> yes, of course. stupid "purloined letter" effect. no excuse for not even looking at the TV and seeing that mythprogfind already does that. </duncecap>
12:53<moegreen>heh, well i should get around to that tonight, bbl
12:54<rkulagow>thanks.
12:54<rkulagow>chutt, are you here?
12:56<Chutt>mostly
12:58<rkulagow>hi, chutt. in mythfrontend->setup->appearance->theme, the help text for GUI height is still being displayed when the cursor moves to date format and time format, but correctly updates when the cursor moves back to GUI width.
13:00<Chutt>it disappears for me..
13:00<poptix>Chutt: do you have any thoughts on IPv6 support?
13:01<Chutt>if qt supports it, it should be transparent to mythtv
13:01<poptix>i didn't even think about that
13:01<poptix>hmm.
13:03<rkulagow>hrmm.
13:03<poptix>i'll have to look at that.
13:05-!-Universe [~Yeah@pwc2-hs-nk.bbnplanet.com] has joined #mythtv
13:16<Chutt>rkulagow, easiest way to "fix" it would be to write help text for the date and time format entries =)
13:19<rkulagow>Chutt: That's what I figured. I think I raised it is because there are other places in setup where there's no help text and it blanks out when the cursor moves to the position.
13:50<mdz_>I get the same behaviour with the help text staying around
13:50<mdz_>on the buttons anyway, not sure about the input widgets
13:51<mdz_>I was thinking about adding help text which would be displayed when the buttons are focused (including when the window first opens)
13:52<rkulagow>chutt, mdz: any thoughts on context-sensitive help, like hitting F1 to get a list of the keys and their actions in mythfrontend in the various screens?
13:53<rkulagow>(essentially, a recap of keys.txt)
13:54<mdz_>sure, if you want to do it
14:03<Chutt>mdz, i'm moving the bookmark and cutlist stuff into the db
14:05<mdz_>Chutt: good plan
14:21<Chutt>ok
14:21<Chutt>this is strange
14:22<Chutt>update recorded set bookmark = '1234' where chanid = '1007' and starttime = '20030113220000';
14:22<Chutt>for some reason, sets the starttime to the current time
14:24<Chutt>ah
14:24<Chutt>silliness
14:39-!-rcaskey [~rcaskey@adsl-81-42-189.asm.bellsouth.net] has joined #mythtv
14:42-!-nevertheless [] has quit [Remote closed the connection]
14:44<mdz_>yeah, dumb timestamp fields
14:44<Chutt>heh
14:44<mdz_>I think you actually want DATETIME for most of those
14:45<Chutt>probably
14:45<Chutt>heh
14:45<Chutt>bookmarks with mpeg4 files recorded recently were broken
14:47<mdz_>yeah, I noticed that
14:47<mdz_>would crash when resuming
14:47<Chutt>libavcodec change
14:47<mdz_>ah
14:48<Chutt>they no longer store _all_ the header info every keyframe
14:48<rkulagow>chutt: i added help text for the date and time format, but they still don't update. i've make cleaned and then make; make installed.
14:48<Chutt>instead, the first frame is special
14:48<Chutt>fixed it, anyway
14:48<rkulagow>(in mythfrontend, globalsettings.cpp)
14:48<Chutt>rkulagow, i'll look into it more, then
14:48<rkulagow>ok. i'll commit the help text.
14:48<Chutt>can you commit your help text changes, though?
14:48<Chutt>thanks
14:49<rkulagow>done
14:53<Chutt>rkulagow, the new help text shows up here
14:53<poptix>hey Chutt
14:53<poptix>root 7097 27.2 5.4 75404 27996 ttyp6 S 06:36 40:51 mythbackend
14:54<poptix>root 7362 2.5 3.3 49920 17504 ttyp7 S 11:24 3:56 mythfrontend
14:54<poptix>myth* is using much less CPU now
14:54<poptix>that's an Athlon XP 2000+
14:54<Chutt>heh
14:54<poptix>it used to use ~85-90% cpu =)
14:54<poptix>i did tweak the compile flags though
14:55<Chutt>the split backend/frontend stuff helps a bit
14:55<Chutt>as do the playback optimizations mdz made
14:55<rkulagow>really. bizarre. mdz, you reported also seeing the help text not get reset (same issue I was having) when cursor moved while chutt reported blanks. do you see the new help text that I just committed?
14:55<poptix>that's rtjpeg, 720x480, 100 rtjpeg quality
14:56<Chutt>only 100?
14:56<Chutt>heh
14:56<poptix>i couldn't remember which way was higher quality =p
14:56<Chutt>ah
14:56<Chutt>higher is better
14:56<mdz_>rkulagow: dunno, what new help text? I can't look right now
14:56<poptix>i thought someone said lower was
14:56<poptix>shrug
14:56<mdz_>rkulagow: I'm using an older Qt as well, it has other problems
14:56* poptixmodifies
14:56<Chutt>set it really low for fun
14:56<Chutt>all you get is big moving colored blocks =)
14:56<mdz_>set it really high to fill your disk
14:57<Chutt>140 or so is good
14:57<Chutt>for that size of video
14:57<Chutt>iirc
14:57<Chutt>haven't used rtjpeg in ages, though
14:57<rkulagow>mdz: i added help text for the date / time formats. for me, it didn't work - i still see the previous help text; chutt says it worked for him.
14:57<mdz_>yes, I think I may have seen it not change
14:58<mdz_>but I'll have to check
14:58<mdz_>my mythtv machine is destroying itself; it's hung right now and I'm not at home to reset it
14:58<rkulagow>ok, thanks.
15:00<poptix>Chutt: are you clearing the ringbuffer when changing channels now?
15:00<Chutt>yup
15:00<Chutt>easiest way to handle it
15:01<poptix>hmm
15:01<poptix>it incurrs a noticable delay when you've got a large ringbuffer
15:01<poptix>(i've got a 15GB ringbuffer)
15:01<Chutt>heh
15:01<Chutt>yeah, i can imagine that
15:02<Chutt>though
15:02<Chutt>it should just seek back to the beginning and start overwriting it, not completely clear it
15:02<poptix>hmm.
15:02<poptix>one other thing i've been thinking about
15:03<poptix>when changing channels, there's a god awful screeching noise
15:03<poptix>seems to be common with WinTV cards
15:03<Chutt>yeah
15:03<Chutt>need to mute the tuner card before the change and unmute it after
15:03<Chutt>should fix that, at least
15:03<mdz_>the seek should be instantaneous with the right filesystem
15:04<Chutt>mdz, yeah, i _think_ i'm just seeking
15:04<Chutt>i might be clearing the file, though, i dunno
15:04<mdz_>truncate(2) on big files on ext[23] is way slow though
15:04<poptix>well, i got sick of the filesystem thread on the list
15:04<poptix>'this is beter, that is better..'
15:04<poptix>damnit.
15:04<Chutt>heh
15:05<Chutt>that whole discussion was silly
15:05<poptix>this is _not_ the stargate that was supposed to be on TV
15:05<Chutt>it's tv recordings, not mission critical data
15:05<Chutt>just use ext2 for its higher speed
15:05<poptix>Chutt: is there an option somewhere to go ahead and record a duplicate show?
15:05<Chutt>for writing and stuff
15:05<Chutt>poptix, nope
15:05<poptix>alright
15:06<poptix>for some reason the info for Stargate is wrong 50% of the time
15:06<Chutt>heh
15:06<poptix>and i've verified it's wrong in TV guide too =p
15:06<poptix>so it's not a zap2it/xmltv/mythtv issue.
15:26<rkulagow>chutt: i make clean distcleaned, make; make installed still don't get the help text for date and time format to show up. running qt 3.0.5 over here on mdk 9.0. i'll check in the code and see if there are other places where the help text doesn't show up - looks like TunerCardSetting uses similar code, so i'll see what happens there.
15:28<mdz_>rkulagow: I'm running Qt 3.0 on my system as well; it may just be a 3.0 vs. 3.1 thing
15:29<rkulagow>chutt: didn't work for TunerCardInput either. The common feature appears to be ComboBoxSetting
15:29<rkulagow>mdz: could be.
15:35-!-poptix [] has quit [leguin.freenode.net irc.freenode.net]
15:40-!-journey [~journey@adsl-67-113-57-142.dsl.sktn01.pacbell.net] has joined #mythtv
15:41<journey>anyone arround? I'm having just an impossible time getting the framebuffer TVout to work on a DH matrox G400(works with the matrox X drivers, just not through the framebuffer) . . . anyone who has experience setting this up?
15:45-!-journey [] has quit ["BitchX-1.0c19 -- just do it."]
15:46-!-poptix [pop-tix@precious.net] has joined #mythtv
15:46<rkulagow>journey: check the archives for a thread called "RE: [mythtv] G400-TV capture and playback?", 2003-01-14
16:01-!-nevertheless [~neverthel@pD952CF46.dip.t-dialin.net] has joined #mythtv
17:01<mdz_>Chutt: I'm not convinced that obfuscating the CVS login info is creating a significant barrier to entry. I think it's mostly generating a lot of traffic on the mailing list where one person asks for the info, and another person gives it to them or posts a link to the HOWTO
17:02<Chutt>yeah
17:02<Chutt>ah well
17:02<Chutt>heh
17:03<Chutt>check out the change i made to globalsettings.cpp
17:03<Chutt>i don't know how it was working before =)
17:07<mdz_>I think I have a lead on why my myth box is unstable
17:07<mdz_>http://pub65.ezboard.com/fk7s5amotherboardforumfrm5.showMessage?topicID=261.topic
17:07<nevertheless>mdz_: oh, you're running a k7s5a?
17:08<mdz_>nevertheless: yep
17:08<mdz_>it was my primary desktop machine for many months with no problems
17:08<mdz_>then it was a myth box for about 5 months with no problems
17:08<mdz_>now it is crashing at least once per day
17:09<nevertheless>hmm, I tried it, too, but I couldn't get the onboard audio to record stuff without bad noise, so I jumped for an epox one
17:09<mdz_>Chutt: wow, I'm amazed that worked before
17:10<mdz_>actually not that amazed...I remember I tried to re-use one of those string args in multiple places and it didn't work
17:10<mdz_>in some SQL
17:10<mdz_>no point in using numbers if they aren't honored, I say
17:12<Chutt>i'm doing something stupid
17:12<Chutt>(updating my unstable install)
17:13<rcaskey>Chutt: nooooo
17:13<rcaskey>KDE 3.1 is going in any day now though
17:13<Chutt>i'm already using cvs kde
17:13<rcaskey>haha
17:13<rcaskey>;)
17:13<rcaskey>I'm using 3.0.5 still
17:14<rcaskey>I was running 3.1rc's but I did a fresh install after I yanked my GeForce card and didn't need the custom kernel stuff any more
17:14<rcaskey>(anyone wanna trade a Matrox for a pair of GeForce2s?)
17:15<mdz_>Chutt: I sent you some caveats a couple of days ago about qt in unstable, you were idle at the time
17:15<Chutt>ah
17:15<mdz_>upgrading from those unofficial packages is a bit of a pain
17:15<Chutt>well, dselect is all happy
17:15<mdz_>and at the time, the packages in unstable were completely broken (missing stuff needed for qmake to work)
17:15<Chutt>heh
17:15<mdz_>oh, the dependencies resolve fine
17:15<Chutt>does it work ok now?
17:16<mdz_>the problem is that the files conflict
17:16<mdz_>yeah, it works now
17:16<mdz_>you'll need to --force-overwrite some stuff
17:16<rcaskey>btw, any chance of getting this stuff into unstable?
17:16<Chutt>no problem, there
17:16<Chutt>rcaskey, nope
17:16<rcaskey>is there something nonfree?
17:16<mdz_>patents
17:16<rcaskey>on what, xmltv?
17:16<mdz_>MPEG encoding
17:17<Chutt>the guide grid
17:17<Chutt>i'm sure someone's patented digital timeshifting
17:17<mdz_>it might be able to go into non-us if things ever get clarified
17:17<Chutt>but it's mainly the mpeg4 stuff
17:17<Chutt>and the mp3 encoding =)
17:17<mdz_>but right now I think everybody's too nervous
17:17<rcaskey>Chutt: ogg + ...dunno for mpeg4 ;)
17:17<Chutt>ogg's too slow
17:17<mdz_>hell, even red hat doesn't ship mp3 software anymore
17:18<Chutt>and the api sucks for this
17:18<mdz_>rcaskey: theora, but it isn't there yet
17:18<Chutt>and theora hasn't been updated in _months_
17:18<rcaskey>Chutt: if reencoding gets in, you might could just store it uncompressed if there is enough bandwith to handle it
17:18<rcaskey>and ogg/flacc it later
17:18<Chutt>not even close
17:19<rcaskey>Chutt: what's not? the bandwith or reencoding?
17:19<mdz_>they insist that work is still going on, though
17:19<Chutt>bandwidth
17:19<Chutt>mdz, unless they're doing all development closed, then no
17:19<mdz_>rcaskey: for audio, but not video
17:19<rcaskey>mdz_: yeah
17:19<mdz_>Chutt: maybe it's a really big checkin :-)
17:19<mdz_>word on the mailing list is that some stuff in ogg needed to be changed to support theora, and monty has been working on that
17:20<mdz_>and tremor, and 50 other things
17:20<mdz_>rcaskey: video is the hard one
17:20<rcaskey>mdz_: is that direct tv pci card supported by v4l?
17:20<rcaskey>im dying to do HD
17:20<Chutt>the vorbis guys are making the neuros play oggs, too
17:21<rcaskey>im moving out at the end of this semester
17:21<Chutt>so that's less time for theora
17:22<mdz_>I think that basically amounts to working on tremor
17:22<mdz_>no floating point, right?
17:22<Chutt>well, they're doing firmware mods, too
17:23<Chutt>yeah, no floating point
17:23<mdz_>is ffmpeg getting updated more frequently lately, or are you just synching up more frequently?
17:23<Chutt>i'm just syncing more frequently
17:23<Chutt>there wasn't anything major in what just went in
17:24<Chutt>i did the merge while i was waiting for it to recompile stuff
17:24<Chutt>they've got a CONFIG_RISKY now
17:24<Chutt>disables the mpeg4/wmv/rm codecs
17:25<rcaskey>Chutt: how much more overhead would be associated with funneling everything through VLC before encoding?
17:26<rcaskey>is it even possible to spit out raw streams over VLC?
17:26<Chutt>i wouldn't know
17:26<Chutt>hmm
17:27<mdz_>rcaskey: before encoding? it would be a ridiculous amount of bandwidth
17:27<mdz_>rcaskey: if you have a gigabit network at your disposal maybe
17:27<rcaskey>mdz_: :}
17:27<Chutt>i want to upgrade to gige here
17:27<Chutt>it wouldn't cost all that much
17:27<mdz_>I'm just going to wait, 10gige is coming down
17:27<Chutt>except for the router/access point dealie
17:28<rcaskey>Chutt: yeah, basically it means you cant use an all in one combo WAP dealie
17:28<rcaskey>and I have had aweful results with the one im using now
17:28<Chutt>i like my smc
17:28<mdz_>do they make a gige pcmcia card?
17:28<rcaskey>the only reason my myth server aint running it is because im constricted on pci slots
17:28<Chutt>i don't think pcmcia goes fast enough
17:28<rcaskey>Chutt: horrible experience with d-link here
17:28<mdz_>neither does wireless
17:29<mdz_>or cable/DSL/whatnot
17:29<rcaskey>at this point wireless is right out
17:29<rcaskey>I guess 802.11a/g could handle a stream
17:29<Chutt>i'm just impressed that smc has free 24/7 tech support, i called at 3 am and got someone competend when my router blew up
17:29<Chutt>competent
17:29<rcaskey>mdz_: but for the most part cable/dsl wont work because the hosts are not likely to be on connections with fast upload speeds
17:30<Chutt>mdz, you're going to get someone asking how to get the AIW working as a recording device now
17:30<mdz_>8-port gigabit switches for under $150 on pricewatch
17:31<rcaskey>mdz_: If Linux is the first OS where you can pop in a DVD or turn on your PVR and immediately have access to the information from anywhere over your LAN, it will draw lots of attention
17:32<mdz_>Chutt: I bet you're chomping at the bit to get that guy's MythTiVo into CVS
17:32<rcaskey>but for that to happen people will need to start making use of SLP or something similar
17:32<rcaskey>MythTiVo?
17:32<mdz_>sounds pretty elegant, what with the 3-stage pipeline with mplayer at the end
17:32<mdz_>rcaskey: mythtv-dev
17:32<mdz_> 8 L Feb 04 usenet@wingert. (2.0K) Re: [mythtv] Crazy Question?
17:33<Chutt>83MB left on this debian update
17:33<mdz_>I guess I forgot the second sentence about how you need a separate capture card
17:33<Chutt>heh
17:33<Chutt>hmm
17:33<Chutt>i like getting 404s when i go to update things
17:34<mdz_>it's that time of day
17:34<_shad>heh, update before it gets to the mirrors
17:35<mdz_>that's Debian bug #6786
17:35<mdz_>a very, very old bug
17:35<mdz_>heh, it was accidentally closed
17:36<Chutt>that is old
18:01-!-rkulagow_ [~a@12-250-190-224.client.attbi.com] has joined #mythtv
18:04<rkulagow_>chutt: i'm going to add "T" for toggling close caption into keys.txt. OK by you?
18:05<Chutt>sure
18:06<rkulagow_>OK, thanks.
18:06<Chutt>not that it works in ntsc-land yet =)
18:09-!-rkulagow [] has quit [Read error: 60 (Operation timed out)]
18:10-!-rkulagow [~rkulagow@12-250-190-224.client.attbi.com] has joined #mythtv
18:10<-- rkulagow_has quit ()
18:37<Chutt>there
18:37<Chutt>working unstable
18:38<vektor>unstable and working?
18:38<vektor>that unpossible!
18:41-!-rcaskey_ [~rcaskey@adsl-81-42-189.asm.bellsouth.net] has joined #mythtv
18:41-!-rcaskey [] has quit [Read error: 54 (Connection reset by peer)]
18:50<-- moegreen(~jdanner@pa-steclge-u2-c3a-154.stcgpa.adelphia.net) has left #mythtv
18:50-!-rcaskey_ is now known as rcaskey
18:57-!-nevertheless [] has quit [Read error: 54 (Connection reset by peer)]
19:07-!-mdz [~mdz@216-15-124-77.c3-0.smr-ubr3.sbo-smr.ma.cable.rcn.com] has joined #mythtv
19:08<Chutt>heh
19:08<Chutt>that's broken
19:08<Chutt>$(QTDIR)3/mkspecs
19:08<Chutt>whose bright idea was _that_
19:08<vektor>hey chutt
19:08<Chutt>hi
19:08<vektor>ahahaha
19:08<vektor>dude, sup :)
19:09<Chutt>not much
19:09<vektor>so, i've decided to do a 'bugreport.c' in tvtime
19:09<vektor>where it dumps to a file shit like /proc/cpuinfo, some X stuff, current load, etc
19:09<vektor>think it's a good idea?
19:09<vektor>i'm thinking it might save me some time
19:10<Chutt>it might
19:10<vektor>it might just also be buggy :)
19:11<mdz>Chutt: eh? QTDIR=/usr/share/qt3 works fine
19:11<vektor>so that will expand to /usr/share/qt33 ?
19:11<vektor>;)
19:11<mdz>where did that come from?
19:12<Chutt>well, i ran qmake in the top level to regenerate the makefile
19:12<Chutt>and that's what it did
19:12<mdz>weird
19:12<mdz>not for me
19:12<vektor>maybe you're weird :)
19:12<mdz>Makefile: mythtv.pro $(QTDIR)/mkspecs/linux-g++/qmake.conf
19:12* vektorj/k
19:12<mdz>vektor: that much is obvious
19:13<Chutt>if you have QTDIR set to /usr/share/qt3, it works
19:13<Chutt>if it's set to /usr/share/qt, like it needed to be previously, that's what it does
19:13<vektor>_ah_
19:13<vektor>that is broken
19:14<Chutt>i think it's building happily now
19:14<mdz>I still have to set QMAKESPEC, though. I thought they fixed that
19:14<Chutt>i have to set both
19:15<Chutt>qmake used to be a shell script wrapper that set QTDIR and QMAKESPEC
19:15<Chutt>that was nice
19:15<mdz>ln -s linux-g++ $QTDIR/mkspecs/default
19:15<Chutt>d'ya know a nice easy way to get the total size of all files in a directory?
19:15-!-moegreen [~jdanner@pa-steclge-u2-c3a-154.stcgpa.adelphia.net] has joined #mythtv
19:16<mdz>du -sh <dir>
19:16<Chutt>programmatically
19:16<mdz>if I set that symlink, I don't need QMAKESPEC
19:16<mdz>popen("du -s my_directory")
19:16<mdz>har har
19:16<Chutt>heh
19:16<mdz>no, not in C anyway
19:16<mdz>python has a nice little library for that kind of stuff
19:16<Chutt>i want to make a simple file cache
19:16<mdz>"I can do it in the shell but give me an API"
19:17<Chutt>for remote storage of stuff like the icons and preview pixmaps
19:17<mdz>hmm
19:17<mdz>why not keep it in memory?
19:17<Chutt>don't want to retransmit stuff like the icons
19:17<Chutt>hmm
19:17<Chutt>keeping it in ram would work, though
19:18-!-PeteCool [~PeteCool@modemcable131.217-202-24.mtl.mc.videotron.ca] has joined #mythtv
19:18<Chutt>transmit once per session
19:18<PeteCool>is there a way to test the Hz rate of the btaudio dsp?
19:18<mdz>I guess it could get big if you have a huge number of recordings
19:19<mdz>but screw it, I say
19:19<Chutt>heh
19:19<mdz>PeteCool: try to record something at a different sampling rate, it will fail if it is not supported
19:19<Chutt>i'll just do it that way for now
19:19<mdz>are the preview pixmaps always a static size?
19:20<Chutt>yup
19:20<Chutt>well
19:20<Chutt>in that frontend instance
19:20<Chutt>they do get scaled to display size
19:21<PeteCool>Chutt: when MythTV fills up it's storage directory/disk, the whole box hangs, do you have any idea why it does that? it (either the kernel or mythtv) should only complain, I think, and not hang
19:21<PeteCool>I filled up my disk many times when doing other things, and it never hung
19:22<PeteCool>do you know if myth might be the source of the hang?
19:22<PeteCool>or do I need to look elsewhere?
19:23<Chutt>mythtv doesn't check for a full disk
19:23<PeteCool>so it'll write and write forever? is that fixable at all?
19:24<PeteCool>or do I need to find some money for a big disk ;)
19:24<Chutt>'course it's fixable
19:24<Chutt>i just haven't ever gotten around to it
19:25<mdz>mythtv is not causing the whole box to hang
19:25<mdz>though if it is using the same disk as other programs, it can affect those programs
19:26<PeteCool>mdz: the buffer/recordings are on their own disk
19:27<PeteCool>mdz: anyways when I come back and the box is hung the disk is always full up to 0 bytes left, and since the box only does mythtv, I don't see what else might be causing it
19:30<mdz>PeteCool: how are you determining that the box is hung?
19:30<PeteCool>mdz: no keypresses work, no mouse, so ssh access
19:31<PeteCool>hrm
19:31<PeteCool>I mean no ssh
19:31<mdz>how would mythtv cause you to lose ssh access?
19:31<PeteCool>If I knew I'd fix it :)
19:32<PeteCool>usually it means nothing works at all
19:33<PeteCool>it's possible to get out of a hung X, but if the ssh daemon doesn't respond, it's usually because the box is frozen: it can't even let you log in!
19:33<PeteCool>or something like that, I don't know how to say it so it makes sense
19:34<mdz>I think there's a question in the FAQ about this
19:35<mdz>but basically, mythtv cannot hang your system
19:38<PeteCool>but hundreds of undeliverable write requests/commands/whateveryounameit I think might mess up the kernel?
19:44<poptix>hah
19:44<poptix>Changing from None to RecordingOnly
19:44<poptix>mythbackend: \xD4\xFB\xBF\xBEOq \xB6(
19:46<yebyen>heh
20:23<rkulagow>chutt: i was thinking about adding a check for duplex, and then i realized that once there's a full front/back split, a full duplex sound card won't be required unless they're on the same box. are there any internal variables that can be checked to see if frontend and backend are running on the same PC?
20:26<Viddy>ip
21:01-!-PeteCool [] has quit ["Client Exiting"]
21:03-!-PeteCool [~PeteCool@modemcable131.217-202-24.mtl.mc.videotron.ca] has joined #mythtv
21:03<PeteCool>are the preemt and lowlatency kernel patches any useful for mythtv?
21:26-!-SoopaKDE [~root@h24-66-55-163.wp.shawcable.net] has joined #mythtv
21:27<vektor>PeteCool: I have reason to believe the preemptive kernel backport to 2.4 breaks the bttv driver.
21:28<vektor>lowlatency might help avoid some dropped frames if your IDE driver or network driver sucks and someone noticed :)
21:29<Justin_>vektor :):)
21:31<PeteCool>vektor: preempt did work for me with bttv
21:33<vektor>Oh?
21:33<vektor>Hmm...
21:33<PeteCool>I'm using gentoo's 2.4.20 patchset
21:33<vektor>Maybe this is an updated version. Gerd said he would expect problems, and I had a user who's bttv was broke hard using gentoo's 2.4.19.
21:33<vektor>Maybe someone fixed a bug.
21:33<vektor>He had some _fucked_up_ bttv problems.
21:34<vektor>But if someone fixed a bug, it wasn't Gerd. :)
21:34<PeteCool>now I need to figure out why I heard a hard disk powering up... this is most probably why I see hangs. But the damn things are plugged in right, and fully in! :(
21:40<Justin_>Your order has completed step 5 of 5. Here is your invoice # 1890395.
21:40<Justin_>weeeeee:)
21:40<Justin_>its already in boston, will probably get here tomorrow:):)
21:42<PeteCool>Justin_: what have you ordered?
21:42<Justin_>ati tv wonder
21:43<SoopaKDE>so what's new in mythtv land?
21:48<PeteCool>what about the new themes? are they getting in cvs soon?
21:52<Chutt>i'm not going to put them into cvs
21:54<PeteCool>Chutt: why not?
21:54<Chutt>because that would be silly
21:55<PeteCool>Chutt: if they're good, why not? (I haven't tried them yet - but they will someday be good if the authors keep working on them)
21:55<Chutt>why bloat the cvs tree for stuff that doesn't need to be in there?
21:58<mdz>so I did the heatsink surgery on my motherboard, hopefully the mythbox will be stable again
21:58<Chutt>heh
21:59<Chutt>so a global context is lookin mighty nice right now
21:59<mdz>rkulagow: do you know anyone who has bought that staples PC? it sounds like a pretty good deal, even for a compaq
21:59<mdz>heh
21:59<SoopaKDE>mdz, what machine?
22:02<mdz>SoopaKDE: on the mailing list
22:03<mdz>ah, the mailing list
22:03<mdz>"runs Linux anyway, so you know the hardware's supported"
22:04<SoopaKDE>heheh
22:04<PeteCool>is the TiVo tuner even close to a bttv type?
22:04<SoopaKDE>i guess i should get up on the mailing list?
22:04<SoopaKDE>err no "?"
22:04<Justin_>the tv on the tivo is the least of the problems
22:04<Justin_>you kinda need access to their encoder board
22:09<rkulagow>mdz: no, i don't. the website keeps timing out.
22:15<vektor>mdz: That's hilarious.
22:15-!-Universe [] has quit [Connection timed out]
22:15-!-PeteCool [] has quit ["Client Exiting"]
22:22<rkulagow>mdz: were you able to confirm the help text thsa i added for the date and time format shows up? i'm wondering if this is a qt 3.0 vs. 3.1 issue since chutt can see it.
22:27<mdz>well shit
22:27<mdz>still fails memtest86
22:27<mdz>rkulagow: I cannot do anything useful with mythtv until this hardware problem is solved
22:28<rkulagow>eek, sorry to hear about your problems.
22:29<mdz>I have tried everything
22:30<mdz>soon I am going to have to assume that the board is fried
22:30<mdz>anybody know of a good cheap socket a board for my 1.4GHz athlon?
22:34<mdz>or know of any other hidden problems with the k7s5a that I can try to solve before I smash it?
22:35<mdz>"IMHO, an XBox seems like a great Myth FrontEnd"
22:35<mdz>things like this tempt me to unsubscribe
22:41<Viddy>i have a a7v 133a that works well with mine
22:41<Viddy>its stable as a ****** ******
22:41<Viddy>(good)
22:45<SoopaKDE>mdz, someone did myth frontend on xbox?
22:46<mdz>SoopaKDE: of course not. just people talking out of their asses
22:47<SoopaKDE>heheheh
22:47<SoopaKDE>ass talkers are funny
22:52<Chutt>hmm
22:52<Chutt>almost done with remote preview pixmaps
22:53<mdz>hey, all I have to do is clock it down to 1ghz and it's sortof stable
22:53<mdz>too bad I can't actually do anything at that speed
22:53<mdz>like, record and playback
22:53<Chutt>that sucks
22:54<mdz>I just got my other PC stable again and the myth box is failing
22:54<mdz>it's a disease
22:55<Chutt>made the preview pixmap stuff use the seek table
22:56<Chutt>so it doesn't suck anymore
22:56<mdz>good, because I can't use the live preview anymore
22:57<Chutt>heh
22:59<mdz>I always hated this board, I was glad to replace my desktop with something else
22:59<mdz>but still it haunts me
23:00<mdz>hardware prices don't seem to be falling as fast as they were a year ago
23:00<Chutt>heh
23:00<Chutt>so you did get the replacement ram?
23:00<mdz>yeah, didn't fix it
23:00<Chutt>figures
23:00<mdz>then I read an article about how some moron attached the chipset heatsink on this board using double-sided tape instead of thermal compound
23:00<mdz>and a lot of people had instability from that
23:00<Chutt>yeah, saw that
23:00<mdz>so I ripped it off and put it on right
23:01<mdz>and still it sucks
23:01<Chutt>could be the cpu, then
23:01<mdz>could even be the chipset problem, and it was damaged from being too hot for who knows how long
23:02<mdz>it works very hard
23:02<Chutt>heh
23:02<mdz>I would expect it to be more unstable if it were the cpu
23:03<mdz>if it were, then I might as well buy a whole new motherboard and cpu
23:03<mdz>and I'd have to get new ram to match, I have no ddr
23:03<mdz>but I think I've bitched about this enough
23:03<mdz>time to go to bed
23:04<Chutt>g'nite
23:27<rkulagow>moegreen: seems to run ok here.
23:28<moegreen>rkulagow: sounds good, i just committed it
23:28<rkulagow>cool.
23:32<rkulagow>moegreen: font sizes are hardcoded? i see 18*hmult for time, etc.
23:32<moegreen>yeah, i haven't changed that just yet. I should be able to use the big/medium/small font sizes
23:33-!-SoopaKDE [] has quit ["Using Kopete IRC Plugin"]
23:55<poptix>christ
23:55<poptix>what's with people quoting whole threads in their email to say 3 words/
23:56<poptix>there's 7 layers deep worth of >'s in this message