> things to be changed (fix the installer not to guess wrong; fix the UI
First being as this is a MythTV list, and there are appropriate KnoppMyth lists lets clarify for all reading that the installer you are referring to is a part of KnoppMyth and not mythtv. > thinking last night that one way around the "slow delete" issues would > be to divvy up the recordings into, say, 100MB chunks, and then delete Another clarifying point, the ringerbuffer is NOT DELETED WHEN CHANGING CHANNELS. PEOPLE PLEASE STOP STOP STOP SAYING THIS. The ringerbuffer is ONLY deleted when you exit LiveTV. During channel changes myth merely seeks back to the start of the existing buffer. No deleting, no resizing, just jump back to the start and start writing. And of course this will change in the upcoming LiveTV changes. > (I say "MPEG-4 hardware" because I'm leery of loading up an Athlon > 2800+ with all of MPEG-4 software playback, at least one running That box could easily handle what you have describe here and playback an mpeg4 stream. Transcoding and commflagging "generally" happen on the backend, but of course you will have to seperate that work as you see fit based on your hardware. I don't see any reason that a 2800+ couldn't play a mpeg4 file while transcoding and commflagging in the background. > to how much computation I probably want to do -there-, too. Maybe I'm > being too conservative in what the hardware is capable of; I don't Those 250's will take about 2 or 3 % CPU max, in total for capture from all of them at the same time. The main load you have to consider is IO to your drives. Assuming you don't have DMA controller or bad drive issues then capture wont be any effort at all. I know one guy with 4 250's in a Celeron 350(and it does commflagging) without any troubles. > The 350 solution will certainly work, and it's simpler. But I'd be > psyched if I could instead use MPEG-4 to save space, assuming that the In recent months XV support has been added to the IVTV drivers to aid in the playback of regular non mpeg1/2 content which makes playing something like mpeg4 files over the 350 less of a problem. But that is a subject for the ivtv-dev list as they can better explain any hurdles or problems there. IMHO the 350 is not worth the money just to gain the hardware decoding unless you are VERY strapped for CPU. I've run side by side comparisons and the improvement is just not that great unless you have a really crappy videocard. Of course YMMV. > I can believe that, based on my experience so far. Unfortunately this comes down to users exposure to various software and platforms. Some users can install Myth for the very first time and have it up and running in 2 - 3 hours without a hitch. But if you have never been exposed to MySQL, never used any sort of capture card under Linux before, and in some cases never compiled anything manually then your time can increase greatly. Not just because of the ability to "fix" problems during install, but the ability to avoid them altogether. I don't disagree however that certain aspects of the settings menu layout can be streamlined and made more intuitive.
_______________________________________________ mythtv-users mailing list [email protected] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
