vdr

vdr@linuxtv.org

2 participants
6731 discussions

vdr-sxfe: no reaction to enter key, external keyboard works fine
by cedric.dewijs＠telfort.nl 12 Jan '12

12 Jan '12

Hi All, I have installed vdr on 2 laptops and a desktop. On my laptop and the desktop it works OK, but on the laptop of my girlfriend vdr-sxfe does not respond to the enter key. When we connect an external keyboard to the laptop, the enter key works as expected. What can I do to investigate this? Best regards, Cedric

1 0

vdr-sxfe only starts every other time
by cedric.dewijs＠telfort.nl 12 Jan '12

12 Jan '12

Hi All, I have just finished installing my new vdr server. I have followed the following instructions: https://wiki.archlinux.org/index.php/VDR https://wiki.archlinux.org/index.php/Digitenne When I start vdr-sxfe the first time, it hangs. When I then kill it, and then restart it, it works fine. When I then exit it, and start it again, it hangs. then I kill it again, and start it again. Then it works fine again. In short, only attemps 2,4,6 and so on are successfull, 1,3,5,7 hangs On a failed run I see this in the console: [cedric@myhost ~]$ vdr-sxfe 127.0.0.1 vdr-sxfe 1.0.90-cvs (build with xine-lib 1.2.0, using xine-lib 1.2.0) VDR Server: 127.0.0.1 WARNING: MRL does not start with 'xvdr:' (127.0.0.1) vo_vdpau: Can't create vdp device : No vdpau implementation. libva: VA-API version 0.32.0 Xlib: extension "XFree86-DRI" missing on display ":0". libva: va_getDriverName() returns 0 libva: Trying to open /usr/lib/dri/nvidia_drv_video.so libva: va_openDriver() returns -1 ^C On a successfull run I see this: [cedric@myhost ~]$ vdr-sxfe 127.0.0.1 vdr-sxfe 1.0.90-cvs (build with xine-lib 1.2.0, using xine-lib 1.2.0) VDR Server: 127.0.0.1 WARNING: MRL does not start with 'xvdr:' (127.0.0.1) vo_vdpau: Can't create vdp device : No vdpau implementation. libva: VA-API version 0.32.0 Xlib: extension "XFree86-DRI" missing on display ":0". libva: va_getDriverName() returns 0 libva: Trying to open /usr/lib/dri/nvidia_drv_video.so libva: va_openDriver() returns -1 ^C [cedric@myhost ~]$ vdr-sxfe 127.0.0.1 vdr-sxfe 1.0.90-cvs (build with xine-lib 1.2.0, using xine-lib 1.2.0) VDR Server: 127.0.0.1 WARNING: MRL does not start with 'xvdr:' (127.0.0.1) vo_vdpau: Can't create vdp device : No vdpau implementation. [995] [input_vdr] Connecting (control) to tcp://127.0.0.1:37890 ... [995] [input_vdr] Server greeting: VDR-1.7.22 xineliboutput-1.0.90-cvs READY My versions: $ pacman -Qm oscam 1.10-1 ttf-vdrsymbols 20100612-1 vdr 1.7.22-3 vdr-plugin-sc-hg 574-2 vdr-plugin-xineliboutput-git 20111215-2 xine-lib-1.2 20120103-1 Any idea's? Best regards, Cedric

1 0

[PATCH] GOTOXX patch for vdr-1.7.22
by Ales Jurik 11 Jan '12

11 Jan '12

