Thanks for the link, now I've finally got the correct version:).
I am using 2 DVB cards, it can be adjusted in some way that certain device is being addressed?
2010/2/4 Ales Jurik ajurik@quick.cz:
On Thursday 04 of February 2010, Bikalexander wrote:
Even with last patch does not do it:
Which exactly version of patch did you use? What was the output of patching? Was there any rejects? Did you try to patch vanilla version of vdr? Without these basic information people could only guess what happened in your vdr.
For me now it works without problem (latest patch is in http://www.linuxtv.org/pipermail/vdr/2010-January/022017.html).
Ales
On Friday 05 of February 2010, Bikalexander wrote:
Thanks for the link, now I've finally got the correct version:).
I am using 2 DVB cards, it can be adjusted in some way that certain device is being addressed?
AFAIK not. But you are welcomed to improve this patch.
BR,
Ales
Why not using rotor plugin?
It's working ok even with 1.7.11, but there's a bug with my s2-3200. I don't know if it's a HW or SW bug, but if I am on a High Band transponder (22khz is active) the rotor doesn't move, so I have to switch to a low band transponder first. Workround would be to disable 22khz in the plugin automatically then rotate und reactive it again (if it has been active before). But I don't know how to implement that
regards
Newspaperman
--- Bikalexander bikalexander@gmail.com schrieb am Fr, 5.2.2010:
Von: Bikalexander bikalexander@gmail.com Betreff: [vdr] Fwd: GOTOX patch for 1.7.5 An: vdr@linuxtv.org Datum: Freitag, 5. Februar 2010, 2:17 Thanks for the link, now I've finally got the correct version:).
I am using 2 DVB cards, it can be adjusted in some way that certain device is being addressed?
2010/2/4 Ales Jurik ajurik@quick.cz:
On Thursday 04 of February 2010, Bikalexander wrote:
Even with last patch does not do it:
Which exactly version of patch did you use? What was
the output of patching?
Was there any rejects? Did you try to patch vanilla
version of vdr? Without
these basic information people could only guess what
happened in your vdr.
For me now it works without problem (latest patch is
in
http://www.linuxtv.org/pipermail/vdr/2010-January/022017.html).
Ales
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
__________________________________________________ Do You Yahoo!? Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen Massenmails. http://mail.yahoo.com
On Fri, 2010-02-05 at 08:47 +0000, Newsy Paper wrote:
Why not using rotor plugin?
It's working ok even with 1.7.11, but there's a bug with my s2-3200. I don't know if it's a HW or SW bug, but if I am on a High Band transponder (22khz is active) the rotor doesn't move, so I have to switch to a low band transponder first. Workround would be to disable 22khz in the plugin automatically then rotate und reactive it again (if it has been active before). But I don't know how to implement that
This is why originally made the patch (thanks for rotor plugin author for lot's of useful code). I got fed up to unreliable operation and messing up of channels.conf with similar frequencies from other positions. As an example I don't need gotox command repeat any more. Even with gotox repeat I got large error probability.
For a vdr plugin I could not find a way to merge the operations properly to other diseqc operations while ensuring compliance with diseqc spec.
I'd separate rotor plugin to a generic channel scan plugin, that it is doing nicely.
Retrieve (and store position) system of elder motors should be in the core vdr dvb-s support as well IMHO. The same timing hazard is potentially there too unless retrieve position is handwritten to diseqc.conf sequences.
BR, Seppo
regards
Newspaperman
--- Bikalexander bikalexander@gmail.com schrieb am Fr, 5.2.2010:
Von: Bikalexander bikalexander@gmail.com Betreff: [vdr] Fwd: GOTOX patch for 1.7.5 An: vdr@linuxtv.org Datum: Freitag, 5. Februar 2010, 2:17 Thanks for the link, now I've finally got the correct version:).
I am using 2 DVB cards, it can be adjusted in some way that certain device is being addressed?
2010/2/4 Ales Jurik ajurik@quick.cz:
On Thursday 04 of February 2010, Bikalexander wrote:
Even with last patch does not do it:
Which exactly version of patch did you use? What was
the output of patching?
Was there any rejects? Did you try to patch vanilla
version of vdr? Without
these basic information people could only guess what
happened in your vdr.
For me now it works without problem (latest patch is
in
http://www.linuxtv.org/pipermail/vdr/2010-January/022017.html).
Ales
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Do You Yahoo!? Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen Massenmails. http://mail.yahoo.com
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
En/na Seppo Ingalsuo ha escrit:
This is why originally made the patch (thanks for rotor plugin author for lot's of useful code). I got fed up to unreliable operation and messing up of channels.conf with similar frequencies from other positions.
Yes, unfortunately a plugin has currently no way to indicate that tuning is currently impossible because the dish is moving. In the actuator plugin I disable the auto-update of channels while the dish is moving and restore the previous setting afterwards, but that isn't 100% reliable and doesn't help with the detection of dvb subtitles (which fails when the dish moves).
Bye
-
Ales Jurik -
Bikalexander -
Luca Olivetti -
Newsy Paper -
Seppo Ingalsuo