Reply to thread

Message

<blockquote data-quote="mm1352000" data-source="post: 1012720" data-attributes="member: 82144">If it works then it depends how it works. Some tuners only support DiSEqC 1.0 (4 port switches) and have no ability to send raw DiSEqC commands.&nbsp;Sure... but if we do it, it would probably be for the new TV engine.&nbsp;I agree. It is just as important to have good code to enable us to add support for new features quickly and to avoid creating bugs.&nbsp;I'm sorry, if DiSEqC does not already work then I can't provide any guarantee that we will do this. As I have found in the past, it is not just the 1.4 release that must be supported. We are always asked to support the next release, and the next release, and the next release (including alpha, beta, release candidate, final, x.x.1, x.x.2...) and that this a lot of work. We want to focus on the new TV engine where we can quickly add support, not on supplying patches for the current engine which may require nasty hacks.</blockquote>

[QUOTE="mm1352000, post: 1012720, member: 82144"] If it works then it depends how it works. Some tuners only support DiSEqC 1.0 (4 port switches) and have no ability to send raw DiSEqC commands. Sure... but if we do it, it would probably be for the new TV engine. I agree. It is just as important to have good code to enable us to add support for new features quickly and to avoid creating bugs. I'm sorry, if DiSEqC does not already work then I can't provide any guarantee that we will do this. As I have found in the past, it is not just the 1.4 release that must be supported. We are always asked to support the next release, and the next release, and the next release (including alpha, beta, release candidate, final, x.x.1, x.x.2...) and that this a lot of work. We want to focus on the new TV engine where we can quickly add support, not on supplying patches for the current engine which may require nasty hacks. [/QUOTE]

Verification