On Sat, 17 Jan 2009, Patrick Boettcher wrote: > > Same here -- never experienced this ever in some four-ish years > > with one SkyStar2 of model long forgotten, with that card being > Using VDR or a single application (like kaffeine), you most likely don't see > the error anymore thanks to the work-around which is already in place. It is > resetting the streaming interface at the end of a streaming-session, ie. when > the pid-filter count is going from 1 to 0. This happens all the time with VDR > (and similar) when it is retuning. Okay, I've been using `dvbstream' standalone, also modified so that it and related utilities get an exclusive lock on the adapter (otherwise when I'd make a mistake, the second invocation of `dvbstream' would not only fail, but the first recording was also messed up, so less than useless). `scan' has also been used, although in my latest installation (including a 12-output multiswitch), the card I have has been unable to lock or to get error-free output from transponders at the ends of the frequency range -- this affects at Astra 19E2 the ORF transponders among others, and at 28E many of the Channel 4 family, while all other devices on the same multiswitch have no difficulties at even higher frequencies and can scan the entire range perfectly. I've also guessed this could be due to spiders taking up residence in the warm interior of the tuning circuits. Anyway, someday I'll replace this card with an -S2 or perhaps dual- hybrid- whatever is available later. > Now when you launch an application which is just requesting a pid and another > one which is tuning independently, you can fall easily in this problem. > PS: how to reproduce: > shell 1: $ tzap channel > shell 2: $ dvbtraffic > [lots of output that streaming is working] > shell 1: $ <C-c> > shell 1: $ tzap "channel2_which is on a different frequency" > shell 2: no output of dvbtraffic any longer... (problem) This lack-of-output is something that I've experienced with other cards (a dvb-usb DVB-T device), which I did not investigate further. If I remember rightly, and with a more recent kernel. Note that in my `dvbstream'-exclusively use of the SkyStar2, I have never seen the error message (since trimmed from the quoted original post). I'll see if I can reproduce this on my production machine once it's idle, or if my hacks might be involved, and report back about this... thanks barry bouwsma -- 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
