vdr

vdr@linuxtv.org

6731 discussions

Vdr or driver performance dropout
by Kartsa 11 Mar '07

11 Mar '07

I've noticed that earlier when I was using PIII 550 MHz and vdr 1.3.22 (or something about) I made a test by recording nine channels simultaneously and watching a recording at the same time. I remember there seemed to be no trouble doing it. Now when I have vdr 1.4.4 after fourth recording starts vdr becomes sluggish and there starts to come errors on log: dvb-ttpci: warning: timeout waiting in LoadBitmap when pushing menu button. And ofcourse no menu appears or menu appears only partly. Is this vdr related or firmware related. After all the error is fw error isn't it? \\Kartsa

11 28

VPS autotimer stopped prematurely
by Hans-Peter Jansen 11 Mar '07

11 Mar '07

Hi *, my family and me greatly enjoy vdr since years, but I finally got around to update the system to a current state (on top of openSUSE 10.2) lately. The system is running dedicated for vdr (1.4.5) purposes, using two hauppauge ff 2.1 cards. Yesterday we decided to watch the new Dittsche programme from Monday night, but had to notice, that the recording stopped prematurely: Mar 6 00:39:46 ziggy vdr: [3975] channel 1 (Das Erste) event Die 06.03.2007 00:35-01:05 (VPS: 06.03 00:35) 'Dittsche' status 2 Mar 6 00:39:46 ziggy vdr: [3838] switching device 2 to channel 1 Mar 6 00:39:46 ziggy vdr: [3838] timer 3 (1 0035-0105 VPS 'Dittsche~Dittsche~Das wirklich wahre Leben') start Mar 6 00:39:46 ziggy vdr: [3838] Title: 'Dittsche' Subtitle: 'Das wirklich wahre Leben' Mar 6 00:39:46 ziggy vdr: [3838] record /video0/Dittsche/Dittsche/Das_wirklich_wahre_Leben/2007-03-06.00.35.50.99.rec Mar 6 00:39:46 ziggy vdr: [3838] creating directory /video0/Dittsche/Dittsche/Das_wirklich_wahre_Leben/2007-03-06.00.35.50.99.rec Mar 6 00:39:46 ziggy vdr: [3838] recording to '/video0/Dittsche/Dittsche/Das_wirklich_wahre_Leben/2007-03-06.00.35.50.99.rec/001.vdr' Mar 6 00:39:46 ziggy vdr: [11192] file writer thread started (pid=3838, tid=11192) Mar 6 00:39:46 ziggy vdr: [11193] recording thread started (pid=3838, tid=11193) Mar 6 00:39:46 ziggy vdr: [11194] receiver on device 2 thread started (pid=3838, tid=11194) Mar 6 00:39:46 ziggy vdr: [11195] TS buffer on device 2 thread started (pid=3838, tid=11195) Mar 6 00:40:33 ziggy vdr: [3975] channel 1 (Das Erste) event Die 06.03.2007 00:35-01:05 (VPS: 06.03 00:35) 'Dittsche' status 4 Mar 6 00:44:00 ziggy vdr: [3991] EPGSearch: search timer update started Mar 6 00:44:00 ziggy vdr: [3991] EPGSearch: search timer update finished Mar 6 00:46:39 ziggy vdr: [3838] switching to channel 1 Mar 6 00:46:45 ziggy vdr: [3838] switching to channel 2 Mar 6 00:46:48 ziggy vdr: [3838] switching to channel 3 Mar 6 00:46:50 ziggy vdr: [3838] switching to channel 4 Mar 6 00:46:56 ziggy vdr: [3838] switching to channel 5 Mar 6 00:47:00 ziggy vdr: [3838] switching to channel 6 Mar 6 00:47:01 ziggy vdr: [3838] switching to channel 7 Mar 6 00:47:03 ziggy vdr: [3838] switching to channel 8 Mar 6 00:47:05 ziggy vdr: [3838] switching to channel 9 Mar 6 00:47:08 ziggy vdr: [3838] switching to channel 10 Mar 6 00:47:14 ziggy vdr: [3838] switching to channel 11 Mar 6 00:47:18 ziggy vdr: [3838] switching to channel 12 Mar 6 00:47:19 ziggy vdr: [3838] switching to channel 13 Mar 6 00:47:22 ziggy vdr: [3838] switching to channel 14 Mar 6 00:47:33 ziggy vdr: [3838] switching to channel 15 Mar 6 00:47:36 ziggy vdr: [3838] switching to channel 16 Mar 6 00:47:39 ziggy vdr: [3838] switching to channel 17 Mar 6 00:48:00 ziggy vdr: [3838] switching to channel 18 Mar 6 00:48:03 ziggy vdr: [3838] switching to channel 19 Mar 6 00:52:55 ziggy vdr: [3975] changing pids of channel 1101 from 201+201:202:204 to 901+901:902:204 Mar 6 00:53:55 ziggy vdr: [3975] changing pids of channel 1101 from 901+901:902:204 to 701+701:702:204 Mar 6 00:54:54 ziggy vdr: [3975] changing pids of channel 1101 from 701+701:702:204 to 901+901:902:204 Mar 6 00:55:55 ziggy vdr: [3975] changing pids of channel 1101 from 901+901:902:204 to 701+701:702:204 Mar 6 00:56:55 ziggy vdr: [3975] changing pids of channel 1101 from 701+701:702:204 to 901+901:902:204 Mar 6 00:57:54 ziggy vdr: [3975] changing pids of channel 1101 from 901+901:902:204 to 701+701:702:204 Mar 6 00:58:54 ziggy vdr: [3975] changing pids of channel 1101 from 701+701:702:204 to 901+901:902:204 Mar 6 00:59:55 ziggy vdr: [3975] changing pids of channel 1101 from 901+901:902:204 to 701+701:702:204 Mar 6 01:00:43 ziggy vdr: [3975] channel 1 (Das Erste) event Die 06.03.2007 00:35-01:05 (VPS: 06.03 00:35) 'Dittsche' status 1 Mar 6 01:00:43 ziggy vdr: [11193] recording thread ended (pid=3838, tid=11193) Mar 6 01:00:43 ziggy vdr: [11195] TS buffer on device 2 thread ended (pid=3838, tid=11195) Mar 6 01:00:43 ziggy vdr: [11194] buffer stats: 118440 (5%) used Mar 6 01:00:43 ziggy vdr: [11194] receiver on device 2 thread ended (pid=3838, tid=11194) Mar 6 01:00:43 ziggy vdr: [11192] file writer thread ended (pid=3838, tid=11192) Mar 6 01:00:43 ziggy vdr: [3838] buffer stats: 118816 (2%) used Mar 6 01:00:43 ziggy vdr: [3838] timer 3 (1 0035-0105 VPS 'Dittsche~Dittsche~Das wirklich wahre Leben') stop Mar 6 01:00:54 ziggy vdr: [3975] changing pids of channel 1101 from 701+701:702:204 to 901+901:902:204 Mar 6 01:01:56 ziggy vdr: [3975] changing pids of channel 1101 from 901+901:902:204 to 701+701:702:204 Mar 6 01:02:55 ziggy vdr: [3975] changing pids of channel 1101 from 701+701:702:204 to 901+901:902:204 Mar 6 01:03:43 ziggy vdr: [3838] switching to channel 1 Mar 6 01:03:46 ziggy vdr: [3838] switching to channel 2 Mar 6 01:03:49 ziggy vdr: [3838] switching to channel 3 Mar 6 01:03:54 ziggy vdr: [3838] switching to channel 4 Mar 6 01:03:55 ziggy vdr: [3975] changing pids of channel 1101 from 901+901:902:204 to 701+701:702:204 Mar 6 01:03:57 ziggy vdr: [3838] switching to channel 5 Mar 6 01:03:59 ziggy vdr: [3838] switching to channel 6 Mar 6 01:04:00 ziggy vdr: [3928] channel 5 (RTL Television) event Die 06.03.2007 01:00-01:05 'Teleshoppingsendung' status 4 Mar 6 01:04:00 ziggy vdr: [3838] switching to channel 7 Mar 6 01:04:02 ziggy vdr: [3838] switching to channel 8 Mar 6 01:04:04 ziggy vdr: [3838] switching to channel 9 Mar 6 01:04:07 ziggy vdr: [3838] switching to channel 8 Mar 6 01:04:54 ziggy vdr: [3928] changing pids of channel 1101 from 701+701:702:204 to 901+901:902:204 Mar 6 01:05:53 ziggy vdr: [3928] changing pids of channel 1101 from 901+901:902:204 to 701+701:702:204 Mar 6 01:06:55 ziggy vdr: [3928] changing pids of channel 1101 from 701+701:702:204 to 901+901:902:204 Mar 6 01:07:07 ziggy vdr: [3975] changing ca descriptors of channel 1132 Mar 6 01:07:48 ziggy vdr: [3975] changing name of channel 52 from 'Golf,;' to 'Basketball BBL,;' Mar 6 01:07:55 ziggy vdr: [3928] changing pids of channel 1101 from 901+901:902:204 to 701+701:702:204 Mar 6 01:08:30 ziggy vdr: [3975] changing pids of channel 45 from 511+511:512=deu,513=deu;515=deu:32 to 511+511:512=deu;515=deu:32 Mar 6 01:08:54 ziggy vdr: [3928] changing pids of channel 1101 from 701+701:702:204 to 901+901:902:204 Mar 6 01:09:42 ziggy vdr: [3974] frontend 1 timed out while tuning to channel 0, tp 111914 Mar 6 01:09:56 ziggy vdr: [3928] changing pids of channel 1101 from 901+901:902:204 to 701+701:702:204 Mar 6 01:10:04 ziggy vdr: [3928] channel 1 (Das Erste) event Die 06.03.2007 01:05-02:45 (VPS: 06.03 01:05) 'Das letzte Kommando' status 4 Mar 6 01:10:08 ziggy vdr: [3838] timer 3 (1 0035-0105 VPS 'Dittsche~Dittsche~Das wirklich wahre Leben') set to no event Mar 6 01:10:26 ziggy vdr: [3838] deleting timer 3 (1 0035-0105 VPS 'Dittsche~Dittsche~Das wirklich wahre Leben') The clock is reliable (adjusted via NTP), thus vdr happened to start the recording at 00:39:46, about 48 sec before the broadcast started, very nice so far. But what happened at 01:00:43? vdr just decided to stop the recording, even a few minutes _before_ the original VPS time frame, vastly prematurely. For the sake of completeness, I included all messages in between, while I don't understand some of them. Yes, I zapped through the channels two times, but what happened at 01:04:00 and 01:10:04? Both times it shows status 4, which means "event running", if I read the source correctly: 0=undefined, 1=not running, 2=starts in a few seconds, 3=pausing, 4=running waht does event mean here, but most most important question is: What happened, that stopped the timer prematurely, and how can I prevent this from happening the next time. Anyway thanks for your patience and this great project. Kind regards, Pete

2 3

Info on function cSkins::QueueMessage
by lukkinosat 10 Mar '07

10 Mar '07

Hello I make a message with: cSkins::QueueMessage( mtInfo, "MyMessage", 30, -1 ) and the message is diplayed for 30 seconds. But if I wish to remove the message before, what I must make? Exist a function? Tank, Luca P.S. Excused me for my english :-) ___________________________________ L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail: http://it.docs.yahoo.com/nowyoucan.html

2 1

Understanding how vdr's tuning algo works.
by Stone 10 Mar '07

10 Mar '07

Hello All, I am curious how vdr's tuning algorithm, in general, works. With all the refactoring that has gone on with how vdr tunes, locks, retunes, and otherwise tries to anticipate various forms of interference, storms, or other activities that could hinder vdr from performing its job adequitely, please describe, in pseudocode, how the tuning algorythm actually works. Some of my questions are: 1) What do all the tuning timers mean? There are some constants in vdr code, what are the meanings of each tuning state? (i.e. the switch statement in dvbdevice.c. 2) Given that we understand what all the timers do, which ones depend on eachother? What are safe limits for each timer? For example, one timer is the DVBS_TUNE_TIMEOUT that traditionally is set to 9000 (miliseconds) but at times it takes my dvb card upwards of 18 seconds to actually tune the channel (so I might wish to set this to 19000 instead of 9000). What other timers need to be adjusted if any to account for this? 3) Does vdr care or know anything about a rotor setup where the channel isn't always present the moment the diseqc commands are sent? 4) There has been some talk in the past about refactoring this process some, do we think the current approach is the best approach? Does vdr-1.5.x plan to offer new and improved tuning algos? Best Regards.

