1. I see similar behaviour, which I think is "on demand" programming. I sometimes can see menu's that look like they are actively being clicked to select progams. I haven't yet found any stable in the clear programming, but I think it will only take time on my part. 2. A question: whenever atscscan actually discovers a signal I get the message "filter timeout". Is this an mpeg2 filter that is crashing when it tries to process the incoming signal? 3. Another question: for the few channels I have successfully "azap-ped" so far, the captured .mpg or .TS will crash mplayer after a short time (10 seconds of video)...same thing if I cat /dvr0 into mplayer. any ideas what is going on here? p.s. sorry for the bad html post, using a pc at work different setup. David Engel wrote: >On Tue, Aug 16, 2005 at 10:57:08AM -0400, Michael Krufky wrote: > > >>David, You must have missed the email that Mac sent rather recently, >> >> > >I saw it after I sent mine. > > > >>cable channels... I have discovered that this content is actually an >>ON-DEMAND session being watched by someone that must live somewhere >>nearby. I have even noticed the stream pause and rewind sometimes. It >>is possible that this is what you are seeing on these other channels. >> >> > >That could explain why I wasn't able to capture a little bit later on >a service that had just worked. One of the captures was of closing >credits. > > > >>>I'm not terribly optimistic, but I guess this warrants a more thorough >>>examination of every service I can detect. >>> >>> >>> >>Be optimistic... The driver is working for you. The only problem is >> >> > >Oh, I am optimistic the card and driver are working. What I'm not >optimistic about is my first choice for the Fusion card to record >digital cable without needing an STB. > >David > >