Hi all, here is patch for using motor with vdr-1.7.22. As the diseqc subsystem changed quite a lot in 1.7.22 please report any problem. I'm using/testing it together with vtuner devices (NessieDVB) and cascade of diseqc switches: 1. DVB device: vtuner(PC) <-> LAN <-> NessieDVB <-> motor <-> uncomm.switch <-> comm. switch) 2. DVB device: vtuner(PC) <-> LAN <-> NessieDVB <-> uncomm.switch <-> comm. switch) I'm using it together with VDR capability of dedicated and undedicated sources to some cards and it works for me without problems. I do not have possibility to test it together with real DVB cards inside PC, so any remarks are welcomed. My diseqc.conf looks like: # ONLY SWITCHES 1 2: S19.2E 11700 V 9750 t v W30 [E0 10 39 F0] W30 [E0 10 38 F0] W30 t S19.2E 99999 V 10600 t v W30 [E0 10 39 F0] W30 [E0 10 38 F1] W30 T S19.2E 11700 H 9750 t V W30 [E0 10 39 F0] W30 [E0 10 38 F2] W30 t S19.2E 99999 H 10600 t V W30 [E0 10 39 F0] W30 [E0 10 38 F3] W30 T S13.0E 11700 V 9750 t v W30 [E0 10 39 F0] W30 [E0 10 38 F4] W30 t S13.0E 99999 V 10600 t v W30 [E0 10 39 F0] W30 [E0 10 38 F5] W30 T S13.0E 11700 H 9750 t V W30 [E0 10 39 F0] W30 [E0 10 38 F6] W30 t S13.0E 99999 H 10600 t V W30 [E0 10 39 F0] W30 [E0 10 38 F7] W30 T .... # MOTOR + SWITCHES 1: S1.0W 11700 V 9750 t V G [E0 10 39 F1] v W30 [E0 10 38 FC] W30 v t S1.0W 99999 V 10600 t V G [E0 10 39 F1] v W30 [E0 10 38 FD] W30 v T S1.0W 11700 H 9750 t V G [E0 10 39 F1] V W30 [E0 10 38 FE] W30 V t S1.0W 99999 H 10600 t V G [E0 10 39 F1] V W30 [E0 10 38 FF] W30 V T S9.0E 11700 V 9750 t V G [E0 10 39 F1] v W30 [E0 10 38 FC] W30 v t S9.0E 99999 V 10600 t V G [E0 10 39 F1] v W30 [E0 10 38 FD] W30 v T S9.0E 11700 H 9750 t V G [E0 10 39 F1] V W30 [E0 10 38 FE] W30 V t S9.0E 99999 H 10600 t V G [E0 10 39 F1] V W30 [E0 10 38 FF] W30 V T .... Enjoy, Ales

1 1

[PATCH v2] multi-frontend-support for vdr 1.7.21
by L. Hanisch 08 Jan '12

08 Jan '12

Hi, Here's version 2 of my multi-frontend-patch. It's still "dirty", since it changes the constructor of cDvbDevice which will break compilation of some plugins. But I think it might be necessary to look at the relevant plugins since they might need to react on frontend changes. I haven't tested any of those plugins but will have a look at some that I'm using. Maybe there have to be some virtual functions like "BeforeFrontendSwitch" and "AfterFrontendSwitch" so the plugins are even able to know about it. Assumption for this patch: All frontends within one adapter have to be used mutually exclusive. All cards I know behave in this way. If there are cards with multiple frontends which can be used simultaneously I'd like to hear about it. Whenever the dvb-api-changes are upstream (the ENUM_DELSYS thingy) I think my patch can easily be converted to use that. I'm still working on this patch, it's not finished yet... :-) Have fun, Lars.

7 8

problems with playback and plugins with vdr-1.7.22
by René 08 Jan '12

08 Jan '12

