vdr May 2010

vdr@linuxtv.org

40 participants
45 discussions

ANNOUNCE vdr-ttxtsubs 0.2.2 for VDR 1.7.13
by Tobi 08 May '10

08 May '10

A maintenance release that mainly fixes a problem with live subtitles on systems with FF cards, where the DVB card might not be in transfer mode. The changes: * Fixed channel retune triggering in VDR patch and updated patch to 1.7.14 (Dropped 1.7.12 and 1.7.13 patch) * Got rid of the background thread * Fixed live TV subtitles on FF cards, where there is no transfer mode * Updated README and TROUBLESHOOTING (Closes #323) * Increased internal frame buffer and log buffer overflows … [View More]

1 1

Re: [vdr] dvb-s2 transponder can be received but channels are not automatically found
by Newsy Paper 07 May '10

07 May '10

sorry, one more thing to mention: I just deleted all those channels on that frequency. Ned3 HD Film1 HD Sport1 HD were automatically added but the other were not. kind regards Newspaperman --- Newsy Paper <newspaperman_germany(a)yahoo.com> schrieb am Fr, 7.5.2010: > Von: Newsy Paper <newspaperman_germany(a)yahoo.com> > Betreff: dvb-s2 transponder can be received but channels are not automatically found > An: vdr(a)linuxtv.org > Datum: Freitag, 7. Mai, 2010 09:45 … [View More]

1 0

Unable to rebuild index on some French HD records
by dplu 05 May '10

05 May '10

Hi When we delete index file on some HD recording due to synchronous problem for editing, sometimes vdr is not able to rebuild it , start for few seconds and generate an errors Stream has "something" in it, you can add mark but not navigate between without crashing vdr , when playing records, time goes not seconds to seconds but every two seconds Is it possible for next release to increase the buffer size to 300 instead of 100 in recording.c , class cIndexFileGenerator ? This has been … [View More]

2 4

vdr 1.7.10 no record channel
by Senufo 03 May '10

03 May '10

Hello This weekend I had a problem with the chains of the transponder 778 000 DTT channels with France 4, i> TELE, Gulli, Virgin 17, BFM TV, Direct 8. I could not see them while all other channels were working correctly. So I made a new scan with: sudo w_scan -c fr My new channels.conf: France 4;NTN:778000:B8M2:T:27500:720=2:730=fra:745:0:519:8442:2:0 i>TELE;NTN:778000:B8M2:T:27500:420=2:430=fra:445:0:516:8442:2:0 Gulli;NTN:778000:B8M2:T:27500:620=2:630=fra:645:0:518:8442:2:0 Virgin … [View More]17;NTN:778000:B8M2:T:27500:520=2:530=fra:545:0:517:8442:2:0 BFM TV;NTN:778000:B8M2:T:27500:320=2:330=fra:345:0:515:8442:2:0 Direct 8;NTN:778000:B8M2:T:27500:120=2:130=fra:145:0:513:8442:2:0 My old channels.conf France 4;NTN:778000:B8M2:T:27500:166=2:104:0:0:519:8442:2:0 i>TELE;NTN:778000:B8M2:T:27500:163=2:92:0:0:516:8442:2:0 Gulli;NTN:778000:B8M2:T:27500:165=2:100:48:0:518:8442:2:0 Virgin 17;NTN:778000:B8M2:T:27500:164=2:96:44:0:517:8442:2:0 BFM TV;NTN:778000:B8M2:T:27500:162=2:88:0:0:515:8442:2:0 Direct 8;NTN:778000:B8M2:T:27500:160=2:80:32:0:513:8442:2:0 Now I can see these channels directly but when I want to make a record that does not work I have these error messages: May 2 2:09:03 p.m. karmic vdr: [8324] switching device 3 to Channel 9 May 2 2:09:03 p.m. karmic vdr: [8324] Timer 24 (9 from 1409 to 1709 '@ EPISODE TITLE') home May 2 2:09:03 p.m. karmic vdr: [8324] Title: 'L'école des fans' Subtitle: '(null)' May 2 2:09:03 p.m. karmic vdr: [8324] record / video / @ The école_des_fans / 2010-05-02.14.09.9-0.rec May 2 2:09:03 p.m. karmic vdr: [8324] Creating directory / video / @ The école_des_fans / 2010-05-02.14.09.9-0.rec May 2 2:09:03 p.m. karmic vdr: [8324] recording to '/ video / @ The école_des_fans / 2010-05-02.14.09.9-0.rec/00001.ts' May 2 2:09:03 p.m. karmic vdr: [11693] recording thread started "(pid = 8324, tid = 11693) May 2 2:09:03 p.m. karmic vdr: [8324] info: Registration has begun May 2 2:09:03 p.m. karmic vdr: [11694] Effects EnigmaNG thread started "(pid = 8324, tid = 11694) May 2 2:09:06 p.m. karmic vdr: [11694] Effects EnigmaNG thread ended (pid = 8324, tid = 11694) May 2 2:09:07 p.m. karmic vdr: [11751] Effects EnigmaNG thread started "(pid = 8324, tid = 11751) May 2 2:09:11 p.m. karmic vdr: [11751] Effects EnigmaNG thread ended (pid = 8324, tid = 11751) May 2 2:09:14 p.m. karmic vdr: [11864] Effects EnigmaNG thread started "(pid = 8324, tid = 11864) May 2 2:09:20 p.m. karmic vdr: [11055] ERROR: video data stream broken May 2 2:09:20 p.m. karmic vdr: [11055] emergency exit request to setup Ignored LUKAS May 2 2:09:21 p.m. karmic vdr: [8324] Timer 24 (9 from 1409 to 1709 '@ The School of fans') set to event Sun 5.2.2010 14:30-16:05 'Lois and Clark' May 2 2:09:34 p.m. karmic vdr: [11693] ERROR: video data stream broken May 2 2:09:34 p.m. karmic vdr: [11693] emergency exit request to setup Ignored LUKAS May 2 2:09:39 p.m. karmic vdr: [11864] Effects EnigmaNG thread ended (pid = 8324, tid = 11864) May 2 2:09:39 p.m. karmic vdr: [12215] Effects EnigmaNG thread started "(pid = 8324, tid = 12215) May 2 2:09:51 p.m. karmic vdr: [11055] ERROR: video data stream broken I'm running Ubuntu 9.10 with 1.7.10 vdr-launched with the following command: screen -S VDR -dm ./vdr -u vdr -c /video/vdrconf/ -v /video -L ./PLUGINS/lib --localedir=$VDRPATH/locale\ -P'sc' \ -P'xine -r' \ -P'streamdev-server'\ -P'streamdev-client'\ -P'skinenigmang' \ -P'extrecmenu' \ -P'epgsearch' \ -P'pin' \ -P'femon' Currently in France some transponders changes configuration to go all digital. Does anyone has an idea? thank you for your help Senufo [View Less]

2 1

vdr-sxfe crashing all the time
by Martti Kuparinen 03 May '10

03 May '10

Hi, I have self-compiled VDR 1.7.14 and xineliboutput, see http://kuparinen.org/martti/comp/vdr/ if you want to know the details. Both my server and client are running 64-bit Ubuntu 10.04. The client has an integrated ATI Radeon HD 3200 graphics adapter and I use the fglrx driver. When I start my client, I'll see this on the server May 2 15:04:00 a18o2 vdr: [1479] [xine..put] Data connection (TCP) requested May 2 15:04:00 a18o2 vdr: [1479] [xine..put] cBackgroundWriterI initialized (… [View More]buffer 512 kb) May 2 15:04:00 a18o2 vdr: [1479] [xine..put] cTcpWriter initialized (buffer 512 kb) May 2 15:04:02 a18o2 vdr: [1484] [xine..put] cXinelibServer::Play_PES Buffer overflow (TCP/PIPE) May 2 15:04:02 a18o2 vdr: last message repeated 64 times May 2 15:04:02 a18o2 vdr: [1479] [xine..put] Client 1 disconnected and on the client (gdb) run --post=tvtime:method=Linear,cheap_mode=1,pulldown=0,use_progressive_frame_flag=1 xvdr://a18o2:37890 ... Press Esc to exit [New Thread 0x7fffdab44710 (LWP 2603)] [2602] [demux_vdr] PMT changed [2602] [input_vdr] SCR jump: +40 ms (live=1, tuning=2) Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fffed55e710 (LWP 2594)] rle_scale_nearest (old_rle=<value>, rle_elems=<value>, w=<value>, h=<value>, new_w=<value>, new_h=4294967295) at tools/rle.c:144 144 *new_rle++ = *prevline++; (gdb) p prevline $1 = (xine_rle_elem_t *) 0x7fff36ffda1c (gdb) p *prevline Cannot access memory at address 0x7fff36ffda1c (gdb) p new_rle $2 = (xine_rle_elem_t *) 0x7fff36ffdcfc (gdb) p *new_rle Cannot access memory at address 0x7fff36ffdcfc (gdb) p n $3 = <value> (gdb) p elems_current_line $4 = 184 (gdb) bt #0 rle_scale_nearest (old_rle=<value>, rle_elems=<value>, w=<value>, h=<value>, new_w=<value>, new_h=4294967295) at tools/rle.c:144 #1 0x0000000000410744 in osd_data_init (self=0xadbd70, frame=0xada2a0, overlay=0xae4ff0) at xine/vo_osdscaler.c:148 #2 scale_overlay (self=0xadbd70, frame=0xada2a0, overlay=0xae4ff0) at xine/vo_osdscaler.c:322 #3 osdscaler_overlay_blend (self=0xadbd70, frame=0xada2a0, overlay=0xae4ff0) at xine/vo_osdscaler.c:347 #4 0x0000000000410c71 in osdreorder_overlay_end (self=0xadbe10, vo_img=0xada2a0) at xine/vo_osdreorder.c:78 #5 0x00007ffff6dca261 in ?? () from /usr/lib/libxine.so.1 #6 0x00007ffff6dc2767 in ?? () from /usr/lib/libxine.so.1 #7 0x00007ffff6dc2bb3 in ?? () from /usr/lib/libxine.so.1 #8 0x00007ffff65e39ca in start_thread () from /lib/libpthread.so.0 #9 0x00007ffff68e069d in clone () from /lib/libc.so.6 #10 0x0000000000000000 in ?? () Any ideas what's going on here? This happens every time, about 1 or 2 seconds after starting the vdr-sxfe. This is an emergency situation, wife acceptance factor is going down day by day so I'll have hard time to get any new hardware in the future if I don't fix this soon :-) Martti [View Less]

2 5

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr May 2010