vdr

vdr@linuxtv.org

6731 discussions

*** glibc detected *** double free or corruption 1.4.2-1 Patch
by martin 08 Sep '06

08 Sep '06

Hello Klaus, I've problems when implementing the latest 1.4.2.-1 Patch. Here's the problem: I used VDR-Admin to change a timer setting. Every time I try to save the changed timer, VDR crashes, please see attached strace. I've checked against all 1.4.1-* versions, with bigpatch, without. It must be something with the latest 1.4.2-1 Patch. My system is a Pentium-M: [root@htpc /usr/local/src]# cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 13 model name : Intel(R) Pentium(R) M processor 1.70GHz Please let me know, if you need any additional information. Regards, Martin

6 22

Videgor is missing on the plugin list on http://www.cadsoft.de/vdr/plugins.htm
by Rene Bartsch 08 Sep '06

08 Sep '06

Hi, the Videgor plugins are missing on the plugin list on http://www.cadsoft.de/vdr/plugins.htm. The website is http://www.videgor.net >From the description: Videgor is a peer-to-peer hard disc video recorder. With its help it is possible to record missed broadcasts from the past. Videgor is based on a extension of Klaus Schmidinger's Video Disk Recorders (VDR). VDR is a program that converts a Linux PC into a video disc recorder with time shifting capabilities. Videgor extends the VDR to a distributed video recorder (D-VDR) by including three plugins ((D-VDR-EPG, D-VDR-SCHEDULE, D-VDR-VIDEOTRANS) and by automatically connecting the participating devices to a peer-to-peer network (IGOR). With this peer-to-peer system the Videgor recorders can share recordings. Videgor was developed at the University of Karlsruhe as part of a DFG research project for peer-to-peer overlay networks. The idea for this projects is derived from the desire not only to do research on the improvement of overlay networks but how to apply these research results in practice. Renne

5 7

GCC 4.1.1 and glibc 2.4 nptlonly with vdr 1.4.x + subtitles plugin for extra
by Jukka Palko 08 Sep '06

08 Sep '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Anyone had good experiences using this combination? Looks like my vdr system started to have some subtitles plugin issues on Finnish Yle channels after upgrading gcc and glibc. Looks like from time to time on subtitles plugin utilizing recordings I get nasty image breakdown. Not entirely sure that subtitles plugin is the culprit, could be other issues naturally with those new parts. Especially with nptl only system. :) This has though only shown up in recordings from Yle channels in Finland. The MTV3, Nelonen and SubTV plus my cable tv subscription channels have no such problems. This is why I have suspected the subtitles plugin. - -- Jukka Palko jpalko(a)gmail.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFAAItgfJN/zhm0W0RAoRzAJsFj/xlMlE9vbn8nTEUz8t3Ff8KTACdFS0y RktMNukSxT3nHGFP3D3RBgE= =yHWQ -----END PGP SIGNATURE-----

2 2

execute command after vdr starts
by C.Y.M 08 Sep '06

08 Sep '06

Is there a command line switch that would allow me to define a command vdr must excute after initial startup? I see one for before and after recordings, but I am looking for a way to execute a command after startup only. Best Regards.

3 8

Problem with xineliboutput
by Jose Alberto Reguero 07 Sep '06

07 Sep '06

I have a problem with xineliboutput (latest cvs). When the client vdr-sxfe crash, X freeze and I must to harware reset. It can be reproduce by presing control-c when playing vdr-sxfe. I dont now if it is a prolem of vdr-sxfe or of the X drivers(Xorg 7.1 + nvidia) Thanks Jose Alberto

1 2

Viaccess Cam Update
by Marco Goebenich 05 Sep '06

05 Sep '06

Hi! I got a problem while receiving TF1 (TPS France). I can tune to this channel, and then view the channels for about 20 seconds, but after that the stream stops, the screen is somehow distorted, if I switch again to TF1 I get the message "No right to watch" and the channel is never shown until I do a CAM reset. My Viaccess CAM has firmware version 1.07, and I tried to update the firmware to 1.08, I tried vdr-1.3.38 and 1.4.2, but after the message "Please do not extract ..." no further messages are shown, in the manual for updating the CAM they tell that the update should need 30 minutes, I had this channel tuned about 2 days and nothing happed. No progress messages, and no update. After reinserting the CAM the firmware version is still 1.0.7. Can anybody tell me what to do, to get TF1 working again? Regards Marco -- vierzehn Bahnhofstr. 27 Telefon 0 26 32 / 98 98 - 120 public relations 56626 Andernach Telefax 0 26 32 / 98 98 - 111 GmbH & Co. KG E-Mail: mg(a)vierzehn.com

4 4

LCDproc plugin 0.1.0 with VDR 1.4.1-1
by Christian Kruft 05 Sep '06

05 Sep '06