Hi all, I finally managed to upgrade my vdr-1.6.x to vdr-1.7.22 and get the LiveBuffer patch compiled in Gentoo. There was however some problems i bumped into. The first issue i have is when starting vdr. I get the following plugins to fail during startup: ERROR: loading plugin libvdr-epgsearch.so.1.7.22: undefined symbol: _ZN6cTimerC1EbbP8cChannel ERROR: loading plugin libvdr-skinenigmang.so.1.7.22: undefined symbol: _ZN6cTimerC1EbbP8cChannel ERROR: loading plugin libvdr-text2skin.so.1.7.22: undefined symbol: _ZN6cTimerC1EbbP8cChannel ERROR: loading plugin libvdr-burn.so.1.7.22: undefined symbol: _ZN8vdr_burn13chain_archiveC1ERNS_3jobE ERROR: loading plugin libvdr-streamdev-server.so.1.7.22: undefined symbol: _ZN6cTimerC1EbbP8cChannel I have compiled vdr, and after this i recompiled all plugins without any errors. The use-flags that are active are these: cutterlimit ddepgentry hardlinkcutter lircsettings mainmenuhooks pinplugin timerinfo wareagleicon yaepg The same use-flags worked fine with vdr 1.6.x LiveBuffer for vdr-1.7.22 again failed with these use-flags: dvlvidprefer liemikuutio jumpplay setup ttxtsubs Is there anything that i forgot to enable/disable in my setup? Then i got an other problem. When watching a recording, and i fastforward of rewind the program, i get to a situation that the "timecounter" get's stuck to the frame i start from. The film moves, but when i hit play, i end up back to the frame from where i started to rewind/fastforwad. The only way to fix this is to jump with the yellow/green buttons. AFter this i can rewind/fastforwad normally. This again works for a while, but again if it fails to stop to the place i rewind to, i have to "reset" the rewind-issue with the yellow/green buttons... Is this a known bug in vdr, or is it something that i have messed up in my setup? Regards, René

3 12

Re: [vdr] problems with playback and plugins with vdr-1.7.22
by Rolf Ahrenberg 08 Jan '12

08 Jan '12

On Sat, 7 Jan 2012, René wrote: > Then i got an other problem. When watching a recording, and i fastforward of > rewind the program, i get to a situation that the "timecounter" get's stuck > to the frame i start from. The film moves, but when i hit play, i end up back > to the frame from where i started to rewind/fastforwad. The only way to fix > this is to jump with the yellow/green buttons. AFter this i can > rewind/fastforwad normally. This again works for a while, but again if it > fails to stop to the place i rewind to, i have to "reset" the rewind-issue > with the yellow/green buttons... > > Is this a known bug in vdr, or is it something that i have messed up in my > setup? I was under impression that this is already fixed in xineliboutput 10.12.2011 or newer. BR, -- rofa

2 1

vdr-1.7.22 error while reading (config files...)
by Infonux 08 Jan '12

08 Jan '12

Hi, i can't get working vdr-1.7.22 in my "mips box" based on openwrt. the VDR not able to get configuration from some files. root@dvb:/media# vdr -Pxineliboutput -c /media vdr: error while reading '/media/sources.conf' vdr: error while reading '/media/channels.conf' vdr: error while reading '/media/remote.conf' vdr: [1606] VDR version 1.7.22 started vdr: [1606] codeset is 'ASCII' - unknown vdr: [1606] found 28 locales in /usr/share/vdr/locale vdr: [1606] loading plugin: /usr/lib/vdr/plugins/libvdr-xineliboutput.so.1.7.22 vdr: [1606] loading /media/setup.conf vdr: [1606] loading /media/sources.conf vdr: [1606] ERROR: error in /media/sources.conf, line 1 vdr: [1606] loading /media/channels.conf vdr: [1606] ERROR: error in /media/channels.conf, line 1 vdr: [1606] loading /media/timers.conf vdr: [1606] loading /media/svdrphosts.conf vdr: [1606] loading /media/remote.conf vdr: [1606] ERROR: error in /media/remote.conf, line 52 vdr: [1608] video directory scanner thread started (pid=1606, tid=1608) vdr: [1608] video directory scanner thread ended (pid=1606, tid=1608) vdr: [1607] video directory scanner thread started (pid=1606, tid=1607) vdr: [1607] video directory scanner thread ended (pid=1606, tid=1607) vdr: [1606] reading EPG data from /media/video/epg.data vdr: [1606] registered source parameters for 'A - ATSC' vdr: [1606] registered source parameters for 'C - DVB-C' vdr: [1606] registered source parameters for 'S - DVB-S' vdr: [1606] registered source parameters for 'T - DVB-T' vdr: [1606] probing /dev/dvb/adapter0/frontend0 vdr: [1606] creating cDvbDevice vdr: [1606] new device number 1 vdr: [1606] frontend 0/0 provides DVB-S2 with QPSK ("Conexant CX24116/CX24118") kernel: tbsqboxs2: tbsqboxs2_set_voltage 0 vdr: [1606] found 1 DVB device vdr: [1606] initializing plugin: xineliboutput (1.0.90-cvs): X11/xine-lib output plugin vdr: [1606] new device number 9 --- sources.conf ------- S19.2E Astra ------------------------ --- channels.conf ------ NIXE SD:12460:hC34M2O0S0:S19.2E:27500:3311=2:3312=deu@3:0:0:764:133:5:0 ------------------------ is the codeset problem ? the mime encoding of channels.conf and sources.conf is "us-ascii" any idea how fix this ? Thanks.

