vdr

vdr@linuxtv.org

6731 discussions

Limit discovered channels to those that can be viewed?
by M.Kiesel 14 May '06

14 May '06

Hi! I'm running VDR 1.4 on a DVB-S system without CICAM (so I can watch only unencrypted/free-to-all channels). VDR 1.4 adds all channels it discovers to the channels list so I've got about 1000 channels in the list now, including radio channels. However, only very few of them are actually viewable since most are encrypted. Since this is impractical for zapping (try to go to a channel that's located about at the 700th position if you don't know its exact position and almost all 700s channels give "Channel not available" when typing in their number ;-) and for example master-timer programs tons of unusable timers (since the EPG for encrypted channels still gets received)... 1. Is there a way to limit the channels VDR adds to the channel list to those that can be viewed with the hardware setup? 2. Is it possible to move radio stations to the end of the list (or something similar)? Regards

4 3

softdevice problem
by Paul ZHU 14 May '06

14 May '06

hello, I have a Twinhan VP-1025A budget card which can use szap lock the DVB-S signal and using xine to wtach it. now I compiled vdr-1.4.0 and ffmpeg-0.4.9 with softdevice-0.2.3a plugins,but when I start vdr like this: ./vdr -P"softdevice -vo xv:" There is no TV show up, the problems are: 1. No TV showup 2.The OSD blinks 3.learn keyboard key not completely 3.in /var/log/messages, it said: frontend 0 timed out while tuning to channel 1, tp 112581 This is the file /video/channels.conf [zhuhx@pc1 video]$ cat channels.conf JJCTV:12581:h:S146.0E:25600:165:100:0:0:16:0:0:0 TTBN:12581:h:S146.0E:25600:166:104:0:0:17:0:0:0 I don't understand the frequency in channels.conf is 12581, then why vdr try to tune "tp 112581" The following is the command output,(no error messages): --------------------------------------------------------- [zhuhx@pc1 vdr-1.4.0]$ ./vdr -P"softdevice -vo xv:" [softdevice] processing args [softdevice] argv [0] = softdevice [softdevice] argv [1] = -vo vo_argv: xv: [softdevice] initializing Plugin [softdevice] Initializing Video Out [softdevice] ffmpeg version(CVS) build(3344128) [XvVideoOut]: osd_image shmid = 7012372 [XvVideoOut]: got osd_image: width 1280 height 1024, bytes per line 5120 [XvVideoOut]: max area size 2046 x 2046 [XvVideoOut]: using area size 736 x 576 [softdevice] Subplugin successfully opend [softdevice] Video Out seems to be OK [softdevice] Initializing Audio Out [softdevice] Audio out seems to be OK [softdevice] A/V devices initialized, now initializing MPEG2 Decoder ---------------------------------------------------------------------- Please give any help, thanks Paul ZHU

1 0

Re: [PATCH] Priority of transfer-mode should not be -1
by Martin Dauskardt 14 May '06

14 May '06

> > - Now avoiding the 'actual' device when starting a recording, so that a > > Transfer > > Mode for live tv isn't interrupted. a little bit off-topic, but.... I think you mean with "actual" the currently used device? But "actual" doesn`t mean "aktuell" in german. The right translation is "wirklich, tatsachlich, eigentlich." Maybe ActualDevice()) should be renamed to CurrentDevice()) to avoid misunderstanding.

2 1

svdrp stat fe command feature request.
by jik jikman 14 May '06

14 May '06

Hi All, Could somebody add svdrp support to femon plugin? I mean it is very nice to have, for example, STAT FE in svdrp commands to report frontends status. i.e. #svdrpsend.pl stat fe and the responce fe0: signal 73eb | .... fe1: siganl ... ... It would be very nice feature and could be used to record a log of frontends status in a pc client. With the best wishes. John Anderson.

3 5

[Announce] vdr-mlist 0.0.3
by Joachim Wilke 13 May '06

13 May '06

Hi everyone, as I use SVDRP-MESG command to show various notifications from different scripts, I have written a small plugin. The mlist plugin shows a list of all shown osd messages since last vdr startup. --- Changes since 0.0.2 --- 2006-05-13: Version 0.0.3 - Added a setup option to hide the mainmenu entry --- End of changes --- The plugin can be downloaded from: http://joachim-wilke.de/vdr-mlist.htm Best regards, Joachim.

1 0

Occassional stuttering in video with vdr-xine(network)
by Mika Orajärvi 13 May '06

13 May '06

Hi, I have a server containing the DVB cards, and a separate frontend machine using VDR via xine-network. In the frontend machine I have AMD sempron 3400+, NVidia FX5200, 512MB RAM. I'm using the tv-out (via S-video) from the Nvidia card, and I'm using xv for video output Greedy2Frame/GreedyH deinterlacer. My frontend machine also boots up through network and has root file system behind NFS on the server.. I have a very persistent problem with my system that I would hope someone could give some hints.. The video stutters occasionally, especially with high motion video e.g. icehockey and football. With these kind of content the video is not even near "smooth", it kind of stops and jumps every couple of seconds or even more frequently. But on the other hand with most of time with some "normal" content the problems are not so visible and disturbing. I think it is not about cpu power at least, the whole system load seems to be around 80% when watching. Regards and thanks in advance.. -Mika

2 2

Re: [vdr] TT-budget S2-3200
by Vladimir Kangin 13 May '06

13 May '06

Good news, Do you have any info about any other cards that already working with DVB-S2 on Linux? Regards, Vladimir -------- Forwarded Message -------- From: Manu Abraham <abraham.manu(a)gmail.com> Reply-To: VDR Mailing List <vdr(a)linuxtv.org> To: VDR Mailing List <vdr(a)linuxtv.org> Subject: Re: [vdr] TT-budget S2-3200 Date: Fri, 12 May 2006 18:36:06 +0400 Vladimir Kangin wrote: > Hi All, > > Did anyone try the TT-budget S2-3200 card? Is it supported by Linux > kernel? > Soon.. Check for the stb0899 driver developments. There has been developments in this front. The driver is unusable for now, as it stands it is a huge driver supporting DVB-S , DVB-S2 and DSS requiring DVB API changes as well, for now it is there now in www.linuxtv.org/hg/~manu/stb0899 Manu _______________________________________________ vdr mailing list vdr(a)linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

2 1

vdr exits while starting a recording
by Bernhard Wager 13 May '06

13 May '06

Hello, I'm using vdr for a few years now and last weekend I upgraded to version 1.4.0. When vdr is running awhile and now starts a recording, it exits. On the other hand when the recording starts immediately after booting my system everything is fine. In the log file is a little difference between the two cases. In the first case the cam module is already loaded, when the recording starts. In the second case the recording starts before my cam module is loaded. My configuration: Ubuntu 5.10, one dvb device (fujitsu siemens dvb-c ff) with a cam - vdr primary device, another dvb device (hauppauge dvb-c ff) without a cam. Perhaps someone out there has a solution for my problem. Thanks to all contributors for the great work. Greetings Berni

3 5

plugin error while installing/compiling
by Bernhard Frühmesser 12 May '06

12 May '06

Hello, I have downloaded several Plugins for vdr and when i do a make plugins in the vdr-sourcedir i get something like <pluginname> error plugin does´t honor APIVERSION what´s wrong with these plugins, and how can i get a clean install? Thanks, BF.

2 1

[PATCH] jumpplay patch 0.8
by Thomas Günther 12 May '06

12 May '06

Hi! Here is a new version of the jumpplay patch: http://toms-cafe.de/vdr/download/vdr-jumpplay-0.8-1.4.0.diff (applicable to VDR >= 1.3.29) Changes since version 0.7: - Fixed segfault in dvbplayer thread while the replaycontrol thread is reloading the marks (thanks to horchi at vdrprtal.de for reporting this - see http://vdrportal.de/board/thread.php?postid=450463#post450463): New class cMarksReload checks the timestamp of marks.vdr in 10 seconds intervals, so the marks in the threads dvbplayer and replaycontrol can be reloaded independently - Changed setup parameter "Load marks interval (s)" to "Reload marks" - Updated description in README.jumpplay This patch changes the replay behaviour for recordings that contain editing marks. It allows to immediately continue the replay after jumping forward to the next mark, and to automatically jump over the commercial break to the next "start" mark, if an "end" mark is reached. The features of this patch can be turned on or off in the replay setup. See README.jumpplay included in the patch for details, history and contributors. Tom

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