[00:11] <hot_wheelz> Hi guys
[00:12] <Seeker`> lhi
[00:12] <maikeru|> I'm running Mythbuntu 8.10 with a WinTV-HVR 950 (USB). I've followed the instructions at http://ubuntuforums.org/showthread.php?p=6230325, a variety of other sources (including the MythTV wiki), and my own variations and still in mythtv-setup it can't detect it.
[00:17] <hot_wheelz> what is the command u have to run to flash a device for example af9015 device with it firmware again this is what i am will be running http://www.mythtv.org/wiki/DigitalNow_Tiny_Twin_Dual_Tuner
[00:18] <hot_wheelz> can somone give me the full path of what i need to run thanks :-)
[00:25] <hot_wheelz> the device works OTB in 9.04 and 9.10 i just want to keep it's f\w up to date corret me if i am wrong is the udo apt-get install bcm43xx-fwcutter
[00:25] <hot_wheelz> sorry udo apt-get install bcm43xx-fwcutter
[00:25] <hot_wheelz> a9015
[00:26] <hot_wheelz> all one line
[00:26] <hot_wheelz> not bcm43xx of course
[00:32] <tgm4883> err, isn't bcm43xx-fwcutter just for broadcom devices?
[00:32] <hot_wheelz> yeah that was a mistake tgm4883
[00:33] <tgm4883> hhe
[00:33] <tgm4883> guess I should read everything
[00:36] <hot_wheelz> tgm4883 based on this url http://www.mythtv.org/wiki/DigitalNow_Tiny_Twin_Dual_Tuner should the correct commmand be Sudo apt-get install af9015-fwcutter
[00:37] <hot_wheelz> or dvb_usb_af9015
[00:40] <hot_wheelz> tgm4883 what do u think?
[00:41] <tgm4883> hot_wheelz, sec, dealing with some other issues of my own at the moment
[00:42] <hot_wheelz> ok
[00:43] <tgm4883> hot_wheelz, i don't think so
[00:43] <tgm4883> don't you just need to put the firmware in /lib/firmware
[00:44] <hot_wheelz> ah yes ok thanks
[01:01] <hot_wheelz> is  Myth 0.22 due with 9.10 does anyone know?
[01:01] <Seeker`> I believe it should be
[01:01] <Seeker`> 0.22 release is imminent
[01:02] <hot_wheelz> it's on the 9.10 beta disk right?
[01:02] <superm1> Yup
[01:03] <superm1> and there is a newer version in the archives -  just do apt updates after install
[01:03] <hot_wheelz> what v is that?
[01:04] <hot_wheelz> oh yeah u mean than what ships om disk
[01:08] <mrand> Yes, 0.22 is scheduled to release this week and 9.10 will have it.  We've been having trouble with our daily CD's, so don't try one from today or yesterday.  If you don't already have an install that you are just going to upgrade, then install with the beta disk, then do an update.  Daily CD should be fixed in the next few days.
[01:09] <hipitihop> darthanubis: you about ?
[01:15] <hipitihop> even after todays update I still cannot login in into normal mythbuntu or xfce session, have to use xterm and then run mythfrontend by hand
[01:16] <mrand> sorry hipitihop.  My mythweb login died, but that's completely different.   normal login works.
[01:18] <hipitihop> mrand: my normal login hasn't worked since yesterday morning update....I can login via ssh but normal I get the following .xsession-errors http://paste.ubuntu.com/290621/
[01:19] <hipitihop> leaves me back at xfce user select screen. I can pick the normal user, enter password, it seems to login, mythtv progress shows for a moment and drops right back to the same login screen
[01:20] <hipitihop> maybe just something broke specific to my box but would love the magic incantation to just reset
[01:20] <superm1> i thought you fixed that a few days ago?
[01:20] <superm1> renaming ~/.config and ~/.cache?
[01:21] <hipitihop> superm1: nope still trying.. only way I can run mythfrontend is to chose an xterm session
[01:21] <hipitihop> superm1:  ahh, that was a different problem... that was trying to get task bar to hide.
[01:21] <superm1> so how did this problem develop?
[01:22] <superm1> (it should be the same solution as your taskbar problem though too ... .cache and .config)
[01:22] <hipitihop> superm1: afaik, yesterday morning (my time) update && upgrade
[01:23] <hipitihop> superm1: btw,  ~/.config and ~/.cache did not fix my task bar problem ... I had to tweak one of the xfce files .. I thought I had posted my solution here before
[01:26] <hipitihop> superm1: I had to change <property name="autohide" value="1"/> in .config/xfce4/panel/panels.xml
[01:27] <hipitihop> I don't think it behaves exactly as the default install but gets the desired result which is mythtv in full screen
[01:29] <hipitihop> superm1: but if you think renaming ~/.config and ~/.cache will help this issue, I'm willing to give it a go
[01:31] <hipitihop> hmm, intersting, don't have either
[01:31] <hipitihop> my bad ignore that.
[01:37] <hipitihop> mrand: superm1: that seems to have sorted it... obviously have to rest the session setup, but all good, progress. thanks
[01:55] <mrand> hipitihop: good to hear
[01:56] <hot_wheelz> also another question
[01:58] <hot_wheelz> when it comes transcoding a file to another format ie an ipod\phone does it convert the origianal file or make a copy and transcode that
[02:13] <mrand> It is a pretty rare program that overwrites the original, if that is what you are asking.
[02:24] <stunt> hey superm1 are you around?
[02:25] <superm1> what's up?
[02:26] <stunt> testing your patch
[02:26] <stunt> oh this is kost
[02:26] <superm1> which patch?
[02:27] <stunt> the one for safe mode graphics
[02:27] <superm1> ah right
[02:27] <stunt> i had the nvidia 7050pv
[02:27] <superm1> yeah
[02:27] <superm1> unfortunately live disks broke over the weekend
[02:27] <superm1> so you won't have too much luck
[02:27] <stunt> nope still garbled graphics
[02:27] <hipitihop> so anyone here know enough of lirc to help me get my imon basic remote going. google turns up various posts which suggest I have to disable usbhid as the driver for the device
[02:29] <stunt> i know i just signed in, but i have to run. ill try to check back in soon
[02:42] <mrand> hipitihop, if you can stand to wait, they are trying to get approval to push a newer version of lirc into the 9.10 build, which I believe greatly improves imon support.
[02:48] <mrand> Might be many days before it happens, and there is a small chance it won't happen at all.
[02:52] <hipitihop> mrand: are we talking about 0.8.6 ?
[02:54] <tmkt> lirc is a pain
[02:54] <tmkt> 0.84 worked great for me
[02:54] <tmkt> upgraded to 9.10 with 0.85
[02:54] <tmkt> and boom broken everything
[02:55] <tmkt> and tried 86...without any luck
[02:57] <hipitihop> tmkt: eek ... its really the only thing stoping from using as main tv/recording at the moment, since I have no remote use.
[02:57] <tmkt> so i went back to mythbuntu 9.04
[02:57] <tmkt> and installed mythtv trunk on that
[02:57] <tmkt> and couldn't be happier
[02:58] <hipitihop> mrand: btw I have upgraded lirc to 0.8.6 already.
[02:58] <tmkt> i know i'm going to continue to have a nagging feeling that i should be using 9.10
[02:58] <tmkt> but probably going to wait until i hear some better stories about getting HVR-1600 working with the newer lirc versions
[02:59] <hipitihop> tmkt: is it not possible to got he other way around, iow, have 9.10 and change lirc back to 0.8.4 ?
[02:59] <tmkt> probably just too much of a pain
[03:00] <tmkt> much easier to just install mythbuntu 9.04, select the remote from the menu and voila working
[03:01] <hipitihop> tmkt: hmm although for me there is no guarantee that it would be that simple for my Antec Veris Basic (Imon)
[03:01] <tmkt> yeah..no clue..i just know it was working for me before i had upgraded
[03:01] <tmkt> then it quit working
[03:01] <tmkt> not /dev/lirc0 anymore
[03:01] <tmkt> no matter what i did
[03:20] <mrand> Yeah, I was talking about 0.86.  Sorry to hear that doesn't work either.  There are some smart and persistent people out there with the same hardware - I'm sure that someone is figuring out what it takes.
[03:23] <hipitihop> mrand: I'm certainly persistent :-) this guide seems to be on the right track http://xbmc.org/forum/showthread.php?t=40290&highlight=antec+micro+fusion but I can't quite adapt the right combination for my device so usbhid is still the driver
[03:28] <hipitihop> mrand: btw mine shows up as Vendor=15c2 ProdID=0043 Rev= 0.02
[03:29] <mrand> So of course, you altered the quirks line according to that.
[03:30] <mrand> Kernel problem?  http://www.gossamer-threads.com/lists/linux/kernel/1114767
[03:37] <mrand> quirks=0x152c:0x0043:0x0004' is all over the internet.    Hmmm... in fact, I see a discussion about someone reading it wrong (15c2 vs. 152c)  If you can't figure it out,  talking to the lirc people (they have a mailing  list) may be your best bet.  Jarod is VERY helpful.
[03:37] <mrand> errr 15c2 vs. 152c
[03:37] <mrand> *shrug*
[03:38] <mishehu> [ 8459.816020] Corrupted low memory at ffff880000001000 (1000 phys) = 555500005555
[03:38] <mishehu> ouch
[03:39] <mishehu> [ 8459.821066] WARNING: at /build/buildd/linux-2.6.28/arch/x86/kernel/setup.c:71
[03:39] <mishehu> 9 check_for_bios_corruption+0xdd/0xe0()
[03:39] <mrand> Bummer.  Time for an overnight memory test?  Or just assume that is correct and replace it?
[03:41] <mishehu> I'll run a memory test but this lockup seems to occur when specific visualizations are running in mythmusic...
[03:41] <mrand> Recent build of Mythtv 0.22, or still 0.21?
[03:42] <mishehu> 9.04
[03:42] <mrand> I assume that means you're running 0.21.  You can technically run 0.22 on 9.04 also, but not many people know that.
[03:43] <mishehu> I didnt try, just using standard 0.21 that comes with 9.04
[03:44] <mrand> Gotcha.  I remember reading about that sort of problem with 0.21.  Developers are completely focused on 0.22 though, so the best you can do is make sure you are updated to the latest 0.21 via the auto-builds.
[03:45] <mishehu> I'm hoping that 9.10 will be out of beta soon :-)
[03:45] <mrand> ha.  It will release on schedule at the end of the month.
[03:46] <hipitihop> I just had a power flip here and mythbackend had to restart. it was in the midle of a recording. however now that it has restarted the mythweb back end status says it is still recording but in recorded programs the entry no longer has "currenly recording edit"... so is it or not recording and if not how do I get it to continue ?
[03:47] <mishehu> hipitihop: I'd also check with mythfrontend
[03:47] <hipitihop> mishehu: how ?
[03:47] <mishehu> you don't have a frontend somewhere?
[03:48] <hipitihop> mishehu: yes on same box at the moment
[03:48] <mishehu> under manage recordings there should be an option to see upcoming (and active) recordings.  also when you go to view recordings, you should see that which is being recording.
[03:48] <mrand> I think the ultimate answer would be to inspect mythbackend.log... the last few entries should give you a clue.
[03:52] <tgm4883> mishehu, it should continue to record in a second recording after the restart
[03:55] <hipitihop> tgm4883: indeed it has
[03:56] <mrand> There is at least one stable thing in the world.
[03:57] <mishehu> tgm4883: which is why I was suggesting he look there, it might look more obvious :-)
[03:58] <tgm4883> mishehu, whoops, my bad. I had just skimmed the convo and thought your backend had stopped recording
[03:59] <hipitihop> so to have another laptop just run mythfrontend, how big is that ? can I just install that on existing jaunty desktop ?
[04:01] <mishehu> tgm4883: nah, my backend/frontend hit a speed bump with a mythmusic visualization again.  wasn't paying attention to which one it was when it locked up X, so don't know yet which one I need to disable.
[04:01] <tgm4883> hipitihop, make sure the mythtv service is active in MCC on the backend
[04:01] <tgm4883> then install the fronted on it
[04:01] <mrand> hipitihop, yes you can.  It's quite small.  I believe the main backend will need to have an IP address configured for everything to work correctly.
[04:01] <tgm4883> and get your backend info from /etc/mythtv/mysql.txt
[04:01] <tgm4883> mrand, mythtv service in MCC
[04:02] <tgm4883> that and make sure the ip address isn't localhost
[04:02] <mishehu> I'd set a static IP for the primary backend.
[04:02] <mishehu> no dhcp.
[04:03]  * tgm4883 has static dhcp addresses
[04:03] <mishehu> that's a reservation
[04:03] <mishehu> not the same
[04:03] <tgm4883> yea i know
[04:03] <mishehu> if your dhcpd goes down, so will your backend.
[04:03] <mishehu> or your network connectivity
[04:04] <tgm4883> mrand, is there a way to forcefully uninstall packages?
[04:04] <tgm4883> i can't get these two themes uninstalled
[04:04] <mishehu> dhcp reservation didn't work well for me with my POS crisco/linksys WAP4400n dying every half hour.
[04:04]  * hipitihop also has reservation so all machines on home network get same ip.
[04:04] <mrand> purge?
[04:05] <tgm4883> mrand, nope
[04:05] <hipitihop> mishehu: I run a linksyd wrt54GL with tomato firmware... solid as a rock, only time it goes down is power outage :-)
[04:05] <tgm4883> hipitihop, +1 for tomato
[04:05]  * hipitihop apologises for going off topic
[04:05] <mishehu> hipitihop: yeah, but not the case with the WAP4400n.  just google "wap4400 connectivity problems"
[04:05]  * tgm4883 tomato on my wrt54gs V4
[04:06] <tgm4883> which is basically a wrt54GL
[04:06] <mishehu> probably one of hte worst WAP's out there on the market.
[04:06] <mishehu> spend all that money for something that's marketed as small business, and I wouldn't even use it for a paperweight.
[04:07] <hipitihop> mishehu: have you checked if open-wrt or tomato or dd-wrt will run on it ?
[04:07] <mishehu> hipitihop: highly unlikely.
[04:07] <tgm4883> E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution).
[04:07] <mrand> tgm4883:  maybe this:  sudo dpkg --purge --force-remove-reinstreq <pkg>
[04:07] <tgm4883> How do you specify a solution?
[04:07] <tgm4883> mrand, i'll try
[04:09] <mrand> I had that problem last week when one of the packages was out of sync (the first time the themes were out of sync, I think).  Through various attempts with apt-get , apt-get -f install, and upgrade manager, it went away on its own.
[04:10] <tgm4883> mrand, yea, that removed them
[04:10] <tgm4883> but it's still pretty broken :(
[04:10] <mrand> haha
[04:10] <tgm4883> won't upgrade without removing a bunch of mythtv packages
[04:10] <mishehu> ah the joys of package management.
[04:11] <mishehu> except for mythtv, my other systems all run slackware.  heh.
[04:11] <mrand> If debian based is better than the others, I pity the poor fools that are on the others.
[04:11]  * tgm4883 hates RPMs
[04:11] <mrand> I haven't run anything else in a decade.
[04:11] <tgm4883> and yum
[04:11] <mishehu> hipitihop: neither tomato nor dd-wrt support my unit.
[04:11]  * mishehu has been running slackware since around 1994.
[04:12] <mishehu> HEY YOU KIDS!!!!   GET OFF OF MY LAWN!!!
[04:12] <hipitihop> mishehu: pitty, sometimes jsut the firmware can make a world of difference
[04:12] <hipitihop> hehe
[04:12] <hipitihop> so anyone care to finish this for me to install frontend onto a jaunty laptop "sudo apt-get install ----"
[04:12] <mishehu> hipitihop: yeah well it'd be nice if crisco would fix it finally.  this is not a new problem with that unit.  they even had the balls to release a newer revision of it - the 4410, and it's got the same problems...
[04:13] <mrand> hipithop, you might consider just installeding MCC and let it do the work for you.
[04:13] <mrand> installeding.  nice.
[04:14] <mrand> But if you want to do it, the most important package is mythtv-frontend
[04:17] <hipitihop> ok, trying mythtv-frontend
[04:18] <mrand> The reason for using MCC is because it makes it easier to find and add the plugins and such
[04:18] <tgm4883> +1 for MCC
[04:20] <hipitihop> hmm in jaunty is that mythbuntu-control-center ?
[04:21] <tgm4883> yea
[04:21] <mrand> English spelling.  mythbuntu-control-centre
[04:22] <mrand> Daviey must have named it.
[04:22] <tgm4883> oh yea, i forgot
[04:22] <mrand> British spelling, I mean.
[04:22] <mrand> keeps life interesting.
[04:22] <hipitihop> and I will continue to be able to use as normal laptop
[04:23] <mishehu> dang british always thinking they own the language :-)
[04:24] <mrand> hipitihop: sure thing.  As I recall (on 8.04) it used to mess with your theme, but that may have been changed.  Otherwise it should not impact you other than having some extra packages installed.
[04:24] <hipitihop> cool thanks
[04:25] <mishehu> if audio worked a bit better in kvm, I'd run a frontend on a kvm session on my main workstation
[04:25] <hipitihop> I have another question while that is running... how can I get more details on the following from backend status "Last mythfilldatabase run started on 2009-10-12 13:04 and ended on 2009-10-12 13:04. mythfilldatabase ran, but did not insert any new data into the Guide for 1 of 1 sources. This can indicate a potential grabber failure.There's guide data until 2009-10-20 13:50 (8 days). "
[04:25] <mishehu> since I prefer to not build everything from sores.
[04:27] <mrand> Hmmm... only 8 days of guide data.  Normally it's ~14 days, so this has likely been broken for 6 days now.  /var/log/mythtv/mythfilldatabase.log is what you are looking for (although it's a mess of a log).
[04:46] <hipitihop> mrand: no such beast only have /var/log/mythtv/jamu.log , mtd.log, mythbackend.log, mythfronend.log & mythwelcome.log
[04:46] <hipitihop> checking the mythbackend.log
[05:04] <hipitihop> mrand: can't find such a log, however I have found /var/crash/_usr_bin_mythfilldatabase.1000.crash
[05:49] <darthanubis> hipitihop, back
[05:49] <darthanubis> fornow
[05:49] <darthanubis> f or now
[05:49] <darthanubis> geez
[05:51] <hipitihop> darthanubis: heh, need that error free keyboard hey :-)
[05:52] <darthanubis> or a backlit one
[05:52] <hipitihop> earlier you said " that is not how you go about doing it" not sure what you were refering to
[05:52] <darthanubis> no, but I was saying to install from an alternate cd
[05:53] <hipitihop> ah in regards to gnome vs xfce ??
[05:53] <darthanubis> you could just install xubuntu, then the mythtv packages
[05:53] <darthanubis> yes
[05:53] <superm1> you're goign to have trouble with that in karmic
[05:53] <superm1> some of the xubuntu stuff will conflict the mythbuntu stuff
[05:53] <darthanubis> or like I do, gnome and then mythtv packages
[05:53] <hipitihop> I see thanks... I sorted my xfce login problem by deleting the .config and .cache folders.
[05:54] <darthanubis> well then not xubuntu superm1 , but regular ubuntu for sure
[05:54] <superm1> well if you want to deal with possible pulseaudio problems, sure...
[05:54] <darthanubis> I have no such issues
[05:54] <superm1> well *now* the main issue is fixed
[05:55] <darthanubis> good
[05:55] <superm1> but before there was a mess with it
[05:55] <superm1> and still it's not ideal. mythfrontent suspends pulseaudio when you start it
[05:55] <superm1> meaning no audio out of most other apps in gnome
[05:55] <darthanubis> the last few updates broke my backend, but other than that, everything has been peachy
[05:56] <darthanubis> just waiting for mythtv-backend to become available again
[05:56] <hipitihop> does anyone know why playing back any of the recorded *.asx links via vlc on a normal desktop plays for a few seconds then stops ? don't remember it doing that with 9.04 release
[05:56] <darthanubis> hipitihop, maybe the backend is still transcoding the source file?
[05:58] <hipitihop> darthanubis: is there a way to tell, I though as soon the asx link is available then it should be playable
[05:59] <darthanubis> it will be available right after record
[06:00] <darthanubis> but if you have other jobs running on it like gencutlist or transcoding to remove commercials..then things can interrupt the stream
[06:00] <darthanubis> you can check the log, or just use mythweb to see current backend status
[06:02] <hipitihop> darthanubis: meaning as soon as recording has started.... I see, might be related to commercial skip or something
[06:03] <darthanubis> right
[06:03] <darthanubis> I just stream it via mythweb or just use the mythtv frontend, even wirelessly I use the frontend
[06:04] <darthanubis> Will my new router, streams from the backend downstairs without incident
[06:04] <darthanubis> screw trying to watch it via standalone player
[06:05] <hipitihop> darthanubis: hmm certainly not commercial pauses...must be something about that asx stream and vlc and even wireless...
[06:05] <hipitihop> darthanubis: so you just run frontend on your nromal desktop ?
[06:06] <darthanubis> try to set vlc's stream buffer higher?
[06:06] <darthanubis> yes
[06:06] <darthanubis> frontend on my laptop
[06:06] <darthanubis> if quality does not matter, then via mythweb
[06:06] <darthanubis> flash fullscreen
[06:06] <hipitihop> works ?
[06:06] <darthanubis> perfectly
[06:07] <hipitihop> probably have to enable that in backend.... how did you install the beta frontend ? I have jaunty here and normal pkg repo obviously doe snot have the beta so complains about DB version when connect to my beta back end
[06:08] <darthanubis> Now when I was across town, THEN I'd download the whole file and play it locally. But as long as I'm on the network, frontend, or mythweb
[06:08] <darthanubis> frontend and backend must match versions
[06:08] <darthanubis> I only use 9.10 now
[06:09] <hipitihop> aah so you're running 9.10 beta on your laptop too
[06:09] <darthanubis> it's not mission critical to me, although I did miss my recording of Cheaters due to the updates breaking mythtv tonight. Hopefully,  superm1 and the guys will have this fixed in hours, or by morning?;)
[06:09] <superm1> what's broke?
[06:10] <superm1> i've not seen any bug reports about anything breaking...
[06:10] <darthanubis> I'm running 9.10 on my main box, laptop, and mythtv backend. The laptop has the frontedn on it
[06:10] <darthanubis> the backend has both frontend and backend
[06:11] <superm1> did the backend not start up? or is it crashing? or what's happening?
[06:11] <darthanubis> superm1, well after updates, I lost the backend, and when I try to reinstall it, it complains about certain packages not being available to install.
[06:11] <darthanubis> the backend was REMOVED oddly enough
[06:11] <superm1> the build probably wasn't done yet when you updated then
[06:11] <darthanubis> as though the repos changed
[06:11] <darthanubis> right
[06:11] <superm1> apt-get update and check for it again
[06:12] <darthanubis> I've been doing that periodically
[06:12] <superm1> you're amd64?
[06:12] <darthanubis> yup
[06:12] <superm1> build finished 23 minutes ago
[06:13] <superm1> https://edge.launchpad.net/ubuntu/+source/mythtv/0.22.0~trunk22359-0ubuntu1/+build/1287581
[06:13] <superm1> in the future dont do upgrades if it's gonna try to remove stuff like that, wait for the mirrors to settle down
[06:14] <darthanubis> superm1, it caught me by surprise sup. It did not warn of any removal, just upgrade...
[06:14] <hipitihop> superm1: I did get an nfs problem this morning
[06:14] <superm1> hipitihop, file a bug for the package using apport-bug if the popup didn't come up
[06:15] <hipitihop> I have a crash file
[06:15] <superm1> hipitihop, then use sudo apport-bug /var/crash/FILE
[06:15] <superm1> it will file the report to the right people
[06:15] <hipitihop> cool thanks will do.
[06:20] <hipitihop> superm1: I also notice I have a large crash file for mythfilldatabase but it says the crash was due to an assert and aaport-bug doe snot support reporting those
[06:20] <superm1> hipitihop, yeah i've been seeing crashes for mythfilldatabase too, but i cant make anything of them
[06:21] <superm1> it's a shame
[06:24] <hipitihop> I guess that explains my missing mythfilldatabase.log which I want to check to see why backend is suspecting a grabber failure
[06:44] <hipitihop> I'm getting "The following packages have been kept back: linux-generic linux-headers-generic linux-image-generic mythtv mythtv-backend-master mythtv-common mythtv-database
[06:45] <superm1> try dist-upgrade
[06:45] <superm1> but make sure it's not trying to remove anything
[06:45] <hipitihop> will do when this curretn update && upgrade completes
[06:46]  * hipitihop shudders to think what might break next now that he's getting close to a usable backend
[06:48] <hipitihop> in the meantime... anyone know how to use full width & height of the tv screen across the hdmi output/input .. I seem to get 2-3 pixel vertical borders
[06:48] <darthanubis> superm1, thanks for the link to those files. Got my backend back up and running
[07:05] <hipitihop> superm1: dist-upgrade want to remove  mytharchive mythgallery mythmovies mythmusic mythtv mythtv-backend mythtv-backend-master mythtv-frontend mythtv-theme-gray-osd mythtv-theme-isthmus mythtv-transcode-utils mythvideo mythweather
[07:09] <superm1> hipitihop, well dont do it then
[07:09] <superm1> sounds like some builds aren't ready yet
[07:09] <superm1> are you amd64 too?
[07:11] <hipitihop> superm1: yes
[07:11] <superm1> you hit the same thing as darthanubis
[07:11] <hipitihop> its a ION Atom dual core
[07:11] <superm1> just need to wait for the builds to hit the mirrors
[07:11] <hipitihop> superm1: ok patience for me
[07:13] <boblawblah> hola everyone, i just installed mythbuntu 8.04 and i get these diagnal lines across the login screen and desktop but not the loading splash screen
[07:16] <boblawblah> ive tried downloading 9.04 but every time i do, the download errors about halfway through. so thats why i am stuck using 8.04
[07:20] <hipitihop> is there a correct way to restart backend machine from an ssh session apart from  "sudo shutdown -r now" I can''t see an option on mythweb
[07:21] <hads> sudo reboot
[07:21] <hads> Which is just the same thing you posted.
[07:21] <hipitihop> k thanks
[07:30] <boblawblah> ok i did ctrl+alt+f1, and i got a normal screen with no diaglnal lines, anyone know of anything i can check or modify to fix this?
[14:03] <olejl> Anyone know if nvidia-vdpau driver v 190 will be available in the repos soon?
[16:24] <ripperda> hello, I'm playing around with a new install of mythbuntu and trying to get a couple of things working
[16:24] <ripperda> one of the things I was trying to get working this morning was dvd playback/ripping
[16:24] <ripperda> I've installed libdvdcss
[16:24] <ripperda> I'm trying to start with dvd playback, to verify everything is working, but both mplayer and xine are having very basic problems
[16:25] <ripperda> xine fails with a BadWindow error whenever I try to run it
[16:25] <ripperda> mplayer will run, but if I try to playback a dvd, it appears to be failing with a mismatched colorspace
[16:26] <ripperda> I did install mythbuntu 9.10 beta, so I'm wondering if these are known problems, or if I'm having a user error
[16:27] <ripperda> actually, mplayer complains about the colorspace and VDecoder init failing, still opens a window for a second, then exits out. not sure if the colorspace is the problem or not
[16:47] <tgm4883> ripperda, odd
[16:47] <tgm4883> I think* it works fine on 9.10, but I haven't checked lately
[16:47] <ripperda> I actually think I'm seeing 2 different problems
[16:48] <ripperda> I think mplayer works (?), but I'm getting disk i/o errors
[16:48] <ripperda> I see a lot of reports online, digging through them
[16:48] <ripperda> looks like the ubuntu kernel has occasional problems with dvd r/w drives
[16:51] <sbak> anyone know anything about this? : 2009-10-12 11:42:44.689 Using the Qt painter
[16:51] <sbak> mythtv: could not connect to socket
[16:52] <sbak> I have installed mythtv several times, this is the first on 9.04. this is the first time i have had issues with installation
[17:03] <ripperda> strange, xine suddenly started working and everything appears fine, I'll try mplayer next
[17:05] <ripperda> mplayer's still giving me problems, complaining about not opening the video out device
[17:08] <ripperda> ok, I'm getting the mplayer video out device errors, even with an avi
[17:08] <ripperda> I noticed in an xterm that it looks like it's trying to access /dev/fb, but I'd really prefer it uses xvmc or vdpau, I'll play around with that
[17:18] <ripperda> I'll worry about that later, the main intent of dvd playback was just to verify that dvd decoding was working
[17:18] <ripperda> what I really want to do is rip dvds via mythdvd
[17:18] <ripperda> I'm in mythdvd and looking at the options for ripping. is there a page that goes into the details of the various options?
[17:22] <tgm4883> ripperda, http://www.mythtv.org/wiki/MythVideo
[17:22] <tgm4883> there is no mythdvd anymore, it was merged with mythvideo
[17:22] <ripperda> ah ok, thanks
[17:22] <tgm4883> you might also check http://www.mythtv.org/wiki/MythDVD#Usage
[17:23] <ripperda> yes, I had just found that page and was reading through it
[17:23] <ripperda> out of curiousity, it looks like most ripping just grabs the main movie and not the extras
[17:23] <ripperda> can those be ripped separately?
[17:23] <ripperda> or do most people just ignore those?
[17:24] <tgm4883> I ignore extras
[17:24] <mrand> It is possible to rip everything. I don't know if the Linux tools will do it or not.
[17:25] <ripperda> ok, thanks, I'll play around with things
[17:25] <mrand> Or rather, how well they do it.
[17:25] <ripperda> also, I have a french movie + english subtitles, I see the option to rip subtitles. will those be "always on" in the rip?
[17:25] <tgm4883> you can in k9copy, which is what I usually use anyway
[17:25] <ripperda> or will I be able to turn them on/off like a normal dvd?
[17:26] <tgm4883> my gut says you can turn them on/off, as long as you don't encode the video into another format
[17:26] <ripperda> ok. my sample disk is just a 30 minute video, so easy to experiment with
[17:30] <ripperda> ok, completely different question while that rips
[17:30] <ripperda> I have a hauppauge hd pvr, which I plan to use to record from my directv recorder
[17:31] <ripperda> I'm not really scheduling a recording, so much as recording "live tv" while I playback
[17:31] <ripperda> I did a simple test last night, and see that it automatically records live tv playback, and saves metadata based on schedule data
[17:31] <ripperda> I assume there's some way to edit these recordings?
[17:32] <ripperda> for example, the playback looks like it was broken into multiple records, due to my playback crossing the 1 hour program data of what was really live
[17:32] <ripperda> I'd like to parse the recorded video back into a single recording and correct the metadata
[17:32] <ripperda> is there a way to do that?
[17:39] <mrand> I'm not aware of myth having a way to join video files.
[17:40] <mrand> There should be other tools happy to do it for you though.
[17:41] <ripperda> and they look like mpg files, so any mpeg editor should do?
[17:44] <mrand> Yes.  Your commerical flagging will likely be off or break, but you can re-run it, or you could generate a cut-list yourself after the editing.
[17:45] <superm1> so that doesn't happen for actual recordings generally, they'll stick to a single file for the duration the program data indicates
[17:45] <superm1> i believe that's only for live that such things happen
[17:46] <superm1> and if you find that your guide data is inaccurate you can schedule it to start early or end late by X minutes
[17:49] <ripperda> thanks guys
[17:58] <ripperda> ok, got my first dvd ripped, but mythtv is having trouble finding it
[17:59] <ripperda> I opted to store all data under the user account "/home/mythtv/*" instead of "/var/lib/mythtv/*", due to disk partition layout
[17:59] <ripperda> I've updated all config locations that I can find, in the back and front end
[17:59] <ripperda> I now have 2 videos in /home/mythtv/video: a previously recorded mp4 and my newly recorded iso
[17:59] <ripperda> when I go into the video playback of mythtv frontend, it can't find those videos
[18:00] <ripperda> is this likely a frontend or backend config problem?
[18:00] <ripperda> livetv recorded to /home/mythtv/livetv and is working fine
[18:01] <mrand> Not sure how to answer that question.  mythvideo is a frontend plugin.  But the configuration data is stored in the database.
[18:01] <mrand> I don't have a front-end handy, but I'd expect in one of the mythvideo setup screens it specs where the videos are found.
[18:02] <ripperda> yes, I just updated that, but still not getting video. I'll try linking video to the original location and see if that works
[18:02] <superm1> ripperda, so by default we set up storage groups. so that complicates things a little
[18:02] <superm1> did you make sure that the videos storage group was configured in the backend to your new directory?
[18:02] <ripperda> superm1, probably not
[18:03] <superm1> ripperda, there is a a whole slew of storage groups that need to be updated in mythtv-setup then
[18:03] <ripperda> I see the original locations have the group bit sticky and my new ones don't
[18:04] <ripperda> superm1, ok, I'll take a look at that
[18:04] <superm1> also, if you were ripping to .iso, mythvideo can't play iso files when storage groups are activated
[18:04] <superm1> unfortunate, but known deficiency
[18:04] <superm1> you'll be missing out on a lot of the really cool metadata too if you don't remember to make storage groups for fanart/coverart/banners/screenshots etc
[18:06] <ripperda> superm1, so the next step is to edit the storage groups in mythtv-setup then?
[18:06] <superm1> Yup
[18:06] <superm1> you can launch it command line, or you'll find a button in the mythbuntu control centre that spawns it
[18:06] <ripperda> ok working on that now
[18:08] <mrand> Good one on the SG - completely skipped my mind.
[18:14] <ripperda> ah ok, I had already updated those, so no luck there
[18:17] <sbak> does anyone know about Firewire and mythprime?
[18:18] <superm1> ripperda, oh did you scan for video changes in mythvideo plugin?
[18:19] <superm1> hit "i", leave the plugin for about 5 seconds, and come back
[18:19] <superm1> there is a bug that is fixed in mythtv trunk as of yesterday requiring you to leave and come back after 5 seconds, but not yet on the repositories
[18:19] <sbak> seems like mythprime works 1/50 times? I have a SA4250HDC.
[18:19] <mrand> superm1: after today (or maybe even yesterday), the exit, 5sec, come back in should no longer be required.
[18:20] <superm1> mrand, yeah but the version in karmic doesn't have that
[18:20] <superm1> it was uploaded about 40 minutes before that commit
[18:20] <mrand> gotcha.  Oh, I see you said something like that up there.  Running busy/slow today.
[18:22] <ripperda> superm1, I tried that, but no luck. at what point am I in the mythvideo plugin? does that take over when the screen changes from the default mythtv style menus?
[18:23] <superm1> ripperda, when you choose "watch videos" you're in the mythvideo plugin
[18:24] <ripperda> superm1, ok, that's what I suspected
[18:24] <ripperda> is there a way to get more verbose output on where mythvideo is looking for files?
[18:25] <superm1> probably different verbosity flags on mythfrontend's invocation, possibly in /var/log/mythtv/mythfrontend.log too
[18:25] <ripperda> ok, I checked that logfile, but will take a look at options for more verbosity
[18:25] <ripperda> also, I have an old mp4, which perhaps mythvideo legitimately isn't recognizing, and you mentioned that isos shouldn't be recoginized
[18:25] <superm1> did you actually set a storage directory in the frontend mythvideo settings too?  you generally shouldn't need to - and it's actually set to nothing by default
[18:26] <ripperda> I believe I did, but I also linked the iso to both locations (old and new)
[18:26] <ripperda> perhaps I should transcode the iso to mpg? is there a simple command line to do so?
[18:26] <superm1> you can enable ISO support by just not using storage directories
[18:26] <superm1> just then you can't share videos to other machines
[18:26] <superm1> via myth://
[18:27] <ripperda> can I temporarily disable storage directories then?
[18:27] <superm1> Yeah, just remove the storage directory video group in mythtv-setup
[18:27] <superm1> and set the directory in mythfrontend
[18:27] <ripperda> trying to simplify the problem to verify I have a legitimate file to playback
[18:27] <ripperda> ok, will try that
[18:34] <ripperda> hmm, still no luck. I'm going to re-rip my video to mpg and take a look at verbosity options
[18:36] <superm1> try turning on file browse mode
[18:36] <superm1> its in the same menu that you'd normally scan for changes
[18:36] <superm1> disables any metadata stuff
[18:48] <ripperda> I'll give that a try shortly. transcode is running right now, so I'm going to go run some errands for a while.
[18:48] <ripperda> will come report back in an hour or so
[19:02] <ToeBee> superm1: do you know if the fix to your bug got committed in time to be in todays CD?
[19:03] <superm1> ToeBee, hasn't been uploaded to the archive yet.
[19:03] <superm1> it's just "committed" to the bzr branch
[19:03] <ToeBee> ah
[19:03] <superm1> so 10-12 disks are still busted
[19:03] <superm1> 10-13 get generated at 1:06am, so hopefully it will get uploaded in time for that
[19:13] <bobbob1016> For some reason, my backend seems not to be auto-starting anymore.  When I ran "mythbackend" from terminal, it says it can't connect to my mysql or something.  The frontend and backend are on the same machine.  I haven't changed anything network related, all I did was add a raid5 mdadm array.  Any ideas?
[19:20] <mrand> bobbob1016: Sounds like mysql is not running for some reason, or mythconverg database is not there or massively corrupted.
[19:23] <bobbob1016> mrand, I get this from terminal when I run "mysql" http://pastebin.ca/1616102
[19:28] <mersault> I'm trying out the new mythbuntu beta. I want to migrate my recordings from my old backend, but there's a mysql schema mismatch when I follow the directions in the mythtv manual. Anyone know how I can fix the mysql data?
[19:29] <gunni> mrand: I got tv again :)
[19:32] <gunni> mersault: Maybe you should only export/import the tables needed, that minimizes the possibility for scheme mismatches
[19:33] <mersault> gunni, I did that. The directions in the manual list the exact tables necessary. Still, there's a mismatch.
[19:33] <mrand> gunni: cool!   bobbob1016: internet is littered with that error message.  Might be that that an upgrade hosed or even removed mysql (although probably not your actual database) - I seem to recall seeing a bug about that recently.
[19:33] <mersault> gunni, I figured someone else here may have done that, and had a quick one-line query they executed to fix the issue.
[19:35] <mrand> bobo1016: I don't know if this is related to your problem or not, but is what i was thinking of: https://bugs.launchpad.net/ubuntu/karmic/+source/mysql-dfsg-5.1/+bug/413789
[19:35] <gunni> mrand: As described in the bugreport i reverted two patches against cx88, and got it working. cpu cooler fall off while doing and testing, so i first thought my patching did some kernel oops, but was just the cooler, and mainboard shut down. I will now reenable the first patch, and try again.
[19:36] <mrand> Excellent.  thanks for updating that bug with your conclusions!
[19:45] <bobbob1016> mrand, apt-get says mysql-server is installed already
[19:48] <ripperda> how long should a transcode of a 30 minute dvd take? it's been sitting at the "thinking" page since I last posted (40-60 minutes?)
[19:48] <ripperda> ah I see, mtd.log has an error:
[19:48] <ripperda> 12:38:58: Error: Exiting runTranscode(1) transcode exit code: 1
[19:48] <ripperda> 12:312:38:58: Error: Exiting runTranscode(1) transcode exit code: 1
[19:48] <ripperda> 12:38:59: job failed: job dvd 2 1 6 1 0 /home/mythtv/videos/The Red Balloon
[19:48] <ripperda> 8:59: job failed: job dvd 2 1 6 1 0 /home/mythtv/videos/The Red Balloon
[20:26] <sbak> Does anyone anyone in here have knowlege of Firewire. Does majoridiot ever show up in here anymore?
[20:27] <rhpot1991> sbak: some people may :)
[20:27] <rhpot1991> and I haven't seen MI in a while, he comes and goes
[20:29] <sbak> rhpot1991: thanks for the response! I'm pretty sure the issues I am having are cable box specific... But was hoping someone had tips on getting a stable connection
[20:30] <rhpot1991> sbak: what kinda issues, what hardware?
[20:31] <sbak> mythprime works 1/50 times. i have the SA4250HDC. I have had it working and recording, but I recently upgraded to 9.04 and now i can not get it to lock to a channel
[20:31] <sbak> I can change channels, and i know im tunned to a channel without encryption
[20:32] <sbak> I tried power cycleing both STB and Server and still can not prime the connection
[20:33] <rhpot1991> sbak: what version of mythprime?
[20:33] <sbak> Last night i did get a succesful mythprime, but have not been able to since.
[20:33] <sbak> 69h beta
[20:33] <sbak> is that the most recent?
[20:35] <rhpot1991> looks like it
[20:36] <sbak> rhpot1991: side note, I have time warner cable. when I originaly asked for firewire box in Jan they told me they don't support it. A week later I read the FCC note on the myth wiki. I called back and requested a FW cable box again. They played dumb again. I then stated the FCC reg, and they put my on hold and had a FW cable box shipped out to me within 3 days
[20:37] <rhpot1991> sbak: I've heard some shady things about TWC 5c encrypting everything, could explain your issues
[20:37] <sbak> rhpot1991: TimeWarner have been complete jerks about this, so i filled a complaint with the FCC. They closed the case without doing anything though.
[20:37] <rhpot1991> sbak: ya, fighting a losing battle there
[20:38] <sbak> rhpot1991: Yea, I feel like my frustraition is due to TWC because many people have had great success with the SA4250
[20:39] <ToeBee> sbak: the FCC regs only require them to provide you with the channels you could get OTA over FW, right?
[20:39] <rhpot1991> ToeBee: that and active ports
[20:39] <ToeBee> so I can't expect to record HD Discovery channel via FW
[20:39] <sbak> I am able to get into debug mode on the SA4250, and see that local channels are not 5c encypted, but everything else is. Which was another reason for my FCC complaint. I don't think that content i PAY for should be 5c encrypted
[20:40] <ToeBee> well good luck with that
[20:40] <rhpot1991> sbak: nope, only locals are required
[20:40] <sbak> rhpot1991: yup, frustraiting.
[20:40] <ToeBee> the only reason CableCard exists is so that they CAN encrypt the content that you pay for
[20:41] <ToeBee> I'm about to drop my cable TV service because of this. If I can't use my own mythtv box to record in HD then frack them AND the $15/month they want me to pay for a DVR
[20:42] <sbak> ToeBee: I agree. but in need the broadband. DSL doesnt have enough BW for me
[20:42] <ToeBee> I can still get cable internet without cable TV
[20:42] <ToeBee> that's what my coworker does already
[20:42] <gunni> mrand: Still there?
[20:43] <sbak> true. Do people have better luck recording HD with dish or directtv?
[20:43] <ToeBee> doubt it :(
[20:43] <sbak> haha
[20:44] <mrand> gunni: just walked up
[20:44] <ToeBee> my coworker just spends the money he would have spent on TV buying DVD box sets. I'm thinking I might do a little of that plus use boxee
[20:44] <sbak> I guess my only option is to apply for a job in a location that doesn't have 5c encryption (i think san fran is one)
[20:44] <gunni> mrand: Could it be, that upstart starts mythbackend to early. I have to once stop it, and start it again for dvb device to be recognized?
[20:45] <sbak> Hulu is amazing... that has potential to kill mythtv
[20:45] <sbak> if everything is free and on demand.. why pay
[20:45] <ToeBee> wait, such places exist? In the US?!
[20:45] <rhpot1991> hulu just released a linux client :)
[20:45] <ToeBee> rhpot1991: wait, what?
[20:45] <rhpot1991> !hulu
[20:45] <Zinn> Hulu has released a Linux version of their desktop client. While support for this is available in the Hulu forums http://www.hulu.com/discussions/19 , there is a quick writeup on how to get it working from your frontend here http://ubuntuforums.org/showthread.php?p=8075632
[20:45] <sbak> ToeBee: I am pretty sure that Some guy filled a law suit in SanFran and won. very liberal
[20:46] <mrand> Lots of things have the _potential_ to kill mythtv.  But I'm guessing it will continue to live on for quite a long time.
[20:46] <ToeBee> hmmm no encryption AND close to mythbusters HQ...
[20:47] <mrand> gunni: interesting theory.  Basically you are suggesting that the dvb driver (or device) is not ready before the backend process is launched?
[20:47] <sbak> mrand: I will always use it.. but the ability to not record HD drives me insane.. might have to spend 200$ on that haupauge with component in.
[20:47] <mrand> sbak: I agree.
[20:48] <gunni> mrand: Yes, it seems so. Could of course be because of my changes in the driver, but i killed some udelays, so should be faster to init
[20:48] <ToeBee> until they stop making cable boxes with component and force everyone to HDMI with HDCP :/
[20:48] <sbak> lol
[20:48] <gunni> mrand: cx88 is the latest driver in my /var/log/messages
[20:48] <mrand> gunni: if it is a race condition, try putting some extra delays back in.
[20:48] <mrand> To make it worse.
[20:49] <gunni> I will now try to contact the original patcher from linux tv, maybe he can say something
[20:50] <rhpot1991> sbak: so you used the -f flag to try out the different SA's listed?
[20:50] <sbak> rhpot1991: Yes.
[20:51] <rhpot1991> and -c to set to a safe channel?
[20:52] <mrand> gunni: An easy way to check your theory is to simply shutdown and restart (or don't auto-launch) the backend.
[20:52] <ToeBee> re: hulu. There are rumors that they are looking at going to subscriptions :/
[20:53] <mrand> ToeBee: for the amount of bandwidth, they either need subscriptions or ads.
[20:53] <sbak> yea, but the -c option isn't changing the channel right now wich is odd
[20:53] <gunni> Yes, after a restart, the backend has this problem, i try not autolaunching it
[20:53] <rhpot1991> sbak: have you tried PMing majoridiot on the forums?
[20:54] <mrand> gunni: was that "You tried", or "you will try"?
[20:54] <gunni> mrand: I tried rebooting sometimes, but did not disable backend on start.
[20:54] <mrand> I don't know that you have to disable it.  You could just stop the backend and then restart it well after bootup
[20:55] <gunni> For me its started automaticaly since i run it
[20:56] <sbak> rhpot1991: no, have not PMed him. I will though. I just was hoping it was something simple. Im to the point where im going to learn all i can about ieee1394. I really want to know why it works, and then with out any change to the environent - it doesn't work.
[20:57] <sbak> to me, that doesn't add up. ieee1394 should have never been released if its so unstable or whatever
[20:57] <rhpot1991> sbak: IMO it sounds like an issue with your box, but I dunno if you will be able to do anything about it
[20:58] <sbak> rhpot1991: right... oh well
[20:59] <rhpot1991> priming doesn't normally break if your setup is usable, and normally resets fix it when it does
[21:02] <beavis> Hey guys, do you know if there are any known issues with DVB-t on karmic atm?
[21:03] <beavis> I installed karmic beta last week and lost dvb-t after an update 2 or 3 days ago
[21:04] <beavis> mythtv doesn't find any channels (nor does me-tv or similar)
[21:06] <_ben> it's fine for me
[21:07] <_ben> what tuner do you have?
[21:07] <beavis> b2c2-flexcop: initialization of 'Air2PC/AirStar 2 DVB-T' at the 'PCI' bus controlled by a 'FlexCopIIb' complete
[21:08] <mrand> beavis: please see Bug #439163.  If that doesn't describe your problem, you can open a new ticket.
[21:08] <Zinn> Bug 439163 in mythbuntu "Channel scan timed out" [Undecided, Confirmed] http://www.launchpad.net/bugs/439163
[21:08]  * mrand pets Zinn
[21:09] <_ben> so
[21:09] <_ben> i'm getting pretty bad dvd playback
[21:09] <_ben> it's fine if i rip the DVD but ideally I'd like to put a dvd in and just watch it
[21:11] <beavis> I guess it's an issue with karmic not with mythtv since me-tv doesn't work either
[21:11] <mrand> Ben, if it works from a rip, that is good news in my mind... means you don't have a video card related problem.
[21:11] <_ben> mmm
[21:11] <beavis> modules get loaded correctly
[21:11] <beavis> everything was ok last week
[21:11] <mrand> beavis: that is possible.  My current theory is that the kernel changed and a few programs (like myth, and maybe me-tv) didn't follow the changes.
[21:12] <mrand> beavis: if you can figure out when it changed, it might be helpful.
[21:12] <beavis> there's only one thread on ubuntuforums about these changes
[21:12] <beavis> http://ubuntuforums.org/showthread.php?t=1278275
[21:12] <mrand> _ben: you should check your frontend logs for any useful messages.
[21:13] <beavis> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/421258 this one?
[21:15] <mrand> beavis: that was changed a month ago - well before the beta was released.
[21:34] <jfry> simple question... I am upgrading to the new beta and plan to do a full reformat... is there a way to update my database schema before backing it up.  I want to clean out all the crud and only restore my current and previous recordings tables
[21:39] <mrand> jfry - I'm considering doing something similar... I would love to hear how it goes for you.   On the assumption you are running 9.04/Jaunty, I was thinking of going the paranoid route: (1) backup current database  (2) install 0.22 [it is available for Jaunty], which upgrades  database  (3) backup THAT upgraded database as well (4) clear out database and try restoring as you plan to do with 9.10.
[21:39] <mrand> Then finally, move to 9.10 and do the real restore.
[21:43] <mrand> I want to do it so that I'm sure to pick up all the new defaults for the database, especially storage groups.   Mine was originally set up with 0.20 on 7.10.
[21:45] <jfry> that's my thinking.  I'm pretty sure the schema upgrade is only a series of scripts.  So I figure I could 1. backup current db, 2. run schema upgrades from .22 source, 3. backup 0.22 version of current data. 4. reformat and install new beta. 5. do partial restore as seen on myth wiki pages.
[21:45] <rhpot1991> mrand: shouldn't be needed really, when you upgrad to karmic it should upgrade the db, but yes backups are safe so do them
[21:45] <hads> Just backup and do it.
[21:45] <jfry> rhpot1991, the problem is that we only want a partial restore.
[21:46] <jfry> and you can't do a partial restore and schema upgrade at the same time
[21:46] <rhpot1991> jfry: hmmm I didn't read yours, that makes sense now
[21:46] <mrand> rhpot1991: But when they are upgraded, they will keep your current directories and settings and such.  I'm considering starting over from scratch so I get all the latest defaults for stuff.
[21:47] <hads> DELETE FROM settings; :)
[21:47] <mrand> hehehe
[21:48] <hads> There's very few tables you would need to deal with to do it manually.
[21:48] <mrand> jfry: yes, if you look in the myth source, schema upgrades are simply a series of if(current_schema=NNNN) statements .
[21:48] <rhpot1991> mythweb flash player annoys me
[21:48] <rhpot1991> randomly doesn't know the length of the videos and chops them off
[21:50] <jfry> mrand, yeah... I just downloaded the 0.22 source and I'm looking for the schema upgrade script... do you know it's name?
[21:50] <mrand> It isn't a script.  It's contained in the source.  It's distributed :-)
[21:50] <jfry> ahh... so it's in a binary then... so there is no way for me to upgrade my schema before taking down my current server.
[21:51] <hads> Well, you could copy all the SQL out of the source.
[21:51] <jfry> uh... no
[21:51] <mrand> Not easily.  You could do.... yes, what hads said
[21:51] <mrand> hehehehe
[21:51] <mrand> why not?!  *grin*
[21:51] <mrand> Besides all the opportunity for human error, what could possibly go wrong?
[21:52] <hads> A little bit of sed/awk/grep should get it out without too much pain
[21:52] <jfry> I can do a full restore, then upgrade, then backup, then drop, then partial restore.... it's just a pain to do it that way.
[21:52] <hads> BUt like I said, deleting the settings would be a lot easier.
[21:52] <jfry> I'd much rather the old data never touch the new server.
[21:52] <hads> Then just lose your recordings
[21:52] <jfry> hads, actually, the new 0.22 has a partial-restore option on it's restore script.
[21:53] <mrand> jfry: what are you referring to?
[21:53] <jfry> there are a lot of tables that can be dropped if you want a clean setup.
[21:53] <hads> Yeah, just some perl script which does SQL for you.
[21:53] <jfry> http://www.mythtv.org/wiki/Database_Backup_and_Restore#Partial_restore_of_a_backup
[21:54] <mrand> jfry: good find.
[21:57] <jfry> yeah... it still requires doing a full restore of my .21 database on my new clean server... but I guess dropping that database afterward will clear it all up anyway.
[22:00] <gunni> mrand: mythbackend starting to early seems to be true. Nearly every reboot i get this, and as it changed to upstart i think thats the reason. Should i file a new bugreport about it?
[22:10] <mrand> gunni: I'm having a hard time following you:  "as it changed to upstart"?    Did you delay the startup (or stop and then restart) the backend?
[22:11] <gunni> For me it looks like the change to upstart happened recently?
[22:12] <tgm4883> mrand, gunni i know there was testing but I wasn't sure if superm1 had pushed that through
[22:12] <gunni> I dont know how to prevent the backend from starting on boot, so i stopped it and then started it
[22:12] <mrand> gunni: and when you started it, things worked fine?
[22:12] <gunni> Yes
[22:12] <tgm4883> the change to upstart should actually allow us to depend on other things to be started first before the backend starts
[22:13] <mrand> gunni: That's great news.  yes, please open a ticket.
[22:13] <mrand> tgm4883: I may be missing something, but this looks like it is firing off the backend before the device is even initialized by the kernel.  Surely we don't fire it off that early!
[22:16] <superm1> gunni, what are you getting about it starting early?
[22:17] <superm1> er what's wrong with it starting so early for you  better yet
[22:17] <gunni> mythbackend seem to not recognize the dvb card
[22:17] <gunni> in mythweb the "encoder status" stays empty
[22:18] <gunni> like this: http://pastebin.com/mc0752ae
[22:19] <superm1> gunni, what service needs to run for it to be ready?
[22:20] <gunni> dont know, i will file a bug and paste as much info as i find into it.
[22:21] <superm1> gunni, can you pastebin /etc/default/mythtv-backend?
[22:21] <superm1> and how are you restarting the service to make it work?
[22:21] <gunni> sudo stop mythtv-backend
[22:21] <gunni> sudo start mythtv-backend
[22:21] <mrand> gunni: When you stop mythbackend and restart it, you said things work.  Is this with the stock kernel, or the modified one?
[22:22] <gunni> Its the modified one, as thats the only way to get it working at all
[22:23] <gunni> But the upstart thing came in just when i updated to trunk mythtv again, so there was some overlapping.
[22:23] <mrand> Ok, so you are thinking it is a two part thing.  First, the (old) change in the kernel is causing some grief. Then on top of that, mythbackend fires too early.
[22:24] <gunni> I could try reverting mythbackend to the old version (think that was not based on upstart), to check that, but that tomorrow, today i am happy it runs again
[22:25] <gunni> Thats odd. Mythbackend does not log anything since my crash this afternoon
[22:28] <gunni> Is there a log where i can see when mythbackend is started? (Not mythbackend.log, as it stopped logging)  Maybe something like upstart.log or like this?
[22:33] <superm1> gunni, it still should be logging to /var/log/mythtv/mythbackend.log
[22:33] <superm1> if it's not, then check /etc/default/mythtv-backend
[22:33] <superm1> it should have a logfile argument set
[22:34] <gunni> http://pastebin.com/f2b768947
[22:38] <superm1> gunni, you've  got the wrong content in there
[22:38] <superm1> this won't work right with that
[22:38] <gunni> Never touched that file
[22:38] <superm1> http://bazaar.launchpad.net/~ubuntu-mythtv/mythtv/mythtv-trunk-022/annotate/head%3A/debian/mythtv-backend.default
[22:38] <superm1> that's what you should be having
[22:38] <superm1> it should have updated when you updated the package
[22:40] <superm1> (which would explain why it wasn't logging) - and also means it was launching as root, not 'mythtv'
[22:40] <gunni> I now changed it by hand. After the actual recording ended, i restart the backend
[22:41] <gunni> Oh, you are right: root      4676  3.3  1.4 701556 60320 ?        Sl   22:23   2:37 /usr/bin/mythbackend
[22:41] <gunni> As it never did that must have been the today update
[22:41] <gunni> 0.22.0~trunk22373-0ubuntu0~mythbuntu3
[22:43] <superm1> wonder if there is a different bug present here though
[22:43] <superm1> indicating why that /etc/default/mythtv-backend didn't get updated
[22:43] <superm1> you sure you never touched it?
[22:45] <gunni> I am sure
[22:46] <gunni> Was changed 2009-6-26: -rw-r--r-- 1 root root  219 2009-06-26 05:37 mythtv-backend
[22:48] <gunni> It logged correct, till the update from today, so i am a bit confused
[22:49] <gunni> And it ran as mythtv before
[22:55] <gunni> mrand: I think http://svn.mythtv.org/trac/ticket/7292 can be closed, as it seems to be a driver bug
[22:56] <superm1> gunni, it looks like a bug indeed
[22:56] <superm1> because i dont see it in that deb on https://bugs.edge.launchpad.net/~mythbuntu/+archive/trunk-0.22/+packages
[22:57] <gunni> Maybe the logfile and user was in the wrapper script just before, or in the init.d script?
[22:58] <superm1> it was in the init.d script before
[22:58] <superm1> but also /etc/default/mythtv-backend was getting installed before
[22:58] <superm1> weird!
[22:59] <superm1> i can literally compare mythtv-backend_0.22.0~trunk22373-0ubuntu0~mythbuntu2_i386.deb and mythtv-backend_0.22.0~trunk22373-0ubuntu0~mythbuntu3_i386.deb and see it missing in the karmic build only
[22:59] <gunni> Sorry, i have to go to bed. 8 hours till work :)
[23:00] <gunni> Will have a look at the "mythbackend starting too early bug" tomorrow
[23:03] <_ben> mmm
[23:03] <_ben> meh
[23:03] <_ben> i can play dvds fine with vlc but not the internal player
[23:03] <_ben> frustrating++
[23:18] <mrand> _ben: you should be able to capture some logs with the correct verbose setting to help the devs debug that issue.
[23:24] <_ben> i'm kinda making progress
[23:24] <_ben> sound/subtitles are out of sync
[23:24] <_ben> i think that is a known bug/ticket tho
[23:25] <mrand> sound is out of sync with video on mythvideo?  I'm not immediately aware of that being a known problem, but then again, I don't know all problems ;-)
[23:25] <mrand> or are you saying sound out of sync with subtitles?
[23:28] <_ben> atm, the main annoyance is stuttering playback
[23:28] <_ben> but then with external players playback is fine - but audio/subtitle sync isn't great
[23:29] <_ben> yeah, audio/subs are out of sync atm with Internal player
[23:29]  * _ben tries to find said ticket
[23:32] <_ben> http://svn.mythtv.org/trac/ticket/6753
[23:37] <mrand> ah... ok.  subtitles are minor enough that I don't pay close attention to that.  I thought you meant that audio itself was out of sync.
[23:38] <mrand> For the stuttering playback, can you capture a verbose log?
[23:38] <_ben> yeah, lots of variables in this
[23:38] <_ben> http://svn.mythtv.org/trac/ticket/6367
[23:38] <_ben> looks interesting
[23:39] <mrand> Very interesting.  Didn't see that one.
[23:40] <mrand> Good find.  So we may be stuck on that for a bit.
[23:40] <_ben> also: http://svn.mythtv.org/trac/ticket/6456 which is a dupe of the above bug
[23:41] <mrand> That one was on 0.21  6367 is active on 0.22, so all we can do is wait.  Sorry!
[23:42] <_ben> Yeah
[23:42] <_ben> i might mess with different players
[23:42] <Seeker`> hmm, my playback bug seems to have disappeared