Back to Home / #mythtv / 2002 / 12 / Prev Day | Next Day
#mythtv IRC Logs for 2002-12-15

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:16<yebyen>then i will refrain from adding anything, since it's probably already done
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<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 [] 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: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<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>BTW, how many people have CVS write access (just out of curiosity)
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>mythtv doesn't seem to be listening to my increased font size settings in theme.txt
01:38<yebyen>well, epg is
01:42<-- nyquiljer(jer@ has left #mythtv
01:48<yebyen>now nothing is
01:48<yebyen>what have I done
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:58<DigDig>Ok, i thought was crazy(er)
01:58<yebyen>whoa, setup does something now?
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>stuff's broken
01:59<yebyen>debs it is
01:59<mdz_>oh, so they do
01:59<mdz_>I forgot I left that as defaulting to max
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>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>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<mdz_>mythtv sux0rzz it sez permishun denide all the tiem
02:02<Chutt>i can write a little script, i suppose
02:03<Chutt>, 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: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<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<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>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: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<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>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>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<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>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<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_>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>or alternate
02:31<Chutt>i dunno what i want to call that
02:32* yebyenponders
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<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<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: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<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
03:01* Soopamancurses at his $^!$ nforce box
03:01<DigDig>What is nforce anyway? Is that an all nVidia thing?
03:02<Soopaman>integrated chipset
03:02<DigDig>Sound, video, PCI, everything?
03:04<DigDig>Sound like a good idea anyway...
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 [] 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 [] has joined #mythtv
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 [] 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:37-!-_bigguy_ [] 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 [] 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<Soopaman>did you encounter any problems?
06:23-!-bigguy [] has quit [Read error: 113 (No route to host)]
06:28-!-bigguy [] has joined #mythtv
07:02-!-bigguy [] has quit ["Off to B-E-D"]
10:08-!-Edgan [] has joined #mythtv
10:25-!-liscio [~root@] has joined #mythtv
11:08-!-Edgan [] has quit [Read error: 110 (Connection timed out)]
11:20-!-Edgan [] has joined #mythtv
11:22-!-_shad [] has quit [Read error: 110 (Connection timed out)]
11:24-!-moegreen [] 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@] has joined #mythtv
12:29<-- Universehas quit ()
12:30-!-Universe [] 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 [] has joined #mythtv
12:52-!-_shad [] has joined #mythtv
12:53<_shad>Stupid internet
12:53<_shad>Chutt: alive?
12:56-!-moegreen [] has joined #mythtv
13:15<Chutt>now i am
13:34<_shad>I'm dumb
13:34<_shad>I have mythbackend stuck in a D state now
13:34<Chutt>can't kill -9 it?
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>I had it partially working a couple days ago
13:35<Chutt>you did edit the backend_settings.txt file, right?
13:35<_shad>I put in
13:35<_shad>maybe that's why
13:35<Chutt>naw, that should be fine
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>it's my tv box
13:36<Chutt>don't background it =)
13:36<_shad>it doesn't do anything
13:36<_shad>so I'll have to open another shell to start mythtv?
13:36<Chutt>for now
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* _shadlaughs
13:37<Chutt>my dev box has been up for months
13:38<_shad>you know how not to crash stuff though
13:38<Chutt>ok, i'll bbl
13:45<_shad>Hrm. it segfaults the backend
13:45-!-moegreen [] has quit [Read error: 104 (Connection reset by peer)]
13:51<Universe>missed him again
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>do a make clean
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>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<Universe>it might be the QT version I am running
13:59<_shad>which ver?
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>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: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>I get a seg fault on opening livetv :)
14:03<Universe>I get it on closing
14:03<_shad>how do you compile with debug info?
14:05<_shad>I hate computers
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<_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: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<_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:11<Chutt>oh, from the dialogbox
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<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>universe, err, that's not right :)
14:15<Chutt>universe, e=;<8n?
14:15* Universeshrugs
14:15<Chutt>kinda looks like you've got some file system corruption going on
14:15<Universe>thats what it says
14:15<Chutt>i'm goin shopping =)
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>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>#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/
14:18<_shad>#5 0x406fc0b5 in pthread_start_thread_event () from /lib/
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>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<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<liscio>_shad: never knew about that cmd. will try it one day.... :)
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<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<_shad>hopefully it IS the ram :)
14:29<liscio>_shad: yeah...fortunately nowadays RAM is cheap. :)
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* _shadworks 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>it's what we get in and fix
14:31<_shad>I take it home to play with
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>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: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>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: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<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 [] has joined #mythtv
14:38-!-Universe [] has quit [Read error: 60 (Operation timed out)]
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<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>it was bad enough i had to fight my way through the nvidia bastard kernel thing
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: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>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: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>just wait a couple weeks
14:52<_shad>and debian unstable will be 3.2
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: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<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 Compiler Collection (base package).
14:54<liscio>so when debian unstable's ready with 3.2, then just doing a dist-upgrade with upgrade everything?
14:54<_shad>life is easy :)
14:54<liscio>okay. and how long do debian unstables take to get to debian stable status? :)
14:54<_shad>that's why debian is so stable
14:55<_shad>I just check #debian before updating
14:55<liscio>I see. so by sticking with the debian stable, I'm pretty safe right now.
14:55<_shad>if there's anything currently wrong in unstable, I'll know
14:55<_shad>if you don't mind the old versions of software
14:55<Soopaman>apt-shad, yeah like i thought i was using woodh
14:55<liscio>I *do* have to maintain a certain level of sanity to keep my webserver and email up...
14:55<Soopaman>or do i need to go sid?
14:56<_shad>I use sid
14:56<Soopaman>does everyone use sid?
14:56<_shad>liscio: hey, I use unstable and have a web/email server :)
14:58<liscio>_shad: so do I just add the word unstable to my sources?
14:59<liscio>hmm...what kernel is unstable running right now? 2.4.19?
14:59<_shad>that's just for the install
14:59<_shad>you can run anything
14:59<liscio>or will it not touch my kernel?
14:59<_shad>it won't
14:59<liscio>I see. so doing a dist-upgrade after s/stable/unstable/ would not bother anybody...
14:59<_shad>you can safely upgrade
14:59<_shad>as long as you know how to use apt-get
14:59<_shad>and dselect
15:00<_shad>foo) || DO NOT USE UNSTABLE (SID) unless you know how to use dpkg
15:00* lisciowill wait then. ;)
15:00<_shad>there might be some dependency conflicts
15:01<liscio>no sense causing more headaches. My kernel's as up to date as possible for my wireless adapter, so all is well. :)
15:01<_shad>I should go read
15:01<_shad>so I can relax
15:01<_shad>maybe Chutt will be back later to fix my problem
15:01* _shadlaughs
15:02<liscio>everytime I build the kernel, I have to then build my nvidia kernel driver again, my alsa drivers, and then my lirc...jeez.
15:02<_shad>2.5.x comes with alsa now
15:02-!-moegreen [] has joined #mythtv
15:03<liscio>can't wait 'til that's safe for normal human consumption...
15:04<Soopaman>i can't wait until i can stab my computer in it's eye
15:04<Soopaman>this thing is driving me insane
15:04<liscio>soopaman, if you find an eye in there, I strongly urge you to take the computer back to the manufacturer... :)
15:04<_shad>Ok, I'll be back later
15:04<liscio>ttyl shad..
15:04* lisciochooses to read as well...
15:05-!-Edgan [] has joined #mythtv
15:39-!-Universe [] has joined #mythtv
15:40<Universe>it was the ram... and more than just a bit..
16:17<liscio>Universe: that sucks bad?
16:20<Chutt>shad, mdz broke things
16:21<Chutt>get him to fix it =)
16:21<Chutt>thanks for the backtrace, though
16:21<Chutt>mdz, your changes to tv_rec.cpp took out the call to SetupRecorder()
16:27<Universe>liscio... its just one of my 128 sticks and its bad
16:27<Universe>just took it out
16:27<Universe>no biggie
16:28<Universe>so cvs is busted?
16:31<Chutt>it'll be fixed in a minute or two
16:32<Chutt>fixed now
16:33<Universe>even better.
16:44<liscio>Chutt: you have an ati tvwonder ve in your machine, correct? how much do you miss not having stereo?
16:44<Chutt>i have a hauppauge wintv radio as the primary card
16:44<Chutt>bought primarily because the wonder ve didn't do stereo
16:45<liscio>Chutt: so you did use MythTV with the ve at some point though, correct?
16:45-!-mdz_ [] has quit [Read error: 60 (Operation timed out)]
16:45<liscio>Chutt: Hmm...Because a basic mythtv box that I could put together could use a ve, along with a 40gb hd...then you're down to about 550US...
16:46<liscio>Getting there... :)
16:46<Chutt>the lack of stereo is a big thing, imo
16:46<liscio>I think I'd be so much better off if I could find a uATX mobo that just had on-board tvout with the on-board video...
16:46<liscio>Chutt: I'm sure it would be. But it'd be good to give the option for someone looking to save a buck, or so... :P
16:46* lisciodoesn't really have a basis for comparison between the two. Got stereo from the get-go. :
16:48<Chutt>no dolby surround
16:49<liscio>How does the dolby surround survive the mp3 compression?
16:49<Chutt>pretty well
16:49<liscio>I usually leave compression off anyway, myself...
16:50<liscio>Yeah. It makes sense to stick with the tvwonder pci, but maybe keep the HD a bit smaller. 35GB should give you about 35H of recording...what do tivos default with nowadays?
16:50<Chutt>i dunno
16:50<Chutt>never used one
16:51<Universe>I have the first tivo.. only has a 15 gig hd in it..
16:52<liscio>alright. so 35GB of recording space should do pretty well then... :)
16:53<Chutt>i'm applying your video settings patch
16:53<liscio>Thanks, Chutt. How do they work for you?
16:54<Chutt>shad, should be fixed in cvs now
16:54<_shad>Glad to be of service :)
16:54<liscio>Chutt: i see how this works... ;)
16:54<Chutt>like i said, blame mdz
16:54<liscio>Chutt: for what? is stuff b0rked?
16:55<_shad>How much will the debug version slow down mythtv?
16:55<Chutt>he broke stuff minorly
16:55<Chutt>usually too much to be useable
16:55<_shad>especially on a p3-450 :)
16:55<liscio>oh well...good to keep my butt away from the cvs for a few days then...because if I find a broken cvs tree, I just might put all my studying time into fixing it. :)
16:56<_shad>I don't want to study, that's why I'm doing this
16:56<liscio>Stupid pure math exam tomorrow...homomorphisms, ideals, rings, fields, ecch...
16:56<liscio>"hey beavis, he said homo..."
16:56<_shad>I have Microprocessor Analysis and Electronic Communications
16:57<liscio>sounds like a bit more fun... :)
16:57<_shad>Chutt: Where do you change the resolution now?
16:57<_shad>It is, sometimes
16:57<_shad>I just want to be done :(
16:58-!-bigguy [] has joined #mythtv
17:00<_shad>I'm blind
17:00<_shad>I still don't think of it as a 'recording' :)
17:02<_shad>mythfrontend is hardcoded to connect to localhost?
17:02<liscio>okay. on monday I'm gonna buy a mobo and video card to test the mythtv setup with...
17:02<Chutt>initially, at least
17:02<_shad>See, I know something. Grin.
17:02<Chutt>still need to change the backend_settings.txt file to change what it connects to later on
17:03<liscio>hopefully those parts will work 100% (as expected) and I will move the project along...
17:03<_shad>liscio: You have done research first, right? :)
17:03<liscio>I think that ideally I'd like to have my site set up similar to the site in that I will provide instructions on how to set the machine up (in the case someone feels adventurous...)
17:04<liscio>by set the machine up, I mean actually building and buying it.
17:04<_shad>Hrm. then I won't have a job, everyone will know how to build a computer
17:04* _shadcrys
17:04<_shad>I won't be in to work until the 23rd
17:05<liscio>_shad: I remember when I was about 12 years old and I installed my first ISA was all downhill from there. :)
17:05<_shad>I told them i have 4 exams, just not when :)
17:05<_shad>liscio: ya, me too, and it was a modem, and damn hard to get in. didn't want to break it :)
17:05<liscio>mine was a handheld (logitech) scanman...
17:05<_shad>'press down gently'
17:06<_shad>I wish I still had my 286-12 with a 2400 baud modem
17:07* brtblooks back at his IBM XT with the (they were evil even then) Microsoft Mach 20 Processor Upgrade board
17:07* lisciodoesn't... ;)
17:08<brtb>still have it, still runs, telnets and watches logfiles for me now. =]
17:08<_shad>I still have my original 42gig maxtor
17:08<_shad>and it works!
17:08<liscio>you mean 42meg, right? :)
17:09<liscio>my first one was 80meg...i must have been spoiled.
17:09<brtb>mine has the Seagate ST412. 10 megabytes...
17:10<brtb>could actually fit a word processor, spreadsheet, graphics and database program on it, with a little bit of room left for games
17:10<-- Universehas quit ()
17:11<liscio>_shad: and yes, I did the research before buying...
17:11<liscio>_shad: (re: the question before...)
17:12<liscio>_shad: I just want to make 100% sure for myself, and if anyone buys from me, I want to be able to say "yeah, I run the same setup..."
17:12<liscio>Right now my setup differs in video card and mainboard...
17:13-!-mdz_ [] has joined #mythtv
17:13<_shad>mythtv doesn't like me now :(
17:13<mdz_>Chutt: <Chutt> eh, commit it
17:14<brtb>I'm guessing it probably wouldn't be a good idea to try CVS at the moment, would it? =]
17:14<liscio>nope... :)
17:15-!-Universe [] has joined #mythtv
17:15<liscio>unless you want to toy with video settings in an otherwise broken environment. ;)
17:15<brtb>I'll... stick with 0.7 then. Might rebuild with Gentoo instead of slack though, just to test it
17:16<_shad>What's a res smaller than 320x240?
17:16<Universe>smaller? ouch..
17:17<liscio>divide both by two...160x120
17:18<_shad>it seems like the settings don't work
17:19* lisciotakes another step away from the cvs tree...
17:19<Universe>its not that bad
17:19<_shad>I've had both the frontend and backend segfault on me now
17:20<Universe>me too shad..
17:20<_shad>and it looks like it's staying in 400x480 or something, or higher
17:20* liscioruns...
17:20<_shad>my poor computer can't handle it now
17:20<Universe>I ran 352x240
17:20<_shad>it just seems so stall for me
17:21-!-CmdrChalupa [] has joined #mythtv
17:22<_shad>Idunno what to do now
17:22<_shad>it's brokered
17:26<mdz_>Soopaman: I was saying that the error message you saw means that there was some problem talking to the database. You can send me the _full_ output if you want and I can tell you more
17:26<mdz_>Soopaman: more than likely, you specified the wrong password for mysql or somethingh
17:29<_shad>here we go again
17:29<_shad>debug version
17:30<_shad>mdz: you like decoding backtraces, right? :P
17:31<mdz_>_shad: do you have a reproducible crash?
17:31<_shad>building with debug now
17:31<_shad>mythbackend: cannot connect to X server
17:31<_shad>do I need to set permissions so I can run from console?
17:32<_shad>set a display variable?
17:32<_shad>I forget now
17:32<_shad>got it
17:33<mdz_>I didn't think the backend required X...I haven't really done much with it since the split
17:33<Chutt>mdz, 'live tv' and 'default' don't show up in the list
17:33<_shad>my 35" is starting to go fuzzy :( very hard to read setup stuff
17:34<brtb>open TV, stay away from 35kilovolt wire and any large capacitors, using nonconductive screwdriver (just in case) mess with focus control until it's somewhat better
17:34<_shad>Chutt: since the switchover, I shouldn't have trouble getting it to run on my computer, when it would run fine at 400x480 with 0.7?
17:34<_shad>brtb: ya, my dad's an electrician. we do that all the time. don't really wanna screw with this yet :P
17:34<Chutt>shad, if you change to those settings, sure
17:35<-- Universehas quit ()
17:35<brtb>35" i understand why
17:35<_shad>Chutt: I even tried to put it down to 160x120, and it doesn't look like it accepted the settings
17:35<mdz_>Chutt: in which list?
17:35<_shad>brtb: it doesn't even have a back cover. :)
17:35<brtb>of course the last time I tweaked a 17" monitor I hiccuped which flipped the screen control all the way up, the protection didn't engage and a nice big cloud of grey smoke came out
17:35<mdz_>hmm, I see, in the editor list. odd.
17:36<_shad>brtb: hahaha
17:36<brtb>no back cover? ew
17:36<mdz_>no, I just don't have them in my db
17:36<brtb>luckily that was a throwaway monitor anyway, i was just trying to salvage it
17:36<mdz_>Chutt: I added them to 0-7-to-0-8.sql
17:37<mdz_>_shad: did you get that segfault to happen again?
17:37<_shad>mdz: just starting gdb
17:37<Chutt>i didn't run that, of course =)
17:39<mdz_>Chutt: should that stuff be in cvs.sql for now? or should cvs.sql be removed?
17:39<_shad>mdz: full backtrace, last couple lines?
17:39<brtb>what are they talking about on the list? re-encoding dvd for remote playback? erm
17:40<mdz_>_shad: send the topmost line or so to the channel, and the rest to the mailing list
17:41<_shad>mdz: just join #flooder
17:41<mdz_>Chutt: 19 downloads of the mplayer patch today
17:42<mdz_>_shad: what were you doing when this happened?
17:42<_shad>I started mythtv :)
17:43<_shad>it sputters for min then stops
17:43<_shad>so I kill mythfrontend
17:43<_shad>and mythbackend segfaults
17:45-!-Universe [] has joined #mythtv
17:48<_shad>mdz_: I just got mythtv to segfault, check the other channel
17:48<mdz_>_shad: yes, I this CVS within the past 5 days?
17:48<_shad>last 10 mins :)
17:50<mdz_>_shad: dunno, can't tell much. I'd have to try it here and poke around, and I don't have another box with a capture card to do it
17:50<mdz_>something looks to be hosed with the socket object
17:51<_shad>It's running on a p3-450
17:51<mdz_>but the problem is most likely due to your interrupting the frontend
17:51<_shad>but mythtv ran fine at 400x480
17:51<mdz_>and unrelated to the sputtering
17:51<_shad>that last one was without me touching anything
17:51<_shad>did my readbuffer fill and segfault?
17:52<mdz_>oh, there's a second one there, I see
17:52<_shad>I can give you access to that box if you want
17:55<mdz_>I don't have time to debug it in-depth, and I'm not familiar with that part of the code
17:55<_shad>I'll bug chutt
17:56<mdz_>I looked at it, and don't immediately see the problem
17:58* _shadgoes to get subs
18:01* lisciocalculates, realizes he only needs 25% or more on the final to pass. yay! :)
18:06<-- Universehas quit ()
18:33-!-gossamer [] has joined #mythtv
18:35-!-hadees [] has joined #mythtv
18:36<hadees>hey about how fast do of a chip do i need to do records and play like mp3s and watch tv
18:36<hadees>possibly at the same time
18:51<mdz_>hadees: it depends entirely on what kind of quality you want
19:00-!-hadees [] has quit [Read error: 60 (Operation timed out)]
19:05<CmdrChalupa>doesn't work on a Via C3 processor, guys
19:06<CmdrChalupa>Illegal Instruction
19:06<CmdrChalupa>for the setup command even
19:06<Chutt>read the faq, or the howto.
19:06-!-Kuwanger [] has joined #mythtv
19:07<Chutt>the 'troubleshooting' section of the docs, to be even more specific
19:08<liscio>Hmm...the price is looking more and more attractive for my american customers. No sales tax applied on the purchase at the time of sale -- only about 520 bucks at this point... :)
19:09<Kuwanger>Any ideas why a show scheduled to be recorded whenever it's on a channel wouldn't be recorded? There are no other shows conflicting, so it's not that. The show conflicts resolver doesn't even list the show.
19:09<Chutt>if the conflicts resolver doesn't list it, it's not scheduled
19:10<Kuwanger>Any ideas why it's not scheduled?
19:10<liscio>Yeah. In fact, I use the conflicts resolver to view what's scheduled for that fact alone. ;)
19:10<Kuwanger>The program manager shows it..
19:13<_shad>Chutt: Yooo
19:14<_shad>Chutt: I wanna watch tv :P
19:15<liscio>_shad: use xawtv ;)
19:16<_shad>I won't use an inferior product
19:16<_shad>It's not nice out :(
19:17<vektor>use tvtime then
19:17<vektor>liscio: did you take C&O 350 ?
19:18<liscio>vektor: that's the only course I've ever failed... :D
19:18<vektor>ahahahaahaha, really?! :)
19:18<liscio>vektor: I hated it so much, and the profs both sucked major ass.
19:18<vektor>which profs?
19:19<liscio>vektor: and on the exams, they put absolutely ridiculous problems that nobody could 12 iterations of the simplex method where they said they wouldn't do >3...
19:19<vektor>i shouldn't laugh, i almost failed it, the prof took major pitty on me
19:19<liscio>vektor: so I got hardcore screwed for time on the final because of stupid crap like that.
19:19<vektor>which profs?
19:20<liscio>vektor: I learned a valuable lesson that term -- never take a course just because someone you know is in it... :P
19:20<liscio>vektor: some young asian guy, and an older indian guy...
19:20<liscio>vektor: the indian guy, as I learned later in the term, was a better prof in class and I sorta understood what he said...
19:20<vektor>i got a 61
19:20<liscio>vektor: the younger asian guy just read out the course notes and transcribed them to the blackboard.
19:20<vektor>anyway, i'm using this reet app now called 'lp_solve'
19:20<liscio>vektor: I think I ended up with a 42...
19:21<vektor>it's cool
19:21<liscio>what lp's are you trying to solve?
19:21<liscio>or are you just playing?
19:21<vektor>it can solve IPs too
19:21<vektor>well, i'm supposed to write this paper on the achromatic number of graphs
19:21<vektor>with some ppl at schoo
19:21<vektor>so i need to prepare for our session tomorrow
19:21<liscio>yuck. so glad I'm stopping at undergrad. :)
19:21<vektor>and so i'm solving some IPs for the achromatic number of some graphs
19:22<vektor>so i wrote a reet program to generate the IPs in the format for this lp_solve app
19:22<vektor>and then run it
19:22<vektor>but it's really ass-slow on massive LPs
19:22<vektor>or IPs :)
19:22<vektor>IP is like NP-hard I think though
19:22<vektor>LP is in P, but still, these are bigass LPs :)
19:22<liscio>yeah...I was just going to say that...
19:22<liscio>'s in P, but in high-order n's...
19:23<vektor>so, solving the IP for the achromatic number of the 12-cycle took 30 seconds on my wimpy P3-733.
19:23<liscio>Interesting what we now class as "slow"...
19:23<liscio>I remember CS370. Now *there* we dealt with *sllllow*
19:24<vektor>well ok it's like still going on the 13 cycle.
19:24<vektor>it's been like 3 minutes
19:24<vektor>and i want this to go up to the 20-cycle.
19:24<vektor>i think i'm fucked.
19:24<vektor>i should just give up now
19:24<liscio>just nice it, and put it away in the background...
19:24<liscio>run a few copies, and just let it go...
19:25<liscio>grab some dinner, smell the flowers... :)
19:25* vektorgives up on the 13 cycle
19:25<vektor>i want to have like a bunch of results for tomorrow
19:25<vektor>and i think i'll have to settle for small graphs :)
19:25<liscio>I stick to n=0,1,2, and 3. after that I'm lazy :)
19:26<mdz_>lots of mythtv discussion going on here, I see ;-)
19:26<vektor>took 2s to solve the LP for the 13-cycle :)
19:26<liscio>mdz: of course. :)
19:26<vektor>mdz: sorry :)
19:26<liscio>mdz: we're solving to see if it's feasible to record 3 programs which may be listed in a cyclic graph...
19:26<bigguy>you guys really know how to make me fell like an idiot
19:27<liscio>and generating data to see if we can scale to 12 or even 13 capture cards... :)
19:27<bigguy>I don't even know wtf you are talking about
19:27<liscio>bigguy: neither do i.
19:27<bigguy>ip and lp?
19:27<liscio>Integer Programming and Linear Programming
19:27<mdz_>ip == intellectual property
19:27<mdz_>lp == line printer
19:29<liscio>vektor: you know what's funnY? I have done so amazingly well (comparatively) on my Pure Math courses than stupid calc and stuff...It's so much more straightforward!
19:29<liscio>I think people just run when they see "Pure Math" :)
19:29<bigguy>I like pure math
19:29<liscio>Anyone here use an SiS 730S chipset with success?
19:29-!-DigDig [] has joined #mythtv
19:30<bigguy>that LP and IP crap sounds difficult tho
19:30<DigDig>Ugh, the mailing list is just TOO active.
19:30<liscio>bigguy: it really isn't...there's an algorithm, and some matrix multiplication...
19:31<bigguy>its been so long since I had a math class tho so It'd prolly be hard for me to grasp ;)
19:31<liscio>bigguy: yeah...especially since math knowledge seems to decrease like radio signals... :)
19:32<bigguy>sure does
19:32<bigguy>I haven't done anything more complicated than balancing a check book in maybe 3 years
19:35<bigguy>course I never took anything higher that plane trig at the community college ;) I was a pre Engineering major at the 4 year but was put on acedemic probation cause out of my 21 hours the first semester I had 1 C and that C was because of a stupid proff. I can't help it if I am smarter than him ;)
19:35<bigguy>anyway couldn't afford to stay without the scholarship
19:36<bigguy>my life sucks that way tho :)
19:39* _shadhas tvtime running
19:43<mdz_>I'm waiting on the tvtime debs
19:44<vektor>mdz: Soon dude, soon.
19:44<vektor>The ITP is done, we just need to release 0.9.7.
19:45<mdz_>vektor: done?
19:45<_shad>where's the xmltv integration? :)
19:45<mdz_>vektor: an ITP is just a couple of paragraphs of text. it's 'done' when the package is done :-)
19:45<vektor>yea yea.
19:46<vektor>anyway, there's a debian directory in CVS :)
19:46<vektor>you can jst build it yourself :)
19:46<mdz_>what version number will it get?
19:46<vektor>good question
19:46<vektor>i don't know, i haven't ever tried it
19:46<mdz_>I'm not a fan of mixing the debian directory in
19:46<_shad>vektor: I waaaaaaaaaaaaaaannnna see an EPG :)
19:51<vektor>then code it
19:53<_shad>I can't code :(
19:53<vektor>then cry
19:53-!-nevertheless [] has quit [Remote closed the connection]
19:54<_shad>but you told me to use tvtime :)
19:54<_shad>Now I'll bug you.
19:54<vektor>bug me on #livid
20:02-!-gossamer [] has quit [Read error: 110 (Connection timed out)]
20:22-!-Randum [] has joined #mythtv
20:23<Randum>hello all, I'm having trouble getting mythtv compiled and setup, can someone help me out?
20:25<moegreen>what's the problem?
20:29<Randum>well, I got through the compile (although I'm not 100% sure everything went OK - got a lot of warnings)...... next step in the doc is to run setup, but I cant find setup in the directory it installed to... I see setup in the extracted source folder, but running it generates an error
20:29<Randum>./setup: error while loading shared libraries: cannot open shared object file: No such file or directory
20:29<_shad>did you make install?
20:30<_shad>did you add /usr/local/lib to /etc/ and run ldconfig?
20:30-!-moegreen [] has quit ["i must, i must, i must increase my bust"]
20:31<Randum>yes and yes
20:32<Randum>is there supposed to be a /setup in /usr/local/share/mythtv ? or does it mean the one in the extracted distro dir?
20:32<_shad>the one in the src dir I guess
20:34<Randum>well I'm not sure if the make went OK... got lots of seemingly path-related warnings....
20:34<_shad>did it end in an error?
20:35<Randum>there was "error 1" i believe a few lines up from the end.
20:35<_shad>so it didn't compile properly then
20:36<Randum>I thinkmaybe I didnt set some paths I needed to, the documentation is kind of confusing... it says "There are some paths that need to be modified before starting the main compile of mythtv, otherwise you will get errors." but then goes on the the ldconfig part and doesnt say what paths need to be added
20:37<Randum>hrmm... is there a maillist I could ask on? or just mail the author?
20:37<_shad>there's a mailing list
20:37<Randum>it called it a 'devel' list though.. I wasnt sure if user-ish installation issues would be welcome there
20:38<_shad>the devel is for commits, there are 2 of them
20:38<_shad>there's just the main one too
20:38<liscio>well the "main" one is still called mythtv-dev
20:39<Randum>yeah, there were 2, one called 'devel' and one called 'commits' - I guess I'll ask on 'devel'
20:39<liscio>and it's understandable to question how developer-centric the list is. People haven't gotten yelled at (too loudly) for asking questions on the list. In fact >90% of stuff on there is user questions...
20:39<Randum>ok cool
20:40<Randum>thx for the help
20:43<liscio>hmm...I wonder how fast the 5400RPM WD drives are...or any recent (<1yr) 5400RPM drives are performing.
20:44<liscio>might be a ton quieter to run...
20:44<bigguy>5400 wd drives suck
20:44<bigguy>if you go wd you want to get the 7200 ones with 8mb cache
20:45<bigguy>the seagate barracuda IV's are nice and they are quiet as well
20:46<liscio>all I can get are WDs from my supplier. I was under the impression that wd's were pretty good in the last year...
20:47<bigguy>well if I was building a myth box I'd want the 7200 wd's with the 8mb cache if wd's all I could get
20:47<liscio>i could be worse...they used to just have samsungs :)
20:48<liscio>how is the noise on the 8M's? hear anything along those lines?
20:48<Randum>i'm running a barracude IV, very decent performance and quieter than most 5400's. great drive
20:49<liscio>I'll have to search those out. I have not put much time into my other supplier, despite the fact they're much larger. I think it's mainly because I wanted to stick with the one that had all the uATX stuff... :)
20:59-!-bigguy [] has quit ["bbl"]
21:05<mdz_>Chutt: weird, I'm getting "DB Error: recorded program insertion failed, SQL query was:" messages from mythtv, but the queries appear to have succeeded (they were inserts, and the rows are there)
21:13-!-TheAsp [] has joined #mythtv
21:14-!-Kuwanger [] has quit ["Client Exiting"]
21:15-!-moegreen [] has joined #mythtv
21:17<mdz_>I feel a database abstraction layer coming on
21:18-!-DigDig [] has quit ["My damn controlling terminal disappeared!"]
21:20* lisciofeels a long delay in the next cvs version that'll work coming on. :)
21:24<liscio>damn. i think spamassasin might need installing on this machine... :P
21:24<liscio>any recommendations for spam taggers that play nice with exim?
21:30-!-Universe [] has joined #mythtv
21:42<-- Randum( has left #mythtv
21:56<-- moegreenhas quit ()
22:01-!-DigDug_ [] has joined #mythtv
22:09<mdz_> it wouldn't be appropriate to send user questions to the development list, so he thought he'd mail the author directly instead
22:11<_shad>poor chutt
22:16<DigDug_>Anyone know how I can get "Display" and "screen_num" out of Qt?
22:18<liscio>I think chutt should remove the line off the main page that says "there are no docs right now really, so feel free to email me..."
22:24<DigDug_>Chutt: how do I access the current x11 Display *dpy from withing MyDialog?
22:26<Chutt>digdug, try qt_xdisplay();
22:27<Chutt>and qt_xscreen()
22:27<Chutt>for the other
22:27<Chutt>so i'm getting bounces from some dumbass who's email account is over quota
22:28-!-bigguy [] has joined #mythtv
22:28<Chutt>but he's forwarding whatever he subscribed as to another account, so i can't tell what his subscription address is :(
22:28<bigguy>Chutt who is?
22:29<Chutt>i dunno
22:29<bigguy>someone on the list?
22:29<Chutt>that's the problem =)
22:29<Chutt>yeah, i've been getting bounces all night, someone's mailbox is over quota
22:30<Chutt>i'll have to page through all the email addresses and see if there's anything similar
22:30<Chutt>ah well
22:30<brtb>block 'em
22:31<Chutt>doesn't get rid of the problem
22:31<liscio>that sucks...thankfully you don't get any problems because my dns is b0rked. :)
22:32<Chutt>well, if you ever find yourself unsubscribed for some reason, it's nothing personal =)
22:32<_shad>it's liscio! ban him!
22:32* lisciohides
22:32<brtb>if he doesn't get any mail from you, it won't bounce... maybe?
22:32-!-liscio is now known as not_liscio
22:32-!-not_liscio is now known as liscio
22:32<Chutt>unless you forward your email to yahoo
22:33-!-Universe [] has quit [Read error: 104 (Connection reset by peer)]
22:34<_shad>Chutt: I suppose you can't help me with my problems. :)
22:34<Chutt>that it's not paying attention to your settings?
22:34<_shad>that is segfaults
22:35<_shad>I have a backtrace
22:35<Chutt>paste away
22:35<mdz_>something not paying attention to settings?
22:35<_shad><_shad> #0 0x4053eb66 in QSocket::consumeReadBuf () from /usr/share/qt/lib/
22:35<_shad><_shad> #1 0x4053f2d7 in QSocket::readBlock () from /usr/share/qt/lib/
22:35<_shad><_shad> #2 0x40095248 in RemoteFile::Seek (this=0x81d97c0, pos=-12, whence=1, curpos=44952692) at remotefile.cpp:206
22:35<_shad><_shad> #3 0x0807ce2c in RingBuffer::Seek (this=0x81d9738, pos=-12, whence=1) at RingBuffer.cpp:602
22:35<_shad><_shad> #4 0x08057bdb in NuppelVideoPlayer::GetFrame (this=0x40e0d008, onlyvideo=0) at NuppelVideoPlayer.cpp:1035
22:35<_shad><_shad> #5 0x08059a6a in NuppelVideoPlayer::StartPlaying (this=0x40e0d008) at NuppelVideoPlayer.cpp:1817
22:35<_shad><_shad> #6 0x08050a78 in SpawnDecode (param=0x40e0d008) at tv_play.cpp:38
22:35<_shad><_shad> #7 0x4077806f in pthread_start_thread () from /lib/
22:35<_shad><_shad> #8 0x407780b5 in pthread_start_thread_event () from /lib/
22:36<_shad>mdz: ya, i set it to 160x120, 320x240, or anything, it doesn't seem to do it :(
22:36<mdz_>_shad: you set it where?
22:36<Chutt>what's the profile called?
22:36<_shad>mdz: through the gui
22:36<_shad>both live tv and default
22:37<_shad>Chutt: I can give you access to the box if you want
22:37<mdz_>_shad: and when you go back into the profile, your settings are preserved?
22:37<Chutt>i'm not _that_ interested in helping :p
22:37<_shad>mdz: yep
22:37<_shad>Chutt: bah, it doesn't work though :)
22:37<mdz_>_shad: when it tries to load the settings, it dumps a bunch of information to standard output
22:37<mdz_>_shad: getValue(...) etc. what do you see there?
22:38<_shad>mdz: from mythbackend, or frontend?
22:38<mdz_>_shad: I assume the backend, where the encoder is
22:38<mdz_>_shad: should be about 10 lines starting with 'getValue'
22:38<mdz_>should be a couple of them that look like this
22:38<mdz_>getValue(width): 640
22:38<mdz_>getValue(height): 480
22:39<_shad>I don't see
22:39<mdz_>Chutt: does the backend close stdout or anything like that?
22:39<_shad>the last thing i see is the strange error
22:39<mdz_>oh, that debugging is gone
22:40<DigDug_>Chutt: hey thanks for the new MyDialog class. BTW, is there any particular reason why the GUI doesn't go fullscreen by default?
22:40<_shad>hrm. now I started backend, then mythtv, it plays choppy, then mythtv exits <not displays anything on screen> but it is still running
22:40<mdz_>_shad: in the getValue function on line 59 of settings.h, add this:
22:41<mdz_>_shad: cout << "getValue(" << getName() << "): " << settingValue << endl;
22:41<mdz_>_shad: or, if you have the mysql query log turned on, send me a copy of that
22:41<Chutt>digdug, well, when i'm developing stuff, it's easier if it's not fullscreen
22:42<mdz_>_shad: you're sure you have a 'live tv' profile that exists?
22:42<liscio>so is anyone devoting their time to setup-related tasks yet?
22:42<_shad>mdz: I ran the 0-7 to 0-8 sql thing
22:42<bigguy>they just don't put enough rye chips in chex party mix
22:42<liscio>not that mdz hasn't done a ton already. :)
22:42<TheAsp>got the cvs working, looks good... segs, back to 0.7
22:43<mdz_>liscio: what in particular are you looking for?
22:43<Chutt>theasp, thanks ever so much for that informative bug report
22:43<liscio>mdz: just anything to ease the settings process...
22:43<_shad> virtual QString getValue(void) const {
22:43<_shad> cout << "getValue(" << getName() << "): " << settingValue << endl;
22:43<_shad> return settingValue;
22:43<_shad> };
22:43<mdz_>there's a bit of code left to be written to add GUI elements for the theme settings
22:43<mdz_>and that's about it
22:43<_shad>is what you want mdz?
22:43<mdz_>_shad: yep, looks right
22:43<TheAsp>hehe, didnt mean it as a bug report, the setup stuff looks good
22:43<liscio>mdz: more for end-users running it for the first time.
22:43<mdz_>liscio: if you want to write the theme settings module, I wouldn't object :-)
22:43<Chutt>wow, really?
22:44<Chutt>if you're not going to run gdb on a segfault, don't even bother.
22:44<DigDug_>Chutt: well, i'll leave it alone for now, but it'd probably be better if the GUI went fullscreen by default so people don't have to change mythtv settings whenever they adjust X resolutions for their TVout.
22:44<TheAsp>actually chutt, im just tired
22:44<mdz_>liscio: there also might be a need for a one-time setup tool which would start the first time mythtv runs
22:44<liscio>mdz: i was thinking of writing a module that learns the remote for users, or presents them with a list of remotes...
22:44<liscio>mdz: among other things, of course.
22:44<mdz_>liscio: which would basically just throw up some of the existing components in sequence and give the user a chance to do initial configuration
22:45<DigDug_>That didn't sound right... :P
22:45<_shad>getValue(height): 480
22:45<_shad>getValue(width): 640
22:45<liscio>mdz: I want to be able to send my parents a box from scratch and get them up and running as easily as possible.
22:45<mdz_>_shad: those are the defaults
22:45<liscio>mdz: or at least think that way...
22:46<mdz_>liscio: in that case, the best thing would be to come up with some way to document the settings on-screen
22:46<mdz_>without taking up too much space
22:46<liscio>mdz: yeah. on-line help is definitely an important thing.
22:46<mdz_>I thought about balloon help, but I think it might suck
22:46<Chutt>dedicate part of the screen for a frame with help text in it
22:46<mdz_>it needs a little one-sentence blurb for each setting, like there is in the configuration file
22:46<liscio>mdz: i think just hitting a help button and bringing up a page that can be scrolled and exited...
22:46<_shad>now, i go to tv->setup->recording->Live TV, right?
22:47<Chutt>like a tooltip, but always on
22:47<Chutt>and in the same place
22:47<liscio>yeah...actually, that'd be neat...
22:47<mdz_>maybe it's possible to force tooltips to appear in a fixed position
22:47<mdz_>that'd be best
22:47<Chutt>but it'd work with just a qlabel in a frame somewhere on screen
22:48<_shad>mdz: where is it taking these defaults from?
22:48<mdz_>_shad: there are hard-coded defaults
22:49<mdz_>well, almost hard coded
22:49<_shad>where do I change it?
22:49<mdz_>_shad: you don't
22:49<mdz_>you override it in the database
22:49<mdz_>it sounds like your profiles don't exist in the database
22:49<_shad>like live tv, and default?
22:49<liscio>is it possible to run mythtv while mythfilldatabase is going?
22:49<mdz_>do a select * from recordingprofiles
22:50<liscio>i.e. will the db update gracefully in the background?
22:50<liscio>alright. because I thought it would be a pain in the ass to require end-users to sit and wait for the db to be 100% populated in a synchronous manner.
22:50<_shad>| 1 | Default | RTjpeg | Uncompressed |
22:50<_shad>| 2 | Live TV | RTjpeg | Uncompressed |
22:51<liscio>so they can just set their locale, and mythfilldatabase can run while they set the other crap up...
22:51<mdz_>_shad: select * from codecparams where profile = 2;
22:51<mdz_>_shad: look at the width and height settings
22:51<_shad>| 2 | height | 120 |
22:51<_shad>| 2 | width | 160 |
22:52<mdz_>_shad: how recent is your build?
22:52<_shad>the latest
22:52<mdz_>Chutt fixed a problem today where I had accidentally removed the bit that actually used the settings it loaded
22:52<_shad>I provided the BT
22:52<_shad>it wouldn't compile before
22:53<mdz_>wouldn't compile?
22:53<_shad>I'm tired
22:53<_shad>it would segfault
22:54<mdz_>ok, give me a login on the box
22:54* lisciohands mdz some DoS scripts... :)
22:55<_shad>he will have root too
22:55<mdz_>Chutt, liscio:
22:55* lisciowishes putty let you c&p more easily...
22:56-!-TheAsp [] has quit [Read error: 104 (Connection reset by peer)]
22:57<Chutt>people that post with the wrong address then email me saying sorry are silly
22:57<Chutt>especially when they leave off if they're going to do the reposting, or going to wait for me to approve it
22:57<mdz_>_shad: something is weird here
22:58<liscio>hmm...maybe instead of tooltips, the user can operate in a "friendly mode" where there's always a space showing help on all the screens. Perhaps it can be incorporated in the theme somehow.
22:58<mdz_>_shad: it's running all the right queries against the database
22:58<mdz_>liscio: that's what QTooltipGroup will do
22:58<liscio>mdz: oh yeah? it'll just sit at the top or bottom constantly? Nice.
22:58<mdz_>liscio: check out the URL
22:59<mdz_>lets you place text in a 'status bar'
22:59<liscio>"...typically in a status bar"
22:59<liscio>yeah. just got to that. :)
22:59<liscio>so we can just grab data from a string table. would that be a db thing?
22:59<liscio>probably would be a bit too slow, methinks.
22:59<_shad>mdz: me having my mysql.txt logon as root wouldn't screw it, right?
22:59<mdz_>nah, it'd be an attribute of the setting class
23:00<mdz_>_shad: nah
23:00<_shad>as long as it access the db. yea.
23:00<mdz_>_shad: can you privately paste me the full output from mythbackend?
23:01<_shad>mdz: just run mythbackend, and it will start
23:01<liscio>mdz: but we'd like to have the opportunity to easily go in and edit the help text without recompiling, right?
23:01<mdz_>_shad: I need you to watch live tv or something so it will load the settings
23:01<_shad>mdz: ok
23:01<mdz_>liscio: doesn't seem necessary
23:02<_shad>ok, it just paused, and kicked me back to the frontend
23:02<liscio>mdz: well I don't know what sort of detail we'd like to get into with the help, in fact, in some cases I'd expect there to be enough info to need scrolling :P
23:02<mdz_>seems to be trying to load profile id 0
23:02<mdz_>which is why it's ending up with the defaults
23:03<_shad>is it a database problem?
23:03<mdz_>argh, found it
23:04<_shad>did I fuck something up?
23:04<mdz_>nope, my bug
23:05* _shadis relieved
23:05<_shad>Don't want to waste your time :)
23:05<mdz_>_shad: update to latest CVS and rebuild and it should work
23:06<mdz_>_shad: actually, hold on, need to fix something
23:06<mdz_>_shad: ok, go
23:07* _shadwaits for his slow machine to compile
23:07* lisciofeels some excitement creeping up to do some settings/first-time work...
23:07<mdz_>Chutt: the fact that you don't get any results until you call next() once gets me every time...I find that so counter-intuitive
23:07<liscio>not used to the UI stuff since most of my code has been fairly low-level... :)
23:09<_shad>(gdb) bt
23:09<_shad>#0 0x080b192d in RTjpeg::bcomp (this=0x8fbed40, rblock=0x8fbed40, old=0x40e32fa0, mask=0x8fbf5f8) at RTjpegN.cpp:3108
23:09<_shad>#1 0x080b2cc1 in RTjpeg::mcompressYUV420 (this=0x8fbed40, sp=0x8fb72c0 "", planes=0xbedffa1c) at RTjpegN.cpp:3196
23:09<_shad>#2 0x080b1b0b in RTjpeg::Compress (this=0x8fbed40, sp=0x8fb5730 "HU\"\b\xDC4\xA0@A\024t@\v%\023\216\032 \026-", planes=0xbedffa1c)
23:09<_shad> at RTjpegN.cpp:3348
23:09<_shad>#3 0x0809848b in NuppelVideoRecorder::WriteVideo (this=0x41201008,
23:09<_shad> buf=0x8257d40 " ET`^igjovvxuwqje_OJE?<<77402150C9>4BJC@4m>;Erwxxzy|}rmdfho}\207\212\210\\??78Jmqppvzu|xe_cZXPH@LUww}\203yx{z|z|pfb`^adkutt{xrkhfhhksptkmprwvvuvxwzwrnmmsrotuvtmlmqxz\201\200\201\200! #KW]chnqtxx|zwvogcTPHC@>;984542358A;="...,
23:09<_shad> len=28800, fnum=2, timecode=161) at NuppelVideoRecorder.cpp:1605
23:09<_shad>#4 0x08097dd0 in NuppelVideoRecorder::doWriteThread (this=0x41201008) at NuppelVideoRecorder.cpp:1434
23:09<_shad>#5 0x08097344 in NuppelVideoRecorder::WriteThread (param=0x41201008) at NuppelVideoRecorder.cpp:1244
23:09<_shad>#6 0x4077806f in pthread_start_thread () from /lib/
23:09<_shad>#7 0x407780b5 in pthread_start_thread_event () from /lib/
23:10<_shad>I see it takes the right profile now though
23:10<_shad>does it not like the res I chose?
23:10<mdz_>does it happen every time?
23:10<_shad>gimme a sec
23:10<_shad>that was the first time I tried
23:10<mdz_>I've never used rtjpeg, so I'm not familiar with the code or the algorithm
23:11<liscio>alright. gotta finish off the studying. talk to y'all later...
23:11<_shad>#0 0x080af782 in RTjpeg::b2s (this=0x8fc1aa0, data=0x8fc1aa0, strm=0x8fd3ffc "", bt8=0 '\0') at RTjpegN.cpp:174
23:11<_shad>#1 0x080b2d94 in RTjpeg::mcompressYUV420 (this=0x8fc1aa0, sp=0x8fd3ffc "", planes=0xbedffa1c) at RTjpegN.cpp:3209
23:11<_shad>#2 0x080b1b0b in RTjpeg::Compress (this=0x8fc1aa0, sp=0x8fb8490 "\020\216%\b\xDC4\xA0@A\024t@\020+@\bH\xF2", planes=0xbedffa1c)
23:11<_shad> at RTjpegN.cpp:3348
23:11<_shad>#3 0x0809848b in NuppelVideoRecorder::WriteVideo (this=0x4100e008,
23:11<_shad> buf=0x825d5d8 " %H\200\220\230\233\230\233\233\234\xA1\xA3\211UILGDDEBD>>@@=?BA><?A@@@BBH>BBDFLIHSQIJHK?IFEHHC@@A@?C@BEEHJMLPOhwt{~~kTPRHKQS@:==CLbaJBQTdVI`wxxqxqyxtytv{{wwwxvrt~vsuuqrtsqwvutstrsutuvttxwoV (G\203\225\230\230\227\227\234\237\230\233\200UGKEGBDCE?<?><A=A>=@>BB@"..., len=28800, fnum=2, timecode=56) at NuppelVideoRecorder.cpp:1605
23:11<liscio>mdz: I'll be able to start on this stuff 100% more seriously come friday until the first monday of january, at the least. :)
23:11<_shad>#4 0x08097dd0 in NuppelVideoRecorder::doWriteThread (this=0x4100e008) at NuppelVideoRecorder.cpp:1434
23:11<_shad>#5 0x08097344 in NuppelVideoRecorder::WriteThread (param=0x4100e008) at NuppelVideoRecorder.cpp:1244
23:11<_shad>#6 0x4077806f in pthread_start_thread () from /lib/
23:11<_shad>#7 0x407780b5 in pthread_start_thread_event () from /lib/
23:11<_shad>second time
23:11<_shad>lemme change the res
23:11<mdz_>that's at a different place
23:11<mdz_>liscio: sounds good
23:12* lisciowaves
23:12<Chutt>something else is wrong
23:12-!-liscio [] has quit ["BitchX Official WWW Site --"]
23:12<mdz_>I probably won't be doing much more until next year
23:12<_shad>it's all my fault
23:12<Chutt>shad, do a complete make distclean
23:12<mdz_>yeah, that's good advice
23:12<Chutt>remove your existing libmyth* stuff
23:12<mdz_>I don't understand why this happens though
23:13<mdz_>is it that the build is linking against the installed library?
23:13<Chutt>why what happens?
23:13<mdz_>isn't there a -L to point it to the library in the source tree?
23:13<Chutt>that 'remove the existing library' is just for link errors at compile time, really
23:13<mdz_>why it breaks if the library is installed
23:13<mdz_>ah, so this is just the source tree not being rebuilt then
23:13<_shad>do a make uninstall first?
23:14<Chutt>i think
23:14<Chutt>shad, naw, don't worry 'bout that
23:14<Chutt>a make distclean should be plenty
23:15* _shadpretends that he knows what he's talking about. :P
23:15<_shad>any of you run ccache?
23:16<_shad>it saves a hell of a lot of time
23:16<mdz_>I run it here
23:16<mdz_>not with mythtv thus far
23:16<_shad>I have it set to run it by default
23:16<Chutt>i don't think you should run it with mythtv
23:17<_shad>after I did a make distclean
23:17<_shad>it's recompiling a lot of stuff now
23:17<Chutt>it should be recompiling everything :p
23:17<_shad>some little stuff it didn't
23:17<mdz_>I was suspicious of it, but it's actually quite careful to do the right thing
23:17<_shad>because of ccache
23:17<Chutt>but, does it work right with c++?
23:17<mdz_>tridge knows what he's doing
23:18<mdz_>I'm pretty sure I've used it with C++ before
23:18<mdz_>I ought to start using it with C++ more often, since g++ is so bloody slow
23:19<_shad>(gdb) bt
23:19<_shad>#0 0x409acbd4 in write () from /lib/
23:19<_shad>#1 0x40781b50 in __JCR_LIST__ () from /lib/
23:19<_shad>#2 0x40c7b9fe in vio_write () from /usr/lib/
23:19<_shad>#3 0x40c7af33 in net_real_write () from /usr/lib/
23:19<Chutt>but when i say 'make distclean'
23:19<_shad>#4 0x40c7b792 in net_write_command () from /usr/lib/
23:19<_shad>#5 0x40c77543 in simple_command () from /usr/lib/
23:19<_shad>#6 0x40c7a7c2 in mysql_real_query () from /usr/lib/
23:19<Chutt>i want you to compile _everything_
23:19<_shad>#7 0x40c645a2 in QMYSQLResult::reset () from /usr/lib/qt3/plugins-mt/sqldrivers/
23:19<_shad>#8 0x4058b87e in QSqlQuery::exec () from /usr/share/qt/lib/
23:19<_shad>#9 0x4058eec0 in QSqlDatabase::exec () from /usr/share/qt/lib/
23:19<_shad>r#10 0x08066da3 in Scheduler::CheckForChanges (this=0x822f928) at scheduler.cpp:121
23:19<Chutt>like, that's total junk
23:19<_shad>#11 0x0805c787 in runScheduler (dummy=0x821bb80) at main.cpp:42
23:19<mdz_>yeah, your build looks to be screwed
23:19<_shad>#12 0x4077806f in pthread_start_thread () from /lib/
23:19<_shad>#13 0x407780b5 in pthread_start_thread_event () from /lib/
23:19<Chutt>i told you to recompile everything
23:19<Chutt>and you didn't.
23:19<_shad>lemme try again without ccache then
23:21<_shad>fun stuff
23:24<_shad>I should resetup distcc
23:29<_shad>I bet you could compile of all kde in the time it takes for me to compile mythtv :)
23:31<_shad>#0 0x080b192d in RTjpeg::bcomp (this=0x8fc5f38, rblock=0x8fc5f38, old=0x40e58fa0, mask=0x8fc67f0) at RTjpegN.cpp:3108
23:31<_shad>#1 0x080b2b91 in RTjpeg::mcompressYUV420 (this=0x8fc5f38, sp=0x8fbbe76 "", planes=0xbedffa1c) at RTjpegN.cpp:3178
23:31<_shad>#2 0x080b1b0b in RTjpeg::Compress (this=0x8fc5f38, sp=0x8fb3328 "(\211\xE0\b\xDC4\xA0@A\024t@\031&\xE1\037h\xF8", planes=0xbedffa1c)
23:31<_shad> at RTjpegN.cpp:3348
23:31<_shad>#3 0x0809848b in NuppelVideoRecorder::WriteVideo (this=0x41201008,
23:31<_shad> buf=0x8257d40 " !7BEl\206QC\226\213J.6@QUr\237\234\223\212i=;4<??637883/.9LQ<.>:>LVO.$*'%#$+10+,,4-._h8(/<;D8+IZ_hkcbab^abacec]]TMSZUW_IJaR(+>D@BA6(\"%$'#)+5840*00&%&*$2Xg]JJcF:W\\<5Te<3@^~ybZlxlj\\gs\214\206\212\213pV>7VRO`fg}{c\205c*,**-/430--++271"..., len=57600, fnum=2, timecode=57) at NuppelVideoRecorder.cpp:1605
23:31<_shad>#4 0x08097dd0 in NuppelVideoRecorder::doWriteThread (this=0x41201008) at NuppelVideoRecorder.cpp:1434
23:31<_shad>#5 0x08097344 in NuppelVideoRecorder::WriteThread (param=0x41201008) at NuppelVideoRecorder.cpp:1244
23:31<_shad>#6 0x4077806f in pthread_start_thread () from /lib/
23:31<_shad>#7 0x407780b5 in pthread_start_thread_event () from /lib/
23:32<Chutt>if you do that again, i'm banning you, ok?
23:32<Chutt>the entire thing isn't needed
23:32<_shad>ok. something is being corrupted
23:32<_shad>the next time i run it:
23:33<_shad>#0 0x080aff71 in RTjpeg::DctY (this=0x8fc8c28,
23:33<_shad> idata=0x8273e40 "\215\215\200wqqxuy~\201\204\205\200\203\203\204\205\200yrs\200\200{~}dC;ANjp[PRS[_TWWYZY^\\XXY\\ZW^cfl{xn`_hfX=GQGJFDa\207\221\227uF?D=93,)/5?Q]]`gox\204\220\225\234\xA0C\xB2\xBCAAEA\223z\207\xA3EE\xC5AA,\xB7\xD1\xF1yyEhL^{\xA2\xB5\xB7\xBA\xBF\xC6A\xBFA\xC9EA\xC4\xC7I\xC9AEIOxOI\xC9\xC5EĻ\xBCE\xC9A\xC5\xC7\xD6\xDCU\xD8OOE\xC7A\xB7\xB7,\xB7,\xB0\xBF\xB6\xBC,,\xBA\xB1C\xA5\xA2"..., rskip=-67108354) at RTjpegN.cpp:732
23:33<_shad>lemme reboot this fuckin box
23:35<mdz_>_shad: stop overclocking it while you're at it
23:36<_shad>I did
23:36<_shad>still garbage bt's
23:41<mdz_>Chutt: something wrong with
23:41<mdz_>I can't get to ssh or pserver
23:41<Chutt>it's off at the moment
23:41<Chutt>needed my connection to do some stuff at the office
23:41<_shad>figured it out
23:41<_shad>when I went back to the settings
23:41<_shad>it was set to 320x120
23:42<_shad>as soon as I changed it to 320x240 it started working
23:42<Chutt>120 isn't divisible by 16
23:42<Chutt>so it doesn't work with rtjpeg
23:43<mdz_>it could fail somewhat more gracefully
23:43<Chutt>yeah, but oh well
23:44<_shad>I can't change it from 320x120 now
23:45<mdz_>Chutt: should the size spinbox move in increments of 16 then?
23:45<Chutt>that's only true in the case of rtjpeg
23:45<Chutt>the mpeg4 encoder pads things automatically, i think
23:45<mdz_>16 is pretty fine granularity though
23:46<Chutt>ok, that'll be fine, then
23:46<mdz_>I don't think it would be any great loss if it weren't possible to ask for 636x476
23:46<Chutt>that's just width
23:46<Chutt>i'm not sure what the constraints are for height
23:46<mdz_>currently it uses 4
23:46<_shad>well. that was weird
23:46<Chutt>more stuff won't work with the tuner card, anyway
23:46<_shad>it wouldn't save the changes, but if I switched to mpeg it did
23:46<_shad>now I can change it again in rtjpeg
23:47<Chutt>mdz, yeah, just make em all moveable by 16
23:48<Chutt>server's connected again
23:48<mdz_>just so that it doesn't take too many button presses to select different sizes
23:48<mdz_>the standard PAL resolutions are divisible by 16, right?
23:48<mdz_>in width
23:48<_shad>it won't save the changes in rtjpeg again
23:50<_shad>heh. I can't change the res from 400x480 to 400x400 :(
23:51<Chutt>are you going all the way through the wizard and using the finish button?
23:52<_shad>sometimes it saves the settings, other times it doesn't
23:52<_shad>it just let me change from 320x480 to 320x240 though
23:52<_shad>but not to 400x400
23:53<_shad>and now from 320x240 to 352x240
23:53<_shad>but not from 352x240 to 352x480
23:53<mdz_>I refuse to believe that it works with some numbers and not others
23:54<_shad>trust me :)
23:55<_shad> 27 Query UPDATE codecparams SET profile = 2, name = 'width', value = '352' WHERE profile = 2 AND name = 'width'
23:55<_shad> 27 Query SELECT * FROM codecparams WHERE profile = 2 AND name = 'height'
23:55<_shad> 27 Query UPDATE codecparams SET profile = 2, name = 'height', value = '240' WHERE profile = 2 AND name = 'height'
23:55<_shad>but I just had 480 in there :)
23:55<mdz_>works fine here
23:55<mdz_>I just tested it again to be sure
23:56<_shad>no idea :(
23:58<_shad>if I type it in
23:58<_shad>it doesn't work
23:58<_shad>but if I use the arrows, it does
23:59<mdz_>after you type it in, what do you do? click next?
23:59<_shad>yep, or tab away first