vdr April 2008

vdr@linuxtv.org

106 participants
122 discussions

Defunct screensaver processes under Xine
by Todd Luliak 15 Apr '08

15 Apr '08

I've been running VDR with a FF card so I'm new to the xine-pluginmethod of running things. I find that the VDR machine is creating avery large number of defunct screensaver processes under Xine-UI. Theydo not clear until Xine is stopped and though they do not take up anysystem resources, they can't be a good thing. I've disabled thescreensaver from the GUI, from the command line, and made thegnome-screensaver app itself non-executable with a chmod -x. I am currently running vdr 1.5.12 with v4l drivers, CoreAVC processes,"walery" xine-lib from the list, Xine-UI 0.99.6, Xine-plugin 0.8.2under Debian 2.6.24-rc4. Pretty sure I'm running Gnome, but this whole X11 thing is new. Much happier at a prompt...I know how to configure THAT! -----snip------- top - 12:07:01 up 16:54, 2 users, load average: 2.58, 2.51, 1.57 Tasks: 212 total, 3 running, 140 sleeping, 4 stopped, 65 zombie -----snip------- top - 12:17:08 up 17:04, 2 users, load average: 2.21, 2.68, 2.10 Tasks: 235 total, 3 running, 140 sleeping, 4 stopped, 88 zombie -----snip------- top - 12:27:04 up 17:14, 2 users, load average: 2.59, 2.73, 2.38 Tasks: 256 total, 5 running, 138 sleeping, 4 stopped, 109 zombie -----snip------- top - 13:50:39 up 18:37, 2 users, load average: 0.72, 0.92, 1.04 Tasks: 614 total, 1 running, 142 sleeping, 4 stopped, 467 zombie -----snip------- root 6980 6570 0 06:52 ? 00:00:00 [gnome-screensav] <defunct> ... root 26745 25679 0 13:44 ? 00:00:00 [gnome-screensav] <defunct> root 26746 6946 0 13:44 pts/3 00:00:00 ps -ef I'd be happy if the screensaver never ran again, as it's of no use here whatsoever. Where do I begin looking to curb the creation of these zombies? ____________________________________________________________________________________ Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ

2 1

Quota and VDR
by Manfred Schmidt-Voigt 14 Apr '08

14 Apr '08

Hello List, I have a diskless VDR machine in my livingroom (so its very quit). My /video is mounted by nfs from a Servermachine under the roof. On that server I have set a groupquota for that /video directory to save some place for other applikations on that filesystem (raid 5 - 4x400G). I have exeeded now the space on that filesystem for that group and in the syslog of the VDR I can see related messages. Example: Mar 9 08:52:32 stereo vdr: [4167] switching device 1 to channel 1 Mar 9 08:52:32 stereo vdr: [4167] timer 18 (1 0852-1152 '@TITLE EPISODE') start Mar 9 08:52:32 stereo vdr: [4167] Title: 'Tigerenten Club' Subtitle: 'Der Club zum Mitmachen' Mar 9 08:52:32 stereo vdr: [4167] record /video/(a)Tigerenten_Club_Der_Club_zum_Mitmachen/2008-03-09.08.52.50.99.rec Mar 9 08:52:32 stereo vdr: [4167] creating directory /video/@Tigerenten_Club_Der_Club_zum_Mitmachen Mar 9 08:52:32 stereo vdr: [4167] ERROR: /video/@Tigerenten_Club_Der_Club_zum_Mitmachen: Disk quota exceeded But the VDR Software doesn't recognize that. It does not start to mark old recording for removing. In the menu overview it show still some hours free space util the end of the complete filesystem. Now my question: Do I have to configure something special in VDR that it recognizes the Quota setting of that directory or have I to use userquota for the user of VDR (in my case it is root but if it is the only solution I could change it to a regular user, but only if it helps for my problem)? Some revision data: VDR 1.4.5 ( yes, I'm waiting for 1.6 ) Debian Etch on both VDR and Server Thank you Manfred -- ------- Manfred Schmidt-Voigt ------- ----- www.mannitec.de ----- ------- mailto:manfred.schmidt-voigt@mannitec.de -------

2 5

DVB API Wrapper for VDR 1.7.0
by Udo Richter 14 Apr '08

14 Apr '08

Hi list, There's a new version of the DVB API wrapper patch that adds fallback compatibility to the current stable DVB API without multiproto support. The new version also fixes a bug with the default DVBFE_MOD_AUTO modulation on DVB-S. Also, the patch for VDR-1.5/1.6 that allows to read a channels.conf from 1.7 is now available on that page. Support for DVBFE_SET_DELSYS will follow in next version. Get it: http://www.udo-richter.de/vdr/patches.en.html#dvb-api-wrapper http://www.udo-richter.de/vdr/patches.html#dvb-api-wrapper Cheers, Udo

