vdr September 2009

vdr@linuxtv.org

50 participants
42 discussions

multiple frontends on HVR 4000
by Tarik Chougua 29 Sep '09

29 Sep '09

Hi, i have vdr178 on ubuntu 9.04. with HVR4000 i can see DVB-S and DVB-S2 channels, but not DVB-T channels. How to configure vdr to using multiple frontends of this card pls ? Thank you.

2 1

vdpau patches
by scott 26 Sep '09

26 Sep '09

I was thinking of giving xine/vdpau/xineliboutput another try after failing earlier in the year. I came across these patches: http://www.nfvdr.net/bbs/thread-5856-1-1.html Is anyone using these? -- Scott

5 7

One recording per device only
by Patrick Rother 24 Sep '09

24 Sep '09

Hello. I have a vdr host with 1 DVB-s FF card and 3 DVB-s USB devices and 3 DVB-t USB devices. When I have 2 concurrent DVB-s recordings at different transponders, these are done at different DVB-s USB devices and there is no problem, but if I have 2 concurrent recordings at the same transponder, I get lots of: Sep 24 16:27:39 vdr vdr: [20650] 2 cRepacker messages suppressed Sep 24 16:27:39 vdr vdr: [20650] cAudioRepacker(0xC1): skipped 572 bytes while syncing on next audio frame Sep 24 16:27:39 vdr vdr: [20650] 3 cRepacker messages suppressed Sep 24 16:27:39 vdr vdr: [20650] cAudioRepacker(0xC0): skipped 1148 bytes while syncing on next audio frame and scrambled data. As a first workaround / test setup I would like to limit vdr to do at most one recording per device and chose a new device even if a second recording is at the same transponder. Most suitably this shall apply one to specific devices or channels, if possible. How could this be achieved? Thank you.

1 0

Jumping while replay causes video to halt
by Kartsa 24 Sep '09

24 Sep '09

Hi all I am having some problems with jumping using yellow/blue and 1/3 buttons. Not always but almost the picture stops after jump. Its not on pause because pushing play does nothing. Using fast forward gets video playing again and then pushing play resumes playback. There is nothing in the logs that would tell me what the problem might be. Or at least I can't find anything. I have ubuntu and vdr installed from packages. vdr -V gives: vdr (1.6.0-2/1.6.0) - The Video Disk Recorder extrecmenu (1.1) - Extended recordings menu streamdev-server (0.3.4) - VDR Streaming Server skinsoppalusikka (1.6.4) - Soppalusikka skin conflictcheckonly (0.0.1) - Direct access to epgsearch's conflict check menu epgsearch (0.9.24) - search the EPG for repeats and more iptv (0.2.5) - Experience the IPTV menuorg (0.4.4) - Reorganizes the main menu burn (0.1.0-pre22) - Versatile convert-and-burn plugin pvrinput (2008-10-04) - use Hauppauge PVR as input device vompserver (0.3.0) - VDR on MVP plugin by Chris Tallon quickepgsearch (0.0.1) - Quick search for broadcasts undelete (0.0.6) - undelete for recordings xineliboutput (1.0.4) - X11/xine-lib output plugin epgsearchonly (0.0.1) - Direct access to epgsearch's search menu ttxtsubs (0.0.9) - Teletext subtitles weatherng (0.0.7-pre2) - Weather.com: Weather forecast osdteletext (0.8.1) - Displays teletext on the OSD I use vdr-sxfe for playback as a remote client on the same host. I tried regenerating index file with genindex with no change. How do I fix this? \\Kartsa

1 2

Segmentation fault with vdr 1.7.9 and femon 1.7.4
by Goga777 20 Sep '09

20 Sep '09

