Re: [vdr] Rotor plugin source?
I haven't tried the patch, just the plugin. The plugin had some nice features that where handy. My rotor isn't even active now. Needs to be realigned after replacing a limit switch and I never have much secess aligning it. That and there is so little FTA in the US on small dish. Hardly worth the effort. On 2/12/2013 11:29 PM, Teemu Suikki wrote: Hi, thanks alot! This works very well! Also I think my section handler delay patch is not necessary with this gotoxx patch.. At least my delay message appears much later now, so the delay is already in the gotox handling. This GotoX patch is so cleanly integrated to VDR, I think it should be included in the official release? I think all current diseqc motors have gotox functionality, so plugins like rotor(ng) are really unnecessary if gotox works. -- Teemu 2013/2/12 Ales Jurik aju...@quick.cz mailto:aju...@quick.cz On 02/12/2013 12:17 PM, Teemu Suikki wrote: Hi! I was trying to find source code for the rotor plugin (not rotorng).. all the links seem to be outdated. Anyone have any version? I'm really only interested in seeing how the GotoX stuff works. I'm trying to send gotox command from diseqc.conf, but the dish doesn't move at all. I have the Eutelsat diseqc 1.2 specification, but the GotoX stuff is marked preliminary and they talk only about terrestrial antennas.. Must be some difference. Here's my non-functioning diseqc.conf entry: #S1.0W - Elevation 17.44, Azimuth 209.62, Motor angle -28.45 S1.0W 11700 V 9750 t W15 [E0 31 6E 0D 07] W15 v t S1.0W 9 V 10600 t W15 [E0 31 6E 0D 07] W15 v T S1.0W 11700 H 9750 t W15 [E0 31 6E 0D 07] W15 V t S1.0W 9 H 10600 t W15 [E0 31 6E 0D 07] W15 V T I actually made a C program that generates these lines for all visible satellites. This might be of interest to people who are waiting for gotox support, if I ever get this working.. _ vdr mailing list vdr@linuxtv.org mailto:vdr@linuxtv.org http://www.linuxtv.org/cgi-__bin/mailman/listinfo/vdr http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr Hi Teemu, I'm using the patch based on patch from Seppo Ingalsuo (see http://patchwork.linuxtv.org/__patch/12911/ http://patchwork.linuxtv.org/patch/12911/) - this version I'm used now with vdr-1.7.27 together with yaVDR, but have info that it works also with later versions. Patch integrate gotoxx into VDR and works without problems. Regards, Ales _ vdr mailing list vdr@linuxtv.org mailto:vdr@linuxtv.org http://www.linuxtv.org/cgi-__bin/mailman/listinfo/vdr http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr -- Teemu Suikki http://www.z-power.fi/ ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Rotor plugin source?
Hi! I was trying to find source code for the rotor plugin (not rotorng).. all the links seem to be outdated. Anyone have any version? I'm really only interested in seeing how the GotoX stuff works. I'm trying to send gotox command from diseqc.conf, but the dish doesn't move at all. I have the Eutelsat diseqc 1.2 specification, but the GotoX stuff is marked preliminary and they talk only about terrestrial antennas.. Must be some difference. Here's my non-functioning diseqc.conf entry: #S1.0W - Elevation 17.44, Azimuth 209.62, Motor angle -28.45 S1.0W 11700 V 9750 t W15 [E0 31 6E 0D 07] W15 v t S1.0W 9 V 10600 t W15 [E0 31 6E 0D 07] W15 v T S1.0W 11700 H 9750 t W15 [E0 31 6E 0D 07] W15 V t S1.0W 9 H 10600 t W15 [E0 31 6E 0D 07] W15 V T I actually made a C program that generates these lines for all visible satellites. This might be of interest to people who are waiting for gotox support, if I ever get this working.. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Rotor plugin source?
On 02/12/2013 12:17 PM, Teemu Suikki wrote: Hi! I was trying to find source code for the rotor plugin (not rotorng).. all the links seem to be outdated. Anyone have any version? I'm really only interested in seeing how the GotoX stuff works. I'm trying to send gotox command from diseqc.conf, but the dish doesn't move at all. I have the Eutelsat diseqc 1.2 specification, but the GotoX stuff is marked preliminary and they talk only about terrestrial antennas.. Must be some difference. Here's my non-functioning diseqc.conf entry: #S1.0W - Elevation 17.44, Azimuth 209.62, Motor angle -28.45 S1.0W 11700 V 9750 t W15 [E0 31 6E 0D 07] W15 v t S1.0W 9 V 10600 t W15 [E0 31 6E 0D 07] W15 v T S1.0W 11700 H 9750 t W15 [E0 31 6E 0D 07] W15 V t S1.0W 9 H 10600 t W15 [E0 31 6E 0D 07] W15 V T I actually made a C program that generates these lines for all visible satellites. This might be of interest to people who are waiting for gotox support, if I ever get this working.. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr Hi Teemu, I'm using the patch based on patch from Seppo Ingalsuo (see http://patchwork.linuxtv.org/patch/12911/) - this version I'm used now with vdr-1.7.27 together with yaVDR, but have info that it works also with later versions. Patch integrate gotoxx into VDR and works without problems. Regards, Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Rotor plugin source?
Hi, thanks alot! This works very well! Also I think my section handler delay patch is not necessary with this gotoxx patch.. At least my delay message appears much later now, so the delay is already in the gotox handling. This GotoX patch is so cleanly integrated to VDR, I think it should be included in the official release? I think all current diseqc motors have gotox functionality, so plugins like rotor(ng) are really unnecessary if gotox works. -- Teemu 2013/2/12 Ales Jurik aju...@quick.cz On 02/12/2013 12:17 PM, Teemu Suikki wrote: Hi! I was trying to find source code for the rotor plugin (not rotorng).. all the links seem to be outdated. Anyone have any version? I'm really only interested in seeing how the GotoX stuff works. I'm trying to send gotox command from diseqc.conf, but the dish doesn't move at all. I have the Eutelsat diseqc 1.2 specification, but the GotoX stuff is marked preliminary and they talk only about terrestrial antennas.. Must be some difference. Here's my non-functioning diseqc.conf entry: #S1.0W - Elevation 17.44, Azimuth 209.62, Motor angle -28.45 S1.0W 11700 V 9750 t W15 [E0 31 6E 0D 07] W15 v t S1.0W 9 V 10600 t W15 [E0 31 6E 0D 07] W15 v T S1.0W 11700 H 9750 t W15 [E0 31 6E 0D 07] W15 V t S1.0W 9 H 10600 t W15 [E0 31 6E 0D 07] W15 V T I actually made a C program that generates these lines for all visible satellites. This might be of interest to people who are waiting for gotox support, if I ever get this working.. __**_ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-**bin/mailman/listinfo/vdrhttp://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr Hi Teemu, I'm using the patch based on patch from Seppo Ingalsuo (see http://patchwork.linuxtv.org/**patch/12911/http://patchwork.linuxtv.org/patch/12911/) - this version I'm used now with vdr-1.7.27 together with yaVDR, but have info that it works also with later versions. Patch integrate gotoxx into VDR and works without problems. Regards, Ales __**_ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-**bin/mailman/listinfo/vdrhttp://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr -- Teemu Suikki http://www.z-power.fi/ ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Rotor / Rotor-NG not working with latest VDR
On Sun, Dec 25, 2011 at 12:32 PM, ilia mane ilmim...@gmail.com wrote: Thank you Lars Hanisch it work for me.I just disable the dynamite plugin in /etc/vdr/plugins/order.conf and the rotorng plugin work now. Just returned from the Christmas period, merry Christmas all! Then it looks like dynamite is the problem. Rotorng has a setup option for the satellite adapter that is connected to the rotor and normally it is set to 1,2,3 etc depending on the allocated adapter # at boot up. I guess this might now change with this virtual proxy for the adapter that is setup by dynamite? How is this handled, for example by femon or other plugins that need to communicate with the required physical adapter #? Thanks, Morfsta ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Rotor / Rotor-NG not working with latest VDR
Hi,
Am 03.01.2012 11:43, schrieb Morfsta:
On Sun, Dec 25, 2011 at 12:32 PM, ilia maneilmim...@gmail.com wrote:
Thank you Lars Hanisch it work for me.I just disable the dynamite plugin in
/etc/vdr/plugins/order.conf and the rotorng plugin work now.
Just returned from the Christmas period, merry Christmas all!
Then it looks like dynamite is the problem. Rotorng has a setup option
for the satellite adapter that is connected to the rotor and normally
it is set to 1,2,3 etc depending on the allocated adapter # at boot
up. I guess this might now change with this virtual proxy for the
adapter that is setup by dynamite?
How is this handled, for example by femon or other plugins that need
to communicate with the required physical adapter #?
A quick grep in the femon sources shows me, that femon opens the frontend on its own. It will use the device's
CardIndex() as adapter number and will always open frontend0 (which will break even without dynamite on
multi-frontend-devices). For now dynamite will not guarantee that adpater #0 will have cardindex #0. If you want to
correlate the shown info to your devices, you'll have to look in the dynamite settings - list all devices (or use the
SVDRP command plug dynamite lstd).
It is possible to assign adapters to specific cardindices with the udev environment variable dynamite_cardindex. But
one should use this on all adapters since the logic behind this is not so smart to first attach all devices with a set
cardindex and then all others.
I think it might be a good idea if dynamite will use the adapter number as a
hint for the cardindex.
I can imagine these things, that will lead to problems with dynamite:
- new virtual functions in cDevice or cDvbDevice: they have to be patched into dynamite's cDynamicDevice so it can
forward calls to its subdevice
- new non-virtual member functions in cDevice/cDvbDevice: for every method it has to be evaluated if the parent's or
subdevice's value has to be return (e.g. CardIndex, DeviceNumber, PatPmtParser, CamSlot etc.). It depends from where
and in which context these functions are called (has the caller a pointer to a subdevice like a call from within
cDvbDevice - has it a pointer from the cDevice::device array which will point to the parent device etc.).
- dynamic_castcDeviceSubclass (like it is used with the new device bonding feature): plugins won't get the real
device like cDvbDevice or similar. It will always be a cDynamicDevice.
rotorng adds one new virtual function to cDevice: SendDiseqcCmd
In yavdr this is included in the dynamite plugin (as nm -d
/usr/lib/vdr/plugins/libvdr-dynamite.so.1.7.22 confirms).
When I look at the cDevice-functions rotorng is using I don't see anything which will lead to problems. Maybe it's
just a cardindex mismatch?
There are two ways to test this (after reactivating dynamite with an * in /etc/vdr/plugins/order.conf, which will
ensure that dynamite loads as the last plugin):
1. The fast way: Detach all devices from vdr with svdrpsend plug dynamite
dtad
Reattach them in the right order with svdrpsend plug dynamite attd
/dev/dvb/adapter0/frontend0 etc.
2. The other way: Add a udev rule to your system that will assign every
frontend a cardindex, it may look like:
ACTION==add, SUBSYSTEM==dvb, ENV{DVB_DEVICE_TYPE}==frontend,
ENV{dynamite_cardindex}=%E{DVB_ADAPTER_NUM}
Reload the modules and restart vdr. This assumes you have no card with
multiple frontends.
Thanks,
Lars.
Thanks,
Morfsta
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Rotor / Rotor-NG not working with latest VDR
Thank you Lars Hanisch it work for me.I just disable the dynamite plugin in /etc/vdr/plugins/order.conf and the rotorng plugin work now. On Sat, Dec 24, 2011 at 10:59 AM, Lars Hanisch d...@flensrocker.de wrote: Hi, Am 23.12.2011 20:07, schrieb Morfsta: Please install the latest updates with: $ sudo apt-get update $ sudo apt-get dist-upgrade There was an error in the vdr-plugin dynamite's Makefile. Hi there, Thanks for your help, but the rotor / rotorng plugins still don't work after the update. Any other ideas? I don't see a dynamite related problem after a quick look over the source of the plugins in the yaVDR PPA. The vdr-patch adds a new method to cDevice and dynamite is aware of it. Please take a look at 'nm -D /usr/lib/vdr/plugins/libvdr-**dynamite.so.1.7.21' if there's a symbol cDynamicDevice::SendDiseqcCmd. If you'r familiar with build debs you can try to rebuild vdr with some logmessages in the SendDiseqcCmd methods of dvbdevice.c to see if there are really sent. I have only DVB-C and can't really test it. Some words to dynamite, a core functionallity of yaVDR: It creates devices between vdr and the real devices like a proxy passing all virtual methods to its subdevice. This makes it possible to start vdr with a lot of dummy devices (not to mix with the plugin) and attach the dvbdevices when they are created, e.g. if they get plugged in via USB. Also dynamite is able to set unused devices to an idle state, which means that it closes all its filehandles including the frontend. Please look in /etc/vdr/plugins/plugin.**dynamite.conf if an idle-timeout is specified. dynamite is running in the yavdr team for months and hasn't shown many problems. But I don't think that anyone of us has tested it with rotor(ng). And take a look at the dynamite repository. There are patches for other plugins which need to be patched. I hope we can get rotor back to work again! If you have dvb hardware, which initialises fast on boot (like PCI/PCIe devices) you can try to disable dynamite in the /etc/vdr/plugins/order.conf, just insert a minus before it. But be aware to insert a * if you want to use it again, since this is needed to asure that dynamite is the last plugin that gets loaded. Regards, Lars. Kind Regards, Morfsta __**_ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-**bin/mailman/listinfo/vdrhttp://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr __**_ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-**bin/mailman/listinfo/vdrhttp://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Rotor / Rotor-NG not working with latest VDR
Hi, Am 23.12.2011 20:07, schrieb Morfsta: Please install the latest updates with: $ sudo apt-get update $ sudo apt-get dist-upgrade There was an error in the vdr-plugin dynamite's Makefile. Hi there, Thanks for your help, but the rotor / rotorng plugins still don't work after the update. Any other ideas? I don't see a dynamite related problem after a quick look over the source of the plugins in the yaVDR PPA. The vdr-patch adds a new method to cDevice and dynamite is aware of it. Please take a look at 'nm -D /usr/lib/vdr/plugins/libvdr-dynamite.so.1.7.21' if there's a symbol cDynamicDevice::SendDiseqcCmd. If you'r familiar with build debs you can try to rebuild vdr with some logmessages in the SendDiseqcCmd methods of dvbdevice.c to see if there are really sent. I have only DVB-C and can't really test it. Some words to dynamite, a core functionallity of yaVDR: It creates devices between vdr and the real devices like a proxy passing all virtual methods to its subdevice. This makes it possible to start vdr with a lot of dummy devices (not to mix with the plugin) and attach the dvbdevices when they are created, e.g. if they get plugged in via USB. Also dynamite is able to set unused devices to an idle state, which means that it closes all its filehandles including the frontend. Please look in /etc/vdr/plugins/plugin.dynamite.conf if an idle-timeout is specified. dynamite is running in the yavdr team for months and hasn't shown many problems. But I don't think that anyone of us has tested it with rotor(ng). And take a look at the dynamite repository. There are patches for other plugins which need to be patched. I hope we can get rotor back to work again! If you have dvb hardware, which initialises fast on boot (like PCI/PCIe devices) you can try to disable dynamite in the /etc/vdr/plugins/order.conf, just insert a minus before it. But be aware to insert a * if you want to use it again, since this is needed to asure that dynamite is the last plugin that gets loaded. Regards, Lars. Kind Regards, Morfsta ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Rotor / Rotor-NG not working with latest VDR
Please install the latest updates with: $ sudo apt-get update $ sudo apt-get dist-upgrade There was an error in the vdr-plugin dynamite's Makefile. Hi there, Thanks for your help, but the rotor / rotorng plugins still don't work after the update. Any other ideas? Kind Regards, Morfsta ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Rotor / Rotor-NG not working with latest VDR
Hi, That may be. Have you installed the latest updates? # sudo apt-get update # sudo apt-get dist-upgrade There should at least be an update for vdr-plugin-dynamite. Sorry, I don't use yavdr. Rotorng works fine for me with the last 1.7.22 and the previous versions. The version 22 is patched only with rotor patch. The 21 with rotor+lnbsharing patches Regards, Jan ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Rotor / Rotor-NG not working with latest VDR
Hi, Am 20.12.2011 09:49, schrieb Morfsta: I have just upgraded my VDR system to yavdr 0.4.0 which uses VDR 1.7.21 and I notice that the Rotor plugin and my own Rotor-ng plugin no longer drive the rotor using any of the functions in the menu. Is anyone else seeing this too? I think that this could be because of recent changes to disecq handling code within VDR as part of the Unicable update. Klaus could you point me in the direction of what might have changed such that these plugins no longer work and I will do my best to implement a fix. Thanks very much for your help, Please install the latest updates with: $ sudo apt-get update $ sudo apt-get dist-upgrade There was an error in the vdr-plugin dynamite's Makefile. Thanks, Lars. Regards, Morfsta ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Rotor / Rotor-NG not working with latest VDR
I think the problem is YaVDR.
Rotorng work whit both vdr-1.7.21/22 (whit patch).
There are only same problem with low/no signal!
The old-rotor not compile for me.
kind regards,
Jan23
diff -ruN 1.7.22//device.h 1.7.22a//device.h
--- 1.7.22//device.h 2011-12-04 14:38:17.0 +0100
+++ 1.7.22a//device.h 2011-12-05 21:17:36.77513 +0100
@@ -24,6 +24,8 @@
#include spu.h
#include thread.h
#include tools.h
+#include asm/types.h
+#include linux/dvb/frontend.h
#define MAXDEVICES 16 // the maximum number of devices in the system
#define MAXPIDHANDLES 64 // the maximum number of different PIDs per device
@@ -324,7 +325,7 @@
virtual bool HasProgramme(void);
/// Returns true if the device is currently showing any programme to
/// the user, either through replaying or live.
-
+ virtual bool SendDiseqcCmd(dvb_diseqc_master_cmd cmd) {return false;}
// PID handle facilities
private:
diff -ruN 1.7.22/dvbdevice.c 1.7.22a/dvbdevice.c
--- 1.7.22/dvbdevice.c 2011-12-03 16:24:27.0 +0100
+++ 1.7.22a/dvbdevice.c 2011-12-08 22:13:44.04113 +0100
@@ -261,6 +261,7 @@
private:
static cMutex bondMutex;
enum eTunerStatus { tsIdle, tsSet, tsTuned, tsLocked };
+ bool SendDiseqc;
const cDvbDevice *device;
int fd_frontend;
int adapter, frontend;
@@ -276,6 +277,7 @@
cMutex mutex;
cCondVar locked;
cCondVar newSet;
+ dvb_diseqc_master_cmd diseqc_cmd;
cDvbTuner *bondedTuner;
bool bondedMaster;
bool bondedMasterFailed;
@@ -297,6 +299,7 @@
uint32_t SubsystemId(void) const { return subsystemId; }
bool IsTunedTo(const cChannel *Channel) const;
void SetChannel(const cChannel *Channel);
+ bool SendDiseqcCmd(dvb_diseqc_master_cmd cmd);
bool Locked(int TimeoutMs = 0);
int GetSignalStrength(void) const;
int GetSignalQuality(void) const;
@@ -308,6 +311,7 @@
{
device = Device;
fd_frontend = Fd_Frontend;
+ SendDiseqc=false;
adapter = Adapter;
frontend = Frontend;
frontendType = FrontendType;
@@ -813,6 +817,10 @@
if (GetFrontendStatus(NewStatus))
Status = NewStatus;
cMutexLock MutexLock(mutex);
+if (SendDiseqc) {
+ CHECK(ioctl(fd_frontend, FE_DISEQC_SEND_MASTER_CMD, diseqc_cmd));
+ SendDiseqc=false;
+ }
switch (tunerStatus) {
case tsIdle:
break;
@@ -867,6 +875,17 @@
}
}
+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;
+}
+
// --- cDvbSourceParam ---
class cDvbSourceParam : public cSourceParam {
@@ -1415,6 +1434,11 @@
return dvbTuner ? dvbTuner-Locked(TimeoutMs) : false;
}
+bool cDvbDevice::SendDiseqcCmd(dvb_diseqc_master_cmd cmd)
+{
+ return dvbTuner-SendDiseqcCmd(cmd);
+}
+
void cDvbDevice::SetTransferModeForDolbyDigital(int Mode)
{
setTransferModeForDolbyDigital = Mode;
diff -ruN 1.7.22//dvbdevice.h 1.7.22a//dvbdevice.h
--- 1.7.22//dvbdevice.h 2011-12-04 14:38:17.0 +0100
+++ 1.7.22a//dvbdevice.h 2011-12-05 21:17:36.75513 +0100
@@ -181,6 +181,7 @@
virtual bool SetChannelDevice(const cChannel *Channel, bool LiveView);
public:
virtual bool HasLock(int TimeoutMs = 0);
+ virtual bool SendDiseqcCmd(dvb_diseqc_master_cmd cmd);
// PID handle facilities
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Rotor / Rotor-NG not working with latest VDR
Hi, Am 21.12.2011 22:12, schrieb jan med: I think the problem is YaVDR. Rotorng work whit both vdr-1.7.21/22 (whit patch). There are only same problem with low/no signal! The old-rotor not compile for me. That may be. Have you installed the latest updates? # sudo apt-get update # sudo apt-get dist-upgrade There should at least be an update for vdr-plugin-dynamite. Regards, Lars. kind regards, Jan23 ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Rotor / Rotor-NG not working with latest VDR
Hi, I have just upgraded my VDR system to yavdr 0.4.0 which uses VDR 1.7.21 and I notice that the Rotor plugin and my own Rotor-ng plugin no longer drive the rotor using any of the functions in the menu. Is anyone else seeing this too? I think that this could be because of recent changes to disecq handling code within VDR as part of the Unicable update. Klaus could you point me in the direction of what might have changed such that these plugins no longer work and I will do my best to implement a fix. Thanks very much for your help, Regards, Morfsta ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Rotor / Rotor-NG not working with latest VDR
On 12/20/11 09:49, Morfsta wrote: Hi, I have just upgraded my VDR system to yavdr 0.4.0 which uses VDR 1.7.21 and I notice that the Rotor plugin and my own Rotor-ng plugin no longer drive the rotor using any of the functions in the menu. Is anyone else seeing this too? I think that this could be because of recent changes to disecq handling code within VDR as part of the Unicable update. Klaus could you point me in the direction of what might have changed such that these plugins no longer work and I will do my best to implement a fix. Thanks very much for your help, Regards, Morfsta ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr Hi Morfsta, I also had to implement changes into Seppo patch for gotoxx - so maybe you could take a look into the latest version of gotoxx patch for 1.7.22, it is working without problems, hope it helps. You could find the patch at http://www.linuxtv.org/pipermail/vdr/2011-December/025511.html Best Regards, Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Rotor / Rotor-NG not working with latest VDR
On 20.12.2011 09:49, Morfsta wrote: Hi, I have just upgraded my VDR system to yavdr 0.4.0 which uses VDR 1.7.21 and I notice that the Rotor plugin and my own Rotor-ng plugin no longer drive the rotor using any of the functions in the menu. Is anyone else seeing this too? I think that this could be because of recent changes to disecq handling code within VDR as part of the Unicable update. Klaus could you point me in the direction of what might have changed such that these plugins no longer work and I will do my best to implement a fix. I don't see what could have changed in version 1.7.21 that might have an impact on this. Satellite Channel Routing (SCR) and Device Bonding (unicable) were implemented in later versions. Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Rotor / Rotor-NG not working with latest VDR
On Tue, Dec 20, 2011 at 9:23 AM, Klaus Schmidinger klaus.schmidin...@tvdr.de wrote: On 20.12.2011 09:49, Morfsta wrote: I don't see what could have changed in version 1.7.21 that might have an impact on this. Satellite Channel Routing (SCR) and Device Bonding (unicable) were implemented in later versions. I think the yavdr VDR distribution has the Unicable patch applied to 1.7.21, there is an option log LNB usage in the LNB menu and there is a # Unicable set of entries in the disecq.conf file. The rotor and rotorng plugin use: - if (ActuatorDevice-SendDiseqcCmd(switch_cmds[KNr])) to send the disecq sequence to move the rotor where KNr is the device number with the rotor atached. Has this means to send the disecqc command now changed as part of unicable support both in core VDR 1.7.21 and as part of the patch? Kind Regards, Morfsta ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Rotor / Rotor-NG not working with latest VDR
On Tue, Dec 20, 2011 at 9:20 AM, Ales Jurik aju...@quick.cz wrote: I also had to implement changes into Seppo patch for gotoxx - so maybe you could take a look into the latest version of gotoxx patch for 1.7.22, it is working without problems, hope it helps. You could find the patch at http://www.linuxtv.org/pipermail/vdr/2011-December/025511.html I don't know the previous patch, what did you have to change? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Rotor / Rotor-NG not working with latest VDR
On 12/20/11 21:51, Morfsta wrote: On Tue, Dec 20, 2011 at 9:20 AM, Ales Jurik aju...@quick.cz wrote: I also had to implement changes into Seppo patch for gotoxx - so maybe you could take a look into the latest version of gotoxx patch for 1.7.22, it is working without problems, hope it helps. You could find the patch at http://www.linuxtv.org/pipermail/vdr/2011-December/025511.html I don't know the previous patch, what did you have to change? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr The previous version you could find at http://www.linuxtv.org/pipermail/vdr/2011-January/024430.html. I'm not personally sure whether it was working with 1.7.21, but I've heard that it was. I've personally used it with 1.7.16 and 1.7.18. Regards, Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] rotor-ng
Excellent news! I am sure the entire rotor vdr community will be very glad to hear that! At the moment I use diseqc.conf with goto position commands for each sat position to move the dish With rotor-ng does diseqc use have to be switched off in vdr and the plugin takes care of everything or does it parse diseqc.conf? Message: 1 Date: Mon, 21 Mar 2011 23:15:11 + From: Morfstamorf...@gmail.com Subject: Re: [vdr] rotor-ng in development [was [ANNOUNCE] vdr-actuator-1.2.0 plugin] To: VDR Mailing Listvdr@linuxtv.org Message-ID: aanlktimupe+jotg9j9v3pn5qg4iojvg9_v8-m0zes...@mail.gmail.com Content-Type: text/plain; charset=ISO-8859-1 On Sun, Mar 20, 2011 at 10:08 PM, Timothy D. Lenztl...@vorgon.com wrote: I only have a Nexus-s for sat card and right now my rotor alignment is all screwed up. Relays went bad and had to replace them. I left the rotor elevation setting untouched but now it over shoots more and more the farther it goes as if the elevation is wrong. Haven't had time to look into it. Well, it seems I found the problem. The HAUPPAUGE NOVA-S2-HD card (HVR4000 lite / CX24116 frontend) won't lock onto DVB-S2 channels with FEC_AUTO or ROLLOFF_AUTO set. So, I modified the plugin to allow selectable values for FEC and ROLLOFF and now it works fine. I can now lock and scan DVB-S and DVB-S2 channels (QPSK and 8PSK) directly from the plugin menu and move the dish to find and store satellites with diseqc and signal strength meter. Ideal for feedhunting now! When I get a bit more time I'll tidy up the plugin and release it as it should now act as a pretty good satellite channel scanner irrespective of whether you have a rotor within VDR. I haven't tested the entire satellite transponder scanning functionality yet for DVB-S/S2, that will be the next task but hopefully it won't need many changes. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] rotor-ng
On Tue, Mar 22, 2011 at 12:05 PM, Arturo Martinez marti...@embl.de wrote: Excellent news! I am sure the entire rotor vdr community will be very glad to hear that! At the moment I use diseqc.conf with goto position commands for each sat position to move the dish With rotor-ng does diseqc use have to be switched off in vdr and the plugin takes care of everything or does it parse diseqc.conf? VDR Diseqc settings are off in my configuration. Similarly to the rotor and actuator plugins there is a file in the plugin directory that stores the disecq postion number for every satellite: - S3.0E 31 S4.0E 30 S4.8E 15 S7.0E 14 S9.0E 29 S10.0E 13 S13.0E 12 S16.0E 11 S19.2E 10 At the moment you need to manually edit the file to set the positions up. A later version might include assigning or changing the position numbers directly in the plugin interface. I should at this point thank Luca Olivetti for all his work on the actuator plugin. I'm no developer, so wouldn't have been able to get this far without all the work he did on the scan interface etc. I've merely hacked his work to modify it to work with disecq 1.1 and fixed some issues with DVBS2 tuning. Ideally, we should probably work together to unify the two plugins so you can select Actuator / Disecq / GOTOX as the motor type attached and have a totally new plugin probably called Dish or something similar. Still left to do: - 1) Remove or fix some actuator specific interface buttons that are not too relevant or don't work 2) Fix enabling and clearing of limits as this doesn't work with my VBOX, I can't clear the limits via the plugin once they are set 3) Look at recalc and see how that can be implemented within rotor-ng 4) Remove old unused code that is related to actuator use 5) Update documentation etc 6) Find somewhere to host it - vdrprojects? 7) Implement GOTOX (though I don't use it so not sure how it would be tested. Might need a volunteer to do this by looking at the GOTOX patches for rotor and implementing them on rotor-ng). Thanks ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] rotor-ng
On Tue, Mar 22, 2011 at 5:41 AM, Morfsta morf...@gmail.com wrote: At the moment you need to manually edit the file to set the positions up. A later version might include assigning or changing the position numbers directly in the plugin interface. I should at this point thank Luca Olivetti for all his work on the actuator plugin. I'm no developer, so wouldn't have been able to get this far without all the work he did on the scan interface etc. I've merely hacked his work to modify it to work with disecq 1.1 and fixed some issues with DVBS2 tuning. Ideally, we should probably work together to unify the two plugins so you can select Actuator / Disecq / GOTOX as the motor type attached and have a totally new plugin probably called Dish or something similar. I don't use a actuator/rotor myself but I know people who do and are really looking forward to your plugin. I think a good stable 'vdr-movedish' plugin has been needed for quite some time. It almost seems like a plugin you'd expect to come with vanilla VDR since it provides such a basic function. Anyways, thanks for your work. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] rotor-ng
I get smoe of the terms confused. gotox is where you tell it the sat postion such as 97w and it goes there as vs telling it to go to a stored location? If that is the case, then gotox is needed as a way to get the rotor to a location. Also, VDR Diseqc should be on to use rotor as well as switches. I use both rotor and switches. On 3/22/2011 5:41 AM, Morfsta wrote: On Tue, Mar 22, 2011 at 12:05 PM, Arturo Martinezmarti...@embl.de wrote: Excellent news! I am sure the entire rotor vdr community will be very glad to hear that! At the moment I use diseqc.conf with goto position commands for each sat position to move the dish With rotor-ng does diseqc use have to be switched off in vdr and the plugin takes care of everything or does it parse diseqc.conf? VDR Diseqc settings are off in my configuration. Similarly to the rotor and actuator plugins there is a file in the plugin directory that stores the disecq postion number for every satellite: - S3.0E 31 S4.0E 30 S4.8E 15 S7.0E 14 S9.0E 29 S10.0E 13 S13.0E 12 S16.0E 11 S19.2E 10 At the moment you need to manually edit the file to set the positions up. A later version might include assigning or changing the position numbers directly in the plugin interface. I should at this point thank Luca Olivetti for all his work on the actuator plugin. I'm no developer, so wouldn't have been able to get this far without all the work he did on the scan interface etc. I've merely hacked his work to modify it to work with disecq 1.1 and fixed some issues with DVBS2 tuning. Ideally, we should probably work together to unify the two plugins so you can select Actuator / Disecq / GOTOX as the motor type attached and have a totally new plugin probably called Dish or something similar. Still left to do: - 1) Remove or fix some actuator specific interface buttons that are not too relevant or don't work 2) Fix enabling and clearing of limits as this doesn't work with my VBOX, I can't clear the limits via the plugin once they are set 3) Look at recalc and see how that can be implemented within rotor-ng 4) Remove old unused code that is related to actuator use 5) Update documentation etc 6) Find somewhere to host it - vdrprojects? 7) Implement GOTOX (though I don't use it so not sure how it would be tested. Might need a volunteer to do this by looking at the GOTOX patches for rotor and implementing them on rotor-ng). Thanks ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] rotor-ng
maybe once it's cleaned up and fully functional, in can be intigrated with vdr. On 3/22/2011 8:49 AM, VDR User wrote: On Tue, Mar 22, 2011 at 5:41 AM, Morfstamorf...@gmail.com wrote: At the moment you need to manually edit the file to set the positions up. A later version might include assigning or changing the position numbers directly in the plugin interface. I should at this point thank Luca Olivetti for all his work on the actuator plugin. I'm no developer, so wouldn't have been able to get this far without all the work he did on the scan interface etc. I've merely hacked his work to modify it to work with disecq 1.1 and fixed some issues with DVBS2 tuning. Ideally, we should probably work together to unify the two plugins so you can select Actuator / Disecq / GOTOX as the motor type attached and have a totally new plugin probably called Dish or something similar. I don't use a actuator/rotor myself but I know people who do and are really looking forward to your plugin. I think a good stable 'vdr-movedish' plugin has been needed for quite some time. It almost seems like a plugin you'd expect to come with vanilla VDR since it provides such a basic function. Anyways, thanks for your work. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] rotor-ng in development [was [ANNOUNCE] vdr-actuator-1.2.0 plugin]
On Sun, Mar 20, 2011 at 10:08 PM, Timothy D. Lenz tl...@vorgon.com wrote: I only have a Nexus-s for sat card and right now my rotor alignment is all screwed up. Relays went bad and had to replace them. I left the rotor elevation setting untouched but now it over shoots more and more the farther it goes as if the elevation is wrong. Haven't had time to look into it. Well, it seems I found the problem. The HAUPPAUGE NOVA-S2-HD card (HVR4000 lite / CX24116 frontend) won't lock onto DVB-S2 channels with FEC_AUTO or ROLLOFF_AUTO set. So, I modified the plugin to allow selectable values for FEC and ROLLOFF and now it works fine. I can now lock and scan DVB-S and DVB-S2 channels (QPSK and 8PSK) directly from the plugin menu and move the dish to find and store satellites with diseqc and signal strength meter. Ideal for feedhunting now! When I get a bit more time I'll tidy up the plugin and release it as it should now act as a pretty good satellite channel scanner irrespective of whether you have a rotor within VDR. I haven't tested the entire satellite transponder scanning functionality yet for DVB-S/S2, that will be the next task but hopefully it won't need many changes. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] rotor-ng in development [was [ANNOUNCE] vdr-actuator-1.2.0 plugin]
On Mon, Oct 11, 2010 at 1:32 PM, Morfsta morf...@gmail.com wrote: This really is sorely missing from VDR. Its a nice project which I might look at if I ever get a spare moment! First I would have to update my VDR from 1.7.0 with multiproto as lack of good support for vdr-rotor has been holding me back from upgrading to S2API and later development versions of VDR. Well, it took awhile but I have updated to yavdr 0.3 with S2API and a NV card and it is pretty stable now. The old rotor plugin is pretty unstable with yavdr (and perhaps later versions of VDR in general) and it seemed that no-one wanted to fix it, so I finally got around to modifying the actuator plugin to work with my disecq rotor (well actually a V-BOX hooked up to a 24V actuator). I can now get rid of the rotor plugin completely and drive my dish to the right positions and find / tune satellites with the modified actuator plugin, which IMHO works and looks better. It also allows me to scan DVB-S channels right from the plugin too. I'd like to release it at some point when I've tidied it up (perhaps as rotor-ng or something), but one issue I have is with DVB-S2 signal tuning and scanning on my Hauppauge Nova HD-S2 card - does anyone have this functionality working either with this card or another card with the actuator plugin's scanner? When I tune to a DVB-S2 channel (QPSK or 8PSK) within the plugin I get nothing, but when I tune in VDR the plugin shows full lock etc. I'd like to get this functionality working before releasing it and I thought it might be a problem with the card not supporting ROLLOFF_AUTO but that doesn't make any difference. Any help would be great. Thanks, Morfsta ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] rotor-ng in development [was [ANNOUNCE] vdr-actuator-1.2.0 plugin]
Al 20/03/11 22:20, En/na Morfsta ha escrit: I'd like to release it at some point when I've tidied it up (perhaps as rotor-ng or something), but one issue I have is with DVB-S2 signal tuning and scanning on my Hauppauge Nova HD-S2 card - does anyone have this functionality working either with this card or another card with the actuator plugin's scanner? Since I don't have an S2 card I never tested that functionality. Bye -- Luca ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] rotor-ng in development [was [ANNOUNCE] vdr-actuator-1.2.0 plugin]
I only have a Nexus-s for sat card and right now my rotor alignment is all screwed up. Relays went bad and had to replace them. I left the rotor elevation setting untouched but now it over shoots more and more the farther it goes as if the elevation is wrong. Haven't had time to look into it. On 3/20/2011 2:20 PM, Morfsta wrote: On Mon, Oct 11, 2010 at 1:32 PM, Morfstamorf...@gmail.com wrote: This really is sorely missing from VDR. Its a nice project which I might look at if I ever get a spare moment! First I would have to update my VDR from 1.7.0 with multiproto as lack of good support for vdr-rotor has been holding me back from upgrading to S2API and later development versions of VDR. Well, it took awhile but I have updated to yavdr 0.3 with S2API and a NV card and it is pretty stable now. The old rotor plugin is pretty unstable with yavdr (and perhaps later versions of VDR in general) and it seemed that no-one wanted to fix it, so I finally got around to modifying the actuator plugin to work with my disecq rotor (well actually a V-BOX hooked up to a 24V actuator). I can now get rid of the rotor plugin completely and drive my dish to the right positions and find / tune satellites with the modified actuator plugin, which IMHO works and looks better. It also allows me to scan DVB-S channels right from the plugin too. I'd like to release it at some point when I've tidied it up (perhaps as rotor-ng or something), but one issue I have is with DVB-S2 signal tuning and scanning on my Hauppauge Nova HD-S2 card - does anyone have this functionality working either with this card or another card with the actuator plugin's scanner? When I tune to a DVB-S2 channel (QPSK or 8PSK) within the plugin I get nothing, but when I tune in VDR the plugin shows full lock etc. I'd like to get this functionality working before releasing it and I thought it might be a problem with the card not supporting ROLLOFF_AUTO but that doesn't make any difference. Any help would be great. Thanks, Morfsta ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] rotor
Приветствую, Timothy Is your bud motorized? yes, I have the motor STRONG SRT DM 2100 http://faraday-systems.uaprom.net/p383218-motopodves-disek-pozitsioner.html (not actuator) and the the dish with diameter 1,1 meter You found a diseqc motor that works with big dishes? 1,1 meter is not big size. And I can watch several satellites in C band with it - the sat positions - 40e, 80e, 90e, 95e The secret is in good LNB, specially and manually adopted for C-band and my dish (from Russian engineer Alyno) http://forum2.alyno.ru/phpBB2/viewtopic.php?p=713#713 Because they need bigger motors then can be powered by the card, they use a different setup. A Actuator that runs on 36v and is told to move one way or the other and then pulses are counted and then the motor is told to stop. Small dish rotors have all that logic on board and you just teil them where you want the dish pointing ok, understand than. But in my case no need any big and special motors Goga On 6/24/2010 1:04 PM, Goga777 wrote: Приветствую, Mike the rotor plugin ( or at least version 1.4mh) can control one rotor per card. For c-band you need a vbox to translate the diseqc commands and to provide the 36 volts to drive the actuator. Thats how I do it. costs about $40 why need vbox for C-band ? I can watch C-band with vdr + rotor + diseqc + 3 Lnb (two LNB are for Ku band, third LNB is for C-band) without any tricks ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] rotor
On 6/24/2010 11:32 PM, Goga777 wrote: Приветствую, Timothy Is your bud motorized? yes, I have the motor STRONG SRT DM 2100 http://faraday-systems.uaprom.net/p383218-motopodves-disek-pozitsioner.html (not actuator) and the the dish with diameter 1,1 meter Suitable for antenna 1,2 m BUD's (Big Ugly Dish) tend to be in the 6'-12' size. 1.2m (3.9'), while the high end of small dish's, is what some call a mini-bud. And is the largest you can go with that kind of motor ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] rotor
the rotor plugin ( or at least version 1.4mh) can control one rotor per card. For c-band you need a vbox to translate the diseqc commands and to provide the 36 volts to drive the actuator. Thats how I do it. costs about $40 (australian). Piece of cake. Or am I missing something? Mike ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] rotor
I've seen those boxes advertised but hadn't looked at them close yet. Seen any diy projects for those? designing/building the hardware is easy, but I'm not much of a programmer. That vbox is what the electronics part of the small dish rotors are. I was thinking of building around an Atmel chip. They are a couple dollars US and could easily do the job. They have enough both ram and flash memory to store the position of every sat up there, not just the ones you can see. On 6/24/2010 3:32 AM, Mike Booth wrote: the rotor plugin ( or at least version 1.4mh) can control one rotor per card. For c-band you need a vbox to translate the diseqc commands and to provide the 36 volts to drive the actuator. Thats how I do it. costs about $40 (australian). Piece of cake. Or am I missing something? Mike ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] rotor
Приветствую, Mike the rotor plugin ( or at least version 1.4mh) can control one rotor per card. For c-band you need a vbox to translate the diseqc commands and to provide the 36 volts to drive the actuator. Thats how I do it. costs about $40 why need vbox for C-band ? I can watch C-band with vdr + rotor + diseqc + 3 Lnb (two LNB are for Ku band, third LNB is for C-band) without any tricks Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] rotor
Is your bud motorized? You found a diseqc motor that works with big dishes? Because they need bigger motors then can be powered by the card, they use a different setup. A Actuator that runs on 36v and is told to move one way or the other and then pulses are counted and then the motor is told to stop. Small dish rotors have all that logic on board and you just teil them where you want the dish pointing On 6/24/2010 1:04 PM, Goga777 wrote: Приветствую, Mike the rotor plugin ( or at least version 1.4mh) can control one rotor per card. For c-band you need a vbox to translate the diseqc commands and to provide the 36 volts to drive the actuator. Thats how I do it. costs about $40 why need vbox for C-band ? I can watch C-band with vdr + rotor + diseqc + 3 Lnb (two LNB are for Ku band, third LNB is for C-band) without any tricks Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] rotor screen missing stuff
The plugin has been downgraded. There are people who use a patched and patched 0.1.4 rather than the official 0.1.5 The situation with the rotor plugin is so bad (so much patching needed to get it to work and then I found it makes vdr unstable) I've resorted to having two parallel installations of vdr one I use just for the rotor plugin when I need to use it to align the dish and store the positions. In my 'normal' vdr installation I don't use the rotor plugin but rather diseq commands 'Go to position X' Here is my diseqc.conf if it helps you: S19.2E 11700 V 9750 t v W15 [E0 31 6B 13] W25 [E0 31 6B 13] W15 t S19.2E 9 V 10600 t v W15 [E0 31 6B 13] W25 [E0 31 6B 13] W15 T S19.2E 11700 H 9750 t V W15 [E0 31 6B 13] W25 [E0 31 6B 13] W15 t S19.2E 9 H 10600 t V W15 [E0 31 6B 13] W25 [E0 31 6B 13] W15 T S13.0E 11700 V 9750 t v W15 [E0 31 6B 0D] W25 [E0 31 6B 0D] W15 t S13.0E 9 V 10600 t v W15 [E0 31 6B 0D] W25 [E0 31 6B 0D] W15 T S13.0E 11700 H 9750 t V W15 [E0 31 6B 0D] W25 [E0 31 6B 0D] W15 t S13.0E 9 H 10600 t V W15 [E0 31 6B 0D] W25 [E0 31 6B 0D] W15 T S28.2E 11700 V 9750 t v W15 [E0 31 6B 1C] W25 [E0 31 6B 1C] W15 t S28.2E 9 V 10600 t v W15 [E0 31 6B 1C] W25 [E0 31 6B 1C] W15 T S28.2E 11700 H 9750 t V W15 [E0 31 6B 1C] W25 [E0 31 6B 1C] W15 t S28.2E 9 H 10600 t V W15 [E0 31 6B 1C] W25 [E0 31 6B 1C] W15 T S28.5E 11700 V 9750 t v W15 [E0 31 6B 1D] W25 [E0 31 6B 1D] W15 t S28.5E 9 V 10600 t v W15 [E0 31 6B 1D] W25 [E0 31 6B 1D] W15 T S28.5E 11700 H 9750 t V W15 [E0 31 6B 1D] W25 [E0 31 6B 1D] W15 t S28.5E 9 H 10600 t V W15 [E0 31 6B 1D] W25 [E0 31 6B 1D] W15 T I guess it comes down to the hard truth that there is no vdr 1.7.x user with C programming skills using a rotor who needs something more than USALS 1.2 Message: 5 Date: Tue, 22 Jun 2010 19:12:16 -0700 From: Timothy D. Lenz tl...@vorgon.com Subject: [vdr] rotor screen missing stuff To: vdr@linuxtv.org Message-ID: 4c216d80.2090...@vorgon.com Content-Type: text/plain; charset=ISO-8859-1; format=flowed I am trying to get my rotor working again. I had been using v0.1.4 with vdr-1.6.0. Now I'm trying to get v.0.1.5 working with vdr-1.7.15. On the rotor page, Postion information no longer shows the sat it matches to, the option to do a scan on the current TP is gone, and the lock and other indicators are gone. Was that all part of the text2skin plugin which I'm not using now? or has the plugin been down graded? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] rotor screen missing stuff
I am trying to get my rotor working again. I had been using v0.1.4 with vdr-1.6.0. Now I'm trying to get v.0.1.5 working with vdr-1.7.15. On the rotor page, Postion information no longer shows the sat it matches to, the option to do a scan on the current TP is gone, and the lock and other indicators are gone. Was that all part of the text2skin plugin which I'm not using now? or has the plugin been down graded? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] rotor plugin puzzling question
I think the rotor plugin is a bit of a mess now and the latest version (1.5) is a step backwards with no transponder scan facility. A clever friend of mine has doctored the previous version to work with vdr-1.7.9, to still scan transponders and better still to scan C-band transponders. Rotor switches diseqc off it appears and VDR defaults to Ku settings so all c-band appears to be out of rangeanyone else have this problem? Mike ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] rotor plugin puzzling question
I think the rotor plugin is a bit of a mess now and the latest version (1.5) is a step backwards with no transponder scan facility. A clever friend of mine has doctored the previous version to work with vdr-1.7.9, to still scan transponders and better still to scan C-band transponders. Rotor switches diseqc off it appears and VDR defaults to Ku settings so all c-band appears to be out of rangeanyone else have this problem? may the best solution - to use vdr-reelchannelscan ? nor rotor ? Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] rotor plugin puzzling question
I couldn't apply a patch
/usr/src/vdr/PLUGINS/src/rotor-0.1.5# cat patch1 | patch -p0 --dry-run
patching file rotor.c
patch: malformed patch at line 6:
(diseqc=Diseqcs.Get(source-Code(),12000,'v')) ||
any clue ?
Is it just me or the newly released rotor plugin for vdr 1.7.9 needs the
following patch to the plugin itself in order to run (although it compiles
fine without it)
If the author reads these lines I would love to know why...
--- rotor.c.old 2006-06-14 23:44:27.0 +0200
+++ rotor.c 2006-06-14 23:46:43.0 +0200
@@ -96,7 +96,8 @@
continue;
if ((diseqc=Diseqcs.Get(source-Code(),12000,'h')) ||
(diseqc=Diseqcs.Get(source-Code(),12000,'v')) ||
(diseqc=Diseqcs.Get(source-Code(),12000,'l')) ||
(diseqc=Diseqcs.Get(source-Code(),12000,'r')))
{
- char *c=strdup(diseqc-Commands());
+ char *commandstring=strdup(diseqc-Commands());
+ char *c=commandstring;
while (c = strchr(c, '['))
{
char *e = strchr(++c, ']');
@@ -131,7 +132,7 @@
break;
}
}
- free(c);
+ free(commandstring);
}
cRotorPos *p = RotorPositions.GetfromSource(source-Code());
if (p==RotorPositions.First())
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] rotor plugin puzzling question
Goga777 wrote: I couldn't apply a patch /usr/src/vdr/PLUGINS/src/rotor-0.1.5# cat patch1 | patch -p0 --dry-run patching file rotor.c patch: malformed patch at line 6: (diseqc=Diseqcs.Get(source-Code(),12000,'v')) || if ((diseqc=Diseqcs.Get(source-Code(),12000,'h')) || (diseqc=Diseqcs.Get(source-Code(),12000,'v')) || (diseqc=Diseqcs.Get(source-Code(),12000,'l')) || (diseqc=Diseqcs.Get(source-Code(),12000,'r'))) There only one line and it wrapped to 4 parts. You should join these parts to one line. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] rotor plugin puzzling question
Is it just me or the newly released rotor plugin for vdr 1.7.9 needs the
following patch to the plugin itself in order to run (although it compiles
fine without it)
If the author reads these lines I would love to know why...
--- rotor.c.old 2006-06-14 23:44:27.0 +0200
+++ rotor.c 2006-06-14 23:46:43.0 +0200
@@ -96,7 +96,8 @@
continue;
if ((diseqc=Diseqcs.Get(source-Code(),12000,'h')) ||
(diseqc=Diseqcs.Get(source-Code(),12000,'v')) ||
(diseqc=Diseqcs.Get(source-Code(),12000,'l')) ||
(diseqc=Diseqcs.Get(source-Code(),12000,'r')))
{
- char *c=strdup(diseqc-Commands());
+ char *commandstring=strdup(diseqc-Commands());
+ char *c=commandstring;
while (c = strchr(c, '['))
{
char *e = strchr(++c, ']');
@@ -131,7 +132,7 @@
break;
}
}
- free(c);
+ free(commandstring);
}
cRotorPos *p = RotorPositions.GetfromSource(source-Code());
if (p==RotorPositions.First())
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] rotor plugin puzzling question
Hello,
ACK: this was clearly a bug ;-)
marti...@embl.de a écrit :
Is it just me or the newly released rotor plugin for vdr 1.7.9 needs the
following patch to the plugin itself in order to run (although it compiles
fine without it)
If the author reads these lines I would love to know why...
--- rotor.c.old 2006-06-14 23:44:27.0 +0200
+++ rotor.c 2006-06-14 23:46:43.0 +0200
@@ -96,7 +96,8 @@
continue;
if ((diseqc=Diseqcs.Get(source-Code(),12000,'h')) ||
(diseqc=Diseqcs.Get(source-Code(),12000,'v')) ||
(diseqc=Diseqcs.Get(source-Code(),12000,'l')) ||
(diseqc=Diseqcs.Get(source-Code(),12000,'r')))
{
- char *c=strdup(diseqc-Commands());
+ char *commandstring=strdup(diseqc-Commands());
+ char *c=commandstring;
while (c = strchr(c, '['))
{
char *e = strchr(++c, ']');
@@ -131,7 +132,7 @@
break;
}
}
- free(c);
+ free(commandstring);
I am not the author (nor even a user) but you are absolutely right.
You must free the pointer as returned by strdup; not one that you have
modified or incremented :(
So you need to keep a virgin copy of the pointer as you have done.
Cheers,
Chris
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] vdr-rotor-0.1.5
http://home.vrweb.de/~bergwinkl.thomas/downro/vdr-rotor-0.1.5.tgz vdr-rotor for vdr 179 ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-rotor-0.1.5
Goga777 ha scritto: http://home.vrweb.de/~bergwinkl.thomas/downro/vdr-rotor-0.1.5.tgz vdr-rotor for vdr 179 ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr Hi, i upload here the italian translation. Bye, Diego Pierotto -- Member of the Italian VDR Wiki http://vdr.spaghettilinux.org/ rotor-0.1.5.tar.bz2 Description: application/bzip ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] rotor plugin, anybody got it working with vdr 1.7.5?
Hi, Does your positioner support gotox? See the patches for vdr 1.6.0 and 1.7.0 maintained by Ales J. Works for me with fine with vdr 1.7.5. There no patch rejects. http://www.linuxtv.org/pipermail/vdr/2008-September/017637.html Vdr rotor plugin stopped working for me reliably enough with multiproto drivers and probably the same issues are in s2api as well. There were timing hazards that violated the diseqc spec. This patch is based on Rotor plugin's internals patched into vdr's diseqc core. BR, Seppo ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] rotor plugin, anybody got it working with vdr 1.7.5?
I try to run vdr -Pxine -Protor and get: - MakePrimaryDevice: 1 = SetVideoFormat: 1 SetVolumeDevice: 0 *** glibc detected *** vdr: munmap_chunk(): invalid pointer: 0x09b2c28c *** === Backtrace: = /lib/tls/i686/cmov/libc.so.6[0xb7c83454] /usr/lib/vdr/plugins/libvdr-rotor.so.1.7.5(_ZN12cPluginRotor5StartEv+0x541)[0xb7a186b1] vdr(_ZN14cPluginManager12StartPluginsEv+0x4b)[0x80f1bbb] vdr(main+0x23af)[0x8128d8f] /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe5)[0xb7c2a685] vdr[0x8098681] === Memory map: 08048000-08179000 r-xp 08:01 975113 /usr/bin/vdr 08179000-0817a000 r--p 0013 08:01 975113 /usr/bin/vdr 0817a000-0817b000 rw-p 00131000 08:01 975113 /usr/bin/vdr 0817b000-08187000 rw-p 0817b000 00:00 0 097d1000-09b4a000 rw-p 097d1000 00:00 0 [heap] b4ffd000-b4ffe000 ---p b4ffd000 00:00 0 b4ffe000-b57fe000 rw-p b4ffe000 00:00 0 b57fe000-b57ff000 ---p b57fe000 00:00 0 b57ff000-b5fff000 rw-p b57ff000 00:00 0 b5fff000-b600 ---p b5fff000 00:00 0 b600-b680 rw-p b600 00:00 0 b680-b6821000 rw-p b680 00:00 0 b6821000-b690 ---p b6821000 00:00 0 b699e000-b69c9000 rw-p b699e000 00:00 0 b69c9000-b69ca000 ---p b69c9000 00:00 0 b69ca000-b71ca000 rw-p b69ca000 00:00 0 b71ca000-b71cb000 ---p b71ca000 00:00 0 b71cb000-b79cb000 rw-p b71cb000 00:00 0 b79cb000-b79d1000 r--s 08:01 2089260 /var/cache/fontconfig/945677eb7aeaf62f1d50efc3fb3ec7d8-x86.cache-2 b79d1000-b79d4000 r--s 08:01 2089254 /var/cache/fontconfig/e383d7ea5fbe662a33d9b44caf393297-x86.cache-2 b79d4000-b79d5000 r--s 08:01 2089253 /var/cache/fontconfig/4c73fe0c47614734b17d736dbde7580a-x86.cache-2 b79d5000-b79d8000 r--s 08:01 2089262 /var/cache/fontconfig/a755afe4a08bf5b97852ceb7400b47bc-x86.cache-2 b79d8000-b79df000 r--s 08:01 2089256 /var/cache/fontconfig/6d41288fd70b0be22e8c3a91e032eec0-x86.cache-2 b79df000-b79e2000 r--s 08:01 2089252 /var/cache/fontconfig/de156ccd2eddbdc19d37a45b8b2aac9c-x86.cache-2 b79e2000-b79ea000 r--s 08:01 2089255 /var/cache/fontconfig/e3de0de479f42330eadf588a55fb5bf4-x86.cache-2 b79ea000-b79f5000 r--s 08:01 2089251 /var/cache/fontconfig/0f34bcd4b6ee430af32735b75db7f02b-x86.cache-2 b79f5000-b79f6000 r--s 08:01 2088971 /var/cache/fontconfig/4794a0821666d79190d59a36cb4f44b5-x86.cache-2 b79f6000-b79f9000 r--s 08:01 2089259 /var/cache/fontconfig/de9486f0b47a4d768a594cb4198cb1c6-x86.cache-2 b79f9000-b7a0 r--s 08:01 2089257 /var/cache/fontconfig/d52a8644073d54c13679302ca1180695-x86.cache-2 b7a0-b7a06000 r--s 08:01 2089258 /var/cache/fontconfig/089dead882dea3570ffc31a9898cfb69-x86.cache-2 b7a06000-b7a0d000 r--s 08:01 2089261 /var/cache/fontconfig/e13b20fdb08344e0e664864cc2ede53d-x86.cache-2 b7a0d000-b7a28000 r-xp 08:01 1261911 /usr/lib/vdr/plugins/libvdr-rotor.so.1.7.5 b7a28000-b7a29000 ---p 0001b000 08:01 1261911 /usr/lib/vdr/plugins/libvdr-rotor.so.1.7.5 b7a29000-b7a2a000 r--p 0001b000 08:01 1261911 /usr/lib/vdr/plugins/libvdr-rotor.so.1.7.5 b7a2a000-b7a2b000 rw-p 0001c000 08:01 1261911 /usr/lib/vdr/plugins/libvdr-rotor.so.1.7.5 b7a2b000-b7a2c000 rw-p b7a2b000 00:00 0 b7a2c000-b7a68000 r-xp 08:01 1261916 /usr/lib/vdr/plugins/libvdr-xine.so.1.7.5 b7a68000-b7a69000 ---p 0003c000 08:01 1261916 /usr/lib/vdr/plugins/libvdr-xine.so.1.7.5 b7a69000-b7a6a000 r--p 0003c000 08:01 1261916 /usr/lib/vdr/plugins/libvdr-xine.so.1.7.5 b7a6a000-b7a8b000 rw-p 0003d000 08:01 1261916 /usr/lib/vdr/plugins/libvdr-xine.so.1.7.5 b7a8b000-b7aac000 rw-p b7a8b000 00:00 0 b7aac000-b7aae000 r-xp 08:01 1287915/usr/lib/gconv/ISO8859-15.so b7aae000-b7aaf000 r--p 1000 08:01 1287915/usr/lib/gconv/ISO8859-15.so b7aaf000-b7ab rw-p 2000 08:01 1287915/usr/lib/gconv/ISO8859-15.so b7ab-b7ab5000 r--p 08:01 1803930 /usr/share/locale/es_ES/LC_MESSAGES/vdr.mo b7ab5000-b7af4000 r--p 08:01 1237164 /usr/lib/locale/en_US.utf8/LC_CTYPE b7af4000-b7bd5000 r--p 08:01 1237171 /usr/lib/locale/en_US.utf8/LC_COLLATE b7bd5000-b7bd7000 rw-p b7bd5000 00:00 0 b7bd7000-b7bfb000 r-xp 08:01 1107560/usr/lib/libexpat.so.1.5.2 b7bfb000-b7bfd000 r--p 00023000 08:01 1107560/usr/lib/libexpat.so.1.5.2 b7bfd000-b7bfe000 rw-p 00025000 08:01 1107560/usr/lib/libexpat.so.1.5.2 b7bfe000-b7c12000 r-xp 08:01 1107452/usr/lib/libz.so.1.2.3.3 b7c12000-b7c14000 rw-p 00013000 08:01 1107452/usr/lib/libz.so.1.2.3.3 b7c14000-b7d6c000 r-xp 08:01 1163319 /lib/tls/i686/cmov/libc-2.8.90.so b7d6c000-b7d6e000 r--p 00158000 08:01 1163319 /lib/tls/i686/cmov/libc-2.8.90.so b7d6e000-b7d6f000 rw-p 0015a000 08:01 1163319 /lib/tls/i686/cmov/libc-2.8.90.so b7d6f000-b7d72000 rw-p b7d6f000 00:00 0 b7d72000-b7d7f000 r-xp 08:01 1163862/lib/libgcc_s.so.1 b7d7f000-b7d8 r--p
Re: [vdr] rotor and vdr
Ales Jurik wrote: Original patch from Seppo (vdr-1.5.16): http://www.mail-archive.com/vdr@linuxtv.org/msg05864.html Patches for 1.6.0 and 1.7.0 (could be used up to 1.7.4): http://www.linuxtv.org/pipermail/vdr/2008-September/017637.html Do You have any additional hints? It doesn't compiles with vdr-1.7.4 :( AK ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] rotor and vdr
On Saturday 14 of February 2009, Arthur Konovalov wrote: Ales Jurik wrote: Original patch from Seppo (vdr-1.5.16): http://www.mail-archive.com/vdr@linuxtv.org/msg05864.html Patches for 1.6.0 and 1.7.0 (could be used up to 1.7.4): http://www.linuxtv.org/pipermail/vdr/2008-September/017637.html Do You have any additional hints? It doesn't compiles with vdr-1.7.4 :( I've just tested it and no problem at all. BR, Ales AK ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] rotor and vdr
Hi is there any working solution for moving of rotor with vdr ? Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] rotor and vdr
On Thursday 12 of February 2009, Goga777 wrote: Hi is there any working solution for moving of rotor with vdr ? Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr Hi, I'm using vdr-gotox patch. For which version of vdr do you need it? I've send it to this ml some months (year) ago, but no problem to resend. I'm not original author od this patch but I have permission from the author to change it to newer versions of vdr. BR, Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] rotor and vdr
Goga777 wrote: Hi is there any working solution for moving of rotor with vdr ? Yes Matthieu PS : I let you search it (hint search in vdr plugin page). ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] rotor and vdr
Приветствую, matthieu is there any working solution for moving of rotor with vdr ? Yes Matthieu PS : I let you search it (hint search in vdr plugin page). do you mean rotor plugin ? But it didn't work correctly with goto xx / goto position on my мвкю Also it couldn't save the satellite position in rotor memory for goto xxx Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] rotor and vdr
On Thursday 12 of February 2009, Ales Jurik wrote: On Thursday 12 of February 2009, Goga777 wrote: Hi is there any working solution for moving of rotor with vdr ? Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr Hi, I'm using vdr-gotox patch. For which version of vdr do you need it? I've send it to this ml some months (year) ago, but no problem to resend. I'm not original author od this patch but I have permission from the author to change it to newer versions of vdr. Original patch from Seppo (vdr-1.5.16): http://www.mail-archive.com/vdr@linuxtv.org/msg05864.html Patches for 1.6.0 and 1.7.0 (could be used up to 1.7.4): http://www.linuxtv.org/pipermail/vdr/2008-September/017637.html BR, Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] rotor and vdr
I'm using vdr-gotox patch. For which version of vdr do you need it? vdr 174 Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Rotor patches
My patch that patches Rotor plugin's gotox/usals functionality into vdr's DiSEqC system is here. The motivation for this work is unreliability of Rotor plugin that I experienced with multiproto driver for TT-budget S2-3200. http://linuxtv.org/pipermail/vdr/2008-March/016164.html Cheers, Seppo ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Rotor patches
Hy. No, just Rotor-0.1.4-vdr1.5.10.diff. Lucian. Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Rotor patches
Strange, that patch fails on all hunks. looking to patch by hand, it's not even close. The vdr-1.5.5-rotor.diff patch applies. - Original Message - From: lucian orasanu [EMAIL PROTECTED] To: vdr@linuxtv.org Sent: Tuesday, April 15, 2008 11:45 PM Subject: [vdr] Rotor patches Hy. No, just Rotor-0.1.4-vdr1.5.10.diff. Lucian. Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Rotor patches
On Wed, 2008-04-16 at 16:23 -0700, Timothy D. Lenz wrote: Strange, that patch fails on all hunks. looking to patch by hand, it's not even close. The vdr-1.5.5-rotor.diff patch applies. Where does one find these patches? - Original Message - From: lucian orasanu [EMAIL PROTECTED] To: vdr@linuxtv.org Sent: Tuesday, April 15, 2008 11:45 PM Subject: [vdr] Rotor patches Hy. No, just Rotor-0.1.4-vdr1.5.10.diff. Lucian. Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Rotor patches
The vdr-1.5.5-rotor.diff patch comes with the newest version. the other patch has been floating around on this group and the german board. Try looking back in the archives here. - Original Message - From: Malcolm Caldwell [EMAIL PROTECTED] To: vdr@linuxtv.org Sent: Wednesday, April 16, 2008 8:13 PM Subject: Re: [vdr] Rotor patches On Wed, 2008-04-16 at 16:23 -0700, Timothy D. Lenz wrote: Strange, that patch fails on all hunks. looking to patch by hand, it's not even close. The vdr-1.5.5-rotor.diff patch applies. Where does one find these patches? - Original Message - From: lucian orasanu [EMAIL PROTECTED] To: vdr@linuxtv.org Sent: Tuesday, April 15, 2008 11:45 PM Subject: [vdr] Rotor patches Hy. No, just Rotor-0.1.4-vdr1.5.10.diff. Lucian. Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr Rotor-0.1.4-vdr1.5.10.diff Description: Binary data ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Rotor patches
There are 2 patches for the Rotor plugin: vdr-1.5.5-rotor.diff Rotor-0.1.4-vdr1.5.10.diff They patch different areas. Are they both needed for vdr-1.6? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] vdr-rotor support patches for VDR-1.5.16
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% success. I have been looking at rotor plugin and didn't get
idea how switching off tone could be syncronized to tuning and
diseqc.conf sequences without possible negative influence to tuning. Or
is there a guarantee for some order of execution? I wonder if it worked
with the existing Linux kernel DVB-S driver with just good luck.
Wouldn't it be better to have in diseqc.conf possibility for this kind
of setup
S19.2E 11700 V 9750 t V W15 G W15 v t
S19.2E 9 V 10600 t V W15 G W15 v T
S19.2E 11700 H 9750 t V W15 G W15 V t
S19.2E 9 H 10600 t V W15 G W15 V T
where the continuous tone is first switched off, then LNB voltage is set
to 18V for better rotor speed and then GotoX is sent with internal
computation based on new position and geographic location, etc (to be
added to vdr setup, e.g. LNB diseqc config page). There could blind be
waiting of positioning inside G operation with estimate about rotor
speed to avoid temporary tuning to intermediate positions. Finally the
proper tone and voltage is set. This way there would be exact control
when GotoX is issued. It would be possible to enable EIT scan and
channel/multiplex updates with rotor without fear that it messes up
channels.conf. With some more thinking the t V W15 and W15 should
perhaps be put inside G.
This could be done by utilizing code from rotor plugin this into dvbdevice.c
if (frontendType (DVBFE_DELSYS_DVBS | DVBFE_DELSYS_DVBS2)) {
unsigned int frequency = channel.Frequency();
if (Setup.DiSEqC) {
cDiseqc *diseqc = Diseqcs.Get(channel.Source(),
channel.Frequency(), channel.Polarization());
if (diseqc) {
if (diseqc-Commands() (!diseqcCommands ||
strcmp(diseqcCommands, diseqc-Commands()) != 0)) {
cDiseqc::eDiseqcActions da;
for (char *CurrentAction = NULL; (da =
diseqc-Execute(CurrentAction)) != cDiseqc::daNone; ) {
switch (da) {
case cDiseqc::daNone: break;
case cDiseqc::daToneOff: CHECK(ioctl(fd_frontend,
FE_SET_TONE, SEC_TONE_OFF)); break;
case cDiseqc::daToneOn:CHECK(ioctl(fd_frontend,
FE_SET_TONE, SEC_TONE_ON)); break;
case cDiseqc::daVoltage13: CHECK(ioctl(fd_frontend,
FE_SET_VOLTAGE, SEC_VOLTAGE_13)); break;
case cDiseqc::daVoltage18: CHECK(ioctl(fd_frontend,
FE_SET_VOLTAGE, SEC_VOLTAGE_18)); break;
case cDiseqc::daMiniA: CHECK(ioctl(fd_frontend,
FE_DISEQC_SEND_BURST, SEC_MINI_A)); break;
case cDiseqc::daMiniB: CHECK(ioctl(fd_frontend,
FE_DISEQC_SEND_BURST, SEC_MINI_B)); break;
case cDiseqc::daGotoX: {
...
int gotoXTable[10] = { 0x00, 0x02, 0x03, 0x05, 0x06, 0x08,
0x0A, 0x0B, 0x0D, 0x0E };
int satlong = (Source ~0xC800);
if ((Source 0xC000) != 0x8000)
return;
if (Source 0x0800)
satlong = satlong * (-1);
int Long=data.GotoxEW ? -data.GotoxLong : data.GotoxLong;
int Lat=data.GotoxSN ? -data.GotoxLat : data.GotoxLat;
double
azimuth=M_PI+atan(tan((satlong-Long)*M_PI/1800)/sin(Lat*M_PI/1800));
double
x=acos(cos((satlong-Long)*M_PI/1800)*cos(Lat*M_PI/1800));
double elevation=atan((cos(x)-0.1513)/sin(x));
double
SatHourangle=180+atan((-cos(elevation)*sin(azimuth))/(sin(elevation)*cos(Lat*M_PI/1800)
-cos(elevation)*sin(Lat*M_PI/1800)*cos(azimuth)))*180/M_PI;
int tmp=(int)(fabs(180-SatHourangle)*10);
tmp=(tmp/10)*0x10 + gotoXTable[ tmp % 10 ];
int p2=(tmp%0x0100);
int p1=(tmp/0x0100);
if (SatHourangle 180)
p1 |= 0xe0;
else
p1 |= 0xd0;
DiseqcCommand(Gotox,p1,p2);
}
...
break;
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!
Or does this make sense?
Cheers,
Seppo
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] vdr-rotor support patches for VDR-1.5.16
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! This seems to be already checked in status.c. I've used debug message to show all diseqc commands send and it seems to work fine (for me). BR, Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] vdr-rotor support patches for VDR-1.5.16
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 noticed that zapping works reliably with between channels in different positions with LNB tone off (frequency 11700, if I got this right...). V/H polarization didn't matter (13V or 18V LNB voltage). There should be 15 ms tone off between DiSEqC messages and continuous tone that might not happen with rotor plugin and this DVB driver. I wonder if that could be the reason? Yes, my fault - I've switched between satellites only on lower band. But with newest version of multiproto also this was not possible. But I'm using it with cascade switch/motor, so my tests could have different results. BR, Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] vdr-rotor support patches for VDR-1.5.16
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 between channels in different positions with LNB tone off (frequency 11700, if I got this right...). V/H polarization didn't matter (13V or 18V LNB voltage). There should be 15 ms tone off between DiSEqC messages and continuous tone that might not happen with rotor plugin and this DVB driver. I wonder if that could be the reason? I wish the GotoX would be better integrated to vdr's DiSEqC architecture. Now it looks a bit flaky, rotor plugin seems to monitor channel switch events in status.c. I wonder if additing tone off controls around gotox transmission would have impact to tuning where tone and voltage are set? BR, Seppo ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] vdr-rotor support patches for VDR-1.5.16
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 compiling rotor plugin (vdr-rotor-0.1.4-vdr1.5.7.tgz)? As mentioned above, you'll need an updated vdr-rotor too (see attachment), which makes use of the new API. As a brutal fix I added dummy parameters (zeros, copy language strings, etc.) for SetSatTransponderData() and SetPids() calls to get it compiled. I appreciate a real correction if such exists ;^) Well, 0 is not a good dummy value in case of the multiproto tree, but the attached vdr-rotor should solve this issue. I'm having problems in getting my diseqc motor positioner to work with multiproto+h.264 patched vdr 1.5.16. It is at the moment very unreliable. Most of the time it just stays stuck into the old position so possibly the commands get corrupted. Is a Technotrend S2-3200 capable to control a positioner? My old budget-s Tecnotrend was very reliable in driving the same positioner. Hhm, as I do not own a positioner myself, I cannot test vdr-rotor in practice. Bye. -- Dipl.-Inform. (FH) Reinhard Nissl mailto:[EMAIL PROTECTED] vdr-rotor-0.1.4-vdr-1.5.14.tgz Description: GNU Unix tar archive ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] vdr-rotor support patches for VDR-1.5.16
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 DVB-S2+H.264 support. Do you get this error when compiling rotor plugin (vdr-rotor-0.1.4-vdr1.5.7.tgz)? g++-4.3 -O2 -Wall -Woverloaded-virtual -Wno-parentheses -fPIC -c -D_GNU_SOURCE -DPLUGIN_NAME_I18N='rotor' -I/home/seppo/src/dvb/multiproto-0448e5a6d8a6/linux/include -I../../..//include -I/home/seppo/src/dvb/multiproto-0448e5a6d8a6/linux/include menu.c menu.c: In member function 'virtual eOSState cMainMenuRotor::ProcessKey(eKeys)': menu.c:304: error: no matching function for call to 'cChannel::SetSatTransponderData(int, int, char, int, fe_code_rate)' ../../..//include/vdr/channels.h:226: note: candidates are: bool cChannel::SetSatTransponderData(int, int, char, int, int, int, int, int) menu.c:316: error: no matching function for call to 'cChannel::SetSatTransponderData(int, int, char, int, fe_code_rate)' ../../..//include/vdr/channels.h:226: note: candidates are: bool cChannel::SetSatTransponderData(int, int, char, int, int, int, int, int) menu.c: In member function 'void cMenuScan::AddChannel(int)': menu.c:429: error: no matching function for call to 'cChannel::SetPids(int, int, int [33], char [33][8], int [17], char [17][8], int)' ../../..//include/vdr/channels.h:232: note: candidates are: void cChannel::SetPids(int, int, int*, char (*)[8], int*, char (*)[8], int*, char (*)[8], int) menu.c: In member function 'void cMenuScan::SetPids(int, int, int, int*, char (*)[8], int*, char (*)[8], int)': menu.c:467: error: no matching function for call to 'cChannel::SetPids(int, int, int*, char (*)[8], int*, char (*)[8], int)' ../../..//include/vdr/channels.h:232: note: candidates are: void cChannel::SetPids(int, int, int*, char (*)[8], int*, char (*)[8], int*, char (*)[8], int) make[1]: *** [menu.o] Error 1 As a brutal fix I added dummy parameters (zeros, copy language strings, etc.) for SetSatTransponderData() and SetPids() calls to get it compiled. I appreciate a real correction if such exists ;^) I'm having problems in getting my diseqc motor positioner to work with multiproto+h.264 patched vdr 1.5.16. It is at the moment very unreliable. Most of the time it just stays stuck into the old position so possibly the commands get corrupted. Is a Technotrend S2-3200 capable to control a positioner? My old budget-s Tecnotrend was very reliable in driving the same positioner. BR, Seppo ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] vdr-rotor support patches for VDR-1.5.14
Morfsta wrote: Nope, it's all compiled - just doublechecked with fresh source: - vdr-1.5.14 vdr-rotor-0.1.4-vdr-1.5.14.tgz vdr-1.5.14-h264-other-rotor.diff vdr-1.5.14-h264-syncearly-framespersec-audioindexer-fielddetection-speedup.diff ./vdr -Protor vdr: ./PLUGINS/lib/libvdr-rotor.so.1.5.14: undefined symbol: _ZN7cDevice13SwitchChannelEPK8cChannelPS_ Could be the mismatch between device.c and device.h in eSetChannelResult SetChannel. I don't know. Hi! Do You solved this problem? I have same situation. AK ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] vdr-rotor support patches for VDR-1.5.14
Morfsta wrote: Nope, I had to roll back to an earlier version of rotor that I patched myself. Cool. Can You share it? I can't live without rotor. AK ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-rotor support patches for VDR-1.5.14
lucian orasanu wrote: I say that i will be tester, so rotor patcheches aply fine and compile only in this order. 1. Rotor patch vdr-1.5.14-h264-other-rotor.diff to vdr-rotor-0.1.4-vdr-1.5 2. Rotor patch vdr-1.5.14-h264-other-rotor.diff to vdr. I tried same order, but got error: g++ -g -O2 -Wall -Woverloaded-virtual -Wno-parentheses -c -DREMOTE_KBD -DLIRC_DEVICE=\/dev/lircd\ -DRCU_DEVICE=\/dev/ttyS1\ -D_GNU_SOURCE -DVIDEODIR=\/video\ -DCONFDIR=\/video\ -DPLUGINDIR=\./PLUGINS/lib\ -DLOCDIR=\/usr/local/src/vdr-1.5.14/locale\ -I/usr/include/freetype2 -I/usr/local/src/multiproto/linux/include device.c device.c:780: error: prototype for ‘eSetChannelResult cDevice::SetChannel(const cChannel*, bool)’ does not match any in class ‘cDevice’ device.h:253: error: candidate is: eSetChannelResult cDevice::SetChannel(const cChannel*, bool, cDevice*) device.c: In member function ‘eSetChannelResult cDevice::SetChannel(const cChannel*, bool)’: device.c:800: error: call of overloaded ‘SetChannel(const cChannel*, bool)’ is ambiguous device.h:253: note: candidates are: eSetChannelResult cDevice::SetChannel(const cChannel*, bool, cDevice*) device.c:780: note: eSetChannelResult cDevice::SetChannel(const cChannel*, bool) make: *** [device.o] Error 1 AK ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-rotor support patches for VDR-1.5.14
Hy.
use this patch too.
--- device.c2008-01-28 10:33:00.0 +
+++ device.c.new2008-01-28 10:32:47.0
+
@@ -790,7 +790,7 @@ bool cDevice::SwitchChannel(int
Directio
return result;
}
-eSetChannelResult cDevice::SetChannel(const cChannel
*Channel, bool LiveView)
+eSetChannelResult cDevice::SetChannel(const cChannel
*Channel, bool LiveView, cDevice
*SpecificSourceDevice)
{
if (LiveView) {
StopReplay();
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now.
http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
vdr-1.5.14a-dvbs2-h264-other-rotor.diff
Description: 2086136847-vdr-1.5.14a-dvbs2-h264-other-rotor.diff
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] vdr-rotor support patches for VDR-1.5.14
I forgot afther that patches 3 Patch vdr-1.5.14-h264-syncearly-framespersec-audioindexer-fielddetection-speedup.diff and compile ok, if i change order 3 first then 2 i get errors above compiling vdr. Luc. Never miss a thing. Make Yahoo your home page. http://www.yahoo.com/r/hs ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] vdr-rotor support patches for VDR-1.5.14
Hy I say that i will be tester, so rotor patcheches aply fine and compile only in this order. 1. Rotor patch vdr-1.5.14-h264-other-rotor.diff to vdr-rotor-0.1.4-vdr-1.5 2. Rotor patch vdr-1.5.14-h264-other-rotor.diff to vdr. and compile ok but I could not testit because i meseed up my xine-lib tryng with core-avc that for me image is worst diferent then ffmpeg. I will post soon news, how i can see from patches now supports dvbs-2 or not? Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [ANNOUNCE] vdr-rotor support patches for VDR-1.5.14
I got the following error when compiling 1.5.14 with h264 patch
applied and your VDR diff from the tgz: -
g++ -g -O2 -Wall -Woverloaded-virtual -Wno-parentheses -c -DREMOTE_KBD
-DLIRC_DEVICE=\/dev/lircd\ -DRCU_DEVICE=\/dev/ttyS1\ -D_GNU_SOURCE
-DVIDEODIR=\/video\ -DCONFDIR=\/video\
-DPLUGINDIR=\./PLUGINS/lib\ -DLOCDIR=\./locale\
-I/usr/include/freetype2 -I/root/multiproto/linux/include device.c
device.c:793: error: prototype for âeSetChannelResult
cDevice::SetChannel(const cChannel*, bool)â does not match any in
class âcDeviceâ
device.h:255: error: candidate is: eSetChannelResult
cDevice::SetChannel(const cChannel*, bool, cDevice*)
device.c: In member function âeSetChannelResult
cDevice::SetChannel(const cChannel*, bool)â:
device.c:813: error: call of overloaded âSetChannel(const cChannel*,
bool)â is ambiguous
device.h:255: note: candidates are: eSetChannelResult
cDevice::SetChannel(const cChannel*, bool, cDevice*)
device.c:793: note: eSetChannelResult
cDevice::SetChannel(const cChannel*, bool)
make: *** [device.o] Error 1
The following patch fixes it: -
--- device.c2008-01-28 10:33:00.0 +
+++ device.c.new2008-01-28 10:32:47.0 +
@@ -790,7 +790,7 @@ bool cDevice::SwitchChannel(int Directio
return result;
}
-eSetChannelResult cDevice::SetChannel(const cChannel *Channel, bool LiveView)
+eSetChannelResult cDevice::SetChannel(const cChannel *Channel, bool
LiveView, cDevice *SpecificSourceDevice)
{
if (LiveView) {
StopReplay();
I'll test the functionality of the new rotor + patches shortly. I had
a brief look through the output, should it now be able to scan DVB-S2
transponders?
Thanks
On Jan 27, 2008 11:05 PM, Reinhard Nissl [EMAIL PROTECTED] wrote:
Hi,
the attached patch is based on these files:
vdr-rotor-0.1.4-vdr1.5.tgz
rotor-0.1.4-vdr-15.12.diff
For simplicity a patched version is attached too.
NOTES:
- I couldn't test with a real rotor device
- I couldn't test with a FF card
Have fun!
Bye.
--
Dipl.-Inform. (FH) Reinhard Nissl
mailto:[EMAIL PROTECTED]
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] vdr-rotor support patches for VDR-1.5.14
Seems that I spoke too soon - I get a problem running rotor on my
system after compilation: -
vdr: ./PLUGINS/lib/libvdr-rotor.so.1.5.14: undefined symbol:
_ZN7cDevice13SwitchChannelEPK8cChannelPS_
Whatever I try I can't seem to fix it. Reverting back to my old
version of rotor works fine.
On Jan 28, 2008 10:34 AM, Morfsta [EMAIL PROTECTED] wrote:
I got the following error when compiling 1.5.14 with h264 patch
applied and your VDR diff from the tgz: -
g++ -g -O2 -Wall -Woverloaded-virtual -Wno-parentheses -c -DREMOTE_KBD
-DLIRC_DEVICE=\/dev/lircd\ -DRCU_DEVICE=\/dev/ttyS1\ -D_GNU_SOURCE
-DVIDEODIR=\/video\ -DCONFDIR=\/video\
-DPLUGINDIR=\./PLUGINS/lib\ -DLOCDIR=\./locale\
-I/usr/include/freetype2 -I/root/multiproto/linux/include device.c
device.c:793: error: prototype for âeSetChannelResult
cDevice::SetChannel(const cChannel*, bool)â does not match any in
class âcDeviceâ
device.h:255: error: candidate is: eSetChannelResult
cDevice::SetChannel(const cChannel*, bool, cDevice*)
device.c: In member function âeSetChannelResult
cDevice::SetChannel(const cChannel*, bool)â:
device.c:813: error: call of overloaded âSetChannel(const cChannel*,
bool)â is ambiguous
device.h:255: note: candidates are: eSetChannelResult
cDevice::SetChannel(const cChannel*, bool, cDevice*)
device.c:793: note: eSetChannelResult
cDevice::SetChannel(const cChannel*, bool)
make: *** [device.o] Error 1
The following patch fixes it: -
--- device.c2008-01-28 10:33:00.0 +
+++ device.c.new2008-01-28 10:32:47.0 +
@@ -790,7 +790,7 @@ bool cDevice::SwitchChannel(int Directio
return result;
}
-eSetChannelResult cDevice::SetChannel(const cChannel *Channel, bool LiveView)
+eSetChannelResult cDevice::SetChannel(const cChannel *Channel, bool
LiveView, cDevice *SpecificSourceDevice)
{
if (LiveView) {
StopReplay();
I'll test the functionality of the new rotor + patches shortly. I had
a brief look through the output, should it now be able to scan DVB-S2
transponders?
Thanks
On Jan 27, 2008 11:05 PM, Reinhard Nissl [EMAIL PROTECTED] wrote:
Hi,
the attached patch is based on these files:
vdr-rotor-0.1.4-vdr1.5.tgz
rotor-0.1.4-vdr-15.12.diff
For simplicity a patched version is attached too.
NOTES:
- I couldn't test with a real rotor device
- I couldn't test with a FF card
Have fun!
Bye.
--
Dipl.-Inform. (FH) Reinhard Nissl
mailto:[EMAIL PROTECTED]
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] vdr-rotor support patches for VDR-1.5.14
I demand that Morfsta may or may not have top-posted... Seems that I spoke too soon - I get a problem running rotor on my system after compilation: - vdr: ./PLUGINS/lib/libvdr-rotor.so.1.5.14: undefined symbol: _ZN7cDevice13SwitchChannelEPK8cChannelPS_ Whatever I try I can't seem to fix it. Reverting back to my old version of rotor works fine. c++filt says cDevice::SwitchChannel(cChannel const*, cDevice*). Maybe you need to recompile something...? [snip; don't top-post] -- | Darren Salt| linux or ds at | nr. Ashington, | Toon | RISC OS, Linux | youmustbejoking,demon,co,uk | Northumberland | Army | URL:http://www.youmustbejoking.demon.co.uk/progs.packages.html I don't suffer from insanity: I enjoy every minute of it. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] vdr-rotor support patches for VDR-1.5.14
On Jan 28, 2008 5:15 PM, Darren Salt [EMAIL PROTECTED] pedantically wrote: c++filt says cDevice::SwitchChannel(cChannel const*, cDevice*). Maybe you need to recompile something...? [snip ; don't top post] Nope, it's all compiled - just doublechecked with fresh source: - vdr-1.5.14 vdr-rotor-0.1.4-vdr-1.5.14.tgz vdr-1.5.14-h264-other-rotor.diff vdr-1.5.14-h264-syncearly-framespersec-audioindexer-fielddetection-speedup.diff ./vdr -Protor vdr: ./PLUGINS/lib/libvdr-rotor.so.1.5.14: undefined symbol: _ZN7cDevice13SwitchChannelEPK8cChannelPS_ Could be the mismatch between device.c and device.h in eSetChannelResult SetChannel. I don't know. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Rotor patch for 1.5.12
Hy Sorry for late reply. I dont know why but when apliing the patch dvbdevice.h not geting patched so i modified manual and now its working. About functionality i wil post later beacause i'am at work. I will be to your tester and 10x again. Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Rotor patch for 1.5.12
Has anyone managed to get the signal strength, SNR and lock functions working with multiproto and rotor 1.5.12? I took a look at menu.c and compared it with szap2 but couldn't find much difference! On Jan 11, 2008 10:21 PM, Reinhard Nissl [EMAIL PROTECTED] wrote: Hi, lucian orasanu schrieb: Hy again! thanks for the patch and cmd line, but afther patching vdr with that patch i get the following error when compiling vdr: dvbdevice.c:946: error: no 'bool cDvbDevice::SendDiseqcCmd(dvb_diseqc_master_cmd)' member function declared in class 'cDvbDevice' Hmm, the patched VDR compiled flawlessly. And the last chunk of the patch adds the function declaration to dvbdevice.h. So I don't see how you can get this error. Are there any other reports? Bye. -- Dipl.-Inform. (FH) Reinhard Nissl mailto:[EMAIL PROTECTED] ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Rotor patch for 1.5.12
On Thursday 10 January 2008, Reinhard Nissl wrote: Hi, lucian orasanu schrieb: it is changed after patch with function above and in menu.c at line 304 is expecting another function like this: SChannel-cChannel::SetSatTransponderData(RotorPos-R_Code(),Frequenz,Pol ,Symbolrate,FEC_AUTO); so i modified this line in menu.c like this: SChannel-cChannel::SetSatTransponderData(RotorPos-R_Code(),Frequenz,Pol ,Symbolrate,Symbolrate,Symbolrate,Symbolrate,Symbolrate); Try changing it to: SChannel-cChannel::SetSatTransponderData(RotorPos-R_Code(),Frequenz,Pol,S ymbolrate,DVBFE_FEC_AUTO,DVBFE_MOD_AUTO,DVBFE_DELSYS_DVBS,DVBFE_ROLLOFF_UNKN OWN); You'll need to apply the attached VDR patch instead of the one included with vdr-rotor. Hi, I've tested it, it seems that it works - but I have motor behind the switch (port D of 4port) and in some cases the dish doesn't went back to east (with SS1, old driver, old rotor, vdr-1.5.12 no such problem detected). In that case I have to switch to channel which is not behind portD and then back to portD and the dish begin to move. I'm using gotoX functionality. I'm using for testing: - Debian Lenny - TT S2-3200 - HH120 - vdr-1.5.13 patched by vdr-1.5.12-dvbs2-h264-syncearly-framespersec-audioindexer-fielddetection-speedup.diff, vdr-1.5.12-speedup-fix1.diff and vdr-1.5.12-speedup-fix2.diff. - rotor version vdr-rotor-0.1.4-vdr1.5.7.tgz patched by Rotor-0.1.4-vdr1.5.10.diff and vdr-1.5.12-dvbs2-h264-other-rotor.diff and with changes of SChannel-cChannel::SetSatTransponderData proposed above by Reinhard. Reinhard, if you agree I'm ready to cooperate in testing. Ales Please keep in mind that I cannot test this patch. The suggested line above will only support DVB-S. For DVB-S2 and H.264 support, a lot more needs to be changed. Bye. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Rotor patch for 1.5.12
On Sunday 13 January 2008, Morfsta wrote: Has anyone managed to get the signal strength, SNR and lock functions working with multiproto and rotor 1.5.12? I took a look at menu.c and compared it with szap2 but couldn't find much difference! Hi, I've tried to pass through the source code and it seems to me that problem is that multiproto driver for dvb-s2 frontend return SNR and STR in 0.1dB and the value is by vdr-rotor (and by vdr-femon) then recalculated to dB once more. Ales ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Rotor patch for 1.5.12
Hy again! thanks for the patch and cmd line, but afther patching vdr with that patch i get the following error when compiling vdr: dvbdevice.c:946: error: no 'bool cDvbDevice::SendDiseqcCmd(dvb_diseqc_master_cmd)' member function declared in class 'cDvbDevice' rotor plugin compile ok! 10x!! for reply and help! Never miss a thing. Make Yahoo your home page. http://www.yahoo.com/r/hs ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-rotor patch for multiproto
I want to ask in another way - Anybody know a way to make work the latest vdr-rotor 0.1.4 with multiproto api, h.264 dvb-s2 patches from Reinhard Nissl on vdr 1.5.12 ? Igor ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] vdr-rotor patch for multiproto
Hi all!!! Anybody know a way to make work vdr-rotor with multiproto api? Byez! _ La mia Cartella di Posta in Arrivo è protetta con SPAMfighter 182 messaggi contenenti spam sono stati bloccati con successo. Scarica gratuitamente SPAMfighter http://www.spamfighter.com/lit ! ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Rotor patch for 1.5.12
Hi, lucian orasanu schrieb: Hy again! thanks for the patch and cmd line, but afther patching vdr with that patch i get the following error when compiling vdr: dvbdevice.c:946: error: no 'bool cDvbDevice::SendDiseqcCmd(dvb_diseqc_master_cmd)' member function declared in class 'cDvbDevice' Hmm, the patched VDR compiled flawlessly. And the last chunk of the patch adds the function declaration to dvbdevice.h. So I don't see how you can get this error. Are there any other reports? Bye. -- Dipl.-Inform. (FH) Reinhard Nissl mailto:[EMAIL PROTECTED] ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-rotor patch for multiproto
Hi, Igor schrieb: I want to ask in another way - Anybody know a way to make work the latest vdr-rotor 0.1.4 with multiproto api, h.264 dvb-s2 patches from Reinhard Nissl on vdr 1.5.12 ? I'll give it a try this weekend (most likely). Testers are welcome as I do not own a rotor. Regarding the VDR patch which is needed for rotor: please have a look at the patch which I released yesterday (see other thread) and tell me whether it works for DVB-S. Bye. -- Dipl.-Inform. (FH) Reinhard Nissl mailto:[EMAIL PROTECTED] ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Rotor patch for 1.5.12
Hy. Afther aplyng the patch from you stil cant compile i get the following error: menu.c:304: error: no matching function for call to 'cChannel::SetSatTransponderData(int, int, char, int, fe_code_rate)' ../../..//include/vdr/channels.h:231: note: candidates are: bool cChannel::SetSatTransponderData(int, int, char, int, int, int, int, int) menu.c:316: error: no matching function for call to 'cChannel::SetSatTransponderData(int, int, char, int, fe_code_rate)' ../../..//include/vdr/channels.h:231: note: candidates are: bool cChannel::SetSatTransponderData(int, int, char, int, int, int, int, int) I use vdr-1.5.12 patched with dvb-s2 suppor. It seams in vdr/channels.h at line 231 this function: bool SetSatTransponderData(int Source, int Frequency, char Polarization, int Srate, int CoderateH, int Modulation, int ModulationSystem, int RollOff); it is changed afther patch with function above and in menu.c at line 304 is expecting another function like this: SChannel-cChannel::SetSatTransponderData(RotorPos-R_Code(),Frequenz,Pol,Symbolrate,FEC_AUTO); so i modified this line in menu.c like this: SChannel-cChannel::SetSatTransponderData(RotorPos-R_Code(),Frequenz,Pol,Symbolrate,Symbolrate,Symbolrate,Symbolrate,Symbolrate); it compile but is not working because functios is not ok, i dont know any coding and i think is because of dvb-s2 api. Could somebody telme right functions. Looking for last minute shopping deals? Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Rotor patch for 1.5.12
Hi,
lucian orasanu schrieb:
it is changed after patch with function above and in
menu.c at line 304 is expecting another function like
this:
SChannel-cChannel::SetSatTransponderData(RotorPos-R_Code(),Frequenz,Pol,Symbolrate,FEC_AUTO);
so i modified this line in menu.c like this:
SChannel-cChannel::SetSatTransponderData(RotorPos-R_Code(),Frequenz,Pol,Symbolrate,Symbolrate,Symbolrate,Symbolrate,Symbolrate);
Try changing it to:
SChannel-cChannel::SetSatTransponderData(RotorPos-R_Code(),Frequenz,Pol,Symbolrate,DVBFE_FEC_AUTO,DVBFE_MOD_AUTO,DVBFE_DELSYS_DVBS,DVBFE_ROLLOFF_UNKNOWN);
You'll need to apply the attached VDR patch instead of the one
included with vdr-rotor.
Please keep in mind that I cannot test this patch. The suggested
line above will only support DVB-S. For DVB-S2 and H.264 support,
a lot more needs to be changed.
Bye.
--
Dipl.-Inform. (FH) Reinhard Nissl
mailto:[EMAIL PROTECTED]
--- ../vdr-1.5.12-dvbs2-other/device.h 2007-10-21 11:21:52.0 +0200
+++ device.h 2008-01-10 22:09:12.0 +0100
@@ -23,6 +23,7 @@
#include spu.h
#include thread.h
#include tools.h
+#include linux/dvb/frontend.h
#define MAXDEVICES 16 // the maximum number of devices in the system
#define MAXPIDHANDLES 64 // the maximum number of different PIDs per device
@@ -261,6 +266,7 @@ public:
virtual bool HasProgramme(void);
/// Returns true if the device is currently showing any programme to
/// the user, either through replaying or live.
+ virtual bool SendDiseqcCmd(dvb_diseqc_master_cmd cmd) {return false;}
// PID handle facilities
--- ../vdr-1.5.12-dvbs2-other/dvbdevice.c 2008-01-01 22:55:18.0 +0100
+++ dvbdevice.c 2008-01-10 22:13:39.0 +0100
@@ -71,6 +71,7 @@ static int DvbOpen(const char *Name, int
class cDvbTuner : public cThread {
private:
enum eTunerStatus { tsIdle, tsSet, tsTuned, tsLocked };
+ bool SendDiseqc;
int fd_frontend;
int cardIndex;
int tuneTimeout;
@@ -83,6 +84,7 @@ private:
cMutex mutex;
cCondVar locked;
cCondVar newSet;
+ dvb_diseqc_master_cmd diseqc_cmd;
bool GetFrontendStatus(fe_status_t Status, int TimeoutMs = 0);
bool SetFrontend(void);
virtual void Action(void);
@@ -91,12 +93,14 @@ public:
virtual ~cDvbTuner();
bool IsTunedTo(const cChannel *Channel) const;
void Set(const cChannel *Channel, bool Tune);
+ bool SendDiseqcCmd(dvb_diseqc_master_cmd cmd);
bool Locked(int TimeoutMs = 0);
};
cDvbTuner::cDvbTuner(int Fd_Frontend, int CardIndex, dvbfe_delsys FrontendType)
{
fd_frontend = Fd_Frontend;
+ SendDiseqc = false;
cardIndex = CardIndex;
frontendType = FrontendType;
tuneTimeout = 0;
@@ -145,6 +149,17 @@ bool cDvbTuner::Locked(int TimeoutMs)
return tunerStatus = tsLocked;
}
+bool cDvbTuner::SendDiseqcCmd(dvb_diseqc_master_cmd cmd)
+{
+ cMutexLock MutexLock(mutex);
+ if (!(frontendType (DVBFE_DELSYS_DVBS | DVBFE_DELSYS_DVBS2)) || SendDiseqc)
+return false;
+ diseqc_cmd=cmd;
+ SendDiseqc=true;
+ newSet.Broadcast();
+ return true;
+}
+
bool cDvbTuner::GetFrontendStatus(fe_status_t Status, int TimeoutMs)
{
if (TimeoutMs) {
@@ -348,6 +363,10 @@ void cDvbTuner::Action(void)
if (GetFrontendStatus(NewStatus, 10))
Status = NewStatus;
cMutexLock MutexLock(mutex);
+if (SendDiseqc) {
+ CHECK(ioctl(fd_frontend, FE_DISEQC_SEND_MASTER_CMD, diseqc_cmd));
+ SendDiseqc=false;
+ }
switch (tunerStatus) {
case tsIdle:
break;
@@ -918,6 +950,11 @@ bool cDvbDevice::HasLock(int TimeoutMs)
return dvbTuner ? dvbTuner-Locked(TimeoutMs) : false;
}
+bool cDvbDevice::SendDiseqcCmd(dvb_diseqc_master_cmd cmd)
+{
+ return dvbTuner-SendDiseqcCmd(cmd);
+}
+
int cDvbDevice::GetAudioChannelDevice(void)
{
if (HasDecoder()) {
--- ../vdr-1.5.12-dvbs2-other/dvbdevice.h 2008-01-01 22:55:18.0 +0100
+++ dvbdevice.h 2008-01-10 22:09:12.0 +0100
@@ -66,11 +67,13 @@ public:
virtual bool SetChannelDevice(const cChannel *Channel, bool LiveView);
public:
virtual bool HasLock(int TimeoutMs = 0);
+ virtual bool SendDiseqcCmd(dvb_diseqc_master_cmd cmd);
// PID handle facilities
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Rotor patch for 1.5.12
Did you had to adapt manually the patch, because when i try this patch on vdr 1.5.12 everything is rejected ? Thanks, serge -Oorspronkelijk bericht- Van: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Namens Arthur Konovalov Verzonden: maandag 7 januari 2008 20:57 Aan: VDR Mailing List Onderwerp: Re: [vdr] Rotor patch for 1.5.12 [EMAIL PROTECTED] wrote: I am looking for the patch to compile the rotor plugin together with vdr-1.5.12. Does anyone achieved to compile it with 1.5.12 I had success with attached patch. Regards, AK ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Rotor patch for 1.5.12
serge pecher wrote:
Did you had to adapt manually the patch, because when i try this patch on
vdr 1.5.12 everything is rejected ?
Previosly mentioned patch applied to attached version of rotor plugin.
I suspect that I found it in vdr-portal.de
Fresh generated patch attached also.
Regards,
AK
vdr-rotor-0.1.4-vdr1.5.tgz
Description: application/compressed
diff -Nur old/filter.c new/filter.c
--- old/filter.c2006-01-09 22:41:50.0 +0200
+++ new/filter.c2007-10-16 08:21:54.0 +0300
@@ -368,12 +368,15 @@
int Ppid = pmt.getPCRPid();
int Apids[MAXAPIDS + 1] = { 0 };
int Dpids[MAXDPIDS + 1] = { 0 };
+int Spids[MAXDPIDS + 1] = { 0 };
#if VDRVERSNUM = 10332
char ALangs[MAXAPIDS + 1][MAXLANGCODE2] = { };
char DLangs[MAXDPIDS + 1][MAXLANGCODE2] = { };
+char SLangs[MAXDPIDS + 1][MAXLANGCODE2] = { };
#else
char ALangs[MAXAPIDS + 1][4] = { };
char DLangs[MAXDPIDS + 1][4] = { };
+char SLangs[MAXDPIDS + 1][4] = { };
#endif
int Tpid = 0;
int NumApids = 0;
@@ -448,7 +451,7 @@
delete d;
}
}
-Menu-SetPids(pmt.getServiceId(),Vpid, Vpid ? Ppid : 0, Apids, ALangs,
Dpids, DLangs, Tpid);
+Menu-SetPids(pmt.getServiceId(),Vpid, Vpid ? Ppid : 0, Apids, ALangs,
Dpids, DLangs, Spids, SLangs, Tpid);
Menu-SetCaIds(pmt.getServiceId(),CaDescriptors-CaIds());
Menu-SetCaDescriptors(pmt.getServiceId(),CaDescriptorHandler.AddCaDescriptors(CaDescriptors));
}
diff -Nur old/menu.c new/menu.c
--- old/menu.c 2007-07-06 23:52:57.0 +0300
+++ new/menu.c 2007-10-16 08:21:54.0 +0300
@@ -406,12 +406,15 @@
channel-SetId(Channel[Num].Nid(),Channel[Num].Tid(),Channel[Num].Sid(),channel-Rid());
int Apids[MAXAPIDS + 1] = { 0 };
int Dpids[MAXDPIDS + 1] = { 0 };
+int Spids[MAXDPIDS + 1] = { 0 };
#if VDRVERSNUM=10332
char ALangs[MAXAPIDS + 1][MAXLANGCODE2] = { };
char DLangs[MAXDPIDS + 1][MAXLANGCODE2] = { };
+char SLangs[MAXDPIDS + 1][MAXLANGCODE2] = { };
#else
char ALangs[MAXAPIDS + 1][4] = { };
char DLangs[MAXDPIDS + 1][4] = { };
+char SLangs[MAXDPIDS + 1][4] = { };
#endif
int CaIds[MAXCAIDS+1] = { 0 };
for (int i=0; i=MAXAPIDS; i++)
@@ -426,7 +429,7 @@
}
for (int i=0; i=MAXCAIDS; i++)
CaIds[i]=Channel[Num].Ca(i);
-
channel-SetPids(Channel[Num].Vpid(),Channel[Num].Ppid(),Apids,ALangs,Dpids,DLangs,Channel[Num].Tpid());
+
channel-SetPids(Channel[Num].Vpid(),Channel[Num].Ppid(),Apids,ALangs,Dpids,DLangs,Spids,SLangs,Channel[Num].Tpid());
channel-SetCaIds(CaIds);
}
else
@@ -456,7 +459,7 @@
}
#if VDRVERSNUM=10332
-void cMenuScan::SetPids(int Sid,int Vpid, int Ppid, int *Apids, char
ALangs[][MAXLANGCODE2], int *Dpids, char DLangs[][MAXLANGCODE2], int Tpid)
+void cMenuScan::SetPids(int Sid,int Vpid, int Ppid, int *Apids, char
ALangs[][MAXLANGCODE2], int *Dpids, char DLangs[][MAXLANGCODE2], int *Spids,
char SLangs[][MAXLANGCODE2], int Tpid)
#else
void cMenuScan::SetPids(int Sid,int Vpid, int Ppid, int *Apids, char
ALangs[][4], int *Dpids, char DLangs[][4], int Tpid)
#endif
@@ -464,7 +467,7 @@
for (int i=0; inum; i++)
if (Sid==Channel[i].Sid())
{
- Channel[i].SetPids(Vpid,Ppid,Apids,ALangs,Dpids,DLangs,Tpid);
+
Channel[i].SetPids(Vpid,Ppid,Apids,ALangs,Dpids,DLangs,Spids,SLangs,Tpid);
display(i);
}
}
diff -Nur old/menu.h new/menu.h
--- old/menu.h 2007-07-06 23:57:42.0 +0300
+++ new/menu.h 2007-10-16 08:21:54.0 +0300
@@ -116,7 +116,7 @@
virtual eOSState ProcessKey(eKeys Key);
void AddChannel(int Num);
void NewChannel(const cChannel *Transponder, const char *Name, const char
*ShortName, const char *Provider, int Nid, int Tid, int Sid);
- void SetPids(int Sid,int Vpid, int Ppid, int *Apids, char
ALangs[][MAXLANGCODE2], int *Dpids, char DLangs[][MAXLANGCODE2], int Tpid);
+ void SetPids(int Sid,int Vpid, int Ppid, int *Apids, char
ALangs[][MAXLANGCODE2], int *Dpids, char DLangs[][MAXLANGCODE2], int *Spids,
char SLangs[][MAXLANGCODE2], int Tpid);
void SetCaIds(int Sid,const int *CaIds);
void SetCaDescriptors(int Sid,int Level);
cChannel* GetChannel(int Sid);
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Rotor plugin crashing with valid data in diseqc.conf
Any more ideas on this? Not sure why rotor plugin would even need to look at
the diseqc.conf. For moving the dish on channel switch, it can get the sat
location from the 4th entry in the channels.conf. Why would it need to deal
with diseqc commands in the diseqc.conf when it was fine with them before?
Anything chang in 1.5.x that would require a change like this? because the
plugin is crashing the same way with 1.4.6. So it must have somthing to do
with changes to make it work with 1.5.x
- Original Message -
From: Igor [EMAIL PROTECTED]
To: VDR Mailing List vdr@linuxtv.org
Sent: Friday, September 21, 2007 2:40 AM
Subject: Re: [vdr]Rotor plugin crashing with valid data in diseqc.conf
Built a new system with an Athlon64 x2 running and64 linux. I went with
vdr-1.5.9. I tried to use the diseqc.conf from my old system, but vdr
crashes in startup when the rotor plugin is used. I found the problem
seems
to be the use of commands to control the rotor in the diseqc.conf. with
[E0
31 6B 26] and rotor plugin, vdr crashes at startup. remove ether the
rotor
plugin or all [E0 31 6B xx] entries and it starts. I used the vdr-1.5.5
patch in the patches folder of rotor.
may be the logs in syslog from rotor plugin will help to you. For this you
need to use this path
--- 1/dvbdevice.c 2007-09-07 21:54:12.0 +0200
+++ 2/dvbdevice.c 2007-09-10 18:52:42.0 +0200
@@ -168,6 +168,7 @@
dvb_frontend_event Event;
while (ioctl(fd_frontend, FE_GET_EVENT, Event) == 0)
; // just to clear the event queue - we'll read the actual
status below
+ isyslog(Rotor-command %X %X %X %X %X
sent,diseqc_cmd.msg[0],diseqc_cmd.msg[1],diseqc_cmd.msg[2],diseqc_cmd.msg[3
],diseqc_cmd.msg[4]);/*MIROHA*/
}
}
while (1) {
Igor
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Rotor plugin crashing with valid dat a in diseqc.conf
Built a new system with an Athlon64 x2 running and64 linux. I went with
vdr-1.5.9. I tried to use the diseqc.conf from my old system, but vdr
crashes in startup when the rotor plugin is used. I found the problem seems
to be the use of commands to control the rotor in the diseqc.conf. with [E0
31 6B 26] and rotor plugin, vdr crashes at startup. remove ether the rotor
plugin or all [E0 31 6B xx] entries and it starts. I used the vdr-1.5.5
patch in the patches folder of rotor.
may be the logs in syslog from rotor plugin will help to you. For this you need
to use this path
--- 1/dvbdevice.c 2007-09-07 21:54:12.0 +0200
+++ 2/dvbdevice.c 2007-09-10 18:52:42.0 +0200
@@ -168,6 +168,7 @@
dvb_frontend_event Event;
while (ioctl(fd_frontend, FE_GET_EVENT, Event) == 0)
; // just to clear the event queue - we'll read the actual
status below
+ isyslog(Rotor-command %X %X %X %X %X
sent,diseqc_cmd.msg[0],diseqc_cmd.msg[1],diseqc_cmd.msg[2],diseqc_cmd.msg[3],diseqc_cmd.msg[4]);/*MIROHA*/
}
}
while (1) {
Igor
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Rotor plugin crashing with valid data in diseqc.conf
Applied the patch and started with the problem conf. Not much help. Only
mention I found of any problem was in the syslog:
Sep 21 15:38:59 x64VDR vdr: [20139] starting plugin: dvd
Sep 21 15:38:59 x64VDR vdr: [20139] starting plugin: femon
Sep 21 15:38:59 x64VDR vdr: [20139] starting plugin: weatherng
Sep 21 15:38:59 x64VDR vdr: [20139] plugin 'weatherng' called obsolete
function RegisterI18n()
Sep 21 15:38:59 x64VDR vdr: [20139] starting plugin: rotor
Sep 21 15:38:59 x64VDR vdr: [20139] plugin 'rotor' called obsolete function
RegisterI18n()
Sep 21 15:38:59 x64VDR vdr: [20139] loading /etc/vdr/plugins/rotor.conf
Sep 21 15:38:59 x64VDR vdr: [20150] CI adapter on device 0 thread started
(pid=20139, tid=20150)
Sep 21 15:38:59 x64VDR vdr: [20153] EPGSearch: conflictcheck thread started
(pid=20139, tid=20153)
The Weatherng plugin, thoug showing the same error, seems ok.
- Original Message -
From: Igor [EMAIL PROTECTED]
To: VDR Mailing List vdr@linuxtv.org
Sent: Friday, September 21, 2007 2:40 AM
Subject: Re: [vdr]Rotor plugin crashing with valid data in diseqc.conf
may be the logs in syslog from rotor plugin will help to you. For this you
need to use this path
--- 1/dvbdevice.c 2007-09-07 21:54:12.0 +0200
+++ 2/dvbdevice.c 2007-09-10 18:52:42.0 +0200
@@ -168,6 +168,7 @@
dvb_frontend_event Event;
while (ioctl(fd_frontend, FE_GET_EVENT, Event) == 0)
; // just to clear the event queue - we'll read the actual
status below
+ isyslog(Rotor-command %X %X %X %X %X
sent,diseqc_cmd.msg[0],diseqc_cmd.msg[1],diseqc_cmd.msg[2],diseqc_cmd.msg[3
],diseqc_cmd.msg[4]);/*MIROHA*/
}
}
while (1) {
Igor
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Rotor plugin crashing with valid data in diseqc.conf
Built a new system with an Athlon64 x2 running and64 linux. I went with vdr-1.5.9. I tried to use the diseqc.conf from my old system, but vdr crashes in startup when the rotor plugin is used. I found the problem seems to be the use of commands to control the rotor in the diseqc.conf. with [E0 31 6B 26] and rotor plugin, vdr crashes at startup. remove ether the rotor plugin or all [E0 31 6B xx] entries and it starts. I used the vdr-1.5.5 patch in the patches folder of rotor. Starting VDR - Linux Video Disk Recorder: runvdr. *** glibc detected *** /usr/local/bin/vdr: munmap_chunk(): invalid pointer: 0x05613804 *** === Backtrace: = /lib/libc.so.6(cfree+0x1b6)[0x2aff4f3486b6] /usr/local/bin/PLUGINS/lib/libvdr-rotor.so.1.5.9(_ZN12cPluginRotor5StartEv+0 x299)[0x2aff53aac659] /usr/local/bin/vdr(_ZN14cPluginManager12StartPluginsEv+0x5d)[0x49bc6d] /usr/local/bin/vdr(main+0x1496)[0x4cd626] /lib/libc.so.6(__libc_start_main+0xf4)[0x2aff4f2f0b44] /usr/local/bin/vdr(__gxx_personality_v0+0x229)[0x44b849] === Memory map: 0040-0052d000 r-xp 03:01 1736706 /usr/local/bin/vdr 0072c000-0073 rw-p 0012c000 03:01 1736706 /usr/local/bin/vdr 0073-0562b000 rw-p 0073 00:00 0 [heap] 4000-40001000 ---p 4000 00:00 0 40001000-40801000 rw-p 40001000 00:00 0 40801000-40802000 ---p 40801000 00:00 0 40802000-41002000 rw-p 40802000 00:00 0 41002000-41003000 ---p 41002000 00:00 0 41003000-41803000 rw-p 41003000 00:00 0 41803000-41804000 ---p 41803000 00:00 0 41804000-42004000 rw-p 41804000 00:00 0 42004000-42005000 ---p 42004000 00:00 0 42005000-42805000 rw-p 42005000 00:00 0 42805000-42806000 ---p 42805000 00:00 0 42806000-43006000 rw-p 42806000 00:00 0 2c00-2c021000 rw-p 2c00 00:00 0 2c021000-2aaab000 ---p 2c021000 00:00 0 2aff4de26000-2aff4de43000 r-xp 03:01 819205 /lib/ld-2.6.1.so 2aff4de43000-2aff4de46000 rw-p 2aff4de43000 00:00 0 2aff4de46000-2aff4df7e000 r--p 03:01 1281421 /usr/lib/locale/locale-archive 2aff4e042000-2aff4e044000 rw-p 0001c000 03:01 819205 /lib/ld-2.6.1.so 2aff4e044000-2aff4e065000 r-xp 03:01 1262770 /usr/lib/libjpeg.so.62.0.0 ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Rotor plugin give Seg Fault -- need help!
mlists wrote:
Hi there, trying to set up the Rotor plugin but running into issues.
When I fire up VDR 1.4.4 with my Twinhan 1020a card, and a diseqc rotor
with GOTOX, I can go to the configure menu for the plugin rotor, but
when I select rotor from the main menu, vdr immediately seg faults and
stops.
Has anyone seen this, and if so, is there a fix to the problem?
Please try the attached patch.
--
Anssi Hannula
--- rotor.c.old 2006-06-14 23:44:27.0 +0200
+++ rotor.c 2006-06-14 23:46:43.0 +0200
@@ -96,7 +96,8 @@
continue;
if ((diseqc=Diseqcs.Get(source-Code(),12000,'h')) || (diseqc=Diseqcs.Get(source-Code(),12000,'v')) || (diseqc=Diseqcs.Get(source-Code(),12000,'l')) || (diseqc=Diseqcs.Get(source-Code(),12000,'r')))
{
- char *c=strdup(diseqc-Commands());
+ char *commandstring=strdup(diseqc-Commands());
+ char *c=commandstring;
while (c = strchr(c, '['))
{
char *e = strchr(++c, ']');
@@ -131,7 +132,7 @@
break;
}
}
- free(c);
+ free(commandstring);
}
cRotorPos *p = RotorPositions.GetfromSource(source-Code());
if (p==RotorPositions.First())___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Rotor plugin give Seg Fault -- need help!
Hi there, trying to set up the Rotor plugin but running into issues. When I fire up VDR 1.4.4 with my Twinhan 1020a card, and a diseqc rotor with GOTOX, I can go to the configure menu for the plugin rotor, but when I select rotor from the main menu, vdr immediately seg faults and stops. Has anyone seen this, and if so, is there a fix to the problem? Thanks Norm ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
