Reply to thread

Message

<blockquote data-quote="mm1352000" data-source="post: 821367" data-attributes="member: 82144">Hi bluebearThanks for testing! <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite8" alt=":D" title="Big Grin&nbsp; &nbsp; :D" loading="lazy" data-shortname=":D" />Such issues are hard to track down since it is hard to conclusively prove that they are caused by a code problem. It could be tuner driver issues, signal, DiSEqC switch, intermittent interference...Have you tried temporarily testing with the switch removed to try to narrow down the problems?&nbsp;I think it is unlikely that this patch would cause those kinds of issues, however I guess anything is possible. For those kinds of issues it would be critical to have the TsReader logs from the client.They definitely do. You are the first person to test and confirm that DiSEqC works with the 6922. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />Now I'd really like to find the cause of the crashing!mm</blockquote>

[QUOTE="mm1352000, post: 821367, member: 82144"] Hi bluebear Thanks for testing! :thx: Such issues are hard to track down since it is hard to conclusively prove that they are caused by a code problem. It could be tuner driver issues, signal, DiSEqC switch, intermittent interference... Have you tried temporarily testing with the switch removed to try to narrow down the problems? I think it is unlikely that this patch would cause those kinds of issues, however I guess anything is possible. For those kinds of issues it would be critical to have the TsReader logs from the client. They definitely do. You are the first person to test and confirm that DiSEqC works with the 6922. :) Now I'd really like to find the cause of the crashing! mm [/QUOTE]

Verification