2 2

HD PCIe boards
by lucian orasanu 14 Apr '08

14 Apr '08

Hy too all. It seams the first hardware capable of MPEG 2 and H.264 encoding and decoding at 1080p full HD resolution, will be from Toshiba, look here: http://www.reghardware.co.uk/2008/04/08/tosh_samples_spursengine/ ____________________________________________________________________________________ You rock. That's why Blockbuster's offering you one month of Blockbuster Total Access, No Cost. http://tc.deals.yahoo.com/tc/blockbuster/text5.com

5 4

softdevice and lnb-sharing - is it possible?
by Andreas Holzhammer - GMX 14 Apr '08

14 Apr '08

Hi, I'm currently struggling with lnb-sharing on my budget-only system (Samsung SMT7020 internal DVB-S together with an USB-based Opera S1 DVB-S device). This is running vdr 1.6.0 with the vdr-extensions patch 58 (with lnb-sharing and syncearly only) and softdevice (cvs from February 20th). I can watch live TV fine for a few seconds/minutes, but then the picture freezes. I asume this is because the free dvb-device does it's transponder scans and switches to a wrong polarity/band. Both devices are configured to use the same LNB: root@samsung:~# grep LNB /etc/vdr/setup.conf Card1usesLNBnr = 1 Card2usesLNBnr = 1 Card3usesLNBnr = 3 VerboseLNBlog = 1 The "Card3usesLNBnr" is autogenerated by vdr, and doesn't show up in the LNB configuration OSD menu. Setting it manually to 1 doesn't help. This is what the log says (note that vdr thinks there is a LNB 9 available): Apr 12 20:32:46 (none) user.err vdr: [1469] probing /dev/dvb/adapter0/frontend0 Apr 12 20:32:46 (none) user.err vdr: [1492] tuner on device 1 thread started (pid=1492, tid=1492) Apr 12 20:32:46 (none) user.err vdr: [1493] section handler thread started (pid=1493, tid=1493) Apr 12 20:32:46 (none) user.err vdr: [1469] probing /dev/dvb/adapter1/frontend0 Apr 12 20:32:46 (none) user.err vdr: [1495] tuner on device 2 thread started (pid=1495, tid=1495) Apr 12 20:32:46 (none) user.err vdr: [1496] section handler thread started (pid=1496, tid=1496) Apr 12 20:32:46 (none) user.err vdr: [1469] found 2 video devices Apr 12 20:32:46 (none) user.err vdr: [1469] initializing plugin: softdevice (0.4.0): A software emulated MPEG2 device Apr 12 20:32:46 (none) user.err vdr: [1469] [softdevice] videoOut OK ! [...] Apr 12 20:36:03 (none) user.err vdr: [8596] [VideoOut]: 720x576 [0,0 720x576] -> 720x576 [0,0 720x576] Apr 12 20:36:05 (none) user.err vdr: [8575] changing pids of channel 2 from 110+110:120=deu,121=2ch;125=dd:0:130 to 110+110:120=deu,121=2ch;125=dd:131=deu:130 Apr 12 20:36:05 (none) user.err vdr: [8561] retuning due to modification of channel 2 Apr 12 20:36:05 (none) user.err vdr: [8561] LNB 9: Request for channel 2 on device 2. MaxBadPriority is -2 Apr 12 20:36:05 (none) user.err vdr: [8561] LNB 9: Device check for channel 2, LNBstate 1 on device 2, current LNBstate -1. No other devices affected Apr 12 20:36:05 (none) user.err vdr: [8561] switching to channel 2 Apr 12 20:36:05 (none) user.err vdr: [8591] transfer thread ended (pid=8591, tid=8591) Apr 12 20:36:05 (none) user.err vdr: [8561] buffer stats: 76516 (3%) used Apr 12 20:36:05 (none) user.err vdr: [8561] LNB 1: Request for channel 2 on device 0. MaxBadPriority is -2 Apr 12 20:36:05 (none) user.err vdr: [8561] LNB 1: Request for channel 2 on device 1. MaxBadPriority is -2 Apr 12 20:36:05 (none) user.err vdr: [8561] LNB 9: Switching device 2 to channel 2 Apr 12 20:36:05 (none) user.err vdr: [8561] LNB 1: Switching device 0 to channel 2 Apr 12 20:36:05 (none) user.err vdr: [8606] transfer thread started (pid=8606, tid=8606) Apr 12 20:36:05 (none) user.err vdr: [8593] TS buffer on device 1 thread ended (pid=8593, tid=8593) Apr 12 20:36:05 (none) user.err vdr: [8592] buffer stats: 76140 (3%) used Apr 12 20:36:05 (none) user.err vdr: [8592] receiver on device 1 thread ended (pid=8592, tid=8592) Apr 12 20:36:05 (none) user.err vdr: [8607] receiver on device 1 thread started (pid=8607, tid=8607) Apr 12 20:36:05 (none) user.err vdr: [8608] TS buffer on device 1 thread started (pid=8608, tid=8608) Apr 12 20:36:05 (none) user.err vdr: [8611] [softdevice-audio]: xrun Apr 12 20:37:02 (none) user.err vdr: [8561] LNB 1: Request for channel 130 on device 0. MaxBadPriority is -2 Apr 12 20:37:02 (none) user.err vdr: [8561] LNB 1: Request for channel 63 on device 0. MaxBadPriority is -2 Apr 12 20:37:02 (none) user.err vdr: [8561] LNB 1: Request for channel 62 on device 0. MaxBadPriority is -2 Apr 12 20:37:02 (none) user.err vdr: [8561] LNB 1: Request for channel 54 on device 0. MaxBadPriority is -2 Apr 12 20:37:02 (none) user.err vdr: [8561] LNB 1: Request for channel 1 on device 0. MaxBadPriority is -2 Apr 12 20:37:02 (none) user.err vdr: [8561] LNB 1: Request for channel 71 on device 0. MaxBadPriority is -2 Apr 12 20:37:02 (none) user.err vdr: [8561] LNB 1: Request for channel 2 on device 0. MaxBadPriority is -2 Apr 12 20:37:02 (none) user.err vdr: [8561] LNB 1: Request for channel 60 on device 0. MaxBadPriority is -2 Apr 12 20:37:02 (none) user.err vdr: [8561] LNB 1: Request for channel 68 on device 0. MaxBadPriority is -2 Apr 12 20:37:02 (none) user.err vdr: [8561] LNB 1: Request for channel 24 on device 0. MaxBadPriority is -2 Apr 12 20:37:02 (none) user.err vdr: [8561] LNB 1: Request for channel 88 on device 0. MaxBadPriority is -2 Apr 12 20:37:02 (none) user.err vdr: [8561] LNB 1: Request for channel 3 on device 0. MaxBadPriority is -2 Apr 12 20:37:02 (none) user.err vdr: [8561] LNB 1: Request for channel 23 on device 0. MaxBadPriority is -2 Apr 12 20:37:02 (none) user.err vdr: [8561] LNB 1: Request for channel 36 on device 0. MaxBadPriority is -2 Apr 12 20:37:02 (none) user.err vdr: [8561] LNB 1: Request for channel 34 on device 0. MaxBadPriority is -2 Apr 12 20:37:02 (none) user.err vdr: [8561] LNB 1: Request for channel 15 on device 0. MaxBadPriority is -2 Apr 12 20:37:02 (none) user.err vdr: [8561] LNB 1: Request for channel 4 on device 0. MaxBadPriority is -2 Apr 12 20:37:02 (none) user.err vdr: [8561] LNB 1: Request for channel 40 on device 0. MaxBadPriority is -2 Apr 12 20:37:02 (none) user.err vdr: [8561] LNB 1: Request for channel 148 on device 0. MaxBadPriority is -2 Apr 12 20:37:02 (none) user.err vdr: [8561] LNB 1: Request for channel 21 on device 0. MaxBadPriority is -2 Apr 12 20:37:02 (none) user.err vdr: [8561] LNB 1: Request for channel 10 on device 0. MaxBadPriority is -2 Apr 12 20:37:02 (none) user.err vdr: [8561] LNB 1: Request for channel 112 on device 0. MaxBadPriority is -2 Apr 12 20:37:02 (none) user.err vdr: [8561] LNB 1: Request for channel 53 on device 0. MaxBadPriority is -2 Apr 12 20:37:02 (none) user.err vdr: [8561] LNB 1: Request for channel 116 on device 0. MaxBadPriority is -2 Apr 12 20:37:02 (none) user.err vdr: [8561] LNB 1: Request for channel 52 on device 0. MaxBadPriority is -2 Apr 12 20:37:02 (none) user.err vdr: [8561] LNB 1: Request for channel 48 on device 0. MaxBadPriority is -2 Apr 12 20:37:02 (none) user.err vdr: [8561] LNB 1: Request for channel 51 on device 0. MaxBadPriority is -2 Apr 12 20:37:02 (none) user.err vdr: [8561] LNB 1: Request for channel 19 on device 0. MaxBadPriority is -2 Apr 12 20:37:02 (none) user.err vdr: [8561] LNB 1: Request for channel 16 on device 0. MaxBadPriority is -2 Apr 12 20:37:02 (none) user.err vdr: [8561] LNB 1: Request for channel 72 on device 0. MaxBadPriority is -2 Apr 12 20:37:02 (none) user.err vdr: [8561] LNB 1: Request for channel 14 on device 0. MaxBadPriority is -2 Apr 12 20:37:02 (none) user.err vdr: [8561] LNB 1: Request for channel 130 on device 1. MaxBadPriority is -2 Apr 12 20:37:02 (none) user.err vdr: [8561] LNB 1: Request for channel 130 on device 1. MaxBadPriority is -2 Apr 12 20:37:02 (none) user.err vdr: [8561] LNB 1: Device check for channel 130, LNBstate 0 on device 1, current LNBstate -1. Conflict with device 0, LNBstate 1 Apr 12 20:37:02 (none) user.err vdr: [8561] LNB 1: Switching device 0 to channel 130 Apr 12 20:37:02 (none) user.err vdr: [8561] LNB 1: Device check for channel 130, LNBstate 0 on device 1, current LNBstate -1. No other devices affected Apr 12 20:37:02 (none) user.err vdr: [8561] LNB 1: Switching device 1 to channel 130 So it looks like vdr detects that there is a conflict, but switches anyway? I tried to fix all devices to use LNB 1 by hacking the vdr source (to get rid of this LNB 9), but this resulted in "channel not available" for all channels. Unfortunately I have no clue how softdevice works, but to me it looks like vdr thinks it has an exclusive LNB which it doesn't have to share. Does anyone run lnbsharing together with softdevice successfully, or am I wasting my time on this? Thanks, Andreas