Hi with vdr 179 + femon 174 sometimes I have the vdr crash during of switching between channels with femon Sep 20 20:10:05 arvdr logger: vo_vdpau: deinterlace: temporal_spatial Sep 20 20:10:05 arvdr logger: 200 frames delivered, 0 frames skipped, 59 frames discarded Sep 20 20:10:05 arvdr logger: video_out: throwing away image with pts 28277792 because it's too old (diff : 3732). Sep 20 20:10:05 arvdr logger: input_vdr: flush buffers (vb: 0, ab: 0, vf: 0, af: 0) done. Sep 20 20:10:10 arvdr vdr: [3177] changing name of channel 2 from 'EinsFestival,;ARD' to 'Einsfestival,;ARD' Sep 20 20:10:10 arvdr vdr: [3176] frontend 0 lost lock on channel 1, tp 110743 Sep 20 20:10:10 arvdr logger: input_vdr: execution of rpc command 0 () failed, exiting ... Sep 20 20:10:10 arvdr kernel: [ 409.669020] receiver on dev[3523]: segfault at 9ef1000 ip b7bd7d26 sp b2d5a298 error 6 in libc-2.9.so[b7b5f000+158000] Sep 20 20:10:11 arvdr logger: input_vdr: rpc thread done. Sep 20 20:10:11 arvdr lircd-0.8.3[2477]: removed client gdb output [Thread 0xb026ab90 (LWP 3556) exited] [New Thread 0xb026ab90 (LWP 3557)] [Thread 0xb026ab90 (LWP 3557) exited] [New Thread 0xb026ab90 (LWP 3558)] [Thread 0xb026ab90 (LWP 3558) exited] [New Thread 0xb026ab90 (LWP 3559)] [Thread 0xb026ab90 (LWP 3559) exited] [New Thread 0xb026ab90 (LWP 3560)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xb2468b90 (LWP 3554)] 0xb7ce7d26 in memcpy () from /lib/i686/cmov/libc.so.6 (gdb) bt #0 0xb7ce7d26 in memcpy () from /lib/i686/cmov/libc.so.6 #1 0x000000e8 in ?? () #2 0xb77a1e46 in ?? () #3 0x080a6ee8 in cDevice::Action (this=0x8de9fd0) at device.c:1464 #4 0x08118300 in cThread::StartThread (Thread=0x8de9fd0) at thread.c:257 #5 0xb7fcb495 in start_thread () from /lib/i686/cmov/libpthread.so.0 #6 0xb7d50a4e in clone () from /lib/i686/cmov/libc.so.6 (gdb) disass $pc-32 $pc+32 Dump of assembler code from 0xb7ce7d06 to 0xb7ce7d46: 0xb7ce7d06 <memcpy+38>: push %ss 0xb7ce7d07 <memcpy+39>: movsb %ds:(%esi),%es:(%edi) 0xb7ce7d08 <memcpy+40>: dec %ecx 0xb7ce7d09 <memcpy+41>: test $0x3,%esi 0xb7ce7d0f <memcpy+47>: je 0xb7ce7d1d <memcpy+61> 0xb7ce7d11 <memcpy+49>: movsb %ds:(%esi),%es:(%edi) 0xb7ce7d12 <memcpy+50>: dec %ecx 0xb7ce7d13 <memcpy+51>: test $0x3,%esi 0xb7ce7d19 <memcpy+57>: je 0xb7ce7d1d <memcpy+61> 0xb7ce7d1b <memcpy+59>: movsb %ds:(%esi),%es:(%edi) 0xb7ce7d1c <memcpy+60>: dec %ecx 0xb7ce7d1d <memcpy+61>: push %eax 0xb7ce7d1e <memcpy+62>: mov %ecx,%eax 0xb7ce7d20 <memcpy+64>: shr $0x2,%ecx 0xb7ce7d23 <memcpy+67>: and $0x3,%eax 0xb7ce7d26 <memcpy+70>: rep movsl %ds:(%esi),%es:(%edi) 0xb7ce7d28 <memcpy+72>: mov %eax,%ecx 0xb7ce7d2a <memcpy+74>: rep movsb %ds:(%esi),%es:(%edi) 0xb7ce7d2c <memcpy+76>: pop %eax 0xb7ce7d2d <memcpy+77>: mov %eax,%edi 0xb7ce7d2f <memcpy+79>: mov %edx,%esi 0xb7ce7d31 <memcpy+81>: mov 0x4(%esp),%eax 0xb7ce7d35 <memcpy+85>: ret 0xb7ce7d36 <memcpy+86>: shr %ecx 0xb7ce7d38 <memcpy+88>: jae 0xb7ce7d3b <memcpy+91> 0xb7ce7d3a <memcpy+90>: movsb %ds:(%esi),%es:(%edi) 0xb7ce7d3b <memcpy+91>: shr %ecx 0xb7ce7d3d <memcpy+93>: jae 0xb7ce7d41 <memcpy+97> 0xb7ce7d3f <memcpy+95>: movsw %ds:(%esi),%es:(%edi) 0xb7ce7d41 <memcpy+97>: rep movsl %ds:(%esi),%es:(%edi) 0xb7ce7d43 <memcpy+99>: jmp 0xb7ce7d2d <memcpy+77> 0xb7ce7d45: nop End of assembler dump. (gdb) info all-registers eax 0x0 0 ecx 0x3ffb43f3 1073431539 edx 0xffffffd4 -44 ebx 0x92df5e4 154007012 esp 0xb2468298 0xb2468298 ebp 0xb24682c8 0xb24682c8 esi 0xb266a000 -1301897216 edi 0x94273cc 155349964 eip 0xb7ce7d26 0xb7ce7d26 <memcpy+70> eflags 0x210246 [ PF ZF IF RF ID ] cs 0x73 115 ss 0x7b 123 ds 0x7b 123 es 0x7b 123 fs 0x0 0 gs 0x33 51 st0 0 (raw 0x00000000000000000000) st1 0 (raw 0x00000000000000000000) st2 0 (raw 0x00000000000000000000) st3 0 (raw 0x00000000000000000000) st4 0.31748888888888888889757214362141724 (raw 0x3ffda28de7553e0819da) st5 1 (raw 0x3fff8000000000000000) st6 100 (raw 0x4005c800000000000000) st7 100 (raw 0x4005c800000000000000) fctrl 0x37f 895 fstat 0x4020 16416 ftag 0xffff 65535 fiseg 0x0 0 fioff 0x0 0 foseg 0x0 0 fooff 0x0 0 fop 0x0 0 xmm0 {v4_float = {0x0, 0x0, 0x0, 0x0}, v2_double = {0x0, 0x0}, v16_int8 = {0x0 <repeats 16 times>}, v8_int16 = {0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0}, v4_int32 = {0x0, 0x0, 0x0, 0x0}, v2_int64 = {0x0, 0x0}, uint128 = 0x00000000000000000000000000000000} xmm1 {v4_float = {0x0, 0x0, 0x0, 0x0}, v2_double = {0x0, 0x0}, v16_int8 = {0x0 <repeats 16 times>}, v8_int16 = {0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0}, v4_int32 = {0x0, 0x0, 0x0, 0x0}, v2_int64 = {0x0, 0x0}, uint128 = 0x00000000000000000000000000000000} xmm2 {v4_float = {0x0, 0x0, 0x0, 0x0}, v2_double = {0x0, 0x0}, v16_int8 = {0x0 <repeats 16 times>}, v8_int16 = {0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0}, v4_int32 = {0x0, 0x0, 0x0, 0x0}, v2_int64 = {0x0, 0x0}, uint128 = 0x00000000000000000000000000000000} xmm3 {v4_float = {0x0, 0x0, 0x0, 0x0}, v2_double = {0x0, 0x0}, v16_int8 = {0x0 <repeats 16 times>}, v8_int16 = {0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0}, v4_int32 = {0x0, 0x0, 0x0, 0x0}, v2_int64 = {0x0, 0x0}, uint128 = 0x00000000000000000000000000000000} xmm4 {v4_float = {0x0, 0x0, 0x0, 0x0}, v2_double = {0x0, 0x0}, v16_int8 = {0x0 <repeats 16 times>}, ---Type <return> to continue, or q <return> to quit--- v8_int16 = {0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0}, v4_int32 = {0x0, 0x0, 0x0, 0x0}, v2_int64 = {0x0, 0x0}, uint128 = 0x00000000000000000000000000000000} xmm5 {v4_float = {0x0, 0x0, 0x0, 0x0}, v2_double = {0x0, 0x0}, v16_int8 = {0x0 <repeats 16 times>}, v8_int16 = {0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0}, v4_int32 = {0x0, 0x0, 0x0, 0x0}, v2_int64 = {0x0, 0x0}, uint128 = 0x00000000000000000000000000000000} xmm6 {v4_float = {0x0, 0x0, 0x0, 0x0}, v2_double = {0x0, 0x0}, v16_int8 = {0x0 <repeats 16 times>}, v8_int16 = {0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0}, v4_int32 = {0x0, 0x0, 0x0, 0x0}, v2_int64 = {0x0, 0x0}, uint128 = 0x00000000000000000000000000000000} xmm7 {v4_float = {0x0, 0x0, 0x0, 0x0}, v2_double = {0x0, 0x0}, v16_int8 = {0x0 <repeats 16 times>}, v8_int16 = {0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0}, v4_int32 = {0x0, 0x0, 0x0, 0x0}, v2_int64 = {0x0, 0x0}, uint128 = 0x00000000000000000000000000000000} mxcsr 0x1f80 [ IM DM ZM OM UM PM ] mm0 {uint64 = 0x0, v2_int32 = {0x0, 0x0}, v4_int16 = {0x0, 0x0, 0x0, 0x0}, v8_int8 = {0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0}} mm1 {uint64 = 0x0, v2_int32 = {0x0, 0x0}, v4_int16 = {0x0, 0x0, 0x0, 0x0}, v8_int8 = {0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0}} mm2 {uint64 = 0x0, v2_int32 = {0x0, 0x0}, v4_int16 = {0x0, 0x0, 0x0, 0x0}, v8_int8 = {0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0}} mm3 {uint64 = 0x0, v2_int32 = {0x0, 0x0}, v4_int16 = {0x0, 0x0, 0x0, 0x0}, v8_int8 = {0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0}} mm4 {uint64 = 0xa28de7553e0819da, v2_int32 = {0x3e0819da, 0xa28de755}, v4_int16 = {0x19da, 0x3e08, 0xe755, 0xa28d}, v8_int8 = {0xda, 0x19, 0x8, 0x3e, 0x55, 0xe7, 0x8d, 0xa2}} mm5 {uint64 = 0x8000000000000000, v2_int32 = {0x0, 0x80000000}, v4_int16 = {0x0, 0x0, 0x0, 0x8000}, v8_int8 = {0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x80}} mm6 {uint64 = 0xc800000000000000, v2_int32 = {0x0, 0xc8000000}, v4_int16 = {0x0, 0x0, 0x0, 0xc800}, v8_int8 = {0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0xc8}} mm7 {uint64 = 0xc800000000000000, v2_int32 = {0x0, 0xc8000000}, v4_int16 = {0x0, 0x0, 0x0, 0xc800}, v8_int8 = {0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0xc8}} (gdb) (gdb) (gdb)

