<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Thu, Aug 8, 2013 at 1:02 PM, Gary Buhrmaster <span dir="ltr"><<a href="mailto:gary.buhrmaster@gmail.com" target="_blank">gary.buhrmaster@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">> So please, don't abandon LiveTV--the changes our content providing overlords<br><div class="im">
> are making it a more, not less, desirable feature.<br>
<br>
</div>I have never heard anyone say "Abandon LiveTV" (although from time<br>
to time I have heard comments about it being a twisty maze of<br>
passages, all different, and C-4 might be an answer).<br>
<br>
Personally, if I cared about LiveTV, and it was not working, and I was<br>
unable to perform the necessary debugging(*), I would consider<br>
offering(**) the availability of a remote dedicated/isolated/performant<br>
development system that exhibits the failure with a long term<br>
availability commitment (like a few years). With 100% remote<br>
access (kvm with remote ISO support, root access, remote power<br>
cycle, etc. Perhaps a spiderduo as the kvm). Such remote<br>
development systems, if they were available in differing geographic<br>
regions, would actually be helpful for many cases where the current<br>
development process is iterative. If MythTV were a project run by<br>
a corporation, such remote systems would be an expected cost of<br>
doing business. Providing that type of system is probably a high<br>
barrier for most users, but that is the only way some of these<br>
(edge case) bugs are likely to be able to get resolved, should the<br>
devs find some more of that (ever more elusive) free time, and<br>
would, it seems to me, something that people with a different<br>
skill sets might be able to contribute to the community (not<br>
everyone can code C++, and not everyone can do good documentation,<br>
and not everyone could contribute a remote access system, but all<br>
those things can make the project better).<br></blockquote></div><br></div><div class="gmail_extra">Your description about the quality of the LiveTV code (as it has evolved, not blaming anyone for that) is why I framed my question the way I did. I've gotten this impression after reading the mailing list for years: There may still be issues there, for some people, that require a particular sequence of events only on certain configurations to trigger, but even after finding identifying them and opening a ticket, the only way to really fix things is, as you say, with C-4 and start from the ground up. I know the developers know this. I also realize that starting from the ground up is alot of work and why it hasn't and may never happen. Fine by me.<br>
<br></div><div class="gmail_extra">If I do start using LiveTV after updating to the pending 0.27, and its functionality were important to me, I'd certainly step up and help the developers however I could. Starting with figuring out how to get a backtrace capable version running on my Gentoo system (either my production setup or a debug chroot). Or even, as you suggest, remote access if that were helpful.<br>
<br></div><div class="gmail_extra">Another interesting (to me) quirk with past history of using LiveTV (under 0.23 and 0.24 both I think), back when my primary/only digital tuner was my Motorola DCT-6200 over firewire. I had to be careful, as watching LiveTV on my backend/frontend machine for more than a minute or so would cause it to spontaneously/randomly power down. I mean, what the heck?! Never happened watching recordings in progress from the STB. It was too scary (for the health of my setup) for me to attempt to seriously debug, but it left no obvious log info or core dump to figure out what was happening. Probably some weird kernel driver interaction, but I never tested it further to know whether, perhaps, it could also happen watching LiveTV on a remote frontend too. At any rate, not something to open a ticket about, not without some serious triage to rule out a hardware issue on my end. (And no, I have not noticed any other power supply issue with that machine before or since, but it does make one wonder.)<br>
<br></div><div class="gmail_extra">Before I had my HDHR Prime, I did try looking at the firewire tuner channel change code (yes, I realize firewire STB support will likely atrophy going forward, now that CableCard devices have made our life much easier and the FCC mandated FW support fades), as Comcast in my area moved to 4-digit channel numbers, but the built-in code only supports 3 digit tuning. Yes, I know there are external channel changing script hooks. If my Prime had not come along when it did at about the same time, I would have figured out how to fix that and offered a patch. I still might be interested, eventually, as I might want to make the STB the first priority tuner for LiveTV, and have access to all my channels.<br>
</div></div>