1 0

[ANNOUNCE] VDR maintenance patch 1.6.0-1
by Klaus Schmidinger 14 Apr '08

14 Apr '08

VDR maintenance patch 1.6.0-1 is now available at ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.6.0-1.diff This is a 'diff' against the official version 1.6.0. Small fixes to the officially released VDR versions will be first made available as "maintenance patches" in the Developer directory, so that they can be reviewed and tested before a new official release is published. So please apply this patch to the original VDR version 1.6.0 and report whether it works (or if it causes any new problems). The changes since version 1.6.0: - Fixed handling the counter in detection of pre 1.3.19 PS data (thanks to Reinhard Nissl). - Improved logging system time changes to avoid problems on slow systems under heavy load (suggested by Helmut Auer). - Fixed initializing the timer's flags in the cTimer copy constructor (thanks to Andreas Mair). - Increased the time between checking the CAM status to 500ms to avoid problems with some CAMs (reported by Arthur Konovalov). Have fun! Klaus

3 3

[ANNOUNCE] H.264 support for VDR-1.7.0
by Reinhard Nissl 13 Apr '08

13 Apr '08

Hi, attached you'll find an updated patch for VDR-1.7.0. The patch includes now the formerly released addon patches and fixes. Have a look at this page for more instructions on this concern: http://www.vdr-wiki.de/wiki/index.php/OpenSUSE_VDR_DVB-S2_-_xine Bye. -- Dipl.-Inform. (FH) Reinhard Nissl mailto:rnissl@gmx.de

