Reply to thread

Message

<blockquote data-quote="deeptho" data-source="post: 1145208" data-attributes="member: 215446">I did some experiments with my tbs6504 and found&nbsp; that&nbsp; the chip itself wronly reports the nature of the streams. The driver seems to do the right thing, but the result is wrong. neumoDVB changed over the years and did not care about the stream type in the past but now it does. Workarounds are possible to solve this problem, but the first thing to know is if GSE and GCE streams are actually supported by the si21832 based cards.So I tried crazyscan and ebspro under windows but neither of them seems to work with the card: the spectrum is completely constant, tuning does not work. ebspro freezes.&nbsp; This is not the most recent version, but also a not very old version of streamreader.Any suggestions on how to solve this (I will update the software of course).Or on what happens on non-transport streams (GSE, GS) under windiws with tbs6504 or tbs6522 on GSE and GCS transponders such as 52E 11245V. And what does it do with DVB multistreams such as those on 5.0W. In all cases: does it lock? What is reported about the details of the stream? Regarding the i2c problems: these seem to happen under very specific circumstances also on my card. I will need to investigate further. The workaround is now in the latest drivers. So canning will work again, but GSE and GCS streams will not be locked or wrongly reported astransport strewams. Note that this will be 2x slower than on tbs6903x and 8x slower than on tbs6909x. It will also be slower than crazyscan, because more information is extracted from the stream and each locked dvb mux then can take 30-60 seconds. Nothing can be done about that, except scanning multiple muxes in parallel if the hardware supports it</blockquote>

[QUOTE="deeptho, post: 1145208, member: 215446"] I did some experiments with my tbs6504 and found that the chip itself wronly reports the nature of the streams. The driver seems to do the right thing, but the result is wrong. neumoDVB changed over the years and did not care about the stream type in the past but now it does. Workarounds are possible to solve this problem, but the first thing to know is if GSE and GCE streams are actually supported by the si21832 based cards. So I tried crazyscan and ebspro under windows but neither of them seems to work with the card: the spectrum is completely constant, tuning does not work. ebspro freezes. This is not the most recent version, but also a not very old version of streamreader. Any suggestions on how to solve this (I will update the software of course). Or on what happens on non-transport streams (GSE, GS) under windiws with tbs6504 or tbs6522 on GSE and GCS transponders such as 52E 11245V. And what does it do with DVB multistreams such as those on 5.0W. In all cases: does it lock? What is reported about the details of the stream? Regarding the i2c problems: these seem to happen under very specific circumstances also on my card. I will need to investigate further. The workaround is now in the latest drivers. So canning will work again, but GSE and GCS streams will not be locked or wrongly reported as transport strewams. Note that this will be 2x slower than on tbs6903x and 8x slower than on tbs6909x. It will also be slower than crazyscan, because more information is extracted from the stream and each locked dvb mux then can take 30-60 seconds. Nothing can be done about that, except scanning multiple muxes in parallel if the hardware supports it [/QUOTE]

Verification