vdr

vdr@linuxtv.org

6731 discussions

vdr-1.5.1 & problems with the new shutdown code
by Rolf Ahrenberg 06 Mar '07

06 Mar '07

Hi, I've noticed some shutdown problems with vdr-1.5.1 in my setup: when my vdr wakes up for a timed recording, it doesn't automatically shutdown itself anymore after the recording is done. The MinEventTimeout is set to 15 minutes and MinUserInactivity to 600 minutes, but in my case there hasn't been any user activity, so vdr should have shutdown in 15 minutes after the recording was stopped and the logs don't reveal anything unusual. Have I misunderstood something? Does this automatic shutdown feature still work in your setups? BR, -- rofa

5 11

[ANNOUNCE] svdrpservice-0.0.3
by Frank Schmirler 06 Mar '07

06 Mar '07

Hi there, svdrpservice is a helper plugin which makes it easy for other plugins to send SVDRP commands to an other VDR. Homepage: http://vdr.schmirler.de. Most important changes in 0.0.3: No longer using a fixed buffer size. Users of the epgsync plugin might appreciate this when using external EPG sources with e.g. tvmovie2vdr. The amount of data provided there was often too large for the old buffer. The plugin has its own setup menu now. You can specify default values for the server IP and port, so these values no longer have to be entered in each and every plugin using svdrpservice. If a plugin requests a connection to the special IP 0.0.0.0 or the IP is missing completely (empty string), the default value from the svdrpservice setup will be used. Likewise port number 0 will be replaced. Note that yet it's not possible to enter port number 0 in the plugins which use svdrpservice. Future versions will fix this. A silent change of the service specification came along with the new setup options: Server IP and port are now in/out parameters. After the service call for a new connection these parameter contain the actual values for IP and port, i.e. the svdrpservice default values are returned if they have been used. Note that the service version has not been increased as the modification does not break compatibility. Changelog: - Dynamic buffer size - New setup options: default server IP and port - Silent change of service interface: serverIP and serverPort are now in/out params - Connection handle was not reset to -1 when disconnecting a shared connection which is still in use - Non-blocking connect Enjoy, Frank

1 0

Probs: Twinhan Starbox 2 on NSLU2 with kernel 2.6.20 and cvs driver
by Hubert_Becker＠t-online.de 05 Mar '07

05 Mar '07

Anybody there who can help mir here ? I have debian ETCH on NSLU2 with kernel 2.6.20 and the latest cvs v4l driver which supports the Twinhan Startbox 2 DVB-S usb. Loading the driver is fine Starting vdr 1.4.5 ( compiled wit sources from etobi) without the attached box and without drivers loaded works just fine with plugins (xineliboutput, vompserver, ..) As soon as i start vdr with attached box and loaded driver, the system is kind of locked. The session stays until i remove the usb cable and then i get the kernel oops. See attachment Looks like vdr is causing the kernel oops, but in the log i can't see why. How can i get more debug output to see where the problem is ? Or is there anybody who can help me ? On my debian ETCH system the same installation is just running fine. Regards Hubert

1 0

Re: [vdr] Wakeup On LAN
by Kimmo Taskinen 04 Mar '07

04 Mar '07

Have you tried ethtool to setup WoL options? I run "ethtool -s eth0 wol pg". - Kimmo _____ Alkuperäinen viesti _____ Aihe: [vdr] Wakeup On LAN Tekijä: "Bernd Juraschek" <vdr(a)bjusystems.de> Päivämäärä: 3. maaliskuuta 2007 1:18:32 Hello, I'm trying to wakeup my Siemens Scaleo-T using WOL - but without success :-( The PC to wakeup: - Siemens Scaleo-T AMD64 with Onboard LAN (Tulip chip) - Linux 2.6.20 with ACPI enabled - Gentoo amd64 The router: - ASUS WL-500g Deluxe - OpenWrt White Russian - With X-Wrt Extensions RC6 - WOL-Software: wol What I've done: - BIOS: Wakeup controlled by BIOS and WOL enabled - Gentoo: echo -n PCI0 > /proc/acpi/wakeup ; halt - Router: wol -h PC-IP-Addr PC-MAC-Addr I've configured the router to start wol periodically. On the PC wireshark is now showing incoming UDP packets to the UDP port 40000. The packet contains the ethernet frame, the IP header, the UDP header and the magic data (6x 0xff and 16x MAC-Addr). It seems all ok - but the PC will not be started. What's going wrong? Should I use some ACPI sleep mode? Is this supported by the DVB drivers? Is the Siemens PC not usable for WOL? Thanks for help, Bernd -- Obwohl das Weltall expandiert, findet man nirgendwo ParkplÃ¤tze. -- BR Space night _______________________________________________ vdr mailing list vdr(a)linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

4 9

VDR shutdown when timer gets no video
by mes＠lazo.ca 04 Mar '07

04 Mar '07

VDR 1.4.5 seems to shut down when a timer is triggered and no video is recieved. This happens when the dish is moving or CA keys are out of date. FELOCK is not enough to stop the shut down. Is there some way to turn off this feature? Actually turn off auto shut down all together? Thanks, mark

1 1

[RFC] Shutdown rewrite for 1.5.x
by Udo Richter 04 Mar '07

04 Mar '07

Hi list, The program code for automatic and manual shut down and for automatic restarts for timer recordings is in VDR 1.4.x very complex and error-prone, and behaves strange in some situations. With Klaus' permission I am working on a re-implementation for the upcoming 1.5.x developer builds of VDR. I now want to publish a first draft version for testing and further comments. Not all issues are fixed yet, but it already gives an impression of the new code. http://www.udo-richter.de/vdr/patches.html#shutdown http://www.udo-richter.de/vdr/patches.en.html#shutdown New: - Shutdown related code is now in shutdown.[ch]. vdr.c mainly delegates the work to the cShutdown class, that does all necessary steps for manual or automatic shutdown. - cShutdown tracks whether there is an interactive user or not. (eg. Min User Inactivity run out) - cRemote tracks time of last key press separately and autonomously. - The old 5-minute "Press any key to cancel..." message got replaced by a 5 minute countdown message that counts in 10-second steps - Since the new code is modularized, plugins will have access to activity tracking, can mess with inactivity state, and can initiate shutdown behavior similar to the kPower button. (But, please, only if you have to. ;) ) Fixed: - Pressing power button while recording playback works again, instead of doing nothing visible. (and not shutting down within 5 seconds at playback end.) - Show 5-minute shutdown message after background activity ends, if power button was pressed but not confirmed - Not freezing the VDR main loop while 5-minute shutdown message - Background activity now cancels the 5-minute shutdown message - Not messing with watchdog (and forgetting to re-enable) while 5-minute shutdown message - Timers set via SVDRP while in 5-minute shutdown message did not start and were not considered for reboot time. - Calling the main menu action of a plugin and closing a menu doesn't count as user activity any more Todo: - Start the 5-minute countdown 5 minutes _before_ min user inactivity runs out. (also does not add 5min to SHUTDOWNRETRY any more) - Fix negative time in shutdown confirm if VPS timer is in run-out phase Possible changes: - Make the 'inactive' mode (waiting for background activity to end, then shut down) more visible to the user: - Suggestion was to put up a message 'VDR will shut down when idle. Press power button again to force shutdown' before starting the confirms. - Alternative may be a message 'VDR will shut down later when idle' if shutdown was not confirmed - Alternative may be to permanently put up a message 'VDR is waiting for background tasks to complete'. - What should happen if a user confirms to shut down while a running / pending timer is scheduled. Currently, VDR will reboot after MinEventTimeout, but VDR could also reboot at the next timer that starts after MinEventTimeout - or never. - There is a feature request that the caller should be able to notify VDR whether VDR was started manually or automatically. (VDR currently guesses by searching for nearby timers) - There is a feature request to start the external shutdown script asynchronously, so the shutdown script does not block VDR any more. - A 'bug' in the old code allows to automatically shut down VDR at the end of a playback, though this was probably never intended. It could however be re-added as 'feature'. There's some debug output code to monitor the various timers on console. If you don't want that, you can disable it in vdr.c, search for #define DebugTimeouts and comment it out. Cheers, Udo

20 114

12149 on Astra 19
by Rob Davis 04 Mar '07

04 Mar '07

Anyone know why VDR won't pick up the different channels on this frequency? All I get is Kiosque, but I know there are Cine+ Foot 1 2 3 4 etc..? apart from hacking it by hand, anyone know of a solution?

2 3

Wakeup On LAN
by Bernd Juraschek 03 Mar '07

03 Mar '07

