On 25.10.2012 13:49, Morfsta wrote:
Hi Klaus,

I fixed the problem I had with rotorng, it was a problem with a YAVDR
patch and also your changes to ChannelMonitor.

What "ChannelMonitor"?
There is no such thing in VDR.

I'm trying to get my head around the VDR function
cDVBTuner::ExecuteDiseqc to try and remove the requirement for a patch
for VDR core in future.

If I would like to send a FE_DISEQC_SEND_MASTER_CMD from a plugin, how
would I write the code to do this from inside the plugin? Is this

cDvbTuner is local to dvbdevice.c, and cDvbTuner::ExecuteDiseqc() is private.
So I'm afraid you can't do this without a patch.


I am trying to setup a cDiseqc object but don't know how to build it
just to be able to send a raw command of type dvb_diseqc_master_cmd.

Any help you would be able to give me would be much appreciated and
would hopefully move this plugin forward. I'm not a C++ developer,
more a code hacker so please be gentle! ;-)

Many Thanks,


On Mon, Oct 15, 2012 at 9:29 AM, Morfsta <morf...@gmail.com> wrote:
On Fri, Oct 12, 2012 at 3:31 PM, Klaus Schmidinger
<klaus.schmidin...@tvdr.de> wrote:

I'm afraid I can't think of anything obvious.
Could you try using versions 1.7.13 thru 1.7.27 in turn to see
which version introduced the problem?

Thanks Klaus, I will dig into it.

I suspect it could be related to some changes in YAVDR but I will
build a vanilla VDR(s) at some stage and test it with that too.

vdr mailing list

Reply via email to