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