1 0

[ANNOUNCE] VDR developer version 1.7.0
by Klaus Schmidinger 13 Apr '08

13 Apr '08

VDR developer version 1.7.0 is now available at ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.7.0.tar.bz2 A 'diff' against the latest stable version is available at ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.6.0-1.7.0.diff WARNING: ======== This is a *developer* version. Even though *I* use it in my productive environment, I strongly recommend that you only use it under controlled conditions and for testing and debugging. This version switches to the "multiproto" driver and no longer works with non-multiproto drivers. Hopefully there will soon be *one* driver source that combines the latest "multiproto" version with Oliver Endriss' "full ts mod" changes ;-). Note that this version just implements basic DVB-S2 handling. There is no support for H.264 etc. yet. This will come in later 1.7.x versions. The changes since version 1.6.0: - Re-implemented handling of DVB-S2, which first appeared in version 1.5.14, but was revoked in version 1.5.15 in favor of making a stable version 1.6.0. VDR now requires the "multiproto" DVB driver, e.g. from http://jusst.de/hg/multiproto. Note that the channels.conf file now supports additional parameters, so you may want to make sure you have a backup of this file in case you need to go back to the previous version of VDR! - Fixed displaying transponder data when it is modified (thanks to Reinhard Nissl). - Fixed handling the counter in detection of pre 1.3.19 PS data (thanks to Reinhard Nissl). - Improved logging system time changes to avoid problems on slow systems under heavy load (suggested by Helmut Auer). - Now setting the thread name, so that it can be seen in 'top -H' (thanks to Rolf Ahrenberg). - Fixed initializing the timer's flags in the cTimer copy constructor (thanks to Andreas Mair). - Fixed setting the OSD level in the 'osddemo' example (thanks to Wolfgang Rohdewald). - Increased the time between checking the CAM status to 500ms to avoid problems with some CAMs (reported by Arthur Konovalov). Have fun! Klaus

