vdr

vdr@linuxtv.org

2 participants
6731 discussions

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 tested successfully by at least two users with same problem Thanks in advance

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

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

2 5

Re: [vdr] PVRINPUT plugin and "black/cinema bars"
by Martin Dauskardt 29 Apr '10

29 Apr '10

> From: "Simon Baxter" <linuxtv(a)nzbaxters.com> > Subject: [vdr] PVRINPUT plugin and "black/cinema bars" > > Hi Everyone > > My machine has (among others) a PVR-500 dual-channel analog card and I'm > running vdr-1.6.0 with pvrinput-2008-07-05. you should upgrade to our new pvrinput version: http://projects.vdr-developer.org/attachments/download/288/vdr- pvrinput-2010-04-14.tgz see http://projects.vdr-developer.org/repositories/entry/plg-pvrinput/HISTORY > > Doesn't matter which aspect ratio I choose, every channel under the PVR-500 > displays with black (cinema) bars on the top and bottom of the image. I am pretty sure that your TV station broadcasts analogue TV not anamorphic, which means it "delivers" the black bars to prevent the aspect ratio of a 16:9 content. Using the full screen for 16:9 content would result in "egg heads". We call this anamorphic. A 16:9 TV would stretch this; a 4:3 TV screen would need to scale it down (generating the needed bars). At least in Germany analogue broadcastings are never anamorphic. I gues you are using the extern inputs to supply video from a digital receiver? Then it could be anamorphic of course. You would need to tell your digibox that you have a 16:9 TV. The pvrinput setup-entry "aspect ratio" does not really change the aspect ratio. It is only an ID inside the mpeg which notifies the TV if it is anamorphic or not. Unfortunately there is no way to detect the incoming signal (Tuner or extern). Therefore it is not possible to automatically choose the right setting. > Any ideas how to remove these? The driver does not support clipping/cropping. We will always encode the whole capture size. If there is already a bar, it will also be in the encoded stream. You could try to use the zoom mode of your TV. > > Plugin setup is as follows: > pvrinput.BackupHack = 0 > pvrinput.BackupInterval = 30 > pvrinput.EnableDigibox = 1 > pvrinput.FastChannelChange = 1 > pvrinput.RedRemoteDevice = /dev/ledxmit These setup items have never been in any pvrinput version, so I gues you made patches. Could you provide them to me? Greets, Martin

6 7

Re: [vdr] PVRINPUT plugin and "black/cinema bars"
by Martin Dauskardt 29 Apr '10

29 Apr '10

> From: VDR User <user.vdr(a)gmail.com> > Subject: Re: [vdr] PVRINPUT plugin and "black/cinema bars" > > I am pretty sure that your TV station broadcasts analogue TV not > > anamorphic, which means it "delivers" the black bars to prevent the > > aspect ?ratio of a 16:9 content. > > The 'black bars' are called letterboxing. It's used to _preserve_ the > aspect ratio of widescreen content on 4:3 displays, not prevent it as > you've suggested. I meant that. Sorry for the mistake, english is not my native language. > > > Unfortunately there is no way to detect the incoming signal (Tuner or > > extern). Therefore it is not possible to automatically choose the right > > setting. > > Sure there is, just look in the mpeg headers. If for some reason that > flag isn't set correctly, you can also use the resolution along with > some simple math to calculate the aspect ratio. The mpeg is not delivered by the broadcaster, it is generated by the encoder. The content of the header is a result of the V4L2_CID_MPEG_VIDEO_ASPECT setting done by the application. > > >> Any ideas how to remove these? > > > > The driver does not support clipping/cropping. We will always encode the > > whole capture size. If there is already a bar, it will also be in the > > encoded stream. You could try to use the zoom mode of your TV. > > You _could_ write some functions to detect and remove letterboxing, > though I don't know anyone motivated enough to actually do it. The main goal of the pvrinput-plugin is to use the hardware encoder.I think it is a bad idea to do software-based on-the-fly-recoding. Simon, which output device do you use? Maybe the xine- or xineliboutput-Plugin can do the needed zoom for you. (?) Greets, Martin

5 6

Re: [vdr] help: translating plugin for vdr-1.7.14
by Marek Hajduk 28 Apr '10

28 Apr '10

------Original Message------ From: Halim Sahin Sender: vdr-bounces(a)linuxtv.org To: vdr(a)linuxtv.org ReplyTo: VDR Mailing List Subject: [vdr] help: translating plugin for vdr-1.7.14 Sent: Apr 27, 2010 13:32 Hi, I am seeing a small problem when i do this in my plugin: virtual const char *Description(void) { return tr(DESCRIPTION); } running make i18n doesn't add the DESCRIPTION string for translation to the pot file. Same for Plugin name. BR. Halim _______________________________________________ vdr mailing list vdr(a)linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr s pozdravom Marek Hajduk France-tech s.r.o. konatel spolocnosti

1 0

Re: [vdr] help: translating plugin for vdr-1.7.14
by Marek Hajduk 28 Apr '10

28 Apr '10

1 0

wirblescan 0.0.5-pre11e compilation errors
by YUP 27 Apr '10

27 Apr '10

Hello, Did anybody try to compile latest wirblescan plugin for vdr 1.7.14? I mean version 0.0.5-pre11e. I've got these errors: scanner.c: In member function ‘virtual void cScanner::Action()’: scanner.c:679:25: error: expected type-specifier scanner.c:679:25: error: cannot convert ‘int*’ to ‘cSwReceiver*’ in assignment scanner.c:679:25: error: expected ‘;’ scanner.c:957:28: error: expected type-specifier scanner.c:957:28: error: cannot convert ‘int*’ to ‘cSwReceiver*’ in assignment scanner.c:957:28: error: expected ‘;’ make: *** [scanner.o] Error 1 I didn't find maintener's direct email address, that is why I decided to write to this mailing list. Regards, Yarema

4 5

externalplayer and xineliboutput plugin
by Steffen Barszus 27 Apr '10

27 Apr '10

Hi ! I currently try to track down a problem of externalplayer and xineliboutput. The problem is, that if used with xineliboutput plugin and PlayMode pmNone, one device is not available. With xine this does not happen. May assumption is that here: device.c: 641 m_PlayMode = PlayMode; 642 643 TrickSpeed(-1); 644 if (m_PlayMode == pmAudioOnlyBlack) { 645 TRACE("pmAudioOnlyBlack --> BlankDisplay, NoVideo"); 646 ForEach(m_clients, &cXinelibThread::BlankDisplay); 647 ForEach(m_clients, &cXinelibThread::SetNoVideo, true); 648 } else { 649 if(m_liveMode) 650 ForEach(m_clients, &cXinelibThread::SetNoVideo, m_RadioStream); 651 else 652 ForEach(m_clients, &cXinelibThread::SetNoVideo, 653 m_RadioStream && (m_AudioCount<1)); 654 Clear(); 655 } An action is missing to take care of pmNone, i.e. to stop trying to receive and decode something. This is the Problem: Apr 22 23:41:05 vdr vdr: [3204] receiver on device 2 thread started (pid=2952, tid=3204) Apr 22 23:41:05 vdr vdr: [3204] ERROR: /dev/dvb/adapter1/dvr0: Device or resource busy Apr 22 23:41:05 vdr vdr: [3204] receiver on device 2 thread ended (pid=2952, tid=3204) This does not happen if i use xine, or if i shut down vdr-sxfe before i try to use streamdev oder VNSI plugin. My understanding is that the frontend device needs to do the required action and let vdr know afterwards in order to free the device. Would appreciate if someone with more understanding of the internals could add his opinion here ... Kind Regards Steffen

1 1

help: translating plugin for vdr-1.7.14
by Halim Sahin 27 Apr '10

27 Apr '10

Hi, I am seeing a small problem when i do this in my plugin: virtual const char *Description(void) { return tr(DESCRIPTION); } running make i18n doesn't add the DESCRIPTION string for translation to the pot file. Same for Plugin name. BR. Halim

1 1

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr