Reply to thread

Message

<blockquote data-quote="mm1352000" data-source="post: 684585" data-attributes="member: 82144">Hi gibmanThank you for the comment!There is currently a very bad (in my opinion) hack in the code to try and support DiSEqC switching on Hauppauge cards. What it does is to:1. Try send DiSEqC command normally (before graph is running).2. Run graph.If DiSEqC command failed:3. Don't check for lock.4. Stop the graph.5. Tune again.I am aware through experience with my card that some cards require the DiSEqC commands to be sent *after* the graph is running. This is exactly why I even started making this patch - to support DiSEqC switching on my card which was not working unless the command was sent after the graph was started. MediaPortal currently sends the command *before* the graph is running and most cards seem to work okay. In fact there are probably some cards that require the commands to be sent at that time. Maybe some of the Hauppauge cards are like mine?We could try to take out the hack and do the following (for all cards - more robust):1. Try send DiSEqC command normally (before graph is running).2. Run graph.3. Before checking for lock, resend the DiSEqC command if the first command failed.Very easy to implement for switch control from within the ConditionalAccess class after my refactoring <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" />Not so easy to implement for motor control. Do you have a dish motor?</blockquote>

[QUOTE="mm1352000, post: 684585, member: 82144"] Hi gibman Thank you for the comment! There is currently a very bad (in my opinion) hack in the code to try and support DiSEqC switching on Hauppauge cards. What it does is to: 1. Try send DiSEqC command normally (before graph is running). 2. Run graph. If DiSEqC command failed: 3. Don't check for lock. 4. Stop the graph. 5. Tune again. I am aware through experience with my card that some cards require the DiSEqC commands to be sent [B]*after*[/B] the graph is running. This is exactly why I even started making this patch - to support DiSEqC switching on my card which was not working unless the command was sent after the graph was started. MediaPortal currently sends the command [B]*before*[/B] the graph is running and most cards seem to work okay. In fact there are probably some cards that require the commands to be sent at that time. Maybe some of the Hauppauge cards are like mine? We could try to take out the hack and do the following (for all cards - more robust): 1. Try send DiSEqC command normally (before graph is running). 2. Run graph. 3. Before checking for lock, resend the DiSEqC command if the first command failed. Very easy to implement for switch control from within the ConditionalAccess class after my refactoring :D Not so easy to implement for motor control. Do you have a dish motor? [/QUOTE]

Verification