[02:40] <john____> hi, I am running a headless mythtv backend on top of ubuntu, However when I try to transcode something with the default profile it fails with No video information found! Transcode Errored: Program: Autodetect (exit status 255, job status was Errored" to which the solution requires going to utilities/setup -> setup -> tv settings, but im not sure how to do that over ssh
[02:40] <mrand> john____: vlc over ssh, or nx client/server.
[02:41] <dmfrey> john____: check that your transcoder is set to mpeg4
[02:41] <mrand> vlc... sorry, vnc
[02:41] <john____> how do i check what the transcoder is set to?
[02:42] <dmfrey> run mythfrontend over ssh -X or vnc into that box
[02:42] <john____> mythfrontend isnt installed
[02:42] <john____> should I install it?
[02:43] <dmfrey> is mythweb installed?
[02:43] <john____> yep
[02:43] <dmfrey> look at the database settings there
[02:43] <dmfrey> not sure if those are shown
[02:43] <john____> there are some settings there but not sure what to change
[02:44] <dmfrey> i think you can see your transcoders from a remote frontend
[02:47] <john____> just installing mythfrontnd on my computer
[02:47] <dmfrey> settings -> tv settings -> recording profiles
[02:55] <john____> thanks, got it to work
[04:36] <Gamrok>  hey guys i had a question do i need to install the restricted drivers to properly connect my tv tuner to my machine
[04:39] <mrand> Gamrok: I'm not sure.  The only thing that I can imagine is maybe binary blob firmware for some tuners maybe?
[04:39] <mrand> My first reaction is no, though.
[04:40] <Gamrok> ok thanks for the help mrand
[13:42] <BjornR1989> Are BNC's allowed on this channel?
[13:47] <BjornR1989> nvm, my question got answered.
[14:05] <baalsgate> i have a stuffed setup cant get mythtv-setup to run at all
[14:37] <baalsgate> anyone alive in heree ?
[14:37] <baalsgate> anyone know why i might be missing dvb-fe-tda10046.fw in the /lib/firmware directory ?
[14:38] <DHR> yes.  Your previous message contained no actionable information.  And I'm a newbie.
[14:39] <baalsgate> firmware files in /lib/firmware seem to be kernal specific so umm how do i grab the firmware files for 2.6.31-19-generic
[14:40] <DHR> mine doesn't have that file either
[14:41] <baalsgate> i have it in /lib/firmware/2.6.24-25-generic but im now running 2.6.31-19
[14:43] <baalsgate> the whole setup seemed to crap it after a upgrade need to fix nvidia drivers aswell as cant seem to run the mythtv-setup either
[14:44] <DHR> consider asking "dpkg -S /lib/firmware/2.6.24-25-generic/..." to find out what package contained the fw file (of course ... stands for the rest of the pathname)
[14:46] <baalsgate> its in linux-restricted-modules-2.6.24-25-generic
[14:47] <DHR> have you got linux-restricted-modules-<current kernel level> installed?
[14:47] <baalsgate> no idea
[14:49] <baalsgate> cant find a version with this 2.6.31-19 kernal
[14:53] <DHR> Hmm.  My system is the same in that regard.
[14:54] <baalsgate> well that is very strange there is no linux-restricted-modules-2.6.31-19-generic even searching google does not give much
[14:56] <DHR> I would imagine that firmware that runs on a device would be invariant with kernel versions.  If, however, it runs in the x86 processor (in the kernel), that might not be the case.
[17:31] <coastGNU> since 0.23.0~trunk23567-0ubuntu3 mythfrontend says 'Fehler: Alle Eingänge sind belegt, aber es gibt keine laufenden Aufnahmen?' (error: all inputs are in use, but there is no running recording)
[17:33] <coastGNU> Card is an pvr-150, vlc and the hard way #cat /dev/video <foo.mpeg;mplayer foo.mpg' works.
[17:33] <coastGNU> seems that mythtv can't get a lock on this card?
[17:34] <coastGNU> sry,  'cat /dev/video >foo.mpeg ; mplayer foo.mpeg' of course
[17:40] <mrand> coastGNU: when I google on this error, I see a several forum and mailing list threads.  Most seem to revolve around IP address and/or config.xml (for ALL users, including the ones which execute the backend app).  Maybe with a bit of configuration through in thanks to slave backends.  #mythtv-users or the Mythbuntu forums may have more info.
[17:41] <coastGNU> mrand: didn't change any configuration. did only an update to the latest mythtv packages un ubuntu
[17:42] <mrand> coastGNU: are you saying that 0.23 working fine for you before this week?
[17:44] <coastGNU> mrand: no, there was an pulsaudio error which says pulse is running and it can't disable pulse
[17:44] <mrand> coastGNU: known problem... should be fixed soon.
[17:44] <mrand> (pulse audio)
[17:45] <coastGNU> known Problem, Pulseaudio? or no lock?
[17:46] <coastGNU> mrand: pulseaudio is fixed, playback of recordings works as in 022
[17:47] <mrand> Oh, I see what you're saying now.   Before your latest update, 0.23 was not working because of pulse audio.   Ok, other than pulse audio, was 0.23 not giving the "all inputs are in use" error?
[17:48] <mrand> I.e., last week could you play video, this week you are getting "all inputs are in use".
[17:48] <coastGNU> mraand, yepp. But last week it was 0.22 wasn't it
[17:50] <superm1> okay so this might just be a new bug with 0.23 then :)
[17:50] <superm1> can you check mythtv-setup and make sure it's all still configured right?  i'm wondering if something went wrong with the upgrade possibly
[17:51] <coastGNU> mrand: btw, config.xml? You are talking about the themes *.xml files? kknock, knock, may be I should remove my local themes in ~/.mythtv/themes
[17:51] <mrand> coastGNU: Can you do this:  cd /home ; find . -name config.xml
[17:52] <mrand> coastGNU: No, not themes.  config.xml is where the mysql stuff is stored.
[17:53] <coastGNU> mrand: config.xml for mysql stuff?? I'm running linux here
[17:55] <superm1> coastGNU, config.xml is the default way that it finds the backend/mysql database currently
[17:55] <coastGNU> mrand: ok, there it is seems to be ok, hostname is 127.0.0.1, dbusername and dbpasswd are ok, so are dbname and port
[17:55] <Zinn> [127.0.0.1] MaineFish Productions
[17:56] <coastGNU> mrand: MediaRenderer is set to '0e6e7615-5d56-4de1-98c6-aa2991e8467c'
[17:59] <mrand> coastGNU: and there was only one config.xml file?  Is there a leftover mysql.txt file that might contain conflicting info?
[17:59] <mrand> maybe also compare against /etc/mythtv/config.xml
[18:01] <coastGNU> mrand: the only difference is in mysql.txt: DBType=QMYSQL3
[18:04] <mrand> coastGNU: Only random thing I have left to suggest/try is maybe it would work if you set an ip address rather than using 127.0.0.1 (in mythtv-setup)
[18:05] <coastGNU> mrand: see also http://paste.debian.net/60510/
[18:05] <Zinn> [paste.debian.net] debian Pastezone
[18:06] <coastGNU> mrand: I tried the local 192.168.xx.yy address, it showed up that database requests are answered _verry_ slow. (started mythfrontend with -v all)
[18:07] <mrand> -v all might be very slow... haven't tried it lately (nor in 0.23)
[18:08] <coastGNU> mrand: is there a place in the database where a lock bit is set? may be its an idea to have a look there, but I can't find it. I'm no mysql expert, sorry
[18:10] <coastGNU> mrand: I think it might be a database problem because I'm is also unable to save a new recording schedule.
[18:11] <coastGNU> mrand: s/I'm is/I'm/
[18:12] <mrand> coastGNU: From the googling that I did, I was assuming it is a database access problem.   But I don't know what else to suggest.  If superm1 has any other ideas, he'll pipe up.
[18:12] <superm1> well my only thought is an upgrade problem that the db didn't like
[18:12] <superm1> make sure that in mythtv-setup the inputs are hooked up right, and refer to the right devices
[18:12] <superm1> and to your video source etc
[18:12] <superm1> and data source
[18:13] <mrand> Yeah good point.  First step in debuggin: check your configuration.  Twice.  Then have someone else check your configuration.
[18:17] <coastGNU> mrand: If watching a previous recording works I would asume that mythfrontend is able to access the database. So I would asume that it might be a problem with the database upgrade itself and not a config problem. Right, istn't it?
[18:18] <superm1> well we dont know if that's where the problem is yet, but i'm saying double check that the configuration is right in case the upgrade broke it
[18:19] <coastGNU> mrand: there are several pakets with known problems which affect mythtv at the moment, so I'll wait what will come next...
[18:19] <coastGNU> mrand: thanks a lot ..
[18:20] <mrand> coastGNU: let us know if you figure out something.
[19:16] <DuCkNeT> hi all
[19:16] <DuCkNeT> little question here...
[19:16] <DuCkNeT> if i have divx movie on harddrive or network can it be played in mythbuntu ?
[19:16] <rhpot1991> !ask | DuCkNeT
[19:16] <Zinn> DuCkNeT: Please don't ask if anyone is around or if it is alright to ask a question.  Many people check back periodically and may answer your question when they see it.  IRC is not normally an instant fix so check back often for an answer.
[19:16] <directhex> has there been a change in a recent update (e.g. a recent kernel) which would cause myth to refuse to play audio on a device where the sample rate of the input file doesn't match the only sample rate supported by the output device?
[19:17] <directhex> i.e. the file has 44k1 audio, hdmi out only supports 48k audio
[19:17] <directhex> so i can play dvd rips fine, but not old tv recordings
[19:17] <rhpot1991> DuCkNeT: yes, you can play videos in mythtv with mythvideo
[19:17] <DuCkNeT> rhpot1991: can i browse for file on network store on nas ? i cant seem to figure out how ....
[19:18] <rhpot1991> DuCkNeT: you need to either drop it in the videos storage group (/var/lib/mythtv/videos) or setup mythvideo to look for it
[19:18] <rhpot1991> !iso
[19:18] <Zinn> Storage Groups are a streaming method of transmitting material to a frontend, meaning they don't provide block-level access to the file in question. An ISO is a disk image, and requires block-level access. Upstream has a plan to simulate a block device across the network using NBD for 0.23. Until then you can use the following workaround: http://www.baablogic.net/drupal/node/7
[19:19] <rhpot1991> follow that link, the place in there is the place you want to specify where your files exist
[19:19] <DuCkNeT> k thx
[19:19] <tgm4883> rhpot1991, rather, I think he wants to use the NAS?
[19:19] <rhpot1991> or move the storage group to look at your directory, which can be done in mythtv-setup
[19:19] <rhpot1991> I recommend using the storage group unless you have a reason not to
[19:19] <tgm4883> rhpot1991, he still have to mount the NAS locally?
[19:19] <DuCkNeT> well not much hd space on my unit
[19:19] <DuCkNeT> all is on network storage
[19:20] <directhex> wait, speaker-test works with 44k1
[19:20] <tgm4883> i dont think it will auto find network shares
[19:20] <rhpot1991> DuCkNeT: yes most likely you will need to mount the NAS locally
[19:21] <tgm4883> DuCkNeT, the NAS is an actually NAS unit right, not just a computer you set up as a NAS?
[19:21] <DuCkNeT> yes correct
[19:22] <tgm4883> ok
[19:22] <DuCkNeT> raid 1 nas
[19:22] <tgm4883> yea you will need to mount the NAS locally I think
[19:22] <tgm4883> what protocol does it use?
[19:52] <directhex> argh :'(
[21:34] <nwidger> hello
[21:34] <nwidger> anyone know the size of a default mythbuntu install?
[21:40] <superm1> it depends on the roles you picked
[21:40] <superm1> ~1.5-2gb normally
[21:50] <rhpot1991> lucid fresh backend/frontend install is 1.7gb
[21:51] <superm1> and lucid's is bigger than karmic, so i'd say probably a lil smaller on karmic
[21:56] <rhpot1991> I've run on a 4gb usb stick with success, only had one issue with logs growing once
[22:10] <nwidger> cool, thanks guys
[22:38] <walm> Hi,  I'm having an issue playing some .mkv files 1080P with DTS audio (some play fine).  The video is jumpy and audio crackles.  These files play fine in mplayer.  Audio is through spdif passthrough to AV receiver.  Logs are at http://mythbuntu.pastebin.com/f2462ab42   This has been happening for multiple versions of myth.  I just upgraded to .22 in hopes it might correct this.  I'd appreciate any pointers at to what to look at to correct this.
[22:50] <mrand> walm: Upstream has moved on from 0.22 and isn't doing much in the way of fixes for it.  Instead they are focused on (and are about to release) 0.23, which contains another ffmpeg sync...
[22:50] <mrand> I don't know if you can try that in a virtual machine or on a test box (possibly repartitioning it to make room for a test OS install), but you'd need to capture 0.23 mythfrontend log with -v playback to be something the developers could work on.
[23:09] <mrand> Cool.  Daughter is watching science rather than cartoons: Recording Now:  How Do They Do It? (Science Channel) Ends: 17:30
[23:14] <tgm4883> mrand, no, she just figured out how to make mythtv think it's watching science then use the command line to change the channel to cartoons
[23:14] <tgm4883> honestly, i'm not sure which way is better
[23:21] <walm> Ah, I thought it might just be a setting I missed.  So I should try .23 and go from there?  Is it fairly stable?  Would I have to change the backend as well?  I only use it as a media server/player and not for TV (no tuners).
[23:24] <mrand> walm: good point.  Here in a few days, you could possibly boot a live-CD which contains a front-end.  You could maybe try playing the media on that without having to install anything.
[23:24] <mrand> live-CD for Mythbuntu 10.04 is what I'm referring to.  Wait until tomorrow to download it though.
[23:25] <mrand> walm: it could be a setting.  I'm not up on VDPAU option(s).
[23:26] <mrand> tgm4883: very true.  She could have used the cable box remote to change the channel.
[23:27] <tassbur> hi
[23:28] <walm> mrand, great idea. I keep forgetting about livecd.  I'll give that a shot over the weekend.  Is there a way to capture logs when running from cd?
[23:36] <mrand> walm: there is surely a writable partition ... /tmp if nothing else, that you could capture a log to, then attach that captured log to a launchpad bug report (if live-cd will let you,  "ubuntu-bug mythplugins" is the preferred method, but if that doesn't work, just use your browser)
[23:40] <walm> Ok, one more question.  Will this be available on mythbuntu.org as a beta download (not there yet) or someplace else?
[23:43] <mrand> !qa
[23:43] <Zinn> http://iso.qa.ubuntu.com/qatracker/build/mythbuntu/all
[23:43] <mrand> let's see if it's there.
[23:44] <superm1> walm, http://cdimages.ubuntu.com/mythbuntu/daily-live is where you'll grab the 10.04 disks from
[23:44] <Zinn> [cdimages.ubuntu.com] Index of /mythbuntu/daily-live
[23:45] <superm1> mrand is correct that today's (and earlier) have a bug w/ installer.  tomorrow and later should be sufficient
[23:45] <mrand> Thanks.
[23:58] <walm> Great, thanks for all your help guys!