Hey, does anybody have a patch to make the lcdproc 0.1.0 plugin work with VDR 1.4.1-1 ? I've tried one from January but this patch doesn't help. While starting VDR I got this errors: Close Called Not Connected !!! After that, VDR shuts down. LCDproc is working fine, only this plugin won't work. Greetings, Christian

2 1

Recording priority question
by Jukka Palko 05 Sep '06

05 Sep '06

I am curious on the recording priorities and especially what is the way vdr decides which card to use to record at a given time. My system is now setup this way: Card #1: Technotrend C2100 rev2.1 Card #2: Hauppauge Nexus-CA Card #3: Technotrend C2100 rev2.1 -card #3 has the CI attached to it and a Conax CAM I have setup the card #3 to be my viewing card. So does vdr select the card which to use for recording by starting from card #1 and then if card #1 is busy, then card #2, etc? And if card #2 is recording and card #1 and #3 are not, then card #1 is used? Or is the card chosen in such a way that if one card is already tuned to the frequency then that card is used for recording that channel? The reason I am asking this is that I wish to keep my card #3 free for viewing those encrypted channels and still be able to easily choose recording on those encrypted channels. I noticed there is the priority setting, which for recording I currently have set to 50 and the primary card usage is allowed for only higher priorities than 55. This would be one way to keep my card free, but then if I want to record on encrypted channels, I need to set the recording priority to higher than 55? Not exactly easy for other members of my family. They can be taught to do it so, but wish there was an easier solution. ;) In certain ways I was whondering if there could have been a way to set those encrypted channels to have a higher priority than 55 on recording them so that recording would just happen. I'm basing my question on the understanding that vdr can only tune into encrypted channels using the card that has the CAM attached to. Is this valid still? -Jukka -- Jukka Palko jpalko(a)gmail.com

3 3

When will first 1.5 version of VDR see the daylight?
by Pasi Juppo 05 Sep '06

05 Sep '06

Hi, Not that I have any urgent need for v1.5-series VDR but just interested in when first version is planned to released for public testing. I assume that it is already under development. Br, Pasi

4 6

changes to runvdr for a nexus-s
by C.Y.M 05 Sep '06

05 Sep '06

Here is an example of the changes that I have had to make to runvdr so that my nexus-s works. I have added a maximum retry value to runvdr so that vdr will not keep attempting to start over and over if there is a major problem with reception. Also, I have added a minimum runtime (in seconds) that vdr must have in order to continue attempting to restart after a crash. For example, if vdr crashes within 10 seconds and the minimum runtime required is 45 seconds, then runvdr will consider that VDR has major problems and it will not try to keep restarting up to the maximum allowed retries. However, the maximum retry value can be set to "0" which would tell runvdr to attempt a restart unlimited times after crashing. BR. #!/bin/sh # insmod modules from current directory without having to install them first # KERNELVER=`uname -r` # KERNELDIR="/lib/modules/$KERNELVER/misc" sync function DriverLoaded() { grep -qse dvb[-_]core /proc/modules } case "$1" in load) if ! DriverLoaded; then echo -n -e "\nInserting DVB modules into kernel\n" # av7110 based "full featured" cards modprobe stv0299 # saa7146 based siemens/technotrend/hauppauge cards modprobe dvb-ttpci # wait for udev to create the devices before continuing until [ -e /dev/dvb/adapter0/video0 ]; do sleep 1 done if [ -e "/usr/local/bin/loadkeys/av7110_loadkeys" ]; then /usr/local/bin/loadkeys/av7110_loadkeys /usr/local/bin/loadkeys/hauppauge_grey.rc5 > /proc/av7110_ir sleep 1 fi else echo -e "DVB Drivers already loaded..\n" fi ;; debug) if ! DriverLoaded; then echo -n -e "\nInserting DVB modules (debug) into kernel\n" # av7110 based "full featured" cards modprobe stv0299 debug_switch_timing=1 # saa7146 based siemens/technotrend/hauppauge cards modprobe dvb-ttpci debug=247 until [ -e /dev/dvb/adapter0/video0 ]; do sleep 1 done if [ -e "/usr/local/bin/loadkeys/av7110_loadkeys" ]; then /usr/local/bin/loadkeys/av7110_loadkeys /usr/local/bin/loadkeys/hauppauge_grey.rc5 > /proc/av7110_ir sleep 1 fi else echo -e "DVB Drivers already loaded..\n" fi ;; unload) if lsmod | grep -q "^$(echo dvb_ttpci|sed -e 's/-/_/g') " > /dev/null 2>&1; then echo -n -e "\nRemoving DVB modules from kernel\n" rmmod ves1x93 dvb_ttpci saa7146_vv video_buf saa7146 videodev v4l1_compat \ v4l2_common ttpci_eeprom stv0299 dvb_core echo else echo -e "DVB Drivers not loaded..\n" fi ;; reload) $0 unload && $0 load ;; *) echo "Usage$0 {load|unload|debug|reload}" exit 1 esac sync

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr