home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Development
General Development (no feature request here!)
TBS: CI/CAM support and other improvements
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="mm1352000" data-source="post: 1094235" data-attributes="member: 82144"><p>Yes, it is strange, and no unfortunately I don't have an answer.</p><p>If the failure were closer to the initial tuning I might suspect that we had to tell the driver to send the command at a different time in the tune process, or wait a bit longer after sending the command... or something like that. But 30+ seconds in... I have no explanation for that.</p><p></p><p></p><p>No, I don't think the driver is buggy because it seems to be able to cause the switch to change port successfully. It isn't clear that the driver is the cause of the problem that happens after that, so I don't want to start pointing fingers. Either way it would be definitely be worthwhile to contact TBS support and see what they can do for you.</p><p></p><p></p><p>I have a fair amount of head knowledge about DiSEqC, but only limited experience in practice. The one EMP Centauri 9x8 multiswitch I've owned has worked with every tuner I've tried it with... though effectively that is only a 2 port DiSEqC switch with a cascaded 22 kHz switch.</p><p></p><p></p><p>Updated patch attached. This one sends the command twice every time you tune.</p><p></p><p>Regards,</p><p>mm</p></blockquote><p></p>
[QUOTE="mm1352000, post: 1094235, member: 82144"] Yes, it is strange, and no unfortunately I don't have an answer. If the failure were closer to the initial tuning I might suspect that we had to tell the driver to send the command at a different time in the tune process, or wait a bit longer after sending the command... or something like that. But 30+ seconds in... I have no explanation for that. No, I don't think the driver is buggy because it seems to be able to cause the switch to change port successfully. It isn't clear that the driver is the cause of the problem that happens after that, so I don't want to start pointing fingers. Either way it would be definitely be worthwhile to contact TBS support and see what they can do for you. I have a fair amount of head knowledge about DiSEqC, but only limited experience in practice. The one EMP Centauri 9x8 multiswitch I've owned has worked with every tuner I've tried it with... though effectively that is only a 2 port DiSEqC switch with a cascaded 22 kHz switch. Updated patch attached. This one sends the command twice every time you tune. Regards, mm [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Development
General Development (no feature request here!)
TBS: CI/CAM support and other improvements
Contact us
RSS
Top
Bottom