[09:07] meep =) [09:07] I'm confused -- mythbuntu 14.04.1 isos exist in http://cdimage.ubuntu.com/mythbuntu/releases/14.04/release/ *but* the page at http://www.mythbuntu.org/downloads seems to think 14.04 is latest. Whats' going on? [13:10] enyc: I'm mirroring them still [13:11] tgm4883: aha [13:12] tgm4883: so, they are correct/valid release, just the distribution is not automated // taking ages ? [13:18] Yep [13:18] tgm4883: does the same problem happen with 'most' ubuntu distributed images ?? hrrm [13:19] * enyc wondering to what extent mythbuntu is ''official'' ubuntu project, sharing resources, etc etc... (whatever that really means anyway!!) [13:19] I remember when backports.org was separate then became part of debian 'officially' ... [13:19] No. It doesn't usually happen with our either, but I was out of town during release [13:21] We are an official flavor, just like kubuntu [13:41] =) [14:32] tgm4883: thankyou for the helpfful answer,s anyway [14:32] enyc: it should be listed on the site now [14:33] I'm wondering, in 14.04[.1] how much 'automatic shut down when idle' and 'setwakeup' [for timed recording] systems work [14:34] does this still need much 'manual fiddling' or is there good support for this [14:34] IDK, I don't use either [14:35] I wonder, how well, a Hummingboard http://www.solid-run.com/products/hummingboard/ will work as a frontend with hdtv [14:36] probably not well [14:37] I'm not sure what the support on Linux is like for that GPU [14:37] minimally, you'd want the i2 [14:37] although I'm unsure if that is enough RAM [14:37] hrrm what support matters? [14:37] i (thought) XBMC etc. was a good low resource consumption etc. [14:38] the _backend_ (transcoding, etc.) needs the ram, i thought ... [14:38] transcoding is CPU intensive, but mostly transcoding isn't done anymore [14:38] what does a frontend need these days? [14:39] XBMC was optimized for the RPI, but that doesn't mean it will work well on this device [14:39] Then you need the ability to play back video smoothly [14:39] which is where video card support comes in [14:39] IDK, I just feel like 2GB ram for a FE is the sweet spot [14:40] That might be overkill though, mine has 16GB as it doubles as my gaming rig [14:40] also, I try to stick with x86 based hardware [14:40] but that's just me [14:42] I'm wondering, wrt X86 machines... the virtues of 'entirely separate backend, with low power ARM/x86/whatever frontends' vs. 'combined backend and frontend box', with frontends ... [14:43] well you can have a low power atom x86 frontend [14:43] that is what I ran for quite a while [14:44] what circumstances does XBMC on raspberry pi work well with? [14:44] is it non-hdtv 'basically' ?? [14:45] and... xbmc vs mythtv as a frontend ?? [14:46] I believe video plays back fine. It's browsing though the menu's and loading large lists of recordings/videos/artwork that is slow [14:57] now... for TV-recording *and* streaming to frontends (over gigabit ethernet) from DVB-T2 inputs... What do I need as a backend machine i wonder... it doesn't necessarially have to be a frontend too [14:58] but I want it to WoL and 'go to sleep when not needed' .... and be low power ... and not too costly =) [14:58] what about rainbows and unicorns too? [14:58] i wonder how CPU / IO etc. is impacted if you have many inputs/outputs at once and soforth [14:58] dont care about rainbows or unicorns =) [14:59] dvb 'recording' doesn't need transcoding... so ... puzzle =) [14:59] if DVB-T2 is anything like what we have here in the states, then it's mostly disk I/O you need to be worried about [14:59] granted, commercial flagging is CPU intensive, but you could disable that if you want [14:59] whereas ethernet and CPU load is (less) of issue ? [14:59] (you might be able to schedule it for late night too) [14:59] nodsnods [14:59] yea you are just writing the bits to disk [15:00] so depending on how many concurrent recordings you want to do [15:00] *and* streaming of other recordings to frontends at the same time [...] [15:01] yes, that too [15:01] for a base backend, you don't need much [15:01] I'm thinking that may be a more sensible way to go [15:01] make it like a NAS server as well, etc etc [15:01] low end modern CPU and an SSD should minimally work [15:02] even these ION etc. ?? hrrm [15:02] yea you could [15:02] again, commercial flagging would suffer [15:02] ooo interesting [15:02] ok [15:02] understood [15:03] and you would definitely want an SSD at that point [15:03] Personally, I wouldn't do it, but I like my commercial flagging [15:03] I had always thought recordings would be too much for SSD cost etc. [15:03] puzzle [15:03] recordings on spindles, MySQL DB on SSD [15:03] that makes more sense =) [15:04] do you just use separate mountpoints? [15:04] or are there more clever caching/disk-backed mechanisms to use that are more clever than that? [15:04] I've got my OS on the SSD (including DB) and then a mountpoint for my spinning disks for recordings [15:04] kk makes sense [15:04] you can be more clever with it if you want, but probably not worth it for mythtv [15:05] nodsnods [15:05] I wonder about my choices of disk / power ... one large, raid0 raid1, raid5 over 3 disks, hrrm ... =) [15:06] depends on how many disks you want, but raid is probably not necessary unless you are using it for redundancy [15:06] ive had too much trouble with iffy sectors, i like raid =) [15:06] you'll get write penalties on raid 5, might not be an issue depending on concurrent recordings [15:07] well raid0 isn't going to help you with iffy sectors [15:07] then theres the whole 'mini pci raid card vs linux md raid' etc etc =) [15:08] p.s. release list on http://www.mythbuntu.org/downloads could be corrected, it sayl 14.04 is current release still =) [15:08] outside my scope. At one point I just used my NAS as the backend [15:08] now I just use a single 1TB drive [15:08] kk [15:08] thankyou [15:09] yah, ithink more important thing is to have separate backup system that synchs backup etc etc [15:09] if its considered 'important' =) === dkeith___ is now known as dkeith