Re: [vdr] sxfe and vsync

[jjtt]

On Sat, Dec 24, 2011 at 12:14:05PM +0100, Nicolas Huillard wrote:
> I have the same issue on SandyBridge (vdr 1.7.22-1~ctvdr2,
> xineliboutput-sxfe 1.0.7+cvs20111211.1625-1).
> Are there some news since then ?

I built a new SandyBridge-based VDR-machine last May and
was sorely disappointed by the intel video drivers. My
initial solution was an old nvidia card, but about a month
ago I finally found a tear-free combination of drivers
and settings.

.xine/config_xineliboutput:
video.output.opengl_renderer:2D_Tex

vdr-sxfe --video=opengl

I run a gentoo system and the following versions are
propably relevant:

x11-drivers/xf86-video-intel-2.17.0-r3
media-libs/xine-lib-1.2.

Vdr is 1.7.22, xineliboutput is from cvs and I do not
use compositing or even a window manager.


HTH and YMMV

-- 
Juho Törmä

___
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

[ilia mane]

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  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/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