1 0

Need help - trying to run xinelibout with 1.7.9
by Alex Betis 20 Sep '09

20 Sep '09

Hi all, I'm trying to recover my VDR machine after upgrade to Fedora11 (long sad story). On the way, I've decided to give a try to VDPAU, installed nVidia 185.18.36, xinelib 1.2-vdpau. Compiled all needed plugins and now struggle with xinelibout to get the output. Using 1.7.0 with xinelibout 1.0.4 I get "TS discontinuity" errors on some channels I watch (no output when it happens). Using 1.7.9 with xinelibout 1.0.4 I get "TCP buffer too small" errors with astronomic lengths. Found on some german sites to try latest CVS version since there were some buffers changes. Using 1.7.9 with CVS xinelibout version I get "ERROR (xine_input_vdr.c,860): Resource temporarily unavailable" I've used the xinelibout with xv output for now. What am I doing wrong? Anyone faced with such problems? Thanks. Alex.

1 0

[ANNOUNCE] vdr-iptv-0.3.0
by Rolf Ahrenberg 18 Sep '09

18 Sep '09

Hi, a new version of IPTV plugin is now available and contains an important bug fix that enables correct channel switches between different protocols. http://www.saunalahti.fi/~rahrenbe/vdr/iptv/ 2009-06-01: Version 0.3.0 - Added iptvstream-notrap.sh script. - Fixed setting parameters when protocol changes (Thanks to Peter Holik for reporting this one). - Updated example scripts to use ffmpeg's direct UDP output and added a new "image.sh" script (Thanks to Peter Holik). BR, -- rofa

