[00:17] KungFuJesus, yep [00:47] :( [01:49] I'm thinking of setting up a PVR (using mythbuntu). How powerful of a system do I need? [02:15] edbian: depends on your goals [02:15] HD or SD? [02:16] !developer% [02:16] Sorry I don't know about developer% [02:17] we have a page on the site with all the developer's hardware, but the site is down :( [02:17] my hardware is here: http://baablogic.net/drupal/node/13 [02:17] [baablogic.net] My MythTV Setup | www.baablogic.net [02:18] edbian: really all depends on how powerful you want to go, you could get away with an average desktop and something that can run VDPAU and continue to expand later [02:18] !VDPAU [02:18] http://www.mythtv.org/wiki/VDPAU [02:18] a common setup anymore is a backend out of site and a nice ION box sitting under your TV as a frontend [02:18] !frontend [02:18] Ion Boxes make a great frontend. http://www.baablogic.net/drupal/node/2 [02:18] have a look, yell if you have any questions, I'll be awol walking the dogs for a few minutes === Gibby_away is now known as Gibby === Gibby is now known as Gibby_away [06:32] Is there a site I should use to choose the best playback profile? I have this in my frontend: NV44 [GeForce 6200 TurboCache(TM)] [06:34] you could start with the profile that is selected by default and see how it goes [06:35] That was "Normal". I changed it to CPU++. Things are OK, but I don't know what kind of atrifacts or blips to attribute to the video card, the CPU, network, backend storage, etc... [06:36] I install Cacti to monitor the network traffic with SNMP. I think the network is well underutilized, even when playing HD [06:44] I take it VDPAU is the best to use if it works? [06:54] a 6200 would not be stunning performance and not capable of vdpau [06:55] A few minutes ago, I enabled vdpau and tested playback successfully... must not be using that, 'cause I don't see it on the list for any level of vdpau support. [07:09] I think 8500 and above, this machine I'm on is only 7900GT and not capable [08:45] PMantis, I think your VDPAU performance will also depend on the type of video stream being sent through it [13:41] wawwwww [13:41] ignore that [13:42] hey folks [13:42] any mythexport users? I'm looking for settings that work for the AppleTV and/or iPad - IE HD [13:43] currently everything exported shows up as zero K - so somethings not right [13:58] You might try, http://www.mythbuntu.org/wiki/mythexport-215, you didn't say what distro you're using. [13:59] thanks SteveGoodey know that page well, I'm using ubuntu 10.4 [13:59] No good eh? [13:59] think I found my problem - seems that explicitly setting -ac 2 helps [14:11] if my sound if very quite ... how would I go about increasing it. Is it something I need to address at the server? at the client? or at the client hardware? [14:15] Have you tried the hardware volume sliders? Also I believe the mythtv-setup has volume settings at about 75 percent as default. [14:16] yes i tried both of those [14:16] i didn't know if there was something i should consider in the backend [14:17] I have only used combined front/backend so can't help there, sorry. New Install/upgrade? [14:18] new install ... dedicated backend dedicated front end .. over wifi [14:19] Have you tried sound on the frontend outside of mythtv, xine/VLC mp3 file. Volume low with those? [14:19] thats a good idea -- no i haven't [14:20] that would give me a good control i suppose ... thanks [14:28] I've been watching TV for a little bit, testing this and it's ending with an error: Video frame buffering failed too many times [14:30] http://ubuntuforums.org/showthread.php?t=1316167 [14:30] [ubuntuforums.org] Video frame buffering failed too many times - mythbuntu 9.10 - Ubuntu Forums [14:31] thanks [14:32] Might be more clues in the logs, "how about the front end/back end log files and dmesg?" [14:34] i'm noticing that somewhere between 0.23.1+fixes26407-0ubuntu0+mythbuntu2 and 0.23.1+fixes26434-0ubuntu0+mythbuntu2 the cron.daily job got dropped from mythtv-backend. is this intentional? [14:36] SpaceBass: all good now? [14:36] rhpot1991, think so - thanks for asking! I'm doing an encode right now, will test once it is finished [14:36] Shred00: what did it do, the db optimizer? [14:37] filldatabase and optimize, yes [14:37] auto mythfilldatabase can be enabled in mythtv-setup [14:38] on to a different questions... [14:38] rhpot1991: yes, of course. but if one doesn't want to do it that way. [14:38] but more importantly, yes, the database optimize [14:38] anyone know how to make a job auto-run for every recording? IE default as on [14:39] SpaceBass: I normally enable it per recordings that I want [14:39] SpaceBass: might want to check the userjob page in mythtv-setup, general > page 10 or so [14:39] there are 2 user job pages, if it exists it should be in there [14:40] could check the recording profiles as well [14:41] thanks! I've not see in it in the setup options, I'll check recording profiles [14:42] Shred00: check the mysql tab in MCC [14:42] rhpot1991: i don't run MCC here [14:42] Shred00: that is what creates the optimize tables cronjob [14:43] hrm. why wouldn't that just be a default thing for any mythtv-database/backend machine to do rather than having to require a user to enable it? [14:43] Shred00: http://pastebin.com/5nefuWBs [14:43] paste that into your /etc/cron.daily [14:47] rhpot1991: i already have that in /usr/share/doc/mythtv-backend/contrib/maintenance/optimize_mythdb.pl so i'd really only need to add a call to that in my cron.daily. but my point here is not my particular installation (which i can fix easily) but the bigger picture. i wonder why it was removed from being the default for all installations to being something that somebody has to enable via the "MCC". === dkeith_ is now known as dkeith [14:48] Shred00: as far as I'm aware it has been that way for quite some time [14:49] rhpot1991: so my backups seem to reveal also. i just wonder what the motivation behind the change is. [14:49] is mythbuntu under an SCM that i could browse for a commit message perhaps? [14:50] Shred00: I'm not aware of it ever being included by default [14:50] yep on launchpad [14:51] https://code.launchpad.net/~mythbuntu/mythtv/mythtv-fixes [14:51] [code.launchpad.net] mythtv-fixes : Code : MythTV [14:56] rhpot1991: it must have been in 0.23.1+fixes26407-0ubuntu0+mythbuntu2: [14:56] ii mythtv-backend 0.23.1+fixes26407-0ubuntu0+mythbuntu2 A personal video recorder application (server) [14:56] $ dpkg -S /etc/cron.daily/mythtv-backend [14:56] mythtv-backend: /etc/cron.daily/mythtv-backend [14:57] optimize_mythdb.pl has been enabled in MCC for as long as I can remember [14:57] tgm4883: yep [14:58] it was definitly before 0.23.1 [15:01] yep, once upon a time I used to enable it by hand, that was before foxbuntu (I think) added it to MCC, which was quite some time ago [15:02] hrm. this is strange. debian/changelog says: [15:02] mythtv (0.20-svn20070122-0.0ubuntu2) feisty; urgency=low [15:02] ... [15:02] * Removed debian/mythtv-backend.cron.daily; the database fill must [15:02] happen from backend scheduler to take advantage of next-run hints. [15:02] yet my backend, on 0.23.1+fixes26407-0ubuntu0+mythbuntu2 still says /etc/cron.daily/mythtv-backed is coming from the mythtv-backend package [15:03] $ dpkg -L mythtv-backend | grep daily [15:03] /etc/cron.daily/mythtv-backend [15:05] Shred00: upgraded install? [15:05] rhpot1991: sure [15:06] Shred00: I'd venture its left over from the old days [15:06] rhpot1991: yeah, but the current 0.23.1-fixes package is reporting that file per the above dpkg -L output [15:06] that comment seems to indicate it was removed from code, debian.\/postinst would have to remove it to get it off of your system [15:06] woops debian/postinst [15:07] john@ultramagnus:/etc/cron.daily$ dpkg -L mythtv-backend | grep daily [15:07] john@ultramagnus:/etc/cron.daily$ [15:07] nothing for me [15:08] rhpot1991: indeed. so why is my installation reporting it? it's very strange. [15:08] Shred00: left over from a previous install, it will not remove it unless you remove the package, or we explicitly remove it in postinst [15:09] superm1: should this have been done? ^ [15:10] tbh, i have never used MCC on my mythbuntu installations. [15:10] is MCC an "on-screen" (i.e. on the TV) app? does it come up before the main mythtv menu or something? [15:12] Shred00: its an X application that should be found under the administration menu [15:12] outside of mythtv [15:12] Shred00: are you running mythbuntu or ubuntu + mythtv? [15:14] rhpot1991: it was installed as ubuntu a long time ago and then i added the required mythtv packages from mythbuntu and it's been upgraded through about half a dozen ubuntu releases since, so there never was an MCC on it. never been a need. [15:14] so if my mythtv installation is a stand-alone "set top box" type installation where it powers on and up to the mythtv screen (like any appliance should) how does MCC fit in? [15:15] Shred00: its pretty much only used in the setup phase [15:15] you use it to setup things like your remote [15:15] and then don't open it anymore [16:26] I'm having an issue with MythExport 2.1.5, on Mythbuntu 10.04 with 23.1 fixes. After starting the userjob, mythtranscode runs the lossless transcode to cut the commercials (i.e. -honorcutlist) and outputs to a .mpg.tmp file, once that completes the job shows as successful even though the ffmpeg portion of the job hasn't completed. The ffmpeg portion runs fine, but since this is a combined frontend/backend I'd like it to shut down [16:26] after its finished transcoding, with the userjob showing completed it would shut down while ffmpeg is still running. [16:28] silverdulcet: hmmm thats not gonna work too well [16:28] the userjob itself queues up a task for mythexport and then reports as completed [16:28] silverdulcet: do you have another backend? [16:28] or is this the only one? [16:29] silverdulcet: nope, just a single backend. [16:29] why are you shutting it down then, aren't you going to miss recordings? [16:29] rhpot1991: I use mythwelcome and acpi wakeup, it sets the rtc alarm to wakeup 5 min before the next recording. [16:31] silverdulcet: know perl at all? [16:31] rhpot1991: when I'm done using mythtv/queuing a transcode it exits to mythwelcome, then if it isn't recording/transcoding it will shutdown. [16:31] rhpot1991: no...;-( [16:32] so if the userjob remained open until everything was done, that would essentially fix the issue, right? [16:32] rhpot1991: exactly, it must remain open until ffmpeg completes.. [16:32] * rhpot1991 thinks about it for a little [16:33] rhpot1991: I assumed that was what mythexport did, but I guess its mostly designed for a backend running 24/7? [16:34] silverdulcet: ya I moved most of the code into a daemon so that it could do some of the other features like file maintenance [16:35] so all the userjob really does is makes a mysql entry that the daemon reads [16:37] which points to the name of the job configured in mythexport_settings.cfg [16:38] unfortunately the userjob doesn't know the resulting filename or we could just watch that [16:39] I'm thinking the easiest work around would be to have the userjob touch a file and the daemon delete it, then the userjob would complete once that file is gone [16:39] and in theory the backend should know that it has userjobs queue'd up and not shut down till they are all done [16:40] I'm worried about multiple instances though [16:41] 2 userjobs run, they each create a sql instance, mythexport starts running the first, deletes the file when its done, then starts running the 2nd [16:41] meanwhile the backend sees that both jobs completed and shuts down [16:42] perhaps mythnuv2mkv can give a clue? it assigns a job number to each transcode job queued. [16:43] I would like to still use that, but for some reason after upgrading to mythtv .23 I only get 3fps when doing an xvid transcode where I used to get 20-30. I still get 20fps when doing h264 mkv encodes. [16:44] silverdulcet: well part of the issue is that I can't push any new features into ubuntu until after the maverick release [16:44] so I'd like to give you a chunk of code you can place in your files to fix the issue for now and then tackle it at a later point [16:46] actually I could prob just reuse the id from the sql table and make a unique file which would work out well [16:46] * rhpot1991 is thinking out loud, don't mind [16:46] rhpot1991: well I'm willing to test it, until then I think I'll just do mythshutdown -l to lock the system from shutting down while I transcode things. [16:48] silverdulcet: shoot me an email, and I'll get you something to test when I get a chance [16:48] my irc nick @ubuntu.com [16:49] actually make a bug instead please: https://bugs.launchpad.net/ubuntu/+source/mythexport [16:49] [bugs.launchpad.net] Bugs : âmythexportâ package : Ubuntu [16:50] rhpot1991: ok [16:53] rhpot1991: it looks as if there already is one https://bugs.launchpad.net/ubuntu/+source/mythexport/+bug/596251 shall I add something to that? Its the exact issue I mentioned. [16:53] [bugs.launchpad.net] Bug #596251 in mythexport (Ubuntu): âmythexport reports start and finish of jobs at the same secondâ [17:21] silverdulcet: thanks [17:23] superm1: is mythbuntu in good shape to start testing for RC tomorrow? [17:34] Riddell, I have been running the testing releases for a long time with very very few problems. [17:34] But I have not done a fresh install since 10.04; so I cannot comment on any changes to the fresh install changes [17:35] well it's fresh installs that need tested [17:36] hehe yeah [18:06] Riddell, yes it's looking pretty good imo [18:06] the problems we had at beta should be cleaned up now [18:06] groovy, thanks superm1 [18:07] rhpot1991, it's a conffile, it would only stay if it was hand modified normally [18:07] if we still have that postinst code in place [18:08] superm1: figured so much, also this is the first we've heard about it and thats an old change [18:10] yeah [20:44] kees, can I bug you for about 5 minutes for a security question? [20:48] tgm4883: sure thing [20:50] kees, ok thanks, PM