Back to Home / #mythtv / 2003 / 07 / Prev Day | Next Day
#mythtv IRC Logs for 2003-07-12

00:00<mdz_>term: impossible
00:00<term>well I didn't enter it encrypted!
00:00<mdz_>probably you are looking at a randomly generated password and thinking that it is encrypted
00:00<mdz_>by default it randomly generates a password
00:00<term>I thought it had asked me though
00:00<term>let's ask dpkg-reconfigure
00:00<term>after I ge the phoen
00:00<mdz_>I am right
00:00<mdz_>and I am going to bed now
00:02<term>Configuring Mythtv-common
00:02<term>If you give an empty password, a random one will be generated.
00:02<term>What password should MythTV use to access its database?
00:02<term>I'm gonna enter it again
00:03-!-tdb30_ [] has quit [Read error: 54 (Connection reset by peer)]
00:03<term>it works now
00:04<term>mdz_: I'm not doing well with this. Every time I think I'm having a problem, it either works the second time or I screwed up. Excuse my confusion, I guess. :(
00:04-!-FreddieD [] has quit [Read error: 110 (Connection timed out)]
00:05<bline>yay, it worky
00:05-!-claybo [] has joined #mythtv
00:07<bline>err almost
00:07<claybo>hey, anyone here set up a via epia-based mythtv box? i'm just curious how well they're running.
00:21<bline>Chutt: is this patch for mute timer on ff/rew/ch something you would commit to cvs?
00:23<bline>man it is great to be rid of that squeal
00:25<bline>ok, I'll submit it to the dev list
00:26<bline>the pause is 600ms, it's not noticeable
00:30<Chutt>over half a second?
00:30<-- claybo( has left #mythtv
00:32<bline>I tried 500, but still got the squeal ever so often
00:33<bline>I can't notice the pause, tell me if you can. Sending the email now
00:48-!-tristano [] has joined #mythtv
00:48<tristano>hey guys. anyone here know why my audio works fine in mythtv but not in tvtime? i'm going from audio out of my tv tuner card to audio in of my sound card
00:49<bline>becuase tvtime sucks? =)
00:49<bline>naa, just kidding. I have now idea
00:50<bline>vektor might could help, if he was around
00:50<tristano>well, i'd use mythtv to watch tv, but the video quality sucks because of the on the fly mpeg converting, and the title bar won't go away no matter what i do!? so i see "Myth TV" proudly at the top of my tv =/
00:51<term>need to figure out why mythweather keeps complaining it can't look stuff up
01:15-!-FreddieD [] has joined #mythtv
01:15-!-just1nux [] has quit [Read error: 54 (Connection reset by peer)]
01:20<Chutt>bline, i'm going to move the timer->stop to the beginning of the function
01:22<bline>It started there
01:23<Chutt>why not?
01:23-!-just1nux [] has joined #mythtv
01:23<bline>but if you ff/rew too fast, somehow the timer quits working
01:23<bline>moving the stop right before the start somehow fixed that
01:24<Chutt>i don't think it needs the stop if you're doing the start there, then
01:25<bline>if a timer is started when it hits the function, shouldn't it be stopped before you call start?
01:25<Chutt>i think calling start on an active timer resets it
01:25<bline>I'll test right now removing the stop if you want me to
01:27<Chutt>it does say 'any pending timer will be stopped'
01:27<Chutt>shouldn't these be single shot timers?
01:27<bline>yeah, testing now
01:27<Chutt>i think the current stuff
01:27<Chutt>if you mute it
01:27<bline>it started as a oneshot heh
01:28<Chutt>then change a channel
01:28<Chutt>it'll un mute it
01:28<bline>I should change it back to ->start(600, true)
01:28<Chutt>and you won't be able to mute it again
01:28<Chutt>i can change em when i apply it
01:29<bline>it was one of the things I changed trying to figure out why the timer would quit working if I ff too fast
01:29<bline>->start was getting called, but it would never make it to the UnMute function
01:31<Chutt>oh, wait
01:31<Chutt>you're stopping it in the callback
01:31<Chutt>no need to make em single shots, then
01:31<bline>well, I can remove the stop in the callback that way
01:33<bline>were you able to tell the audio was being paused?
01:33<Chutt>i haven't applied it yet
01:34<bline>ok, I changed it to a oneshot, removed all the ->stop's, and it is working fine
01:34<bline>I'll resubmit
01:34<Chutt>naw, don't bother
01:36<bline>I wish I knew why having those stops at the top of the function would break things
01:38<just1nux>hmm awful lot of logo and title drawing changes to cvs...hope that not *all* my fault.
01:38<Chutt>just1nux, naw, they're not
01:38<Chutt>the logos were getting redrawn too much
01:38<Chutt>and not erased first
01:38<just1nux>:) ok.
01:38<Chutt>so if there was an alpha channel, it'd get drawn over itself
01:38<Chutt>and it'd get progressively darker
01:39<just1nux>am i right in assuming the word "Cut" should only appear onthe edit screen while you are in a cut area?
01:39<Chutt>that was the first commit, then i just made it faster
01:39<just1nux>it seems to appear for me and never go away.
01:40<just1nux>tried my theme and the blue osd both
01:41* just1nuxwaits while chutt checks to see if its doing it on his myth...
01:41* blinedecides to go sleep
01:42<Chutt>not quite yet :p
01:42<Chutt>i'm doing something else right now
01:42* just1nuxis happy that bline has been fixing the screeching noise.
01:46-!-bline [] has quit ["Client exiting"]
01:55<just1nux>why would it take an image 642 across to cover the tv image entirely instead of 640?
01:57<just1nux>ok. strange. had a 2 pixel gap with a 640 image placed at 0 position. 642 works, so ill go with that.
01:58<Chutt>and, yeah, i can confirm that the 'cut' never goes away
01:58<Chutt>once it shows up
01:59<just1nux>ok, cool, so im not loosing my mind. :P
02:02<Chutt>have that fixed in a tiny bit
02:02<just1nux>ok, im not planning on updating my cvs for a couple more days anyway.
02:03<just1nux>just thought id mention it, incase it really was a problem.
02:03<Chutt>it is
02:03<just1nux>i dont use that feature much, but i noticed it while working on the theme
02:13<Chutt>it's fixed in cvs
02:13<Chutt>which also contains bline's mute timer patch
02:18<just1nux>ok, thanks.
02:49-!-Chutt [] has quit [Read error: 54 (Connection reset by peer)]
02:49-!-just1nux [] has quit [Read error: 54 (Connection reset by peer)]
02:56-!-just1nux [] has joined #mythtv
02:57-!-FreddieD [] has quit [Read error: 60 (Operation timed out)]
03:34-!-ahbritto [] has quit [Read error: 110 (Connection timed out)]
03:34-!-just1nux [] has quit [Read error: 54 (Connection reset by peer)]
03:35-!-just1nux [] has joined #mythtv
03:38-!-Ripp [] has quit [""Bring me the hydrospanners! I don't know how we're gonna get out of this one.""]
03:39-!-Ripp [~deadbeef@] has joined #mythtv
04:23-!-FreddieD [] has joined #mythtv
04:30-!-Justin_ [] has quit [Read error: 60 (Operation timed out)]
04:46-!-ahbritto [] has joined #mythtv
04:54-!-FreddieD [] has quit [Read error: 60 (Operation timed out)]
06:30-!-FreddieD [] has joined #mythtv
07:08-!-Drikus [] has joined #mythtv
07:11-!-FreddieD [] has quit [Read error: 110 (Connection timed out)]
08:25-!-bline [] has joined #mythtv
08:31-!-FreddieD [] has joined #mythtv
08:54-!-zaheer [] has joined #mythtv
08:56<zaheer>can one set one soundcard to record if the input of the v4l card is Television
08:56<zaheer>and a different soundcard to record if the input is composite
08:56<zaheer>on the same v4l card
08:56<zaheer>i see the database has audiodevice set per caoture card
08:57-!-Drikus [] has quit ["toedeledoki"]
08:58<zaheer>rather than per cardinput
09:01-!-rkulagow [] has joined #mythtv
09:13-!-FreddieD [] has quit [Read error: 110 (Connection timed out)]
10:06-!-creepy [~lightning@] has joined #mythtv
10:23-!-rkulagow [] has quit [Read error: 110 (Connection timed out)]
10:33-!-FreddieD [] has joined #mythtv
10:36-!-bline [] has quit ["Client exiting"]
10:48-!-extremis [] has quit ["changing servers"]
10:54-!-dub20|afk is now known as dub20
11:02-!-ca1vin [] has quit [Read error: 60 (Operation timed out)]
11:06-!-bline [] has joined #mythtv
11:06-!-FreddieD [] has quit [Read error: 110 (Connection timed out)]
11:20-!-Chutt [] has joined #mythtv
11:25-!-dopez [] has joined #mythtv
11:55<mdz_>Chutt: so how do you think the channel id thing should be fixed?
11:55<Chutt>well, best way would be to have it convert to the new ids
11:55<mdz_>Chutt: try to convert the database, or use my ugly workaround?
11:56<mdz_>are those IDs actually stable?
11:56<Chutt>if he changes em again, i'm forking xmltv
11:58<Chutt>well, basically, we query the channel table with the xmltv id
11:58<Chutt>we can try with the new one first, if that fails, try with the old id
11:58<Chutt>no nasty regexp to get the old id out of the channel information, so it's good that way
11:58<Chutt>then replace the data if the old id's found
11:59<mdz_>hmm, ok
12:01<Chutt>old id's just the channel number
12:04<mdz_>using two display-names instead of two separate tags is the worst idea ever
12:04<mdz_>it should give you <channel-number> and <channel-name> or something
12:09<bline>does QRegExp use libpcre?
12:13<mdz_>I doubt it
12:13<mdz_>Qt implements most of that stuff itself rather than using other libraries
12:14<bline>writting a perl compatible regex engine like that must have been a lot of work to reimplement
12:14<bline>I was just looking at the docs for it
12:15<mdz_>they may have just used an existing implementation
12:15<mdz_>but copied it into libqt
12:15<bline>it's even got perl's zero width negative lookbehind assursions
12:15<mdz_>I don't even know if perl and libpcre use the same implementation
12:15<mdz_>perl certainly doesn't use libpcre
12:16<bline>no, libpcre is seperate than perl, it is perl5 regexs
12:16<bline>5.00504 iirc
12:19<-- creepy(~lightning@ has left #mythtv ("gone..")
12:27<Chutt>mdz, but having two separate tags would break things!
12:27<Chutt>especially since you can't tell which is the tuner number and which is the display name
12:27<Chutt>just if it's numeric won't work in europe
12:36-!-FreddieD [] has joined #mythtv
13:03<mdz_>Chutt: I have a 'works for me' patch...mind looking it over?
13:11<Chutt>looks fine to me
13:11<Chutt>going to check it in?
13:16<Chutt>thanks for handling that
13:19<mdz_>purely selfish
13:19<mdz_>couldn't record a movie because the channel was gone
13:19<mdz_>well, the program info for it anyway
13:20<mdz_>I have the new debs ready with the previous filldata fix and some other things, but dijkstra's network is apparently broken
13:22-!-FreddieD [] has quit [Read error: 110 (Connection timed out)]
13:37-!-Justin___ [] has joined #mythtv
13:40-!-ca1vin [] has joined #mythtv
13:46<mdz_>ah, it's back now
13:47<mdz_>Chutt: so the 0.10-2 debs will be up in a minute or so if you want to tell whomever asked about it
13:48<mdz_>there, done
14:00<Chutt>excellent, thanks
14:01<Chutt>i doubt i can find that email on the -users list, but =)
14:22<bline>yay, just got a dvdr
14:36-!-FreddieD [] has joined #mythtv
14:40-!-sfr [] has joined #mythtv
15:06<Captain_Murdoch>Chutt: I think that guy on the -users list wants Myth to not record a 6th episode if you have MaxEpisodes set at 5 rather than recording the 6th and deleting the oldest. Seems doable and a good idea since the current way will never re-record those episodes it deletes since they're in oldrecorded. I might take a look into adding that functionality as a checkbox along with MaxEpisodes. (ie, check ON = record and delete oldest, OFF
15:06<Captain_Murdoch>ng when read maxEpisodes until one is deleted.
15:21<Captain_Murdoch>actually coding that would be pretty easy it looks like. just add a checkbox setting and in the scheduler's prunelist function check to see if the scheduled recording is over it's max and if so remove it from the list. would be a global setting for all recordings unless added to the record table though. I'll give it some thought. I like the idea of not wasting time recording shows every day if I'm already at my max on that sho
15:21<Captain_Murdoch>'s behind in watching her stuff.
15:25-!-FreddieD [] has quit [Read error: 110 (Connection timed out)]
15:26-!-dopez [] has quit []
15:26-!-mdz_ [] has quit []
15:26-!-GreyFoxx [] has quit []
15:26-!-thor [] has quit []
15:26-!-Scrye [] has quit []
15:26-!-Viddy [] has quit []
15:26-!-dub20 [] has quit []
15:26-!-dopez [] has joined #mythtv
15:26-!-dub20 [] has joined #mythtv
15:26-!-Viddy [] has joined #mythtv
15:26-!-thor [~thor@] has joined #mythtv
15:26-!-mdz_ [] has joined #mythtv
15:26-!-Scrye [] has joined #mythtv
15:26-!-GreyFoxx [] has joined #mythtv
16:40-!-FreddieD [] has joined #mythtv
16:55<mdz_>damn these unreproducible crashes
16:55<mdz_>that's two backend crashes today
16:55<mdz_>I ran it in the debugger for a week and had zero problems
16:55<mdz_>until it got to a few hundred zombie seems to get pretty unhappy then
16:57<dopez>mdz_, did the backend crash while watching a recording in progress and pause it for a few minutes?
16:58<dopez>(that's what i get, and not when runnning the backend in gdb)
17:03-!-FreddieD [] has quit [Read error: 60 (Operation timed out)]
17:04<sfr>heh, welcome in the club
17:07<sfr>anyone running the master backend on a SMP machine?
17:08<dopez>i have the backend on a p4 with hyperthreading and smp kernel, if that counts..
17:13<sfr>don't know, here 2x PIII 850MHz _seems_ to cause random corruption of remote commands 'QUERY_RECORDER' ..., memory is ok, i'm just putting cerring them at different places trying to find where it happens
17:16<dopez>i remember seeing a few strange commands on the backend console , first 2 characters were bogus most of the time (from what i remember it were '??'s)
17:17<sfr>bingo !! same here, but not alway
17:17<dopez>i havent had the crash anymore, i either run it in gdb or wait till the recording finished ;)
17:19<sfr>just happened again, so i'm putting more cerr's, but i don't know C++/Qt at all.
17:23<dopez>hehe, i might be able to remember a few lines of C64 BASIC, but thats as far as my programming experience goes ;)
17:25<sfr>at least i'm not the only one seeing this
17:27<dopez>yes, also 'nice' to hear i'm not the only one too..
17:27<sfr>well, shared pain is half the pain ;-)
17:31<sfr>anyone know what qt is telling me here: 'ASSERT: "i <= nodes" in /usr/share/qt3/include/qvaluelist.h'
17:33<sfr>Chutt, read me?
18:13-!-tdb30__ [] has joined #mythtv
18:13<tdb30__>anyone know of a jp1 channel?
18:18<mdz_>dopez: no, this was upon exiting a recording
18:28-!-sfr [] has quit ["Client exiting"]
18:30-!-Justin___ is now known as Justin_
18:41-!-FreddieD [] has joined #mythtv
19:00-!-bline [] has quit ["Client exiting"]
19:18-!-FreddieD [] has quit [Read error: 110 (Connection timed out)]
19:40-!-just1nux [] has quit ["later"]
19:49<zaheer>would a patch that made audiodevice part of cardinput rather than capturecard?
19:49<zaheer>sorry rephrase
19:49<zaheer>would a patch that made audiodevice part of cardinput rather than capturecard, be acceptable?
19:50<thor>You may want to ask oon the mailing list ... I don't think Chutt is around atm
19:52-!-bline [] has joined #mythtv
19:57<mdz_>Chutt: heh, I was just scratching my head about why that user was complaining about the mixer device not being there, and then noticed that you had just changed that today
19:58<mdz_>zaheer: why would you want audiodevice to be part of cardinput? normally there is one audio device per capture card
19:58<mdz_>zaheer: for example, I have two video sources, one of them uses tuner audio and one of them uses line input. I plug the line input into the capture card and it automatically switches to the appropriate input
20:19-!-bline [] has quit ["Client exiting"]
20:41-!-FreddieD [] has joined #mythtv
20:57-!-Viddy [] has quit [Remote closed the connection]
21:05-!-FreddieD [] has quit [Read error: 60 (Operation timed out)]
21:37-!-Viddy [] has joined #mythtv
21:38-!-tristano [] has quit ["KVIrc 3.0.0-beta1 "Eve's Avatar""]
22:20-!-tdb30_ [] has joined #mythtv
22:21<tdb30_>I'm back again with more whinning. When I do mythfill database I get Unknown xmltv channel identifier for every channel. Any idea why?
22:40<Chutt>most likely, you haven't read the webpage.
22:41-!-FreddieD [] has joined #mythtv
22:44-!-bline [] has joined #mythtv
22:47<tdb30_>humm don't see anything there that looks like it is useful.......
22:53-!-dopez [] has quit [".."]
23:22<tdb30_>humm... looks like its working
23:40-!-FreddieD [] has quit [Read error: 110 (Connection timed out)]