3 10

femon plugin doesn't work "ERROR (femonosd.c, 504): Function not implemented"
by Dieter Bloms 16 Sep '09

16 Sep '09

Hello, I use vdr-1.7.9, v4l-dvb from http://linuxtv.org/hg/v4l-dvb and femon 1.7.4 When I start the plugin I don't get any output on my tv and see the following messages in my logfile: --snip-- Sep 15 08:37:36 video vdr: [17541] ERROR: cOsd::SetAreas returned 6 Sep 15 08:37:36 video vdr: [18523] femon receiver thread started (pid=17541, tid=18523) Sep 15 08:37:36 video vdr: [18524] receiver on device 1 thread started (pid=17541, tid=18524) Sep 15 08:37:36 video vdr: [18525] TS buffer on device 1 thread started (pid=17541, tid=18525) Sep 15 08:37:36 video vdr: [18526] femon osd thread started (pid=17541, tid=18526) Sep 15 08:37:36 video vdr: [18526] ERROR (femonosd.c,504): Function not implemented Sep 15 08:37:36 video vdr: [18526] ERROR (femonosd.c,504): Function not implemented Sep 15 08:37:37 video vdr: [18526] ERROR (femonosd.c,504): Function not implemented Sep 15 08:37:37 video vdr: [18526] ERROR (femonosd.c,504): Function not implemented Sep 15 08:37:38 video vdr: [18526] ERROR (femonosd.c,504): Function not implemented Sep 15 08:37:38 video vdr: [18526] femon osd thread ended (pid=17541, tid=18526) Sep 15 08:37:38 video vdr: [18523] femon receiver thread ended (pid=17541, tid=18523) Sep 15 08:37:38 video vdr: [18525] TS buffer on device 1 thread ended (pid=17541, tid=18525) Sep 15 08:37:38 video vdr: [18524] buffer stats: 114304 (5%) used Sep 15 08:37:38 video vdr: [18524] receiver on device 1 thread ended (pid=17541, tid=18524) --snip-- does anybody know what is wrong with my setup ? PS.: via svdr I can get some infos: --snip-- video:~ # svdrpsend.pl plug femon info 220 video SVDRP VideoDiskRecorder 1.7.9; Tue Sep 15 08:41:59 2009; ANSI_X3.4-1968 900-CARD:0 900-TYPE:0 900-NAME:ST STV0299 DVB-S 900-STAT:1F 900-SGNL:E11E 900-SNRA:EC1F 900-BERA:00000000 900-UNCB:00000000 900 CHAN:Das Erste;ARD:11836:hC34M2O0S0:S19.2E:27500:101=2:102=deu,103=2ch;106=dd:104:0:28106:1:1101:0 221 video closing connection video:~ # --snip-- -- Best regards Dieter Bloms -- I do not get viruses because I do not use MS software. If you use Outlook then please do not put my email address in your address-book so that WHEN you get a virus it won't use my address in the >From field.