2 1

vdr 1.7.0 does not compile
by Helmut Auer 13 Apr '08

13 Apr '08

Hi List, When compiling vdr-1.7.0 i got this error: g++ -g -O2 -Wall -Woverloaded-virtual -Wno-parentheses -march=pentium3 -O2 -pipe -fomit-frame-pointer -fforce-addr -falign-functions=4 -fprefetch-loop-arrays -ffast-math -fPIC -c -DUSE_CHANNELSCAN -DUSE_CMDSUBMENU -DUSE_CUTTERLIMIT -DUSE_CUTTERQUEUE -DUSE_CUTTIME -DUSE_DELTIMESHIFTREC -DUSE_DDEPGENTRY -DUSE_DOLBYINREC -DUSE_DVDARCHIVE -DUSE_DVLRECSCRIPTADDON -DUSE_DVLVIDPREFER -DUSE_DVLFRIENDLYFNAMES -DUSE_GRAPHTFT -DUSE_HARDLINKCUTTER -DUSE_IPTV -DUSE_JUMPPLAY -DUSE_LIEMIKUUTIO -DUSE_LIRCSETTINGS -DUSE_LIVEBUFFER -DUSE_MAINMENUHOOKS -DUSE_MENUORG -DUSE_NOEPG -DUSE_OSDMAXITEMS -DUSE_PINPLUGIN -DUSE_PLUGINMISSING -DUSE_ROTOR -DUSE_SETTIME -DUSE_SOURCECAPS -DUSE_SORTRECORDS -DUSE_TIMERCMD -DUSE_TIMERINFO -DUSE_VALIDINPUT -DUSE_VOLCTRL -DUSE_WAREAGLEICON -DUSE_YAEPG -DREMOTE_KBD -DREMOTE_LIRC -DLIRC_DEVICE=\"/dev/lircd\" -DRCU_DEVICE=\"/dev/ttyS1\" -D_GNU_SOURCE -DVIDEODIR=\"/video\" -DCONFDIR=\"/etc/vdr\" -DPLUGINDIR=\"./PLUGINS/lib\" -DLOCDIR=\"./locale\" -DVFAT -I/usr/include/freetype2 -I/usr/portage/distfiles/hg-src/v4l-dvb-multiproto/multiproto/linux//include dvbdevice.c dvbdevice.c: In member function 'bool cDvbTuner::SetFrontend()': dvbdevice.c:271: error: 'struct dvbfe_info' has no member named 'delivery' dvbdevice.c:286: error: 'struct dvbfe_info' has no member named 'delivery' dvbdevice.c:307: error: 'struct dvbfe_info' has no member named 'delivery' make: *** [dvbdevice.o] Error 1 The driver I am using ist http://jusst.de/hg/multiproto svn from today, and the included frontend.h really has no delivery member in this structure. -- Helmut Auer, helmut(a)helmutauer.de

3 4

Re: [vdr] [Announce] vdr-fritzbox-1.0.0
by Joachim Wilke 13 Apr '08

13 Apr '08

Dear Fritz!Box- and VDR-Users, a new version of the Fritz!Box Plugin is available at http://joachim-wilke.de/index.htm?alias=vdr-fritz This is the recommended stable version for users of VDR 1.6. - - - The Fritz!Box Plugin connects to your Fritz!Box to inform you about incoming calls. The plugin can automatically mute or pause VDR when a call comes in. Via VDR's main menu you can browse your Fritz!Box phone book, the call lists and initiate calls out of all lists. - - - 2008-04-13: Version 1.0.0 - updated italian translations (provided by Diego [24]) - made "This phonebook is not yet available..." error message non-selectable to avoid a segmentation fault when selecting it (reported by ? [25]) - - - Regards, Joachim.

1 0

← Newer
1
...
5
6
7
8
9
10
11
12
13
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr April 2008