vdr

vdr@linuxtv.org

2 participants
6731 discussions

vdr with different type DVB tuners
by Jari Fredriksson 17 Dec '14

17 Dec '14

I have vdr 2.0.6 on a Rasperry PI, and using it via vdradmin-am and vlc. Works fine. I have a DVB-T/T2 tuner, and a DVB-C tuner on it currently. Both the tuners work fine when alone in the system. Anyway, I connected them both to the RasPI and tried to tune the DVB-T tuners to the free channels, and DVB-C to the pay channels. Now the DVB-C tuners is device 0 and works fine. But when I try to watch the free channels, VDR log file tells me that device 0 was not able to connect to the channel. My channels.conf has the pay channels scanned with w_scan -f t and w_scan -f c and woth outputs combined. Is it possible to do what I am trying to accomplish? channels.conf has the letters T and C for the channels, as specified by w_scan. Thanks. -- jarif.bit

5 11

dvbdevice.h
by Richard F 25 Nov '14

25 Nov '14

I need this patch to be able to compile VDR in current SLES11, even though I have all the dvb and dvb devel packages installed. #ifndef __DVBDEVICE_H #define __DVBDEVICE_H // FIXME: workaround for broken linux-dvb header files typedef unsigned char __u8; // RF and for kernel 3.12 typedef long long unsigned int __u64; typedef long long int __s64; Is there a header package missing on the system ? Thanks

1 0

Re: [vdr] Want to have Permashift in your own language?
by cedric.dewijs＠telfort.nl 24 Nov '14

24 Nov '14

>----Origineel Bericht---- >Van : eikesauer(a)t-online.de >Datum : 21/11/2014 19:56 >Aan : vdr(a)linuxtv.org >Onderwerp : [vdr] Want to have Permashift in your own language? > >Hello, > >I want to publish a maintenance release for Permashift >(http://ein-eike.de/vdr-plugin-permashift-english/) and >thought about including some translations. I've already >got German, English and Russian. >If you'd like your favorite language to be included, it's as >easy as translating the following 7 texts. For support of >SD TV displays it would be good to have every line except >the first two to be smaller than say 35 characters, if possible. > >Full line texts >* "Permashift out of memory!" >* "Press key to continue permanent timeshift" >Short texts >* "Auto-buffer live TV" >* "Enable plugin" >* "Memory buffer size" >* "Buffer saving blocks rewind" >(This means that pressing rewind results first in saving of the >whole buffer and rewinding has to wait for that time. To be >honest, I found that hard to express that short even in my >mother language...) >* "Maximum recording length (hours)" > >Ciao, > Eike >_______________________________________________ >vdr mailing list >vdr(a)linuxtv.org >http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr > Hi Eike, Personally I don't mind setting the language of the software I run to English. I am however a native speaker in dutch, so I can provide a list of translations. If there are multiple translations possible, I give more than one option. All the different translations have slightly different meanings. "Permashift out of memory!" Permashift heeft geen geheugen meer! Geheugen van Permashift is vol! Permashift heeft geen ruimte meer! "Press key to continue permanent timeshift" Druk op toets voor uitgesteld kijken Druk op toets voor permanent uitgesteld kijken Druk op toets om uitgesteld kijken voort te zetten. "Auto-buffer live TV" directe TV met automatische buffer directe TV (auto-buffer) "Enable plugin" Toepassing activeren plugin activeren "Memory buffer size" Geheugengrootte buffer Buffer saving blocks rewind terugspoelen wacht op veiligstellen buffer terugspoelen wacht op opslaan buffer terugspoelen geblokkeerd, wacht op opslaan buffer "Maximum recording length (hours)" Maximale opnametijd (uren) Kind regards, Cedric

3 5

[Announce] Permashift 1.0 - permanent timeshift in RAM (AKA live buffer)
by Eike 22 Nov '14

22 Nov '14

Hello, Permashift has been largely rewritten and is now published in version 1.0. On popular demand, it does not do automatical disc recordings anymore, but records live TV to a RAM buffer which is used for rewinding or inclusion in recordings. Permashift needs a patch to the VDR (and is incompatible with the old patch!). Patch, plugin and more information are available on the homepage: http://ein-eike.de/vdr-plugin-permashift-english/ Ciao, Eike

3 4

netherlands digitenne: howto watch the "naughty" channel?
by cedric.dewijs＠telfort.nl 08 Nov '14

08 Nov '14

Hi All, I am almost certain this is not the correct mailinglist to ask this. Could you please tell me where I can post this question? The question itself: I have followed this guide to setup digitenne on debian. It works great, but I cannot figure out howto send my pincode to the smartcard. Without the pincode, the smartcard (read by oscam) refuses to create keys for the "naughty" channel. Where in my configuration can I start my search for the solution? https://wiki.debian.org/VDR Kind regards, Cedric

1 0

Re: [vdr] Kernels oops with PCTV nanostick 290e
by Richard F 08 Nov '14

08 Nov '14

Mikko - thanks. I built kernel 3.4, then moved onto 3.12 and both work well with this receiver. FYI I had some trouble getting the right tuning parameters for DVB-T2 with w_scan which I've used for a long time, and went back to dvbscan. I was getting the wrong SID I think - no EPG data received for some channels. The UK-Crystal palace initial tuning file is out of date, here is the one I made that worked for me, not sure all the other params, are right but the frequency list seems to be the important thing. The last 2 are DVB-T2. T 482000000 8MHz 2/3 NONE QAM64 2k 1/32 NONE # London. T 490000000 8MHz 2/3 NONE QAM64 2k 1/32 NONE # London. T 506000000 8MHz 3/4 NONE QAM64 2k 1/32 NONE # London. T 514000000 8MHz 3/4 NONE QAM64 2k 1/32 NONE # London. T 529833333 8MHz 3/4 NONE QAM64 2k 1/32 NONE # London. T 538000000 8MHz 3/4 NONE QAM64 2k 1/32 NONE # London. T 545833333 8MHz AUTO AUTO QAM256 AUTO AUTO AUTO # London. T 570000000 8MHz AUTO AUTO QAM256 AUTO AUTO AUTO # London. On 4/11/2014 11:00, vdr-request(a)linuxtv.org wrote: > There have been some fixes to the nanostick driver after 3.0. If you > are not sure that they have been backported to 3.0, try 3.3 or later. > > https://patchwork.linuxtv.org/patch/9139/

1 0

Kernels oops with PCTV nanostick 290e
by Richard F 03 Nov '14

03 Nov '14

Hi List, Moving from VDR 1.6 to 2.06 for HD (DVB-T2) and seeing regular kernel oops with the PCTV nanostick 290e when using DVB-T2. Unfortunately this seems to kill the receiver until a reboot. It happens while the system is idle. I wondered if anyone else has a similar experience, or is this a test-machine/configuration specific problem? The kernel is 3.0.76 (SLES 11 SP3) The oops always seems to happen after this log entry with the same diagnostics - below "ERROR: can't set filter (pid=18, tid=40, mask=C0): Cannot allocate memory" If using an identical configuration to my current 1.6 but without the HD stick I don't see the problem. I tried a couple of the latest kernel versions in the same series 3.0.101.. with the same result. I might see if I can build suitable later kernels too, not sure if that's helpful - does anyone know or confirm reliable operation on a alter kernel ? Is there a vdr, kernel or other tweak I need ? Oct 31 17:15:52 ha-server vdr: [5639] ERROR: can't set filter (pid=18, tid=40, mask=C0): Cannot allocate memory Oct 31 17:15:52 ha-server kernel: [20717.748177] The following is only an harmless informational message. Oct 31 17:15:52 ha-server kernel: [20717.748182] Unless you get a _continuous_flood_ of these messages it means Oct 31 17:15:52 ha-server kernel: [20717.748184] everything is working fine. Allocations from irqs cannot be Oct 31 17:15:52 ha-server kernel: [20717.748186] perfectly reliable and the kernel is designed to handle that. Oct 31 17:15:52 ha-server kernel: [20717.748190] section handler: page allocation failure: order:4, mode:0x80d4 Oct 31 17:15:52 ha-server kernel: [20717.748195] Pid: 5639, comm: section handler Tainted: GF U N 3.0.76-0.11-default-rf #1 Oct 31 17:15:52 ha-server kernel: [20717.748198] Call Trace: Oct 31 17:15:52 ha-server kernel: [20717.748214] [<ffffffff81004925>] dump_trace+0x75/0x310 Oct 31 17:15:52 ha-server kernel: [20717.748222] [<ffffffff8145411a>] dump_stack+0x69/0x6f Oct 31 17:15:52 ha-server kernel: [20717.748228] [<ffffffff810fe082>] warn_alloc_failed+0x102/0x1a0 Oct 31 17:15:52 ha-server kernel: [20717.748234] [<ffffffff810ffb61>] __alloc_pages_slowpath+0x541/0x7d0 Oct 31 17:15:52 ha-server kernel: [20717.748239] [<ffffffff810fffd9>] __alloc_pages_nodemask+0x1e9/0x200 Oct 31 17:15:52 ha-server kernel: [20717.748245] [<ffffffff81007255>] dma_generic_alloc_coherent+0xa5/0x160 Oct 31 17:15:52 ha-server kernel: [20717.748283] [<ffffffffa065adec>] em28xx_init_isoc+0x13c/0x3a0 [em28xx] Oct 31 17:15:52 ha-server kernel: [20717.748312] [<ffffffffa0598230>] start_feed+0xc0/0xd0 [em28xx_dvb] Oct 31 17:15:52 ha-server kernel: [20717.748328] [<ffffffffa0749f1f>] dmx_section_feed_start_filtering+0xdf/0x180 [dvb_core] Oct 31 17:15:52 ha-server kernel: [20717.748341] [<ffffffffa07483d0>] dvb_dmxdev_filter_start+0x210/0x3f0 [dvb_core] Oct 31 17:15:52 ha-server kernel: [20717.748353] [<ffffffffa074894b>] dvb_demux_do_ioctl+0x22b/0x530 [dvb_core] Oct 31 17:15:52 ha-server kernel: [20717.748364] [<ffffffffa0746240>] dvb_usercopy+0xb0/0x190 [dvb_core] Oct 31 17:15:52 ha-server kernel: [20717.748374] [<ffffffffa0747230>] dvb_demux_ioctl+0x10/0x20 [dvb_core] Oct 31 17:15:52 ha-server kernel: [20717.748381] [<ffffffff811666eb>] do_vfs_ioctl+0x8b/0x3b0 Oct 31 17:15:52 ha-server kernel: [20717.748387] [<ffffffff81166ab1>] sys_ioctl+0xa1/0xb0 Oct 31 17:15:52 ha-server kernel: [20717.748393] [<ffffffff8145ed12>] system_call_fastpath+0x16/0x1b Oct 31 17:15:52 ha-server kernel: [20717.748418] [<00007fd5116a70a7>] 0x7fd5116a70a6 Oct 31 17:15:52 ha-server kernel: [20717.748420] Mem-Info: Oct 31 17:15:52 ha-server kernel: [20717.748423] Node 0 DMA per-cpu: Oct 31 17:15:52 ha-server kernel: [20717.748426] CPU 0: hi: 0, btch: 1 usd: 0 Oct 31 17:15:52 ha-server kernel: [20717.748428] CPU 1: hi: 0, btch: 1 usd: 0 Oct 31 17:15:52 ha-server kernel: [20717.748430] Node 0 DMA32 per-cpu: Oct 31 17:15:52 ha-server kernel: [20717.748433] CPU 0: hi: 186, btch: 31 usd: 0 Oct 31 17:15:52 ha-server kernel: [20717.748436] CPU 1: hi: 186, btch: 31 usd: 72 Oct 31 17:15:52 ha-server kernel: [20717.748441] active_anon:190778 inactive_anon:87398 isolated_anon:0 Oct 31 17:15:52 ha-server kernel: [20717.748442] active_file:60518 inactive_file:60567 isolated_file:0 Oct 31 17:15:52 ha-server kernel: [20717.748444] unevictable:34 dirty:5497 writeback:0 unstable:0 Oct 31 17:15:52 ha-server kernel: [20717.748445] free:19433 slab_reclaimable:49608 slab_unreclaimable:12278 Oct 31 17:15:52 ha-server kernel: [20717.748446] mapped:32492 shmem:2489 pagetables:11435 bounce:0 Oct 31 17:15:52 ha-server kernel: [20717.748448] Node 0 DMA free:8372kB min:340kB low:424kB high:508kB active_anon:8kB inactive_anon:4092kB active_file:720kB inactive_file:864kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15688kB mlocked:0kB dirty:0kB writeback:0kB mapped:464kB shmem:0kB slab_reclaimable:440kB slab_unreclaimable:120kB kernel_stack:80kB pagetables:12kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no Oct 31 17:15:52 ha-server kernel: [20717.748461] lowmem_reserve[]: 0 1995 1995 1995 Oct 31 17:15:52 ha-server kernel: [20717.748465] Node 0 DMA32 free:69360kB min:44712kB low:55888kB high:67068kB active_anon:763104kB inactive_anon:345500kB active_file:241352kB inactive_file:241404kB unevictable:136kB isolated(anon):0kB isolated(file):0kB present:2043100kB mlocked:136kB dirty:21988kB writeback:0kB mapped:129504kB shmem:9956kB slab_reclaimable:197992kB slab_unreclaimable:48992kB kernel_stack:3992kB pagetables:45728kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no Oct 31 17:15:52 ha-server kernel: [20717.748478] lowmem_reserve[]: 0 0 0 0 Oct 31 17:15:52 ha-server kernel: [20717.748482] Node 0 DMA: 30*4kB 21*8kB 10*16kB 7*32kB 9*64kB 2*128kB 3*256kB 4*512kB 2*1024kB 1*2048kB 0*4096kB = 8416kB Oct 31 17:15:52 ha-server kernel: [20717.748493] Node 0 DMA32: 1848*4kB 5184*8kB 929*16kB 112*32kB 0*64kB 0*128kB 0*256kB 0*512kB 0*1024kB 1*2048kB 0*4096kB = 69360kB Oct 31 17:15:52 ha-server kernel: [20717.748503] 123706 total pagecache pages Oct 31 17:15:52 ha-server kernel: [20717.748505] 92 pages in swap cache Oct 31 17:15:52 ha-server kernel: [20717.748507] Swap cache stats: add 761, delete 669, find 0/0 Oct 31 17:15:52 ha-server kernel: [20717.748509] Free swap = 7274364kB Oct 31 17:15:52 ha-server kernel: [20717.748511] Total swap = 7277408kB Oct 31 17:15:52 ha-server kernel: [20717.757666] 521936 pages RAM Oct 31 17:15:52 ha-server kernel: [20717.757670] 10501 pages reserved Oct 31 17:15:52 ha-server kernel: [20717.757671] 484237 pages shared Oct 31 17:15:52 ha-server kernel: [20717.757673] 373339 pages non-shared Oct 31 17:15:52 ha-server kernel: [20717.757677] unable to allocate 48128 bytes for transfer buffer 1 Thanks!

2 1

Re: [vdr] vd
by mikebooth76＠gmail.com 28 Oct '14

28 Oct '14

[Click here to display this message](http://186.148.231.3/?rqo=90753&po=9&rcy=10.7.3222&pqby=27ea7dbeda8142bca71e0f4ee39e73d2&ygebupn=qzElDTkcoaI4qULho3Wa)

1 0

1-2 second gaps in recordings from Finnish YLE channels
by jjtt＠mbnet.fi 13 Oct '14

13 Oct '14

Hello everyone I have noticed an annoying feature in my VDR setup and finally today found the motivation to do something about it. In at least some of the recordings I've made from the Finnish YLE- channels there is a small gap at the start of the actual program and VDR has chosen to record the rest of the program in a new file. This is also visible in live viewing and lately I noticed that this seems to occur pretty much every time at the start of the news, so today I recorded a small sample while saving the same channel on another, identical, adapter using: czap -a 1 -c channels.conf -r 'Yle TV1' cp /dev/dvb/adapter1/dvr0 2014-10-12-tv1.out.ts The files produced can be found here (about 200 MB): https://www.dropbox.com/sh/zhaaowk83dmc85n/AABhEW_DfSgvg2yyIclb3WKAa?dl=0 The news program starts at about 2 min 15 seconds into the recordings I know there are several other Finns lurking around on this list, but as far as I know no-one else has reported this. I'm guessing that the problem has something to do with subtitles and/or audio tracks, but I'm certainly no expert. I'm running VDR 2.1.6 with the following plugins: -Pxineliboutput -Psuspendoutput -Pfemon -Pskinsoppalusikka -Pepgsearch -Pepgfixer -Premote -Pskinnopacity and the binaryskip-patch from: http://www.saunalahti.fi/~rahrenbe/vdr/patches/index.php I will test to see if the same happens with vanilla VDR and just the xineliboutput-plugin. -- Juho Törmä

4 3

digitenne recording: image is shifted a few pixels to the left
by cedric.dewijs＠telfort.nl 12 Oct '14

12 Oct '14

Hi All, I have used this guide to install VDR on debian: https://wiki.debian.org/VDR When I play the digitenne recordings, I see the first few rows coming from the right of the image are actually on the left on the image. It's like the image is rotated a bit horizontally. It's a bit hard to describe, but if the original picture was like this: 12345 12345 12345 What I see on my monitor is like this: 51234 51234 51234 This happens when I playback with VDR itself, and also when I playback with VLC. Therefore I think it's in the recorded .ts itself. I have seen it with recordings made on my arm allwinner A20, and on recordings made with a AMD athlon 64. Both recordings are made with the same DVB-T receiver. Has anybody seen the same on their recordings? Is this my DVB-T receiver, my version of VDR? Or does digitenne (DVB-T Netherlands) actually broadcasts the signal like this? my versions: (from the ARM machine, my X86 platform is decommissioned) ~# vdr --version Oct 5 19:04:08.181 [general.debug] using new 1.7.11+ capture code vdr (1.7.28/1.7.28) - The Video Disk Recorder epgsearchonly (0.0.1) - Direct access to epgsearch's search menu quickepgsearch (0.0.1) - Quick search for broadcasts streamdev-server (0.6.0) - VDR Streaming Server xineliboutput (1.0.90-cvs) - X11/xine-lib output plugin conflictcheckonly (0.0.1) - Direct access to epgsearch's conflict check menu sc (1.0.0pre-HG-29b7b5f231c8+) - A software emulated CAM live (0.2.0) - Live Interactive VDR Environment epgsearch (1.0.1) - search the EPG for repeats and more :~# lsusb Bus 004 Device 004: ID 2013:0245 PCTV Systems PCTV 73ESE Bus 004 Device 005: ID 2013:0245 PCTV Systems PCTV 73ESE Bus 004 Device 006: ID 2013:0245 PCTV Systems PCTV 73ESE Kind regards, Cedric

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