Hello, I'm trying to wakeup my Siemens Scaleo-T using WOL - but without success :-( The PC to wakeup: - Siemens Scaleo-T AMD64 with Onboard LAN (Tulip chip) - Linux 2.6.20 with ACPI enabled - Gentoo amd64 The router: - ASUS WL-500g Deluxe - OpenWrt White Russian - With X-Wrt Extensions RC6 - WOL-Software: wol What I've done: - BIOS: Wakeup controlled by BIOS and WOL enabled - Gentoo: echo -n PCI0 > /proc/acpi/wakeup ; halt - Router: wol -h PC-IP-Addr PC-MAC-Addr I've configured the router to start wol periodically. On the PC wireshark is now showing incoming UDP packets to the UDP port 40000. The packet contains the ethernet frame, the IP header, the UDP header and the magic data (6x 0xff and 16x MAC-Addr). It seems all ok - but the PC will not be started. What's going wrong? Should I use some ACPI sleep mode? Is this supported by the DVB drivers? Is the Siemens PC not usable for WOL? Thanks for help, Bernd -- Obwohl das Weltall expandiert, findet man nirgendwo ParkplÃ¤tze. -- BR Space night

3 4

ERROR: video data stream broken on second dvb card , but szap works (include recording)
by Dieter Bloms 02 Mar '07

02 Mar '07

Hi, I have two cards in my video server: Technotrend/Hauppauge WinTV Nexus-S rev2.3) Hauppauge Nova-S-Plus DVB-S [card=37] lspci: 01:0c.0 Multimedia video controller: Conexant CX23880/1/2/3 PCI Video and Audio Decoder (rev 05) 01:0c.1 Multimedia controller: Conexant CX23880/1/2/3 PCI Video and Audio Decoder [Audio Port] (rev 05) 01:0c.2 Multimedia controller: Conexant CX23880/1/2/3 PCI Video and Audio Decoder [MPEG Port] (rev 05) 01:0c.4 Multimedia controller: Conexant CX23880/1/2/3 PCI Video and Audio Decoder [IR Port] (rev 05) 01:0f.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01) when I use szap to change the channel, I can switch, record, switch, record .... (record with "cat /dev/dvb/adapter1/dvr0 >/tmp/tsvideo". But when I try to record with vdr, I get the following errors and nothing will be record: (with plain vdr-1.5.0 and plain vdr-1.4.0 and v4l-dvb from yesterdays hg): Feb 9 12:02:00 video vdr: [30529] connect from 127.0.0.1, port 60607 - accepted Feb 9 12:02:00 video vdr: [30529] timer 10 (1 1200-1215 VPS 'Tagesschau um zwölf') added Feb 9 12:02:00 video vdr: [30529] closing SVDRP connection Feb 9 12:02:00 video vdr: [30529] switching device 2 to channel 1 Feb 9 12:02:00 video vdr: [30529] timer 10 (1 1200-1215 VPS 'Tagesschau um zwölf') start Feb 9 12:02:00 video vdr: [30529] Title: 'Tagesschau um zwölf' Subtitle: '' Feb 9 12:02:00 video vdr: [30529] record /data/nobackup/video/Tagesschau_um_zwölf/2007-02-09.12.00.50.50.rec Feb 9 12:02:00 video vdr: [30529] creating directory /data/nobackup/video/Tagesschau_um_zwölf Feb 9 12:02:01 video vdr: [30529] creating directory /data/nobackup/video/Tagesschau_um_zwölf/2007-02-09.12.00.50.50.rec Feb 9 12:02:01 video vdr: [30529] recording to '/data/nobackup/video/Tagesschau_um_zwölf/2007-02-09.12.00.50.50.rec/001.vdr' Feb 9 12:02:01 video vdr: [30529] connect from 127.0.0.1, port 60610 - accepted Feb 9 12:02:01 video vdr: [30529] closing SVDRP connection Feb 9 12:02:01 video vdr: [30603] file writer thread started (pid=30529, tid=30603) Feb 9 12:02:01 video vdr: [30604] recording thread started (pid=30529, tid=30604) Feb 9 12:02:01 video vdr: [30605] receiver on device 2 thread started (pid=30529, tid=30605) Feb 9 12:02:01 video vdr: [30606] TS buffer on device 2 thread started (pid=30529, tid=30606) Feb 9 12:02:03 video vdr: [30529] timer 10 (1 1200-1215 VPS 'Tagesschau um zwölf') set to event Fre 09.02.2007 12:00-12:15 (VPS: 09.02 12: 00) 'Tagesschau um zwölf' Feb 9 12:02:09 video vdr: [30537] frontend 1 timed out while tuning to channel 1, tp 111836 Feb 9 12:02:10 video vdr: [30529] connect from 127.0.0.1, port 60614 - accepted Feb 9 12:02:10 video vdr: [30529] closing SVDRP connection Feb 9 12:02:10 video vdr: [30529] connect from 127.0.0.1, port 60617 - accepted Feb 9 12:02:10 video vdr: [30529] closing SVDRP connection Feb 9 12:02:27 video vdr: [30529] connect from 127.0.0.1, port 60622 - accepted Feb 9 12:02:27 video vdr: [30529] closing SVDRP connection Feb 9 12:02:32 video vdr: [30603] ERROR: video data stream broken Feb 9 12:02:32 video vdr: [30603] initiating emergency exit Feb 9 12:02:32 video vdr: [30529] emergency exit requested - shutting down Feb 9 12:02:32 video vdr: [30604] recording thread ended (pid=30529, tid=30604) Feb 9 12:02:32 video vdr: [30603] file writer thread ended (pid=30529, tid=30603) Feb 9 12:02:32 video vdr: [30529] buffer stats: 0 (0%) used Feb 9 12:02:32 video vdr: [30529] timer 10 (1 1200-1215 VPS 'Tagesschau um zwölf') stop Feb 9 12:02:32 video vdr: [30529] saved setup to /etc/vdr/setup.conf Feb 9 12:02:32 video vdr: [30534] tuner on device 1 thread ended (pid=30529, tid=30534) Feb 9 12:02:33 video vdr: [30606] TS buffer on device 2 thread ended (pid=30529, tid=30606) Feb 9 12:02:33 video vdr: [30605] buffer stats: 0 (0%) used Feb 9 12:02:33 video vdr: [30605] receiver on device 2 thread ended (pid=30529, tid=30605) Feb 9 12:02:33 video vdr: [30533] CI adapter on device 0 thread ended (pid=30529, tid=30533) Feb 9 12:02:33 video vdr: [30535] section handler thread ended (pid=30529, tid=30535) Feb 9 12:02:34 video vdr: [30537] tuner on device 2 thread ended (pid=30529, tid=30537) Feb 9 12:02:34 video vdr: [30538] section handler thread ended (pid=30529, tid=30538) Feb 9 12:02:36 video vdr: [30529] ===================== Feb 9 12:02:36 video vdr: [30529] EPG bugfix statistics Feb 9 12:02:36 video vdr: [30529] ===================== Feb 9 12:02:36 video vdr: [30529] IF SOMEBODY WHO IS IN CHARGE OF THE EPG DATA FOR ONE OF THE LISTED Feb 9 12:02:36 video vdr: [30529] CHANNELS READS THIS: PLEASE TAKE A LOOK AT THE FUNCTION cEvent::FixEpgBugs() Feb 9 12:02:36 video vdr: [30529] IN VDR/epg.c TO LEARN WHAT'S WRONG WITH YOUR DATA, AND FIX IT! Feb 9 12:02:36 video vdr: [30529] ===================== Feb 9 12:02:36 video vdr: [30529] Fix Hits Channels Feb 9 12:02:36 video vdr: [30529] 3 15 Dok&Deb, hr-fernsehen, KiKa Feb 9 12:02:36 video vdr: [30529] 4 5 SWR2, SWR2, 3sat Feb 9 12:02:36 video vdr: [30529] 6 418 MDR SACHSEN, hr-fernsehen, WDR Köln, Bayerisches FS, Das Erste, Phoenix, arte, ... Feb 9 12:02:36 video vdr: [30529] ===================== Feb 9 12:02:36 video vdr: [30529] exiting Feb 9 12:02:36 video vdr: [30529] emergency exit! so why can I get ts streams from the second dvb card and vdr doesn't get any bytes ? -- Gruß Dieter -- I do not get viruses because I do not use MS software. If you use Outlook then please do not put my email address in your address-book so that WHEN you get a virus it won't use my address in the From field.

4 17

How to get sound with tvtime ?
by Guy Roussin 02 Mar '07

02 Mar '07

Hi, I want to use tvtime with vdr and my Full Feature DVB-S. With “tvtime -d /dev/video0”, i have the video but not the sound. How can i obtain the sound with tvtime? If I plug my Loudspeakers to the DVB-S, I have a little shift between the sound and the image. Thank you. Guy

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