On Sun, Jan 25, 2009 at 5:32 PM, CityK <cityk@xxxxxxxxxx> wrote: > I haven't taken the opportunity to ever use Kaffeine for scanning OTA > just yet, however, I do note that it produces similar results for me, as > to what you observed, when I scan on digital cable using QAM256. In my > case, it repeatedly borks at 61%. I spoke with Mkrufky this morning > about Kaffeine's ATSC scanning abilities and he described it as being > less then favourable....this was actually a surprise to me, as I thought > that OTA scanning was fine. I know Devin added this support so perhaps > he could comment upon the capabilities. I also know that Devin does not > have cable, so I am not surprised to see, in my case, scans of digital > cable failing. Yeah, digital cable scanning is pretty much known to be broken in Kaffeine. None of the cable companies followed the recommendations in the ATSC a/63c standard since they rely on the OOB tuner to get channel information. I have some hacks that work around some of the issues, but none of them are upstream yet. As CityK pointed out, I do not have cable, so I have done very little testing in that environment. Regarding OTA, there are no outstanding bugs so it should be fine. There is *one* known issue which was fixed after 0.8.7 went out, but if you hit the issue (a timing bug), Kaffeine will crash. In other words, if you are just getting no channels found, then it's not that case. If you do have a case where OTA scanning in Kaffeine returns different results than w_scan or scan, I would be interested in hearing about it. Send me some email off-list and I will see if we can work through the issue. Regards, Devin -- Devin J. Heitmueller http://www.devinheitmueller.com AIM: devinheitmueller -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
