Back to Home / #mythtv / 2003 / 09 / Prev Day | Next Day
#mythtv IRC Logs for 2003-09-21

---Logopened Sun Sep 21 09:53:41 2003
09:53-!-mikegrb [] has joined #mythtv
09:53-!-Irssi: #mythtv: Total of 58 nicks [0 ops, 0 halfops, 0 voices, 58 normal]
09:53-!-Irssi: Join to #mythtv was synced in 1 secs
09:56-!-FryGuy [] has joined #mythtv
10:10-!-toe [] has quit [Remote closed the connection]
10:10-!-Captain_Murdoch [] has quit [Read error: 104 (Connection reset by peer)]
10:14<Chutt>tmk, yeah, i think
10:14<Chutt>i may have some time later today
10:15-!-toe [] has joined #mythtv
10:27-!-Ripp [] has quit [""Bring me the hydrospanners! I don't know how we're gonna get out of this one.""]
10:40-!-choenig [] has quit [Remote closed the connection]
10:41<tdb30_>which distro would be good and easy to set up if I want to use mythtv with lirc?
10:41<tdb30_>I know mandrake has some issues.
10:46<warlord>It works fine for me on RH9
10:50<warlord>I will note that I had a hardware problem that prevented it from working..
10:56<_rkulagow>works fine for me on mandrake (if you're using a serial-type receiver). had more problems with the hauppauge PVR-250 remote, but now that i figured out what the problem was it's just fine.
10:58<tdb30_>I had a problem getting lirc to work properly in mandrake. I got it to work but it was kind of a pain that it didn't work out of the box.
10:58<tdb30_>Was wondering if redhat was better.
10:58<_rkulagow>no idea. each distro has it's own issues.
11:00<_rkulagow>use whatever you feel comfortable with. there is no "best" distro.
11:00<tdb30_>do most people use pvr 250's? Anyone use win tv's?
11:02<warlord>I've got pvr-250s
11:02<warlord>and RH9..
11:03<warlord>and lirc worked fine once I got a working ir cable (my original ir receiver cable was broken)
11:04<tdb30_>I had a problem because I'm using /dev filesystem. So I had to play around. I guess I'll stick with mandrake since my proof of concept machine basicly worked. (it segfaults like crazy but it works)
11:06-!-kvandivo [] has joined #mythtv
11:09-!-dopez [] has joined #mythtv
11:11-!-nulltank [] has joined #mythtv
11:13<nulltank>does anyone here use a geforce4 440 mmx? i'm trying to get the tv-out working
11:14<nulltank>i'm going to give nvtv a try
11:15<warlord>nulltank: I'm using on onboard geforce4 440 (not sure if its an mmx). are you using the nvidia driver or the open-source 'nv' driver?
11:16<nulltank>when i plug the tv-out svidio up to an NTSC TV i just get wavy lines
11:17<nulltank>i've searched for correct if86config settings and there are a lot to choose from; so i'm just going to try nvtv and if that doesn't work i'll just try other people's configs
11:17<warlord>is this an onboard chip or an agp card?
11:17<nulltank>agp card
11:17<warlord>Ah, hmm..
11:18<warlord>You might have the wrong ntsc config, or output config...
11:18<nulltank>btw, i've got mythtv and all the plugins working (except for MAME) working on a gentoo install -- pretty cool stuff
11:19<nulltank>yeah, i'm sure i do -- i'll start playing with it; i was just hoping someone here might have the same card and already have a working xf86config file for me
11:19-!-jkolb [] has joined #mythtv
11:20<kvandivo>i've got that card.. (maybe a 420.. ) but I'm not using tv out
11:21<warlord>Unfortunately I've got an onboard card so I just set it in the BIOS.
11:22<nulltank>warlord: that sounds way too easy
11:22<warlord>It was.. it _just worked_
11:23<kvandivo>that hardly seems fair
11:23<warlord>If it's any consolation, lirc didn't work at ALL for me (had a hardware problem)
11:24<kvandivo>i think i got mine working.. i've since moved the 250 to the back room on the server and haven't messed with lirc since
11:25<kvandivo>on my xbox i use the xbox remote, and on my pc frontend i haven't messed with a remote (since my hand is normally within reach of the keyboard0
11:26<nulltank>i'm going to try and get lirc to work with my PVR-250 remote, that should be fun
11:26<kvandivo>you have the black or the grey one?
11:27<kvandivo>i'd like to find a good deal on a 250 at some point.. the fall season is going to be crimping my style here in a couple of weeks
11:29<nulltank>is there an ISO for mythtv on the xbox yet? that would really come in handy
11:30<nulltank>my friend has one and it would make for a great demo
11:30<kvandivo>hmmm... i think that there is one.. check the list archives for the name carter. i think 'dennis carter' or someone like that has made one
11:30<Chutt>it's on the front page of the website, still.
11:31<kvandivo>it goes without saying that your friends xbox has to be modded first, of course
11:31* nulltank is emerging nvtv
11:32<warlord>Chutt: are there docs on what needs to happen to update from 0.11 to "current CVS" in terms of database updates?
11:32-!-Timon [] has quit [Remote closed the connection]
11:32<Chutt>you don't need to do anything.
11:32<Chutt>but, no, there generally aren't docs for cvs.
11:32<warlord>Oh, there haven't been any DB changes? Ok.
11:40-!-jkolb [] has quit []
11:40<warlord>WTF? ivtv: Timeout waiting for data!
11:41<warlord>error reading from: /dev/video0
11:41<warlord>read: Input/output error
11:46-!-toe [] has quit [Read error: 110 (Connection timed out)]
11:47-!-toe [] has joined #mythtv
11:48<Chutt>um, it does.
14:02-!-[1]FryGuy [] has joined #mythtv
14:04-!-FryGuy [] has quit [Read error: 104 (Connection reset by peer)]
14:04-!-[1]FryGuy is now known as FryGuy
14:18<choenig>kwenda: I have the same problems here, it does not scale right, and I never found out, why
14:19<kwenda>sometimes its fine
14:19<kwenda>like i can watch 2 streams at once, PIP - no jumps
14:19<kwenda>but if two are recording at once, and i go to watch them later...i can tell it was concurrent
14:19<kwenda>it goes to about 20fps instead of 30
14:21<choenig>I did not work with multiple recordings lately because since my last kernel update X needs about 30% to playback, I don't know why that is, either
14:22<kwenda>hmm... is running mythbackend inside of gdm-binary going to cause problems?
14:22<sfr>choenig: so recording one show and watching another isn't working either currently? what cpu do you have?
14:23<choenig>sfr: recording and watchin LiveTV doesn't work if you mean that, I run an xp 2k+
14:26<sfr>choenig: yes, that's what i meant. :(
14:26<choenig>but X is funny in all its way here lately...
14:28<dis>Isaac: I'll work on getting some backtraces tonight for the "Waiting 2 seconds for data to become available" deadlock if you still need them
14:28-!-bbeattie [] has joined #mythtv
14:28<dis>just FYI it's not an ivtv issue. The other reports I've seen were from ivtv users, I'm using a G400 Marvel
14:29<choenig>I hat the problem that alphablended stuff in visor wasn't transparent, so I upgraded the matrox driver (from xfree to the mga one). I only installed the and everything looked nice from than on. Than I reinstalled X, which cleaned up but I still get the nice transparent stuff :)
14:29<sfr>dis: which msp3400 module are you using?
14:31-!-bbeattie [] has quit [Remote closed the connection]
14:31<dis>sfr: 2.4.20 stock msp3400 patched with the driver_fb version from
14:32-!-nulltank [] has quit [Remote closed the connection]
14:32<sfr>dis: are you using directfb output with myth?
14:32<dis>2.4.20 gentoo-gaming-r5 anyway, which is probably stock 2.4.20 as far as msp3400 is concerned
14:33<dis>sfr: I haven't tried but I assume DRI doesn't work with the directfb driver and I need OGL acceleration for a couple of emus
14:33-!-Jerry` is now known as Jerry
14:33<dis>i am using the framebuffer for tvout
14:34<sfr>dis: what patch to msp3400 do you mean?
14:34<dis>the "mga" driver with "UseFB" option enabled to be precise
14:34<dis>sfr: there's a cvs only version of the marvel drivers in branch driver_fb
14:35<sfr>dis: are they more current than the -0.1.1b release?
14:35<dis>and far better
14:36<dis>sfr: though I don't know if they're better if you're not using a framebuffer for tv-out
14:36<sfr>dis: maybe i should work on my antipathy to cvs :)
14:36<dis>sfr: they solved pretty much all my stability issues
14:36<dis>sfr: and I can watch at 1:1 70% if I wanted to, record at 1:1 100%
14:36<kvandivo>anyone with an antipathy towards cvs should definitely work on it
14:36<sfr>dis: what kind of issues? i'm still using the 0.1.1.b release.
14:37<dis>sfr: I used to have occasional mythbackend/frontend lockups that I'm pretty sure were conflicts between the various i2c modules that were doing the same thing
14:37<dis>since switching to the cvs drivers they went away . . . all was well until this deadlock reared its head
14:39<sfr>dis: hehe. btw. do you experience whining audio while watching live-tv or after changing channels?
14:39<dis>sfr: nope, occasional clicks though
14:39<dis>sfr: but that's an alsa issue with my old sblive. It doesn't happen if I use the oss driver
14:44<sfr>dis: so driver_fb in cvs supersedes driver?
14:45<dis>it's a different branch
14:46<dis>sfr: it's for people using the framebuffer for tv-out, or probably directfb for X11
14:46<dis>sfr: I have no idea if it'd work otherwise
14:46<sfr>dis: which i do (tv-out via framebuffer)
14:46<dis>sfr: then you probably want it. It is more recent than the stuff in driver
14:46<dis>sfr: but then again, if what you're using is working as is . . .
14:47<dis>sfr: can you watch at 1:1 with 0.1.1b?
14:47-!-mythtv_ is now known as jb4
14:48<sfr>dis: decimation 1:1? i think, but never use it as it didn't made a difference on my old tv.
14:49<jb4>anyone know how to turn auto-transcoding on? I've got a PVR-250 and 350 but need them doing mpeg4 rather than mpeg2...can't find the setting anywhere...
14:49<sfr>dis: and you applied all *.diffs to the kernel source files?
14:49<dis>sfr: yes. I had 1 chunk reject on 2.4.20 from one of the files but it was trivial to do it by hand.
14:50<dis>sfr: I believe in the i2c-* dif
14:50<jb4>or could anyone point to the section of docs that cover this? The reference I've found is very vague. thanks in advance...
14:50-!-kwenda is now known as kwenda|afk
14:50<sfr>dis: ok, thanks.
14:52<dis>jb4: "The first is an automatic process that can be enabled/disabled through the setup program"
14:53<jb4>dis: yes....but the instructions if offers to turn it on are very vague. I can't find the option anywhere within either mythtvsetup or the setup portion of mythfrontend
14:55<sfr>anyone here knows of a way to disable macrovision in Matrox binary X drivers for the G400/G200? that perl script doesn't work.
14:56-!-nulltank [] has joined #mythtv
14:56<dis>jb4: dunno then. I know i've seen the option somewhere when flipping through setup options
14:59<jb4>dis: ok, thanks anyway'
15:02-!-toe [] has quit [Read error: 110 (Connection timed out)]
15:04-!-bbeattie [] has joined #mythtv
15:14-!-mattfelsen [] has quit [Remote closed the connection]
15:21-!-billytwowilly [] has joined #mythtv
15:26<billytwowilly>when using mythweb I keep getting sent a file to download instead of a webpage displayed.
15:26<billytwowilly>any ideas on how to fix?
15:39-!-bbeattie [] has quit [Remote closed the connection]
15:43<dis>jb4: It's at the start of the recording profile. The first page...(ie setup->tv->recording->live tv <here>). At least it is with current cvs and the hardware mjpeg profile group
15:55<warlord>I'm trying to set up multiple pvr-250 cards, but when I try to configure /dev/video1 and /dev/video2 it seems to "fall back" to /dev/video0...
15:55<warlord>any clues?
15:55-!-bbeattie [] has joined #mythtv
15:57-!-billytwowilly [] has quit ["Client exiting"]
15:59-!-bbeattie [] has quit [Remote closed the connection]
16:02<warlord>Well, I got it working eventually...
16:02<warlord>Let's see if it works...
16:02<nulltank>well i wasn't able to get my geforce4 mmx to work, but i got an old voodoo3 3000 to work using nvtv
16:03<warlord>Hmm... strange..
16:03<nulltank>... with tv-out
16:03<nulltank>i read that geforce4 is supported well, but the mmx version might not be -- i might have bought the wrong version
16:04<Chutt>'mx' not 'mmx'
16:04<henry_>huh, I just bought a geforce4 mx 440 yesterday to replace my ati radeon, downloaded the latest driver from nvidia, changed my driver line in XF86Config-4 and it started right up (XFree86 4.3.0, Mandrake 9.1).
16:04-!-overridex [] has joined #mythtv
16:05<nulltank>yes you're right mx 440
16:05<nulltank>henry_: really? working with PAL or NTSC?
16:06<henry_>sorry, came into the middle of the conversation. NTSC
16:06<nulltank>henry_: can you send me your XF86Config? I am using NTSC
16:06<henry_>sure, how would you like to receive it?
16:07-!-billytwowilly [] has joined #mythtv
16:07<nulltank>henry_ send it to kylejunk at yahoo dot com
16:07<nulltank>henry_: thx
16:08<nulltank>henry_: did you use nvtv to get it working or just your XF86Config settings?
16:10<nulltank>the weird part is that when i boot my voodoo3 i can see the text mode just fine, but with my geforce4 mx 440 it is scrambled (just like when in xfree)
16:11<billytwowilly>is myth cvs stable right now?
16:11<Chutt>for the most part
16:11<warlord>It seems mostly stable... (I'm using it now)
16:11<billytwowilly>ok, is it faster than 0.11?
16:12<henry_>just the new nvidia driver (copied into /usr/X11R6/lib/modules/drivers) and changed the 'Driver "radeon"' to 'Driver "nvidia"'
16:12<Chutt>why would it be faster?
16:12<billytwowilly>Perhaps it's optimized more? I don't know.. I noticed what seemed like a huge performance hit from ~0.9 or 0.10 to 0.11...
16:12<henry_>the XF86Config-4 should be there (I emailed it).
16:13<billytwowilly>Had to lower recording quality to get rid of skipping somewhere in there.
16:13<Chutt>performance has increased since 0.9 quite a bit.
16:14<nulltank>henry_: got it, thank you
16:14<billytwowilly>perhaps I'm just mucking something up in my install then.. mdk should be coming out with 9.2 really soon, so I think I'm going to do a clean install then. will there be a new release of mythtv soon?
16:14<Chutt>i haven't decided yet
16:15<henry_>btw nulltank, my geforce4 is a "Predator" (not that it should matter).
16:15<nulltank>henry_: how do i tell what mine is?
16:16<billytwowilly>Chutt: what's holding you back if you don't mind me asking?
16:16<henry_>nulltank: uhhh don't know. My box says Predator.
16:17<nulltank>henry_: mine says palit daytona
16:20* nulltank is swaping his cards
16:23<henry_>I'm considering a Chaintech 7NIF2 mobo, anyone have any recommendations?
16:25<Chutt>nothing, i just haven't decided when to make a release
---Logclosed Sun Sep 21 16:34:28 2003
---Logopened Sun Sep 21 16:34:36 2003
16:34-!-mikegrb [] has joined #mythtv
16:34-!-Irssi: #mythtv: Total of 56 nicks [0 ops, 0 halfops, 0 voices, 56 normal]
16:34-!-Irssi: Join to #mythtv was synced in 7 secs
16:37<nulltank>henry_: well that sucks, it doesn't work for me; i don't have anything on my TV and nvtv doesn't recognise my board; did you do anything else? maybe i'm missing a module? can you /msg me your lsmod list?
16:38<Chutt>nvtv doesn't work with the mx boards.
16:38<mdz>nvtv works OK with my geforce2 mx
16:39<Chutt>that's a 2, though :p
16:39<Chutt>the 4mx's have the tv encoder chip built in
16:39<nulltank>i just noticed that my v4l modules were not loading; i'll try X with them loaded
16:41<henry_>nulltank: did you get
16:41<nulltank>henry_: i'm using the nvidia ebuilds in gentoo, so no
16:42<nulltank>it looks like i have nvidia-glx 1.0.4363
16:42<nulltank>maybe i should upgrade
16:43<henry_>I like gentoo, but in this case I also like a distro whose installation gui is functional on a tv-out.
16:43<Chutt>4496 is broken.
16:44<nulltank>henry_: what distro are you using?
16:44<henry_>nulltank: Mandrake 9.1.
16:44<henry_>Chutt: In what sense?
16:44<warlord>Hmm, does PiP actually work?
16:44<Chutt>the built in overscan doesn't work.
16:44<Chutt>warlord, of course it works.
16:45<nulltank>henry_: if i can't get gentoo working i'll give it a try, but i've spent a while getting all the mythtv/add-ons working
16:45<warlord>Hmm, cause mythfrontend crashes whenever I try to use 'B' or 'N' in PiP mode.
16:45<henry_>Chutt: Maybe I'll go to the nvidia archives and get another release, what would you suggest?
16:45<warlord>2003-09-21 20:43:57 rebuffering (135169 256000)
16:45<warlord>Input #0, mpeg, from 'rbuf://':
16:45<warlord> Stream #0.0: Video: mpeg2video, 160x128, 29.97 fps, 16000 kb/s
16:45<warlord> Stream #0.1: Audio: mp2, 48000 Hz, stereo, 384 kb/s
16:45<warlord>2003-09-21 20:44:09 prebuffering pause
16:45<warlord>2003-09-21 20:44:10 prebuffering pause
16:45<warlord>Myth Frontend ended at Sun Sep 21 20:44:12 EDT 2003
16:46<Chutt>the release right before 4496
16:46<Chutt>warlord, oh, don't bother looking into what's wrong
16:46<Chutt>it's going to look _horrible_ with a pvr-x50
16:47<Chutt>there's a nice little driver bug that makes small resolution video look like utter crap
16:47<nulltank>if i get the unstable ebuild of nvidia it would be 4496
16:47<warlord>Chutt: this has nothing to do with how it looks. It has to do with:
16:47<warlord>Program received signal SIGSEGV, Segmentation fault.
16:47<warlord>[Switching to Thread 1166596672 (LWP 3487)]
16:47<warlord>0x42073f80 in _int_malloc () from /lib/tls/
16:47<Chutt>i know, but don't even bother.
16:48-!-FryGuy [] has quit [Read error: 110 (Connection timed out)]
16:48-!-[1]FryGuy is now known as FryGuy
16:48<warlord>Oh, you know about the SEGV?
16:48<Chutt>i'm just saying that even if it did work for you, you wouldn't want to use it :p
16:49-!-sfr [] has quit ["Client exiting"]
16:49<warlord>Well, I'm more worried about the SEGV than how it looks at the moment.
16:49<Chutt>damnit, the ivtv-fb stuff just plain sucks.
16:52<kvandivo>just mailed off version 3 of the recommendations code
16:56<Chutt>kvandivo, just so you know i'm not ignoring your stuff -- i just can't touch any recommendations type code
16:57<warlord>ok, just mailed off the mythfrontend bt info for the PiP SEGV
16:58<Chutt>since one of our products at work is a recommendation engine
16:58<Chutt>warlord, thanks
16:58<warlord>Chutt: NP
16:58<warlord>one of these days I'll actually wrap my brain around the code and submit a patch instead of a crash dump ;)
16:58<Chutt>none of it is very complicated
16:59<warlord>now to figure out why /dev/video2 isn't working (although /dev/video1 and /dev/video0 are)
16:59<kvandivo>so what does that mean, chutt?
16:59<Chutt>means i can't personally work on code outside of work that does similar stuff to what i get paid for
16:59<kvandivo>(re: the health and well being of me continuing to submit versions of this)
17:00<warlord>Chutt: indeed, what I've looked at so far is fairly straightforward, but it's still going to take time to figure out all the pieces, where they live, and how they fit together.
17:01<Chutt>one of the other developers would have to look over and commit your changes, is all
17:01<kvandivo>i can understand (and relate) to that.
17:01<kvandivo>so how should we proceed on this?
17:01<kvandivo>ahh.. ok...
17:03<kvandivo>this is touchy, then.. I was wanting to discuss future plans with someone, but you might not be the best, in light of that
17:03<Chutt>captain_murdoch might be interested in that stuff
17:03-!-mecraw_ [] has quit [Read error: 104 (Connection reset by peer)]
17:03<Chutt>(chris pinkham, commercial skip/other stuff)
17:04<kvandivo>gotcha... I'll get in touch with him
17:04* kvandivo looks around.
17:05-!-mecraw_ [] has joined #mythtv
17:06<dis>henry_: I'm using a Chaintech motherboard in my myth box and quite happy with it. It's lasted more than the usual 13 months I get out of recent via based boards.
17:08<kvandivo>thanks for that explanation, chutt.. that helps a lot, actually. I didn't know if the code was bad, or you weren't interested in recs at all, or what.
17:09-!-dopez [] has quit [Remote closed the connection]
17:10<dis>Chutt: backtraces for my "waiting for input for 2 seconds" deadlock -- &
17:10<Chutt>yeah, i just don't want to explore the boundaries of my employment agreement
17:11<Chutt>dis, do you still have it in gdb?
17:11<kvandivo>particularly if your company has the typical bloodthirsty lawyers waiting in the wings
17:11<Chutt>it's a tiny place
17:12-!-tdb30_ [] has joined #mythtv
17:12<henry_>Thanks dis, it does however sound like I should be looking for a more recent mobo. Any recommendations for one w/similar features (geforce w/tv-out) micro atx?
17:13<dis>Chutt: no but it's being cooperative the last couple of tries and happening within a few minutes of firing up live tv
17:13<dis>Chutt: what would you like me to try?
17:13<Chutt>dis, yes
17:13<Chutt>if you can keep both the frontend and the backend in gdb, i've got a couple things i'd like to see
17:13<Chutt>you're missing tons of information, but maybe i can get it to give up some more
17:14<dis>hmm okay i can debug the backend from up here while i'm chatting, but I have to run back and forth for the front end (it's downstairs)
17:14<Chutt>the backend's fine
17:14<Chutt>for now
17:14<Chutt>the problem's there, most likely, anyway
17:15<dis>ok, i'll let you know when it locks up again . . .
17:15* kvandivo starts humming the Jeopardy theme for dis while he is waiting.
17:16<warlord>ok, why does each PVR card have Composite[0-4], SVideo[0-3], and Tuner0?
17:16<Chutt>because those are all the possible inputs
17:17<warlord>but the card only has two (or three) physical inputs on the back.. What's the difference between /dev/video0-Composite0 and /dev/video0-Composite1?
17:19<warlord>Umm, ok.. So the next question is: if some subset of my channels are only available through /dev/video2-Composite0, but everything else is available through /dev/video[012]-Tuner0, why would mythtv fail to tune to those extra channels?
17:20<Chutt>i dunno
17:21* warlord searches mailing lists for help before bothering Chutt...
17:21<warlord>Is there any way to figure out which particular video device is in use?
17:22<Chutt>you can point a browser to the status port on the backend
17:23-!-choenig [] has quit [Read error: 113 (No route to host)]
17:24<warlord>Does that depend on having MythWeb installed?
17:26<Chutt>just try hitting http://<masterbackendip>:6544/
17:26<Chutt>with a browser
17:26<warlord>Ahh, 44! No wonder...
17:27<Chutt>that's the default, at least
17:27<warlord>ok, so it's using "Encoder 1", whatever that happens to be..
17:27<Chutt>database order
17:27<warlord>Right, which appears to be inverse order to what I enter, or something..
17:27<Chutt>should be in the order you entered thigns
17:27<Chutt>it's an autoincrement field in the database
17:28<warlord>How does the database order map to the list in setup? I think the setup list is in reverse order?
17:29<Chutt>nope, that should be in order as well
17:29<warlord>Hmm.. Ok..
17:29<warlord>Regardless.. It's using one of the devices that doesn't have "channel 150"..
17:30<warlord>Channel 150 is only available via Composite0 on /dev/video2 -- but when I try to tune that it's doesn't like it...
17:30<warlord>I've got two things connected to /dev/video2 -- is that not allowed?
17:30<Chutt>live-tv doesn't really deal with different things available at different places very well
17:30<Chutt>i've never really had that situation, so i haven't really written support code for it
17:30<Chutt>recordings work fine, of course
17:31<warlord>I see...
17:31<warlord>So what would I need to do to add that kind of support?
17:31<Chutt>dunno, really
17:31<Chutt>i've only got one cable feed here, so i haven't ever thought about it
17:33<tdb30_>I was kind of wondering about that too.
17:33<warlord>That's........ unfortunate.
17:33<kvandivo>hmmm... I like :6544.. wasn't aware of it. I wonder what other useful info could be spit out on that..
17:33<tdb30_>I have a digital cable box and was wondering about recording from that and also from a regular basic cable feed.
17:34<warlord>tdb30_: that's my case, too..
17:34<warlord>it does seem to allow recording of it just fine..
17:34<Chutt>kvandivo, bunch of stuff, just a matter of writing the code for it
17:35<Chutt>right, it's just live-tv mode
17:36<warlord>Yea.. Ok. So, how is live-tv different than record mode? (I'm asking because this is a show-stopper for me).
17:37<Chutt>if all you want is it to change channels to other inputs automatically, that's not difficult to do
17:37<Chutt>changing cards in live-tv mode is difficult, however
17:38<warlord>I need both, unfortunately.
17:39<warlord>because there is no guarantee that livetv is going to choose the card with the extra device.
17:40<warlord>well, the ringbuffer is already 'destroyed' across a channel change, so what's the problem with attempting to change encoders, too?
17:40<Chutt>connection to the backend
17:40<Chutt>the desired card may not be available
17:41<warlord>Sure, and if it's not available _THEN_ it should fail (and IMHO it should fail with a dialog saying "encoder for channel not available" rather than just fading the channel away without any indication of why.
17:42<warlord>Some of this is input from my wife, who works as a QA/Test/UI-evaluator/Techwriter for MIT.
17:44<Chutt>making a dialog pop up takes time :p
17:44<Chutt>i don't have that much of that
17:46<warlord>Ok, how about at least a cerr << ... or cout << ... ? ;)
17:46<Chutt>you know where to send patches =)
17:46<Chutt>i'm working on the pip stuff, btw
17:46<Chutt>looks.. weird.
17:47<Chutt>not sure yet what it is
17:47<warlord>So, I'm resettig my encoder cards, but when I add my second tuner it appears earlier in my list.
17:47<warlord>(also, I need to go through the setup process twice for each card because it doesn't take the first time through)
17:48<Chutt>you hitting escape in there?
17:51<warlord>no. should I be?
17:52<warlord>Ok, it IS in order.. It's just that I need to edit each entry twice. First I need to create it (it will always pop back to video0) and then I need to edit it again and reset it apropriately.
17:52<Chutt>huh, weird.
17:53<warlord>yea. not a showstopper by any stretch of the imagination (read: please please please put PiP and multiple-tuner live-tv ahead of this one ;)
17:54<Chutt>i'm not going to do the multi-tuner live-tv stuff
17:54<Chutt>i will fix the pip crash, though
17:55<warlord>Would you accept a patch for the multi-tuner live-tv stuff?
17:55<Chutt>of course
17:55<warlord>Ok :)
17:59<nulltank>anyone have problems getting the MAME module to see the MAME ROMS? anyone know how i can debug?
17:59<warlord>I have a feeling my wife will be unamused until she can auto-tune live-tv to BBC-America :)
18:05<dis>well the damn thing just keeps going and going now that i actually need it to happen
18:06-!-robertj_ [] has joined #mythtv
18:06<dis>it's my bedtime, I'll be back around this time tomorrow by which time i'm sure it will have happened
18:07<kvandivo>there. that add a tiny little bit to 6544 to make it more juicy
18:07<moegreen>ay: I've got the imdb lookup stuff fixed (if you're around)
18:08<dis>nulltank: I was having that problem about a week ago (when i was trying to set it up). I'm not sure if a cvs update or compiling mythgame without my usual heavy optimizations was what fixed it but it was one of the two
18:09<nulltank>dis: hum, i didn't optimize at all when i compiled, so maybe i need the cvs version -- i'll give it a try
18:10<dis>nulltank: when you scan for roms does it just sit at 0% forever?
18:10<nulltank>dis: nope, it scans in about 1-2 seconds and doesn't find any
18:10<dis>anybody interested in pc engine emulation integration into mythgame?
18:10<dis>nulltank: might be a different problem then
18:11<dis>nulltank: which version are you using? 0.11?
18:11<nulltank>i've got the PC game tuxracer working and that's it; if i had any nes or snes roms i would try them to help isolate the problem
18:11<nulltank>yes 0.11
18:11<nulltank>i've checked my binary path and rom dir paths over and over
18:12<dis>do you have a valid catver.ini file?
18:12<nulltank>my roms are zipped; but i tried unzipping one to see if that mattered and it still didn't work
18:12<dis>they work fine zipped
18:12<nulltank>i downloaded the latest from catver.???
18:13<nulltank>what makes it "valid" ?
18:13<dis>just that it exists I suppose :)
18:15<Captain_Murdoch>how stable is current CVS?
18:15<nulltank>do you also have a gui front end? like gmame? does it (or something else) create a catver.ini file based on my roms?
18:15<Chutt>captain_murdoch, works fine for me
18:16<Chutt>'cept for pip mode
18:16<dis>nulltank: no gui front end here. My rom set and catver.ini is lagging at 0.65 but mythgame is the only frontend i use. Just start xmame.x11 from the command line otherwise
18:17<Captain_Murdoch>ok, thanks. been out of the country for over a week then hurricane Isabel decided to pay my area a visit which threw a wrench into things.
18:17<robertj_>does the gui have an option to not use full screen mode unless specified in the default cfg?
18:17<robertj_>full screen mode does not jive with my fixed refresh rate/resolution display
18:17<Chutt>robertj, you can set the ui to run at whatever resolution you want.
18:17<kvandivo>wow.. how close were you to the fun, capt?
18:17<nulltank>dis: yeah, it works if i start it from the command line; i wish there was some dubugging output
18:18<robertj_>Chutt: Its working fine except when it launches xmame it runs it in full screen and sets things out of whack
18:18<robertj_>when I run it from the command prompt everything is fine
18:18<Captain_Murdoch>I live in southeast Virginia, part of the 1.8 Million households in VA & NC without power after the storm.
18:19<robertj_>That will teach you to move away from the fault line! The elements will have their vengence!
18:19<robertj_>"Vulcan demands your presence in California!"
18:20* kvandivo is having fun with 6544.
18:20<dis>robertj_: You mean xmame starts out of whack? Like maybe xmame doesn't completely fill up the screen and you can still see mythfrontend underneath?
18:20-!-moegreen [] has quit ["bbl"]
18:20<Captain_Murdoch>:) well, their vengeance was mainly on my pool with a ton of leaves. it's clear again now though. neighbors didn't fair so well, I could see about 10 trees down just by looking out the front and back windows of the house.
18:21<robertj_>dis: like it runs fullscreen in some mode not specified in the cfg file
18:21<robertj_>which is not cool because my tv doesn't do alternate rezes
18:21<dis>i've been wondering if mythgame honors the .xmamerc settings at all when launching xmame
18:21<dis>cause some of my settings don't seem to be applied when starting from mythfrontend either
18:22<robertj_>I don't think it does
18:22<robertj_>I duno
18:22<dis>is anybody maintaining mythgame at the moment?
18:22<robertj_>the easiest way to check would be to replace xmame with a sh containing echo $*
18:24-!-jb4 [] has quit ["Leaving"]
18:24<dis>Chutt: Anything you'd like me to try regarding the deadlock before I turn in?
18:24<Chutt>no, i need you in gdb with it locked.
18:25<dis>ok, it should be ready for that when i get home tomorrow night
18:32<robertj_>hey Chutt, any chance of a web page update tommorow maybe?
18:33<Chutt>i dunno
18:33<robertj_>dunno either :)
18:37<Chutt>i dunno
18:37<Chutt>if i feel motivated, maybe
18:37<Chutt>moegreen, thanks for fixing the imdb stuff =)
18:41<Captain_Murdoch>Chutt: did you have any targets in mind for the 0.12 release?
18:42<Chutt>i dunno
18:42<Captain_Murdoch>just curious since I've been out of the loop for a while. so no date on the horizon right now then I guess.
18:42<overridex>is there anyway to offset the time mythtv records with? i.e. if you record a show that starts at 7pm have it start at 6:59.. i have my box setup with ntpd, but my cable company seems to start shows a minute early usually
18:43<Chutt>captain_murdoch, relatively soon
18:43<Chutt>overridex, there's a global pre-record and post-record times
18:43<overridex>Chutt: hmmm where are they located?
18:44<warlord>overridex: somewhere in the General Setup, IIRC.
18:44<Chutt>in the general tv settings, i believe
18:44<Chutt>warlord, update your cvs checkout
18:44<Chutt>pip's fixed
18:44<warlord>Chutt: ok.. pulling down..
18:44<overridex>Chutt, warlord: ah, found it thanks :)
18:44<Chutt>at least here it is
18:44<warlord>Ok... I'll let you know...
18:45<Captain_Murdoch>Chutt, not sure if this was discussed or not, but should UpgradeTVDatabaseSchema() only be called by the master?
18:45<Chutt>captain_murdoch, shouldn't matter
18:45<Chutt>i've got it so the first thing running it will do the upgrade
18:45<overridex>ok with high quality recording, it takes about 20-30% of each of my cpus (2 athlon 1700+) on high quality to record... that about normal? would it pay off to get a pvr350 card if i put together a dedicated mythtv box that has a single 1ghz cpu?
18:46<Captain_Murdoch>ok, just thinking in dev mode. so can't accidentilly run a slave backend with current cvs connecting to a master with an older version. :)
18:47<warlord>overridex: I've got 3 pvr-250s in an Athlon-2600+ CPU and I never see the CPU usage go above 50%
18:47<overridex>by the way - setting that prerecord to 1 minute won't cause any conflicts with shows being recorded one after another, like 5 and 5:30 will it?
18:48<Chutt>overridex, nope
18:48<overridex>warlord: does it use the pvr hardware accel. for both encoding and decoding?
18:48<overridex>Chutt: cool, thanks :)
18:48<warlord>overridex: just encoding.
18:48<Chutt>decoding soon
18:49<warlord>Does the 250 support decode?
18:49<overridex>Chutt: sweet.. maybe i'll pick one of those up soon....
18:49<kvandivo>never ceases to amaze me that isaac's mail saying that he has fixed something in cvs always, without exception, arrives a good 5 minutes before the cvs commit log actually arrives
18:49<overridex>i have a wintv2go that i got off ebay for 7 bux :) hehe
18:49<Chutt>cvs commits only get sent every 5 minutes
18:49* kvandivo slaps himself on the forehead.
18:49<kvandivo>no wonder!
18:50<warlord>Chutt: rebuilt -- I'll test it shortly.
18:51<robertj_>sigh, if only there was a way to record off of component inputs
18:51<overridex>the pvr cards put the audio over the pci bus right? no need for a cable going from the card to the line in on the sound card?
18:51<robertj_>Suddenly everything is in HD on my cable service
18:51<warlord>robertj_: you can record off component inputs... it works fine.
18:51<robertj_>warlord: with what?
18:51<warlord>overridex: yea.
18:51<warlord>robertj_: well, it works with my pvr-250
18:51<robertj_>warlord: it has component ins?
18:51<Chutt>not component.
18:52<overridex>warlord: sweet.... the other day i was getting no audio and after trying a lot of settings i noticed my cat and chewed through the wire ;)
18:52<warlord>Er, sorry, it was composite in.
18:52<warlord>my bad
18:52<warlord>overridex: heh. yea..
18:54<dis>Chutt: deadlock finally triggered
18:55<overridex>heh, one more dumb question about the pvr cards.... does the ir receiver work with lirc?
18:55<Chutt>dis, backend backtrace?
18:55<Chutt>you've got, oh, 4 minutes until i'm out of here :p
18:55<dis>1 sec
18:55<robertj_>Today was a milestone though here, the first HD nekkidness on basic cable ;)
18:56<dis>Chutt: want to put it off til tomorrow? I'll just leave it in the debugger
18:56<dis>ok, i don't think four minutes (prolly three now) would quite do it :)
18:56<Chutt>if you can put the backtrace up quickly, i can tell you want to do pretty fast
18:59<Chutt>damn, sorry, there's not enough info in there
18:59<Chutt>but, i'll be back later tonight
18:59<dis>Chutt: would getting a different backtrace help any you think?
18:59<Chutt>get the frontend as well
19:00<dis>Chutt: I'm pretty sure whatever is causing this was submitted to the cvs between the 5th and 10th btw
19:00<Chutt>and i'll take a look later
19:00<Chutt>if you can get a more accurate date, that'd help
19:07<warlord>Chutt: Pip doesn't crash.. However the functionality is still a bit broken. Try this:
19:08<robertj_>Who is Pip ;)
19:08<warlord>enter livetv; type v; type n...
19:08<warlord>this works fine..
19:08<warlord>now type 'b'. that works fine...
19:08<robertj_>ohhhh picture in picture ;)
19:08<warlord>however now 'n' fails to work...
19:11<warlord>shall I send email about it?
19:11<Captain_Murdoch>kvandivo: in RecommendInfo::FromStringList(), you should use [offset + NUMPROGRAMLINES] instead of [offset + 23]. I'll look at it more and try to take a look at it in action tomorrow when I have more time.
19:13<kvandivo>NUMPROGRAMLINES is something like 28 or 29... I had looked at the FromStringList in ProgramInfo and the highest number there was 22. But, I'm game for putting NUMPROGRAMLINES. :)
19:13<Captain_Murdoch>current cvs is 23 for numprogramlines. it's the number of fields in the programinfo stringlist.
19:15<kvandivo>In that case, it seems like that would be totally safe, then..
19:15<Captain_Murdoch>you don't want to have to change that 23 whenever something is added to programinfo
19:16<kvandivo>i despise magic numbers as much as the next person. for some reason I was thinking that NUMPROGRAMLINES was more than that, though...
19:16* kvandivo scratches his head and wonders what he was smoking.
19:16<Captain_Murdoch>looks good so far. I've synced cvs and am recompiling myth and modules so I can get running current cvs on all my systems, then I can take a look at the patch better tomorrow.
19:17<Captain_Murdoch>gotta hit the hay for now.
19:17<kvandivo>sounds like a good idea. I've changed the 23 to NUMPROGLINES in my copy and and recompiling now
19:36-!-ahbritto [] has quit [Client Quit]
19:36-!-accurate [] has joined #mythtv
19:38-!-robertj_ [] has quit ["Client exiting"]
19:41-!-moegreen [] has joined #mythtv
19:57-!-kja [] has quit ["..."]
20:14-!-kvandivo [] has quit ["leaving"]
20:36-!-hfb [] has joined #mythtv
21:03-!-accurate [] has quit [Remote closed the connection]
21:06-!-Sir-Al [~EXiT@] has joined #mythtv
21:09-!-robbie [] has quit []
21:13-!-kwenda|afk is now known as kwenda
21:13<kwenda>Warning: setlocale(): Passing locale category name as string is deprecated. Use the LC_* -constants instead. in /data1/www/virtual/ on line 933
21:14<kwenda>someone broke the webbbbsite ;)
21:29<Chutt>php upgrade.
21:30<kwenda>ahhh so its a 'feature'
21:33<Chutt>should be better once the web cache updates
21:33<Chutt>5 minutes or so
21:37-!-Soopaman [] has joined #mythtv
21:39<nulltank>anyone using mythnews? is it worth me going to the cvs tree to get it?
21:58<o_cee>Chutt: i don't know if this channel is the only one who does its listnings this way (somtimes), but it breaks pretty bad in mythfilldatabase. what they do is that there's first an overlapping block, let's say from 9pm-12pm. inside that block there's like four different "sub" programs. this is beeing marked by mythfilldatabase as a conflict and all kind of strange things happen. one way to solve it would be to check if the conflict is commin
21:58<o_cee>g from the same xmltv file, in that case it shouldn't be a conflict but rather something like this. what do you think? how should this be resolved the best way?
21:58-!-Soopaman [] has quit [Read error: 104 (Connection reset by peer)]
22:03<nulltank>overridex: i'm currently setting up my hauppauge remote with lirc and it is working; go here for directions:
22:05<nulltank>overridex: actually, it's this section:
22:13-!-hfb [] has quit ["Client exiting"]
22:26-!-billytwowilly [] has joined #mythtv
22:28<billytwowilly>on a mandrake 9.1 install, where is the file that holds the mythtv mysql database password and username?
22:34<o_cee>locate mysql.txt
22:36<billytwowilly>search of the mailing list archive turned it up after some work;)
22:38<o_cee>better search before asking..
22:38-!-_kch_ [] has joined #mythtv
22:48-!-billytwowilly [] has left #mythtv ["Client exiting"]
22:58-!-tdb30_ [] has quit [Read error: 110 (Connection timed out)]
23:13-!-Sir-Al [~EXiT@] has quit [Remote closed the connection]
23:26-!-FryGuy [~fryguy@] has quit [Read error: 104 (Connection reset by peer)]
23:40-!-Soopaman [] has joined #mythtv
23:55-!-Soopaman [] has quit [Read error: 104 (Connection reset by peer)]
---Logclosed Mon Sep 22 00:00:45 2003