5 7

No audio with vdr-1.7.9
by Timothy D. Lenz 15 Sep '09

15 Sep '09

I tried going from 1.7.8 to 1.7.9 and I have no audio with .9

1 1

Re: [vdr] femon plugin doesn't work "ERROR (femonosd.c, 504): Function not implemented"
by Martin Dauskardt 15 Sep '09

15 Sep '09

> > Sep 15 08:37:36 video vdr: [17541] ERROR: cOsd::SetAreas returned 6 > > Your OSD is running out of memory. The only cure is to shrink your > current OSD size. Rolf, you know that this happens with the vdr default OSD size? With my FF DVB-C (2 MB) and vdr 1.7.9 I have the following default values after deleting the setup.conf: Left and Right 8% Width 87% Height 84% To avoid the above mentioned error I reduced width and height to 82%. Then I got the femon OSD display, but with an other error: Sep 8 20:26:27 ubuntuvdr vdr: [3668] ERROR: cFemonOsd::cFemonOsd() OSD height (461) smaller than required (480). I increased the height to 84% and the error message disappeared. But now I got no display of the transponder and stream information - only the title. After setting width to 81% and height to 87% everything worked. Why is it not possible to show all femon OSD content with the vdr default OSD size? I don't remember that I had to change the OSD size with earlier vdr/plugin versions.

3 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr September 2009