1 2

[PATCH] Fix build with g++ 4.7.0.
by Ville Skyttä 04 Jan '12

04 Jan '12

This is the PR24163 case mentioned in http://article.gmane.org/gmane.linux.redhat.fedora.devel/157671 --- config.h | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/config.h b/config.h index 7825364..b0233a9 100644 --- a/config.h +++ b/config.h @@ -122,7 +122,7 @@ public: if (!isempty(s)) { T *l = new T; if (l->Parse(s)) - Add(l); + this->Add(l); else { esyslog("ERROR: error in %s, line %d", fileName, line); delete l; -- 1.7.7.5

2 1

vdr-1.7.22 mips_uClibc-0.9.30.1 (tools.c canonicalize_file_name...)
by Infonux 04 Jan '12

04 Jan '12

Hi, I try to compile vdr for openwrt (r29611) but I get the following errors tools.c: In function 'char* ReadLink(const char*)': tools.c:514: error: 'canonicalize_file_name' was not declared in this scope tools.c: In member function 'int cUnbufferedFile::Open(const more info in attached file. I had already successfully compiled (vdr-1.7.22) in a later version of openwrt (r27128) I just wish find out where the error (like missing option in uclibc or library...?) Thanks in advance.

2 3

Crystalhd support and help
by Lists 04 Jan '12

04 Jan '12

Hi all, I have a main frontend box running yaVDR 1.7.21 vdr and I have a version 1 AppleTV with a broadcom crystalhd module installed. I'm running Ubuntu and have loaded from source the crystalhd kernel module and the libraries. I have xbmc-pvr branch from yaVDR running on the appletv and it works most of the time but cannot keep up with 1080 most of the time (can for 720p). Does anyone know if this branch has crystalhd support and how do I know if its using it? Second, I would prefer to use vdr-xineliboutput and have installed vdr-sxfe and vdr-fbfe. I don't need, nor want all the overhead of xbmc. I'm thinking if I can one of these to work then it would be perfect - I could use the vdr OSD, etc. However, I can't find a video module that will work properly. vdr-sxfe shows me: Available video drivers: vdpau aadxr3 dxr3 xv vaapi raw opengl xshm caca aa none xxmc sdl vidixfb vidix fb xvmc Available audio drivers: pulseaudio alsa oss jack none file I understand to 'use' crystalhd you have to invoke the vaapi video driver? Is this correct? When I try it, however, it says libva: libva version 0.31.1 Xlib: extension "XFree86-DRI" missing on display ":0". libva: va_getDriverName() returns 0 libva: Trying to open /usr/lib/dri/nvidia_drv_video.so libva: va_openDriver() returns -1 How can I get around this or is it possible with my setup? Anyone got this going? Thanks for any help. Norm

3 4

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr