Hi,
I haven't been able to make rotor plugin work with the multiproto
driver. I created dummy channel entries that have tone off (f 11700)
into beginning of each satellite position group in my channels.conf and
now zapping with rotor plugin by pressing ok and then and keys works
with 100%
On Friday 07 of March 2008, Seppo Ingalsuo wrote:
But as vdr illiterate I couldn't figure how to check if the zapped
source (diseqc-source?) is a new one to avoid generating unnecessary
DiSEqC traffic and delays, and wondered to get a global variable for
storing the previous position... help!
On Wednesday 05 of March 2008, Seppo Ingalsuo wrote:
I couldn't repeat that but I didn't find exactly that multiproto driver.
Hi,
I'm testing it with this one -
http://jusst.de/hg/multiproto/archive/4df151d5b3fe.tar.bz2.
I've only changed some print and debug options in my tests.
But I
Ales Jurik wrote:
My result is that the problem with stucked motor appears with new multiproto
driver. When I'm using multiproto from 21.12. no problem appears at all.
I couldn't repeat that but I didn't find exactly that multiproto driver.
But I noticed that zapping works reliably with
Hi,
Seppo Ingalsuo schrieb:
the attached patch replaces the previously released but
incomplete patch for VDR-1.5.14, which was part of my recent
rotor support patches.
You have to apply this patch after patching VDR-1.5.16 with
DVB-S2+H.264 support.
Do you get this error when
First, thanks for your vdr patches and all the work with xine-lib!
Reinhard Nissl wrote:
the attached patch replaces the previously released but
incomplete patch for VDR-1.5.14, which was part of my recent
rotor support patches.
You have to apply this patch after patching VDR-1.5.16 with
