On Sun, Dec 25, 2011 at 12:17 PM, Mauro Carvalho Chehab <mchehab@xxxxxxxxxx> wrote: > That's said, the approach there assumes that just one mis can be filtered. I'm wandering > if it wouldn't be better to use the same approach taken inside dvb-core for PIP filtering. i'm not sure that i understand correctly what you mean, but i can't see way how to filter more that one mis stream at the same time, because their id is stored in the bbheader. so, even if we assume it's possible to send two ids for filtering to the hardware and then it outputs ts packets from both of them there is still no way to know which ts packet to which mis stream belongs, because the bbheader is stripped inside the demodulator before the data are outputted. in fact if you don't set any id for filtering to mis capable hardware then usually it outputs the ts packets from all of the streams and that's why the outputted stream looks corrupted, because it contains ts packets from all mis streams and that's why you what to set id for filtering to the hardware in the first place - to make it output ts packets just from one selected stream. however, if dvb-core has support for bbframes like the following unfortunately lost work: http://www.linuxtv.org/pipermail/linux-dvb/2007-December/022217.html then instead setting mis filtering in the hardware you can force it to output bbframes (at least currently all mis capable hardware is supposed to be able to output bbframes) and then filter all streams in the software, which would be significantly more flexible, because that way all streams can be filtered and used in the same time. -- 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
