Back to Home / #mythtv / 2008 / 05 / Prev Day | Next Day
#mythtv IRC Logs for 2008-05-05

---Logopened Mon May 05 00:00:26 2008
00:05-!-xris [] has quit []
00:27-!-nsaspook [] has joined #mythtv
00:28-!-nsaspook [] has quit [Client Quit]
00:28-!-nsaspook [] has joined #mythtv
00:37-!-joobie [] has quit [Remote closed the connection]
00:38-!-joobie [] has joined #mythtv
00:39-!-kash [i=nibblet@] has joined #mythtv
01:03-!-gnome42 [] has quit [Remote closed the connection]
01:10-!-nsaspook [] has quit [Remote closed the connection]
01:11-!-TelnetManta_ [] has joined #mythtv
01:20-!-pyro [] has joined #mythtv
01:22<pyro>Can anyone help me with a prob? I have a pvr-x50 and it looks fine other than it show the same image twice, one on top of the other vertically, like having two tv's on top of each other, and the video is stretched obviously....
01:23-!-TelnetManta [] has quit [Read error: 110 (Connection timed out)]
01:49-!-joobie [] has quit ["This computer has gone to sleep"]
01:49-!-mzb [] has quit [Read error: 113 (No route to host)]
02:24-!-joobie [] has joined #mythtv
02:26-!-superm1 [n=superm1@ubuntu/member/superm1] has joined #mythtv
02:41-!-joobie [] has quit ["Leaving"]
02:44-!-joobie [] has joined #mythtv
02:48-!-pyro [] has quit [Read error: 113 (No route to host)]
02:51-!-xris [] has joined #mythtv
03:06-!-dekar1 [] has joined #mythtv
03:14-!-dekarl [] has quit [Read error: 145 (Connection timed out)]
03:18-!-xris [] has quit []
03:24-!-gbee [] has quit [Read error: 110 (Connection timed out)]
04:00-!-otwin [n=otwin@] has quit [Remote closed the connection]
04:00-!-otwin [n=otwin@] has joined #mythtv
04:34-!-grokky [] has quit [Read error: 110 (Connection timed out)]
04:41-!-gbee [] has joined #mythtv
04:50<gbee>err, weird problem: 2008-05-05 09:50:10.332 NVP: Couldn't find a matching decoder for: /mnt/myth2/1076_20080505094900.mpg
04:51<gbee>that's a channel which has never had any problems, it's managed to create a preview image just fine
04:52<gbee>problem was persistant until I restarted the frontend - cached result?
05:02-!-gardz [] has joined #mythtv
05:12<Dibblah>gbee: I've been seeing that too.
05:12<Dibblah>NVidia card?
05:13<Dibblah>... Standard decoder or libmpeg2?
05:17<gbee>nvidia (though I'm not sure how that matters :) ) ffmpeg decoder
05:22<gbee>I've got to go out, but it's an interesting problem which I'd like to figure out and hopefully fix
05:45<Dibblah>For me it seems to be caused by a corrupted recording and is reproducable. But I don't have any examples at the moment :(
05:55-!-grokky [] has joined #mythtv
05:56-!-famicom [] has quit [Read error: 104 (Connection reset by peer)]
05:57-!-famicom [] has joined #mythtv
06:10-!-Jonny0stars [] has joined #mythtv
06:10-!-Jonny0stars [] has left #mythtv ["Leaving"]
06:18-!-dagar [] has quit [Read error: 110 (Connection timed out)]
06:20-!-dagar [] has joined #mythtv
06:22-!-gardz [] has quit []
06:50<MrGandalf>gbee: I've done some research into that.. what hanneps is if one of the av_* (which remember if it's av_find_stream_info() or another) is called on a garbage file, the frontend will have trouble opening valid files from that point on until restarted.
06:52<MrGandalf>the first of the two av_* calls simply sees the .mpg extension and returns, the other probes the file until it gets something recognozable - it's the second one that's at fault here.
06:52<MrGandalf>I think the first is in NuppleVideoPlayer() and the other in avformatdecoder
06:52<MrGandalf>(this is all from memory)
06:56<MrGandalf>I got the impression the probe thread never exited (at least not until the end of the file). I'm thinking it should somehow be given a subset of the file instead of the whole file.
06:57<MrGandalf>anyway, off to work..
06:57-!-MrGandalf [] has quit ["work"]
07:10-!-TelnetManta_ [] has quit ["Ex-Chat"]
07:18-!-luser [] has joined #mythtv
07:19-!-luser [] has left #mythtv ["Ex-Chat"]
07:34-!-gardz [] has joined #mythtv
07:47-!-melunko [n=hmelo@] has joined #mythtv
08:26-!-TelnetManta [n=benwilli@] has joined #mythtv
09:05-!-moodboom [] has joined #mythtv
09:07-!-grokky [] has quit []
09:24-!-gardz [] has quit []
09:24-!-gardz [] has joined #mythtv
09:28-!-danielk22 [] has left #mythtv []
09:28-!-danielk22 [] has joined #mythtv
09:28-!-gbee [] has quit [Remote closed the connection]
09:31-!-gnome42 [] has joined #mythtv
09:33-!-lsobral [n=sobral@] has joined #mythtv
09:34-!-skamithi [] has joined #mythtv
09:38-!-Cardoe [n=Cardoe@gentoo/developer/Cardoe] has joined #mythtv
09:41-!-gbee [] has joined #mythtv
09:47-!-joobie [] has quit ["This computer has gone to sleep"]
09:54-!-otwin_ [n=otwin@] has joined #mythtv
09:56-!-Netsplit <-> quits: Honk, otwin
10:01-!-otwin_ is now known as otwin
10:13-!-rwalker [n=chatzill@] has joined #mythtv
10:15-!-Honk [] has joined #mythtv
10:29-!-iamlindoro_ [] has left #mythtv []
10:44-!-jmk_ [n=jmk@] has joined #mythtv
10:45<gbee>anyone know what H.222 is? Never heard of it, but it's apparently what at least one HD channel has started to broadcast
10:48<sphery>According to it's a withdrawn standard for "Frame structure for 384-1920 kbit/s channels in audiovisual teleservices" that's been merged with ITU-T H.221 (in 1990)
10:51<Dibblah>ITV HD?
10:52<Dibblah>Someone is saying that it's just h.264 in a TS...
10:53<gbee>Dibblah: yeah
10:53<Dibblah>Mislabeled. Apparently VLC plays it.
10:53<gbee>I suspect it may just be temporary and that they'll switch to native h.264 at some point - but for now they want to obscure it for some reason
10:54<gbee>Dibblah: any idea if ffplay can handle it?
10:54<Dibblah>No idea.
10:55<Dibblah>I haven't rescanned since freesat started.
10:56<gbee>ok, guess I'll find out when I finally get that dvb-s card ;)
10:56-!-MrGandalf [] has joined #mythtv
11:06-!-moodboom [] has quit [Remote closed the connection]
11:07-!-iamlindoro_ [n=robert@] has joined #mythtv
11:23-!-moodboom [] has joined #mythtv
11:25-!-psicobra [] has joined #mythtv
11:25<psicobra>hi guys i have myth tv installed and have set the parental setting on the video's i dont want my kid to see but now i can't see them either
11:26<psicobra>just lists his video's
11:30<rwalker>psicobra: You need to ask this in mythtv-users
11:32-!-Therock_ [] has quit [Client Quit]
11:32-!-Therock_ [] has joined #mythtv
11:35-!-famicom_ [] has joined #mythtv
11:37-!-psicobra [] has quit ["Leaving"]
11:49-!-stoth [] has joined #mythtv
11:51-!-mattwire [] has joined #mythtv
11:52-!-famicom [] has quit [Read error: 110 (Connection timed out)]
11:56-!-xris [] has joined #mythtv
11:58-!-famicom_ [] has quit [Read error: 110 (Connection timed out)]
12:04-!-famicom [] has joined #mythtv
12:08-!-famicom_ [] has joined #mythtv
12:20-!-briand [] has quit [Connection timed out]
12:21-!-briand [] has joined #mythtv
12:22-!-famicom [] has quit [Connection timed out]
12:31-!-reynaldo [n=rverdejo@] has joined #mythtv
12:31-!-Netsplit <-> quits: splat1
12:32-!-famicom_ [] has quit ["Leaving"]
12:32-!-Netsplit over, joins: splat1
12:32-!-famicom [] has joined #mythtv
12:38-!-CrazyFoam [i=gturner@gateway/tor/x-02abcfed3e31b0b4] has quit [Remote closed the connection]
12:39-!-CrazyFoam [i=gturner@gateway/tor/x-adc0d2bad4bf2b26] has joined #mythtv
12:41-!-briand [] has quit [Connection timed out]
12:47<janneg>sphery: I think it's more probable that the autoexpire bug was caused by the new master backend without recorder
12:48<sphery>That could be. Though I think the situation I described can also occur, right?
12:50<janneg>not sure, there shouldn't have been autoexipreable recordings on the root partition if it has only 12G from 50G free
12:51<janneg>and i think the user uses only one big RAID
12:53<sphery>Oh, in that case, I agree, that's probably not what happened here. I didn't read the details too deeply (my brain hurt when I tried).
12:54<janneg>I'm not sure if I understood it correctly hence the request for the complete storage configuration
12:59-!-beandog [n=steve@gentoo/developer/beandog] has joined #mythtv
13:01<janneg>Chutt: ?
13:07<Chutt>i'm home =)
13:16-!-reynaldo_ [n=rverdejo@] has joined #mythtv
13:17-!-reynaldo [n=rverdejo@] has quit [Read error: 104 (Connection reset by peer)]
13:18-!-MrGandalf [] has quit ["brb"]
13:18-!-MrGandalf [] has joined #mythtv
13:26-!-skamithi [] has quit ["WeeChat 0.2.6"]
13:28-!-\S2 [] has joined #mythtv
13:28<sphery>I wonder why I'm still getting "QSqlDatabasePrivate::removeDatabase: connection 'DBManager0' is still in use" messages at shutdown after [17131] (mythtv-setup from trunk/r17239)
13:33-!-\S2 [] has quit [Remote closed the connection]
14:00-!-danielk22 [] has quit ["Leaving."]
14:23-!-stoth [] has quit [Remote closed the connection]
14:28-!-renato [n=renato@] has joined #mythtv
14:32-!-jgarvey [] has joined #mythtv
14:43-!-kormoc [n=kormoc@unaffiliated/kormoc] has quit []
14:57-!-briand [] has joined #mythtv
15:14-!-Packetscan is now known as packetscan
15:15-!-reynaldo_ [n=rverdejo@] has quit [Read error: 110 (Connection timed out)]
15:49-!-kormoc [n=kormoc@unaffiliated/kormoc] has joined #mythtv
15:55-!-reynaldo [n=rverdejo@] has joined #mythtv
15:56<Chutt>all the QTimer changes Daniel did - would an easier fix been to have used QThread intead of a pthread?
16:21<gbee>more qt4 placeholder problems -
16:21<gbee>I'll open a ticket, I know janneg is busy
16:22<sphery>Yeah, I saw those. Looks like programmatically created placeholder names.
16:23<gbee>my backend log is full of them, several hundred Mb worth :)
16:23<sphery>./programs/mythbackend/scheduler.cpp +2229
16:24<sphery>I was afraid to touch the BUSQ, so I haven't considered making a patch. :)
16:26<gbee>I'm not even going to take a look
16:26-!-MrGandalf [] has quit ["home"]
16:34-!-kormoc [n=kormoc@unaffiliated/kormoc] has quit []
16:36-!-TelnetManta [n=benwilli@] has quit ["Ex-Chat"]
17:00-!-skamithi [] has joined #mythtv
17:02-!-kormoc [n=kormoc@unaffiliated/kormoc] has joined #mythtv
17:13-!-reynaldo [n=rverdejo@] has quit ["Lost terminal"]
17:20-!-turbo [] has joined #mythtv
17:22-!-briand [] has quit [Read error: 110 (Connection timed out)]
17:25-!-turbo is now known as briand
17:25-!-Cardoe [n=Cardoe@gentoo/developer/Cardoe] has quit ["Leaving"]
17:27-!-janneg [] has quit ["dist-upgrade"]
17:30-!-reynaldo [n=rverdejo@] has joined #mythtv
17:35-!-kormoc_ [n=kormoc@unaffiliated/kormoc] has joined #mythtv
17:43-!-kormoc [n=kormoc@unaffiliated/kormoc] has quit [Nick collision from services.]
17:43-!-kormoc_ is now known as kormoc
17:44-!-turbo [] has joined #mythtv
17:45-!-briand [] has quit [Connection timed out]
17:56-!-jmk_ [n=jmk@] has quit ["Leaving"]
17:58-!-reynaldo [n=rverdejo@] has quit [Read error: 104 (Connection reset by peer)]
18:16-!-melunko [n=hmelo@] has quit [Read error: 113 (No route to host)]
18:16-!-turbo [] has quit [Connection timed out]
18:17-!-turbo [] has joined #mythtv
18:19-!-rwalker [n=chatzill@] has quit ["ChatZilla 0.9.81 [Firefox]"]
18:21<clever>2008-05-05 19:21:19.699 message is COMMFLAG_UPDATE 1028 2008-05-05T17:58:00
18:21<clever>ASSERT failure in QList<T>::operator[]: "index out of range", file /usr/include/qt4/QtCore/qlist.h, line 394
18:23-!-jgarvey [] has quit ["Leaving"]
18:25-!-skamithi [] has quit ["WeeChat 0.2.6"]
18:26-!-mattwire [] has quit ["Leaving"]
18:29<clever>patch made
18:30<clever>testing thru LD_PRELOAD
18:34-!-janneg [n=janne@] has joined #mythtv
18:35-!-turbo [] has quit [Read error: 110 (Connection timed out)]
18:41-!-turbo [] has joined #mythtv
18:54-!-joobie [n=joobie@] has joined #mythtv
18:58-!-PointyPumper [i=Pintlezz@] has quit [Read error: 110 (Connection timed out)]
19:01-!-iamlindoro__ [] has joined #mythtv
19:16-!-danielk22 [] has joined #mythtv
19:19-!-iamlindoro__ [] has quit [Connection timed out]
19:21-!-czth_ [n=dbrobins@nat/microsoft/x-5b5d3a328a90eca4] has joined #mythtv
19:21-!-joobie [n=joobie@] has quit ["Leaving"]
19:36-!-briand [] has joined #mythtv
19:37-!-czth__ [n=dbrobins@nat/microsoft/x-c6d66ed8a636e933] has quit [Read error: 110 (Connection timed out)]
19:37-!-turbo [] has quit [Connection timed out]
20:12-!-Dibblah [] has left #mythtv ["Kopete 0.12.4 :"]
20:17-!-joobie [n=joobie@] has joined #mythtv
20:35-!-briand [] has quit [Connection timed out]
20:36-!-briand [] has joined #mythtv
20:44-!-iamlindoro__ [] has joined #mythtv
20:44-!-tuxd00d [n=tuxd00d@] has quit ["This computer has gone to sleep"]
20:50-!-iamlindoro__ [] has quit []
20:51-!-jhulst [n=jhulst@unaffiliated/jhulst] has joined #mythtv
20:58-!-cheatersrealm [i=[] has joined #mythtv
20:58-!-cheatersrealm [i=[] has left #mythtv []
21:00-!-TelnetManta [] has joined #mythtv
21:00-!-PointyPumper [i=Pintlezz@] has joined #mythtv
21:13-!-kormoc [n=kormoc@unaffiliated/kormoc] has quit [Read error: 113 (No route to host)]
21:20-!-jhulst [n=jhulst@unaffiliated/jhulst] has quit ["Konversation terminated!"]
21:22-!-stoth [] has joined #mythtv
21:25-!-Winkie [] has quit [Read error: 104 (Connection reset by peer)]
21:30-!-turbo [] has joined #mythtv
21:31-!-briand [] has quit [Read error: 110 (Connection timed out)]
21:39<sphery>Location of (now at mythtv/bindings/python/MythTV/ ) has changed since the "update also" comment at mythtv/libs/libmyth/mythcontext.h +125 was added.
21:42<Anduin>sphery: I'll fix it
21:42<Anduin>(unless someone has a pending mythcontext.h checkin)
21:50-!-beandog [n=steve@gentoo/developer/beandog] has quit ["Leaving"]
21:51<sphery>I'm about to submit a patch that changes the proto version. I don't expect it to be reviewed very quickly, though.
21:55<sphery>Always fun causing a recompile of everything for a comment. :) Thanks for updating it, though.
22:06-!-joobie_ [n=joobie@] has joined #mythtv
22:08-!-joobie [n=joobie@] has quit [Read error: 104 (Connection reset by peer)]
22:08-!-Egghead2 [n=jimbobwa@] has joined #mythtv
22:09-!-tuxd00d [n=tuxd00d@] has joined #mythtv
22:09-!-Egghead2 [n=jimbobwa@] has left #mythtv []
22:10-!-kormoc [n=kormoc@unaffiliated/kormoc] has joined #mythtv
22:14-!-jhulst [n=jhulst@unaffiliated/jhulst] has joined #mythtv
22:20-!-reynaldo [] has joined #mythtv
22:23-!-jhulst [n=jhulst@unaffiliated/jhulst] has quit [Remote closed the connection]
22:23-!-jhulst [n=jhulst@unaffiliated/jhulst] has joined #mythtv
22:24-!-leprechau [i=charlie@] has joined #mythtv
22:24-!-turbo [] has quit [Success]
22:25-!-turbo [] has joined #mythtv
22:33-!-jhulst [n=jhulst@unaffiliated/jhulst] has quit [Remote closed the connection]
22:34-!-jhulst [n=jhulst@unaffiliated/jhulst] has joined #mythtv
22:44-!-jhulst [n=jhulst@unaffiliated/jhulst] has quit [Remote closed the connection]
22:44-!-jhulst [n=jhulst@unaffiliated/jhulst] has joined #mythtv
22:45-!-HRearden [] has joined #mythtv
22:52<HRearden>with respect to qt and time zone stuff. If you don't need the time zone def itself, you can compute current time and then also UTC time and subtract hours all via QT.
22:53<HRearden>would give you the "-4:00" part but not EDT
22:54-!-jhulst [n=jhulst@unaffiliated/jhulst] has quit [Remote closed the connection]
22:54-!-jhulst [n=jhulst@unaffiliated/jhulst] has joined #mythtv
22:55<sphery>Yeah, I noticed that Qt4's QDateTime supports getting time with UTC, but couldn't decide which approach would be better. I suppose if nothing else, I should have done the Qt-based approach for the Windows port.
22:56<HRearden>Just looking out for our Windows friends.... Not that I'll ever use it...
22:58<sphery>I'm also not exactly sure if just knowing -0500 is enough since one system could be at EST and another at CDT (which--if my timezone math is correct--would both be -0500). Then, when computing the starttime of recordings, MythWeb would do the DST conversions incorrectly.
22:58<sphery>The problem is that strftime()'s "names" aren't really standardized and are definitely not what PHP uses. :(
23:01<HRearden>I don't think that's right. If I'm in timezone Eastern and I set it to use daylight savings time then sometimes I'm EST -0500 and sometimes I'm EDT -0400. CST/CDT would similarly switch, right?
23:03-!-famicom [] has quit [Read error: 110 (Connection timed out)]
23:04-!-jhulst [n=jhulst@unaffiliated/jhulst] has quit [Remote closed the connection]
23:05-!-jhulst [n=jhulst@unaffiliated/jhulst] has joined #mythtv
23:11-!-jhulst [n=jhulst@unaffiliated/jhulst] has quit [Remote closed the connection]
23:12<sphery>I have to admit that I really don't know if a system could be misconfigured (which is what I hope to detect) to allow that. There are still some areas of the country that don't observe DST, so I thought a system could be set so it doesn't switch.
23:14<HRearden>I think you'd be OK in any case. I just went through the mythfilldatabase code, at least, and the data comes from schedules direct in UTC, then the QT functions are used to go from a UTC date back to local time. (Well, actually, those functions could use a rewrite under QT4 since the new QTDateTime has it directly now, but it does effectively the same thing). So if your reporter function just reported the delta, and all the deltas
23:14-!-alice__ [] has joined #mythtv
23:15<HRearden>A system can be set so it doesn't switch, but if you were in Central and non-switching (like Indiana at least used to be), you'd always be -0400 and never change to -0300. Delta's from UTC to local would still work.
23:16<HRearden>And also across windows, where some time string name would be totally meaningless.
23:20<sphery>I'll go ahead an implement the QDateTime-based difference calculation, but I'll add it ass a "backup" approach. The reviewer could then just delete the localtime_r() approach, if desired, and--even if committed with both--at least Windows gets something.
23:21-!-gbee [] has quit [Read error: 110 (Connection timed out)]
23:22<HRearden>Only suggesting since you asked. For more info on timezone strings and how they work, there is some info here:
23:23<HRearden>I never use those actual strings on my "normal" boxes, but my hauppauge mvpmc boxes need them since they don't use distro-specific timezone files.
23:23<sphery>Yeah, I appreciate the feedback. I guess the problem stems from my lack of understanding of exactly what the problem is in MythWeb and, therefore, how to fix it. Perhaps xris or kormoc would better know what they need to fix it in MythWeb.
23:28*kormoc reads up
23:28<HRearden>Ahh. Just read 4683. Delta's may make the most sense there, as well, since there's no guarantee that the distro and timezone names would be consistent from the webserver running PHP to the mythbackend. MythWeb would just need to do the same delta calc.
23:30<sphery>kormoc: discussion is regarding , which is supposed to provide a means to allow you ;) to fix #4683
23:31<kormoc>And I assume someone considered using unix timestamps and thought that wasn't acceptable?
23:33<sphery>Well, that would require a /lot/ of changes to a lot of parts of Myth. It's probably a good long-term goal, but may be a very long-term project.
23:33*kormoc nods
23:34<sphery>testing would be the really hard part--then again, now would be a great time to introduce unstable changes (right along side the Qt4 change :)
23:35-!-brandon__ [n=brandon@] has joined #mythtv
23:35<kormoc>Yeah, unix timestamps would be the better way imho, but I understand if it's just too much. We'll be able to figure out a work around one of these days well enough
23:37<brandon__>Is there an environment setting to disable upnp for mythfrontend? There is a --noupnp for the backend but an option was never added for the frontend and a upnp device I can't shut off is segfaulting the frontend via upnp.
23:38<kormoc>brandon__, /topic
23:38<brandon__>kormoc: yup, read it. I wrote a few thousand lines for myth a couple years ago.
23:38<kormoc>heh, fair 'nuff
23:39<kormoc>it's an automatic reflex these days...
23:41<brandon__>no problem.. :) I asked on users just to be safe, thought I'd pop in here and see if I could save myself a couple hours, since I spent most of my night tracking it down. There used to be a configure option to disable upnp but that was removed too. I've made a few fixes to bugs but sadly upnp is too broken for my use.
23:41*Captain_Murdoch2 steps in long enough to say that it might be better to just add a QUERY_TIME to get the current backend date/time and let the client do the offset calc itself if necessary.
23:42<brandon__>Just to save sanity and watch a movie tonight to relax.
23:42<brandon__>that or I set an iptable rule to block it :)
23:43<sphery>kormoc: do you think you can make MythWeb work even if the MythWeb host has a differently-configured timezone from the backend with just a backend time or offset?
23:43<sphery>and, which would you prefer? :)
23:47<sphery>I think the symptom was that programs recorded during DST didn't show (MythWeb requested using recstartts 1hr too early) during standard time on a MythWeb host whose timezone wasn't properly set (wasn't specified in /etc/php.ini). gbee could tell you exactly what was set on the backend and the MythWeb host, but I was thinking it was British Summer Time and UTC, respectively.
23:48<sphery>a lot of users had the same issue (on the lists almost always described as "missing preview images" or "missing recordings" in MythWeb)
23:53<kormoc>if I had the orig timezone, I can do the conversions
23:53<sphery>does that mean just the original timezone's offset or do you need more?
23:54<kormoc>Well, the offset isn't enough, as with daylight savings, -5 becomes -6 or -4 or whatever it is
23:54<kormoc>I'd need the actual code for the timezone
23:55-!-danielk22 is now known as danielk_zzzz
23:55<kormoc>least, that's my understanding, as if it's just a date -5, is that form a computer that respects daylights savings or not, I don't believe one can tell
23:55<kormoc>but PST/PDT EST/EDT is explicit what it's being based off of
23:57<HRearden>I guess I was thinking more of retrieving the UTC offset from localtime from the backend, then doing a forward calculation from UTC in PHP in mythweb based on that same delta.
23:57<HRearden>That way timezone settings on the mythweb host become irrelevant.
23:57<sphery>kormoc: Except for EST/EST (Eastern Standard Time/Eastern Summer Time in Australia)
23:58<kormoc>well, whatever the short name for eastern daylight savings time
23:58<kormoc>HRearden, thing is, I seem to recall a number of broken setups where people hard code one offset, and then the offset to UTC is just wrong
23:59<kormoc>sphery, ooh, I see
23:59<kormoc>sphery, could do the 'full' names
23:59<kormoc>and it gets more complicated by the minute!
23:59<sphery>yeah, it works for almost all, but there are exceptions (and if someone has Eastern Standard Time (US) and Eastern Standard (or Summer) Time (Australia)), we couldn't tell the difference with what I'm giving you.
23:59<HRearden>If they've screwed up the hard coding on the mythbackend, they won't be able to schedule stuff correctly. What I'm saying is take that value as the one constant.
---Logclosed Tue May 06 00:00:03 2008