vdr March 2010

vdr@linuxtv.org

73 participants
72 discussions

VDR & Multiple frontends
by Eddi 25 Jul '15

25 Jul '15

Hi, I wrote a patch to Steve Toth hvr3000 repository, so my FlyDVB Trio can use multiple frontend. So I get: /dev/dvb/adapter0/demux0 /dev/dvb/adapter0/demux1 /dev/dvb/adapter0/dvr0 /dev/dvb/adapter0/dvr1 /dev/dvb/adapter0/frontend0 /dev/dvb/adapter0/frontend1 /dev/dvb/adapter0/net0 /dev/dvb/adapter0/net1 The bus of the two frontend is shared, isn't possible to get access to both frontend simultaneously, so I get an -EBUSY error by trying accessing frontend1 if frontend0 is in use. VDR doesn't support yet the second frontend, and it try to get exclusive access on both frontend on start, so the second frontend is inusabile. Vdr should probe for multiple frontend at start, and access frontend only on channel change. Please can someone give me an help to wrote a patch for this issue? Best Regards, Eddi

4 21

vdr xine-lib eac3
by zaverel 10 Jul '12

10 Jul '12

hello your second patch doesn't work : no sound on eac3 channel if you want there is a sample of vdr hd-eac3 recording here: http://dl.free.fr/ew4rJddM8 103mo else , i don't know what mailing-list is the more indicate for debuging the vdr or xine-dev mailing-list ?

7 38

[ANNOUNCE] noad-0.7.1
by the Noad 01 May '12

01 May '12

Hi, there is a new version of noad at http://noad.heliohost.org This Version handles also TS-Recordings. Greetings theNoad

7 10

CAM auto resetting - feature request??
by Simon Baxter 27 Dec '10

27 Dec '10

Hello My v 1.6.0 system has 2x Alphacrypt multi-CAMs. Occasionally one of the CAMs seems to "crash" and if I go into Setup > CAM one of the CAMs changes from "Alphacrypt" to "CAM Ready" - and will no longer decrypt channels. I then correspondingly get a bunch of timer conflicts, as 1/2 my CAM resources have vanished. Only ever one CAM fails, never both. I rectify this by selecting the CAM, and then hitting "reset" (sometimes a couple of times) - and it comes back. Unless I go into the Setup > CAM menu, I'm unaware that the CAM has "crashed". My request is...... Is there a way I can either 1)Automatically reset a CAM if it falls into this state or 2)Be notified, by generating a console/kernel message, so I can know to come in and fix this. Any ideas?

7 20

Re: [vdr] ERROR: driver buffer overflow on device 1
by peter 07 Oct '10

07 Oct '10