4 5

dvb-c usb box for vdr available?
by Halim Sahin 10 Mar '07

10 Mar '07

Hello @all, I am looking for a external usb dvb-c box for my vdr machine. CI isn't important but nice to have. Is there such a box available and works well with vdr? Thanks. Halim

1 0

Handling of temporarily encrypted channels
by Ondrej Wisniewski 09 Mar '07

09 Mar '07

I am using VDR 1.4.5 with the integrated auto pid feature and without any CAM. When tuning to an encrypted channel, the CA value gets set accordingly and "channel not available" is displayed. So far so good. However there are channels that encrypt only certain programs and are free the rest of the time. When tuning to this "free" channel while the program is encrypted, the CA value will be set and "channel not available" shown. But when tuning to the same channel again when it is not encrypted any more it seems that VDR just checks the CA value and displays "channel not available" instead of checking the currently broadcast CA value. So the channel cannot be watched even if it is free in the moment. This is quite annoying and decreases the WAF a lot :-/ Is there an easy way to fix this? -- Ondrej

6 10

BUG: Incorrect playback times for radio channels
by Patrick Mackin 07 Mar '07

07 Mar '07

I have noticed a potential bug in playing back radio channels. The playback time of recorded radio channels is inflated by almost 40%. This has been confirmed on four North American satellites on three different providers. The reported time for a 10 minute recording will consistently appear as 13:47. Some have hypothesized the problem comes from the fact that vdr's timers are based on video frame rates, which of course don't exist on radio channels. World Radio Network (wrn.org) is one example, and is broadcast on satellite worldwide, so perhaps this can be confirmed on other sats outside NA. The timing problem makes it very difficult to skip commercials or "top of the hour" news reports or to skip between programming that occurs, for example, every 30 minutes. In America, I have made observations on Telstar5. In Europe, you can try Sky Digital (Eurobird 1, 28.5E) or Eutelsat Hotbird 6 (13E) or Afristar (paytv). Additionally, there appears to be a problem that some have reported with certain NA provider varying the video frame rate, causing *underreporting* of playback time, which would seem to confirm this hypothesis.

