vdr May 2005

vdr@linuxtv.org

154 participants
186 discussions

RE: [vdr] Cut Recordings SVDRP patch
by christian jacobsen 04 Jun '05

04 Jun '05

Hallo, > I wanted to write this patch for a long time - now I finally > managed to get > it done. > > I added a SVDRP command "CUTR <number>" that starts a cutting > thread for the > numbered recording on the server Nice idea :) I might add this to AutoCutter as the second option to vdrcutter2. Maybe you should take a look at AutoCutter (English README in the tar) : http://www.vdrportal.de/board/thread.php?threadid=31155 It adds recordings to different Queues and could run on your server but be controlled by your client :) Means (if you like) run NoAD after recording and later when you are ready Batch-Cut all recording with on single commands.conf command. It even supports sharemarks - up/downloading cut-marks from an Web Server - http://www.vdrportal.de/board/thread.php?threadid=34492 The next version 0.3.0 (release within a 3-5 days) is far more configurable than before, has further multi-disk system Optimizations and Renaming of Recording. You can decide what should happen to a recording based on the Channel it was recorded on, Recordingname or summary.vdr content. More when it is released ;) Greetings Christian Jacobsen

3 2

[ANNOUNCE] vdr-pvrinput-0.0.1
by Andreas Regel 03 Jun '05

03 Jun '05

Hello, here is a first release of the pvrinput plugin for VDR. It uses a Hauppauge PVR card (supported by ivtv drivers) as an input device for VDR. I am using it with driver version 0.2.0rc3j and encoder firmware 2.04.211. I have written this plugin because I was a bit unhappy about some things with analogtv. Motivated by a mail from Lars Altenhain on this list I tried an approach a bit different from the analogtv plugin. The reading of the PES data an the conversion to TS is done in a thread in the background without interrupting it on channel switch. The packets are then read out and delivered to VDR in the GetTSPacket function. Additionally the plugin reads the teletext data from the vbi device (/dev/vbi0 is hardcoded at the moment) and converts it to TS packets that the osdteletext plugin is able to receive. Sometimes one or two lines are wrong but its working quite good here. Compared to the analogtv plugin the following is better here with my configuration (Hauppauge PVR 250, Kernel 2.6, ivtv 0.2.0rc3j): - Faster channel switching - no video flickerung after channel switch - just minimal stuttering in sound after channel switch - and of course teletext support Expect problems to get it running in your environment, especially regardings device configuration :). You can find it here: http://home.arcor.de/andreas.regel/files/vdr-pvrinput-0.0.1.tgz Andreas

2 2

[Announce] LNB-sharing patch for VDR 1.3.25
by Matthias Lötzke 02 Jun '05

02 Jun '05

Hello! A new release of the configurable LNB-sharing patch for VDR 1.3 is available at: http://xn--ltzke-jua.de/dvb/VDR_LNB_sharing_patch/configurableLNBshare-VDR_… Changes: - adapted to VDR 1.3.25 The DiSEqC support still needs more testing - I do not have DiSEqC hardware myself. Please provide feedback. I have received a report of problems with a mixed DVB-T DVB-S setup. Due to the lack of hardware I cannot confirm/deny/debug the issue. Does anybody else encounter problems changing the channel of a DVB-T card while recording a DVB-S channel with vertical polarization? For general information about the LNB-sharing patch have a look at: http://xn--ltzke-jua.de/dvb/VDR_LNB_sharing_patch/Description.txt http://www.vdr-wiki.de/wiki/index.php/LNB-Sharing-Patch (german) Matthias.

3 4

vdr delivers wrong time after sucessfull recording
by Rainer Zocholl 02 Jun '05

02 Jun '05

Why does VDR 1.24 deliver the same wakeup time twice? (Debian-Kernel 2.6.11) When VDR shuts down, the wakeup time is OK. But after that power on occured and the recording finshed, VDR delivers the same time again. See partial /var/log/syslog below Too in noticed that the automatically catched "text" for the recording title does (almost?) always belong to the previous program and not to the recorded. 04:05:06 msi vdr[5555]: executing '/video0/pwroff 1117519200 14094 1 "Morgenmagazin" 0' 04:05:06 msi pwroff: VDR shutdown 1:1117519200 2:14094 3:1 4:Morgenmagazin 5:0 04:05:07 msi pwroff: no one logged in 04:05:08 msi pwroff: /proc/acpi/alarm:2005-05-31 06:55:00 Waketime:2005-05-31 06:55:00 04:05:08 msi /video0/pwroff: VDR shutdown delay now 1:1117519200 2:14094 3:1 4:Morgenmagazin 5:0 04:05:08 msi shutdown[7127]: shutting down for system halt 04:05:08 msi init: Switching to runlevel: 0 04:05:08 msi vdr[5555]: max. latency time 60 seconds .. 04:05:22 msi kernel: Kernel logging (proc) stopped. 04:05:22 msi kernel: Kernel log daemon terminating. 04:05:22 msi exiting on signal 15 power off wakeup 06:56:31 msi syslogd 1.4.1#16: restart. 06:56:31 msi kernel: klogd 1.4.1#16, log source = /proc/kmsg started. ... 06:57:02 msi logger[5429]: starting /root/video/VDR/runvdr 06:57:04 msi kernel: lirc_serial: auto-detected active low receiver 06:57:04 msi kernel: lirc_dev: lirc_register_plugin: sample_rate: 0 06:57:06 msi vdr[5554]: VDR version 1.3.24 started ...recording... 07:32:22 msi vdr[5554]: executing '/video0/pwroff 1117519200 1658 1 "Morgenmagazin" 0' 07:32:22 msi pwroff: VDR shutdown 1:1117519200 2:1658 3:1 4:Morgenmagazin 5:0 07:32:22 msi pwroff: no one logged in 07:32:23 msi pwroff: /proc/acpi/alarm:2005-05-31 06:55:00 Waketime:2005-05-31 06:55:00 07:32:23 msi /video0/pwroff: VDR shutdown delay now 1:1117519200 2:1658 3:1 4:Morgenmagazin 5:0 07:32:23 msi shutdown[6166]: shutting down for system halt 07:32:23 msi init: Switching to runlevel: 0 07:32:23 msi pwroff: has a problem? shutdown failed! power off no wake upp... (should have been 10:50) timer.conf.. Sorry, none. i made that timer a "one shot" and VDR already had deleted it. (Is there no flag to tell VDR *not* to delete one-shots automatically? Somestimes a recoding missmatched teh actual schedule. So it's nice to catch an old one-shot, because EPG does not go very much backwards nor very much into the future.) Rainer---<=====> Vertraulich // // <=====>--------------ocholl, Kiel, Germany ------------

6 18

UPT errors on DVB-T (Re: [vdr] VDR Stability)
by Rainer Zocholl 01 Jun '05

01 Jun '05

adrian.challinor(a)osiris.co.uk(Adrian P Challinor) 30.05.05 23:51 >I have used VDR for a 18 months now, but in the last 2 months found >that stability has gone completely out of the window. It started when >I tried to get the vdrsync code working to burn dvd's (never >successful). >I have a Pentium P4, 2.4Ghz, >512 MB Ram, >2 x 120 GB IDE disks, Which type/interfaces? >with an ASUS motherboard. Which asus board? ("nvram-wakeup -d" will show it) >It seems that mostly higher >Cards are a TT-FF DVB-T Which version? >and a Nebula DVB budget card. dto. >I had so many problems I reverted to rebuilding the system from >scratch. I was working on linux 2.6.4, but listening to the list I >upgraded to 2.6.11 on the rebuild. I am using 3 DVB-S TT-FF (v.1.5..2.1) and one Avermedia 771 DVB-T "budget": No problem. Maybe i'll try the TwinHan flying arround here too. >Things have not got better. >It is impossible to record anything from the budget card, which is >VDR's preferred card. Long time ago had the error too. I circumvent with a second FF card...(DVB-S) >I get so many errors trying to sync to skip >bytes to sync to a TS packet it is untrue. >The recording makes old VCR's look good. >Funny this, because the DVBT enabled television is just fine. Because the data does not leave the card... Have you tried to swap the cards in the PCI slots? Too retigger the "PCI elections" in BIOS. >I tried recording just of the TT-FF card. OK, I can only record one >signal at a time, but at least it will be stable, right? Wrong. It's >as unstable as an unpatched windows box. But i assume that this is a hardware problem. Did you try to reduce the CPU clock? Maybe reducing the FSB clock from 133(266?) to 100 is the only way to do, and see if it becomes better. >For example: >May 30 22:50:22 vdr vdr[8931]: timer 1 (1 2240-0045 'Total Recall') >set to event Mon 30.05.2005 22:50-00:35 'Total Recall' >May 30 22:54:11 vdr vdr[8935]: channel 1 (BBC ONE) event 22:50 'Total Recall' status 4 >May 30 23:03:38 vdr vdr[8935]: channel 3 (BBC THREE) event 23:00 'Ideal' status 4 >May 30 23:07:45 vdr vdr[8991]: ERROR: unknown picture type '5' >May 30 23:07:46 vdr vdr[8991]: ERROR: unknown picture type '4' UPT might be caused by a bad antenna too. But you said, the live stream on the FF is OK... >My recording stops in the middle with an unknown picture type. At this >point, nothing I do other than reboot will restore VDRAdmin (probably >the most important feature of VDR IMHO). Which drivers do you use? Did you apply the DVB-drivers from CVS(!) to the linux tree? >I have tried VDR 1.3.25, I have reverted to 1.3.20. I have taken the >latest versions of firmware, I have reverted to those that came with >the card. >Am I alone in thinking that, for anyone who wants to actually watch >TV, the answer is a SKY+ box. Please, god forbid it should come to >that. Linux VDR is NOT just to watch TV quick and easy. It's to LEARN how a computer works ;-) Rainer

2 3

softdevice undefined symbol dts_frame
by Leo Márquez 01 Jun '05

01 Jun '05

Well, finally I have obtained vdr with softdevice build from source. Now when I start vdr with: ./vdr -P "softdevice -vo=dfb:" I get: vdr: ./PLUGINS/lib/libvdr-softdevice.so.1.3.24: undefined symbol: dts_frame I think I'm near the end of the way... -- Salutacions, Leo Márquez [ Enginyeria del Software / Internet ] [ Calidae - www.calidae.com ] [ Himalaya Servers - www.himalayaservers.com ]

5 10

firmware does not load
by Leo Márquez 01 Jun '05

01 Jun '05

Hi!, I have two dvb cards: Hauppauge Nexus-s dvb-s FF Terratec Cinergy 1200 dvb-t budget The two card have the save chipset. I see in lspci: 0000:00:13.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01) 0000:00:14.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01) But when the system starts only load the dbv-t firmware. dmesg: DVB: registering new adapter (Terratec Cinergy 1200 DVB-T). DVB: registering frontend 0 (Philips TDA10046H DVB-T)... The problem comes with the nexus-s. dmesg says: dvb-ttpci: could not load firmware, file not found: dvb-ttpci-01.fw dvb-ttpci: usually this should be in /usr/lib/hotplug/firmware dvb-ttpci: and can be downloaded here http://www.linuxtv.org/download/dvb/firmware/ I'm downloaded the firmware and all of this revisions and have put in the same place that the dvb-t firmware (/usr/lib/hotplug/firmware). The file dvb-ttpci-01.fw exists. I also have tried the /lib/firmware folder to put the firmware but the error continues. Any ideas to solve this problem? Thanks. Leo

2 3

VDR 1.2.6, SuSe 9.0 and Dxr3
by Steve Marshall 01 Jun '05

01 Jun '05

Hi, I'm having a few problems getting VDR to work with dxr3 version 0.2.2 (and others). When I attempt to start vdr I get an error message stating... "vdr: dxr3abstractiondevice.c:78: cDxr3AbsDevice::cDxr3AbsDevice(): Assertion 'm_fdVideo >= 0' failed. Aborted." No addition errors are reported in /var/log/messages The last message is "adv717x.o: Configuring for PAL" Any suggestions would be greatly recieved Steve Marshall

2 1

VDR Stability
by Adrian P Challinor 01 Jun '05

01 Jun '05

I have used VDR successfully for about 18 months now, but in the last 2 months found that stability has gone completely out of the window. It started when I tried to get the vdrsync code working to burn dvd's (never successful). I have a Pentium P4, 2.4Ghz, 512 MB Ram, 2 x 120 GB IDE disks, with an ASUS motherboard. Cards are a TT-FF DVB-T and a Nebula DVB budget card. I had so many problems after I did a few kernel changes that I reverted to rebuilding the system from scratch. I was working on linux 2.6.4, but listening to the list I upgraded to 2.6.11 on the rebuild. Things have not got better. It is impossible to record anything from the budget card, which is VDR's preferred card. I get so many errors with skipped bytes to sync to a TS packet it is unwatchable. The recording makes old VCR's look good. Funny this, because the DVBT enabled television is just fine. I tried recording just of the TT-FF card. OK, I can only record one signal at a time, but at least it will be stable, right? Wrong. It's still unstable. For example: May 30 22:50:22 vdr vdr[8931]: timer 1 (1 2240-0045 'Total Recall') set to event Mon 30.05.2005 22:50-00:35 'Total Recall' May 30 22:54:11 vdr vdr[8935]: channel 1 (BBC ONE) event 22:50 'Total Recall' status 4 May 30 23:03:38 vdr vdr[8935]: channel 3 (BBC THREE) event 23:00 'Ideal' status 4 May 30 23:07:45 vdr vdr[8991]: ERROR: unknown picture type '5' May 30 23:07:46 vdr vdr[8991]: ERROR: unknown picture type '4' May 30 23:11:01 vdr vdr[8931]: connect from 127.0.0.1, port 47508 - accepted May 30 23:11:01 vdr vdr[8931]: closing SVDRP connection May 30 23:16:50 vdr vdr[8991]: ERROR: unknown picture type '5' May 30 23:18:30 vdr last message repeated 5 times May 30 23:18:51 vdr last message repeated 2 times May 30 23:21:02 vdr vdr[8931]: connect from 127.0.0.1, port 43811 - accepted May 30 23:21:02 vdr vdr[8931]: closing SVDRP connection May 30 23:25:15 vdr vdr[8991]: ERROR: unknown picture type '5' May 30 23:25:15 vdr vdr[8991]: initiating emergency exit May 30 23:25:15 vdr vdr[8991]: ERROR: unknown picture type '4' May 30 23:25:15 vdr vdr[8991]: initiating emergency exit May 30 23:25:15 vdr vdr[8991]: ERROR: unknown picture type '5' May 30 23:25:15 vdr vdr[8991]: initiating emergency exit May 30 23:25:16 vdr vdr[8931]: emergency exit requested - shutting down May 30 23:25:16 vdr vdr[8931]: timer 1 (1 2240-0045 'Total Recall') stop May 30 23:25:16 vdr vdr[8931]: saved setup to /root/vdr/setup.conf May 30 23:25:16 vdr vdr[8931]: exiting May 30 23:25:16 vdr vdr[8931]: emergency exit! My recording stops in the middle with an unknown picture type. At this point, nothing I do other than reboot will restore VDRAdmin (probably the most important feature of VDR IMHO). I have tried VDR 1.3.25, I have reverted to 1.3.20. I have taken the latest versions of firmware, I have reverted to those that came with the card. Am I alone in thinking that, for anyone who wants to actually watch TV, the answer is a SKY+ box. Please, god forbid it should come to that. What am I doing wrong here? HELP ! Adrian P Challinor _______________________________________________ vdr mailing list vdr(a)linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

3 5

Re: [ANNOUNCE] vdr-xine-0.7.4 via network
by Lucian Muresan 31 May '05

31 May '05

Hi, peter_weber69 wrote: > Hi, > > xine-plugin on Server, only xine-player on client > > Files on my Homepage: > http://mitglied.lycos.de/peterweber69/ I'd have a huge wish for your next vdr-xine via network release, and maybe it's not too difficult, and maybe others might want this too: Would you please provide your modifications to xine-lib and xine-ui as diffs against the *xine-lib and xine-ui patched with Reinhard Nissl's official patches*? That way, one can clearly see what your modifications beyond Reinhard's are, and integrate it with other patches one might want to apply to an arbitrary xine-lib/xine-ui (maybe a more recent CVS or so...). Are the archives of xine-lib and xine-ui on your homepage "derived" from those hosted on Reinhard's vdr-xine page (applied his and the your mods)? Best regards, Lucian

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 May 2005