>Does this happen too when not using vdpau? I'm not using vdpau (haven't got the hardware for it). vdr-1.7.10 xine-lib-1.2 The problem occurs when running xine with dxr3 output (xine --verbose=1 -V dxr3 -A alsa vdr:/tmp/vdr-xi/stream) Mar 18 13:26:43 vdr-desktop kernel: [ 6250.760298] em8300-0: adjusting scr: 30791 Mar 18 13:26:45 vdr-desktop kernel: [ 6252.872307] em8300-0: adjusting scr: 125823 Mar 18 13:27:05 vdr-desktop vdr: [4159] buffer usage: 70% (tid=4158) Mar 18 13:27:06 vdr-desktop vdr: [4159] buffer usage: 80% (tid=4158) Mar 18 13:27:06 vdr-desktop vdr: [4159] buffer usage: 90% (tid=4158) Mar 18 13:27:07 vdr-desktop vdr: [4159] buffer usage: 100% (tid=4158) Mar 18 13:27:18 vdr-desktop vdr: [4159] ERROR: driver buffer overflow on device 1 Mar 18 13:27:18 vdr-desktop vdr: [4159] buffer usage: 30% (tid=4158) Mar 18 13:27:18 vdr-desktop vdr: [4158] ERROR: skipped 11 bytes to sync on TS packet on device 1 Mar 18 13:27:18 vdr-desktop vdr: [4158] TS continuity error (3) Mar 18 13:27:18 vdr-desktop vdr: [4158] TS continuity error (11) Mar 18 13:27:18 vdr-desktop vdr: [4158] cAudioRepacker(0xC0): skipped 312 bytes while syncing on next audio frame However: When running without dxr3 (xine --verbose=1 -V xshm -A alsa vdr:/tmp/vdr-xine/stream) everything is fine. Here's gdb output from a bad run: (gdb) thread apply all bt Thread 10 (Thread 0xb7648b70 (LWP 4030)): #0 0x0018a422 in __kernel_vsyscall () #1 0x00c5c142 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0 #2 0x0811a56e in cCondVar::TimedWait (this=0x9d7fac4, Mutex=..., TimeoutMs=1000) at thread.c:127 #3 0x080afd3e in cDvbTuner::Action (this=0x9d7f508) at dvbdevice.c:389 #4 0x08119d40 in cThread::StartThread (Thread=0x9d7f508) at thread.c:257 #5 0x00c5780e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #6 0x0074f8de in clone () from /lib/tls/i686/cmov/libc.so.6 Thread 9 (Thread 0xb6e47b70 (LWP 4031)): #0 0x0018a422 in __kernel_vsyscall () #1 0x00741c96 in poll () from /lib/tls/i686/cmov/libc.so.6 #2 0x080ff76a in cSectionHandler::Action (this=0x9d6f610) at sections.c:184 #3 0x08119d40 in cThread::StartThread (Thread=0x9d6f610) at thread.c:257 #4 0x00c5780e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #5 0x0074f8de in clone () from /lib/tls/i686/cmov/libc.so.6 Thread 8 (Thread 0xb6646b70 (LWP 4032)): #0 0x0018a422 in __kernel_vsyscall () #1 0x00741c96 in poll () from /lib/tls/i686/cmov/libc.so.6 ---Type <return> to continue, or q <return> to quit--- #2 0x0811f97b in cPoller::Poll (this=0x64, TimeoutMs=100) at tools.c:1195 #3 0x002a513d in PluginXine::cXineRemote::Action (this=0x9d842d8) at xineRemote.c:157 #4 0x08119d40 in cThread::StartThread (Thread=0x9d842e8) at thread.c:257 #5 0x00c5780e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #6 0x0074f8de in clone () from /lib/tls/i686/cmov/libc.so.6 Thread 7 (Thread 0xb5e1ab70 (LWP 4033)): #0 0x0018a422 in __kernel_vsyscall () #1 0x00c5c142 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0 #2 0x0811a56e in cCondVar::TimedWait (this=0xb5e1d7b8, Mutex=..., TimeoutMs=100) at thread.c:127 #3 0x00298ead in PluginXine::cXineLib::Action (this=0xb5e1d260) at xineLib.c:2632 #4 0x08119d40 in cThread::StartThread (Thread=0xb5e1d260) at thread.c:257 #5 0x00c5780e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #6 0x0074f8de in clone () from /lib/tls/i686/cmov/libc.so.6 Thread 6 (Thread 0xb5619b70 (LWP 4034)): #0 0x0018a422 in __kernel_vsyscall () #1 0x00c5c142 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0 ---Type <return> to continue, or q <return> to quit--- #2 0x0811a56e in cCondVar::TimedWait (this=0xb5e1d310, Mutex=..., TimeoutMs=100) at thread.c:127 #3 0x002a6278 in PluginXine::cXineExternal::Action (this=0xb5e1d2b8) at xineExternal.c:204 #4 0x08119d40 in cThread::StartThread (Thread=0xb5e1d2b8) at thread.c:257 #5 0x00c5780e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #6 0x0074f8de in clone () from /lib/tls/i686/cmov/libc.so.6 Thread 5 (Thread 0xb4e18b70 (LWP 4035)): #0 0x0018a422 in __kernel_vsyscall () #1 0x00c5ec8b in read () from /lib/tls/i686/cmov/libpthread.so.0 #2 0x00113901 in cRemoteDevInput::getKey() () from /usr/lib/vdr/libvdr-remote.so.1.7.10 #3 0x00113d87 in cRemoteGeneric::Action() () from /usr/lib/vdr/libvdr-remote.so.1.7.10 #4 0x08119d40 in cThread::StartThread (Thread=0x9d867f0) at thread.c:257 #5 0x00c5780e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #6 0x0074f8de in clone () from /lib/tls/i686/cmov/libc.so.6 Thread 4 (Thread 0xb4617b70 (LWP 4036)): #0 0x0018a422 in __kernel_vsyscall () #1 0x00741c96 in poll () from /lib/tls/i686/cmov/libc.so.6 #2 0x0811f97b in cPoller::Poll (this=0x32, TimeoutMs=50) at tools.c:1195 ---Type <return> to continue, or q <return> to quit--- #3 0x080f9028 in cKbdRemote::ReadKey (this=0x9d86910) at remote.c:296 #4 0x080f90ce in cKbdRemote::ReadKeySequence (this=0x9d86910) at remote.c:312 #5 0x080f97c2 in cKbdRemote::Action (this=0x9d86910) at remote.c:353 #6 0x08119d40 in cThread::StartThread (Thread=0x9d86920) at thread.c:257 #7 0x00c5780e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #8 0x0074f8de in clone () from /lib/tls/i686/cmov/libc.so.6 Thread 3 (Thread 0xb3cf2b70 (LWP 4070)): #0 0x0018a422 in __kernel_vsyscall () #1 0x00c5ec0b in write () from /lib/tls/i686/cmov/libpthread.so.0 #2 0x0029593a in PluginXine::cXineLib::xwrite (this=0xb5e1d260, f=7, b=0x9f65968, n=585) at xineLib.c:2457 #3 0x0029722b in PluginXine::cXineLib::execFuncStream (this=0xb5e1d260, Data=0x9f65968 "", Length=585) at xineLib.c:2937 #4 0x002972c4 in PluginXine::cXineLib::execFuncStream1 (this=0xb5e1d260, Data=0x9f65968 "", Length=585) at xineLib.c:2906 #5 0x00290072 in PluginXine::cXineDevice::PlayCommon3 (this=0xb5e1b008, Data=0x9f65968 "", Length=585, ptsForce=7920770849) at xineDevice.c:1969 #6 0x002900e5 in PluginXine::cXineDevice::PlayCommon2 (this=0xb5e1b008, Data=0x9f65968 "", Length=585, ptsForce=7920770849) at xineDevice.c:1849 #7 0x00290344 in PluginXine::cXineDevice::PlayCommon1 (this=0xb5e1b008, Data=0x9e1117c "", Length=2048, ptsForce=-1) at xineDevice.c:3134 #8 0x0029182a in PluginXine::cXineDevice::PlayCommon (this=0xb5e1b008, ---Type <return> to continue, or q <return> to quit--- Data=0x9e1117c "", Length=2048, stillImageData=false) at xineDevice.c:3092 #9 0x00293dab in PluginXine::cXineDevice::PlayVideo3 (this=0xb5e1b008, Data=0x9e1117c "", Length=2048, stillImageData=<value optimized out>) at xineDevice.c:2132 #10 0x0029469a in PluginXine::cXineDevice::PlayVideo2 (this=0xb5e1b008, Data=0x9e1117c "", Length=2048, stillImageData=false) at xineDevice.c:2052 #11 0x002948b6 in PluginXine::cXineDevice::PlayVideo1 (this=0xb5e1b008, Data=0x9e1117c "", Length=2048, stillImageData=false) at xineDevice.c:1781 #12 0x00294983 in PluginXine::cXineDevice::PlayVideo (this=0xb5e1b008, Data=0x9e1117c "", Length=2048) at xineDevice.c:1760 #13 0x0029088e in PluginXine::cXineDevice::PlayTsTrampoline (this=0xb5e1b008, Data=0xb33023d2 "G\004\067\030Ƒ\243F\226\266\215\032au\243F\030\215\031\272*P\326\030Yl\255\030=\206\214\347\260i\322\207\326\\8\r0\305h\314\304\a22\263B\353\f6\241{н\343\v\375\240\023\200f\204\200h\003\002\031,\254\002$\214\213e1\022", Length=188, VideoOnly=false) at xineDevice.c:1727 #14 0x002949d1 in PluginXine::cXineDevice::PlayVideo (this=0x249, Data=0xb3cf21dc "", Length=20) at xineDevice.c:1752 #15 0x080a8ad2 in cDevice::PlayPesPacket (this=0xb5e1b008, Data=0xb3cf21dc "", Length=20, VideoOnly=false) at device.c:1174 #16 0x00290a00 in PluginXine::cXineDevice::PlaySingleTs (this=0xb5e1b008, Data=0xb33023d2 "G\004\067\030Ƒ\243F\226\266\215\032au\243F\030\215\031\272*P\326\030Yl\255\030=\206\214\347\260i\322\207\326\\8\r0\305h\314\304\a22\263B\353\f6\241{н\343\v\375\240\023\200f\204\200h\003\002\031,\254\002$\214\213e1\022---Type <return> to continue, or q <return> to quit--- ", Length=188, VideoOnly=<value optimized out>) at xineDevice.c:1646 #17 0x0028d838 in PluginXine::cXineDevice::PlayTsImpl (this=0xb5e1b008, Data=0xb33023d2 "G\004\067\030Ƒ\243F\226\266\215\032au\243F\030\215\031\272*P\326\030Yl\255\030=\206\214\347\260i\322\207\326\\8\r0\305h\314\304\a22\263B\353\f6\241{н\343\v\375\240\023\200f\204\200h\003\002\031,\254\002$\214\213e1\022", Length=188, VideoOnly=false) at xineDevice.c:1590 #18 0x0028e77a in PluginXine::cXineDevice::PlayTs (this=0xb5e1b008, Data=0xb33023d2 "G\004\067\030Ƒ\243F\226\266\215\032au\243F\030\215\031\272*P\326\030Yl\255\030=\206\214\347\260i\322\207\326\\8\r0\305h\314\304\a22\263B\353\f6\241{н\343\v\375\240\023\200f\204\200h\003\002\031,\254\002$\214\213e1\022", Length=188, VideoOnly=<value optimized out>) at xineDevice.c:1572 #19 0x08123541 in cPlayer::PlayTs (this=0x9da5a50, Data=0xb33023d2 "G\004\067\030Ƒ\243F\226\266\215\032au\243F\030\215\031\272*P\326\030Yl\255\030=\206\214\347\260i\322\207\326\\8\r0\305h\314\304\a22\263B\353\f6\241{н\343\v\375\240\023\200f\204\200h\003\002\031,\254\002$\214\213e1\022", Length=188) at player.h:47 #20 cTransfer::Receive (this=0x9da5a50, Data=0xb33023d2 "G\004\067\030Ƒ\243F\226\266\215\032au\243F\030\215\031\272*P\326\030Yl\255\030=\206\214\347\260i\322\207\326\\8\r0\305h\314\304\a22\263B\353\f6\241{н\343\v\375\240\023\200f\204\200h\003\002\031,\254\002$\214\213e1\022", Length=188) at transfer.c:46 #21 0x080a7438 in cDevice::Action (this=0x9d7d250) at device.c:1464 #22 0x08119d40 in cThread::StartThread (Thread=0x9d7d250) at thread.c:257 ---Type <return> to continue, or q <return> to quit--- #23 0x00c5780e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #24 0x0074f8de in clone () from /lib/tls/i686/cmov/libc.so.6 Thread 2 (Thread 0xb32f0b70 (LWP 4071)): #0 0x0018a422 in __kernel_vsyscall () #1 0x00c5c142 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0 #2 0x0811a650 in cCondWait::Wait (this=0x9d9cc04, TimeoutMs=100) at thread.c:71 #3 0x080fd8d7 in cRingBuffer::WaitForPut (this=0x9d9cc00) at ringbuffer.c:58 #4 0x080fdc5c in cRingBufferLinear::Read (this=0x9d9cc00, FileHandle=13, Max=0) at ringbuffer.c:247 #5 0x080a5982 in cTSBuffer::Action (this=0x9d9cbb8) at device.c:1606 #6 0x08119d40 in cThread::StartThread (Thread=0x9d9cbb8) at thread.c:257 #7 0x00c5780e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #8 0x0074f8de in clone () from /lib/tls/i686/cmov/libc.so.6 Thread 1 (Thread 0xb77a96d0 (LWP 4026)): #0 0x0018a422 in __kernel_vsyscall () #1 0x00c5c142 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0 #2 0x0811a56e in cCondVar::TimedWait (this=0x817e080, Mutex=..., TimeoutMs=1000) at thread.c:127 ---Type <return> to continue, or q <return> to quit--- #3 0x080f9258 in cRemote::Get (WaitMs=1000, UnknownCode=0x0) at remote.c:191 #4 0x08126826 in main (argc=9, argv=0xbfc82424) at vdr.c:920 /Peter Odéus

4 5

[PATCH] vcd-0.9 for VDR >= 1.7.3
by Thomas Günther 15 Aug '10

15 Aug '10

Hi! Here is a patch for the vcd plug-in and VDR >= 1.7.3: http://toms-cafe.de/vdr/download/vcd-0.9-1.7.3.diff Tom

2 1

A/V out of sync for BSkyB channels Channel4, More4, E4, Film4
by Günter Merz 27 Jul '10

27 Jul '10

Hi, I'm looking for help with my vdr 1.6 system. I think the problem only affects BSkyB channels Channel4, More4, E4 and Film4: those channels a/v are out of sync (sometimes more, sometimes less). Recordings from those channels are also affected. I think that at some point, I didn't have this a/v sync issue, but I could be wrong. My vdr uses vdr-xine with a new xine-lib 1.2 (for vdpau) as output device. Due to the unstable nature of some of the components, I've tried exchanging parts of my output chain to their stable counterparts: xine-lib 1.1.17, ffmpeg-0.5, xine-ui-0.99.5. Also, I've tried deactivating "Dynamic Ticks" in the kernel. None of those measures have helped. Can anyone here point me to where the a/v sync issue is most likely to originate from? Can it be vdr itself? Does vdr process video separate from audio? >From what I've read so far, xine-lib delegates MPEG TS processing to ffmpeg.

6 17

portability or VDR on FreeBSD
by Joerg Pulz 10 Jul '10

10 Jul '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello list. As the subject already says, this is about VDR portability, or how to get VDR up and running on a FreeBSD system. In times where we have such really nice plugins like softdevice and streamdev, we no longer need real MPEG2 or DVB hardware in a VDR system. As i want to use my FreeBSD systems to watch TV or play VDR recordings i decided to give porting VDR to FreeBSD a try. Attached you can find the results. In short terms: It simply works! The only missing feature right now is, starting VDR as root and switching to another user (-u command line option). For now it is possible to watch any recording made by a VDR with real hardware if the video directory is directly accessible over the network (mountable by the client) or the use the streamdev plugin to stream VDR to VDR. All tests where done using a Linux system with two FF-DVB-S devices, streamdev-server plugin and NFS exported video directory plus a wired and a wireless FreeBSD-7.0 client running VDR with streamdev-client and softdevice plugin. As far as i could test the whole setup until now, everything works the same way on FreeBSD as it does under Linux and i now have real channel-hopping. The patches are made in a way that a patched VDR will still compile under Linux. Every modification, to the source or to the Makefiles is ifdef'd out. So unless you say you want to compile VDR for FreeBSD you have an unmodified version of source. In case the ML software strips the attachments, the files are also available for download at: ftp://ftp.frm2.tum.de/pub/jpulz/VDR/ Thoughts or comments from others are welcome. regards Joerg - -- The beginning is the most important part of the work. -Plato -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFH0Dy8SPOsGF+KA+MRAmVBAJ9Tzfxg0zWNN/fEX8vfeMOW2muvSACgivha raTzC4R92jZ+Petp9Mqwr9E= =f08n -----END PGP SIGNATURE-----

2 3

Dual DVB-S2 Tuner cards
by Theunis Potgieter 25 Jun '10

25 Jun '10

Hi guys, do any of you have information with regards to Dual DVB-S2 Tuners on a PCI or preferably a PCI-E type card working on vdr? I did have a look on http://www.linuxtv.org/wiki/index.php/DVB-S2_PCIe_Cards But only mentions 2 and they seem to be a rare find. Well at least where I live. Does anybody else know of working DVB-S2 cards for Linux? I did find plenty of Hybrid/Dual type cards but they seem to be supporting DVB-T + DVB-S/S2 and not even both at the same time :( Any advice would be appreciated. Thanks, Theunis

11 13

Feature request: program guide scroll
by István Füley 13 Jun '10

13 Jun '10

Hello list, At the moment if I press the Guide button (or select a specific program from EPG list) i can see the detailed description of the event. Now pressing up/down or left/right scrolls the "Long Description", if this doesn't fit in the OSD window. I wonder if it's possible to implement a different behaviour for the left/right keys: to "scroll" between programs. Pressing right should bring up the next event, pressing left should bring up the previous event. To scroll in the OSD window Up and Down are fine. thanks, Füley István

4 5

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr March 2010