Hi,
I am the maintainer of the rotorng source.
Firstly, congratulations on yavdr 0.5.0. It is the fastest, most pain free installation of VDR/YAVDR that I have ever completed - only 1-2 hours to totally rebuild my HTPC. The remote and sound worked out of the box on my system! Amazing!
However, as part of the upgrade from vdr-1.7.22 to 1.7.27 (both within my previous yavdr 0.4 installation using "apt-get upgrade" and from yavdr 0.4 - 0.5) the rotorng plugin has broken. This is shown in the syslog when I try to send a disecq command: -
vdr: [8287] ERROR: frontend 1/0: Invalid argument
Just to recap, the patch within YAVDR VDR source (opt-44_rotor.patch) adds another method to cDvbTuner: -
+bool cDvbTuner::SendDiseqcCmd(dvb_diseqc_master_cmd cmd)
+{
+ cMutexLock MutexLock(&mutex);
+ if ((frontendType!=SYS_DVBS2 && frontendType!=SYS_DVBS) 
SendDiseqc)
+ return false;
+ diseqc_cmd=cmd;
+ SendDiseqc=true;
+ newSet.Broadcast();
+ return true;
+}
and modifies cDvbTuner::GetFrontendStatus with: -
cMutexLock MutexLock(&mutex);
+ if (SendDiseqc) {
+ CHECK(ioctl(fd_frontend, FE_DISEQC_SEND_MASTER_CMD, &diseqc_cmd));
+ SendDiseqc=false;
+ }
Has anything changed in YAVDR, or perhaps the driver that means this no longer works the way that it used to? I've spoken to Klaus on the VDR mailing list and he can't think of anything in core VDR.
Previously we found that the dynamite plugin broke rotorng, but dynamite is still disabled in my setup.
Please let me know if there is anything I can do to debug this problem.
Regards
In May i noticed that the plugin was broken and mini73 offered his help to solve the problem. We did not found a quick solution back then.