2 3

frontend 1 timed out while tuning to channel 0
by Dieter Bloms 07 Mar '07

07 Mar '07

Hi, I get a lot of these messages in my logfile. What does channel 0 mean ? --snip-- video:~ # grep "timed out while tuning" /var/log/vdr Mar 6 19:47:54 video vdr: [19313] frontend 1 timed out while tuning to channel 0, tp 212522 Mar 6 19:50:00 video vdr: [19313] frontend 1 timed out while tuning to channel 0, tp 212699 Mar 6 19:50:22 video vdr: [19313] frontend 1 timed out while tuning to channel 0, tp 212728 Mar 6 19:54:12 video vdr: [19313] frontend 1 timed out while tuning to channel 0, tp 111914 Mar 6 19:59:49 video vdr: [19313] frontend 1 timed out while tuning to channel 0, tp 112544 Mar 6 20:01:55 video vdr: [19313] frontend 1 timed out while tuning to channel 0, tp 112721 Mar 6 20:11:01 video vdr: [19313] frontend 1 timed out while tuning to channel 0, tp 212090 Mar 6 20:14:52 video vdr: [19313] frontend 1 timed out while tuning to channel 0, tp 212522 Mar 6 20:16:58 video vdr: [19313] frontend 1 timed out while tuning to channel 0, tp 212699 Mar 6 20:17:19 video vdr: [19313] frontend 1 timed out while tuning to channel 0, tp 212728 Mar 6 20:21:10 video vdr: [19313] frontend 1 timed out while tuning to channel 0, tp 111914 Mar 6 20:26:46 video vdr: [19313] frontend 1 timed out while tuning to channel 0, tp 112544 --snip the first lines of my channels.conf looks like: --snip-- video:~ # head /etc/vdr/channels.conf :Freie Sender Das Erste;ARD:11836:hC34:S19.2E:27500:101:102=deu;106=deu:104:0:28106:1:1101:0 ZDF;ZDFvision:11953:hC34:S19.2E:27500:110:120=deu,121=2ch;125=dd:130:0:28006:1:1079:0 Bayerisches FS;ARD:11836:hC34:S19.2E:27500:201:202=deu:204:0:28107:1:1101:0 RTL Television,RTL;RTL World:12187:hC34:S19.2E:27500:163:104=deu;106=deu:105:0:12003:1:1089:0 SAT.1;ProSiebenSat.1:12480:vC34:S19.2E:27500:1791:1792=deu;1795=deu:34:0:46:133:33:0 RTL2;RTL World:12187:hC34:S19.2E:27500:166:128=deu:68:0:12020:1:1089:0 ProSieben;ProSiebenSat.1:12480:vC34:S19.2E:27500:255:256=deu;257=deu:32:0:898:133:33:0 Super RTL,S RTL;RTL World:12187:hC34:S19.2E:27500:165:120=deu:65:0:12040:1:1089:0 KABEL1;ProSiebenSat.1:12480:vC34:S19.2E:27500:511:512=deu:33:0:899:133:33:0 --snip-- I use vdr-1.4.5-2 and v4l-dvb from todays hg. -- 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.

2 1

[ANNOUNCE] remoteosd-0.0.2
by Frank Schmirler 07 Mar '07

07 Mar '07

Hi, another new version this week: remoteosd-0.0.2 is out. The remoteosd plugin allows a (client) VDR to operate the menu of a remote (server) VDR. Remoteosd requires the svdrpservice plugin, so make sure both plugins get installed on the client. The svdrpext plugin is required on the server. All three plugins are available on http://vdr.schmirler.de. Most important changes in version 0.0.2: New option "Tune server channel". When opening the remote OSD, the plugin tries to tune the server to the same channel the client is viewing. So when entering e.g. the remote schedules menu, the expected channel will be highlighted. Usually this option makes sense only if you are running a headless server. In this case I recommend to install the dummydevice plugin on the server, too. Otherwise, in some situations the server might not be able to switch channels as expected. Support for MainMenuHooks patch. With this patch a plugin can replace the VDR mainmenus "Schedule", "Channels", "Timers" or "Recordings" (read http://www.linuxtv.org/pipermail/vdr/2007-February/012309.html for more information). Remoteosd allow you to replace "Schedule" and/or "Timers" by the corresponding remote menu. Note that you have to apply the patch before compiling remoteosd, otherwise the setup options won't show up. The MainMenuHooks patch is included in the patches directory of the remoteosd sources. See the patch file for further information and instructions. Changelog: - New option: tune channel on server - Support for MainMenuHooks patch. Plugin may replace the VDR mainmenus Schedule and Timers - Close remote menu when the local menu has been closed by menu key - OSD message if server is not reachable - Support for svdrpservice-0.0.3 default IP/port - Code cleanup Cheers, Frank

1 0

[ANNOUNCE] VDR version 1.4.6 released
by Klaus Schmidinger 06 Mar '07

06 Mar '07

VDR version 1.4.6 is now available at ftp://ftp.cadsoft.de/vdr/vdr-1.4.6.tar.bz2 A 'diff' against the previous version is available at ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.4.5-1.4.6.diff A 'diff' against the latest maintenance patch is available at ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.4.5-2-1.4.6.diff A summary of all the major changes since the last stable version can be found at http://www.cadsoft.de/vdr/download.htm This version is binary compatible with the previous version, so plugins don't need to be recompiled. Thanks to the many people who have contributed in the making, testing and debugging of this new version of VDR. Have fun! Klaus

3 2

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr