vdr

vdr@linuxtv.org

6731 discussions

Re: [vdr] Defunct screensaver processes under Xine
by Todd Luliak 16 Apr '08

16 Apr '08

>...provide some more lines from above it. It looks like it bombs right about here: (hope it's enough...) <snip> in: make -C ffmpeg/libavcodec libavcodec.a <snip>... In file included from i386/dsputil_mmx.c:30: i386/mmx.h:24:2: warning: #warning Everything in this header is deprecated, use plain asm()! New code using this header will be rejected. i386/h264dsp_mmx.c: In function `put_h264_qpel4_h_lowpass_3dnow': i386/h264dsp_mmx.c:1881: error: can't find a register in class `GENERAL_REGS' while reloading `asm' make[6]: *** [i386/dsputil_mmx.o] Error 1 make[6]: Leaving directory `/usr/local/src/xine-lib-1.2/contrib/ffmpeg/libavcodec' make[5]: *** [ffmpeg/libavcodec/libavcodec.a] Error 2 make[5]: Leaving directory `/usr/local/src/xine-lib-1.2/contrib' make[4]: *** [../../../contrib/ffmpeg/libavcodec/libavcodec.a] Error 2 make[4]: Leaving directory `/usr/local/src/xine-lib-1.2/src/combined/ffmpeg' make[3]: *** [all] Error 2 make[3]: Leaving directory `/usr/local/src/xine-lib-1.2/src/combined/ffmpeg' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/usr/local/src/xine-lib-1.2/src/combined' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/local/src/xine-lib-1.2/src' make: *** [all-recursive] Error 1 display mangler ->gone<- Mmmmmm... better. A pair of CPUs say thanks ! ____________________________________________________________________________________ Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ

2 1

Rotor patches
by Timothy D. Lenz 16 Apr '08

16 Apr '08

There are 2 patches for the Rotor plugin: vdr-1.5.5-rotor.diff Rotor-0.1.4-vdr1.5.10.diff They patch different areas. Are they both needed for vdr-1.6?

1 0

Re: [vdr] Defunct screensaver processes under Xine
by Todd Luliak 15 Apr '08

15 Apr '08

>Do you need to run gnome at all? Its quite processor intensive if all >you are doing is using it to watch TV. See the other recent thread on >starting VDR/xine at boot time using startx / replacing the session >manager and those problems with gnome screensaver won't be apparent. > >Also, there is a later version (patch) of CoreAVC for xine that I >released on the list which will apply to the hg version of xine (with >a bit of tweaking with more recent versions). The updated version will >support channels at resolutions different to 1920x1080i (there are >quite a few of them). > >HTH No, I don't "need" Gnome and am looking into alternatives per your suggestion. I hate the idea of having to run a display manager at all, but the picture looks too good to back out now. ;) On the other note, I've been trying with a current HG of xine-lib: changeset: 10295:c22d7a4b5854 tag: tip parent: 10282:6948d6d0a31e parent: 10294:dcabf02a88e6 user: Darren Salt <linux(a)youmustbejoking.demon.co.uk> date: Tue Apr 15 01:06:51 2008 +0100 summary: Merge from 1.1. and applied the patch "xine-lib-1.2hg-coreavc.diff" with fuzz, then ./autogen.sh --disable-dxr3; make only to end up with : make[6]: *** [i386/dsputil_mmx.o] Error 1 make[6]: Leaving directory `/usr/local/src/xine-lib-1.2/contrib/ffmpeg/libavcodec' make[5]: *** [ffmpeg/libavcodec/libavcodec.a] Error 2 make[5]: Leaving directory `/usr/local/src/xine-lib-1.2/contrib' make[4]: *** [../../../contrib/ffmpeg/libavcodec/libavcodec.a] Error 2 make[4]: Leaving directory `/usr/local/src/xine-lib-1.2/src/combined/ffmpeg' make[3]: *** [all] Error 2 make[3]: Leaving directory `/usr/local/src/xine-lib-1.2/src/combined/ffmpeg' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/usr/local/src/xine-lib-1.2/src/combined' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/local/src/xine-lib-1.2/src' make: *** [all-recursive] Error 1 So I've been trying to work my way around that to no avail. Your thoughts there would be MORE than welcome! ____________________________________________________________________________________ Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ

2 1

Re: [vdr] xineliboutput audio lip sync problems
by Theunis Potgieter 15 Apr '08

15 Apr '08

Well it looks like I'm the only Gentoo user here that is experiencing this problem. I noticed a bit more on when it occurs. I've current changed my vdr process to run at -19 priority to see if it makes any difference. Livetv is some how now correct. But I still experience problems with recordings where cutting/editing occured. So I changed to vdr-softdevice, and I'm experience the same problem. LiveTV is acceptable but still experience audio/video sync problems after the replay has reached a edit/cut mark. (This is a recording that was processed) Any ideas?

2 1

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

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr