vdr February 2008

vdr@linuxtv.org

148 participants
104 discussions

[PATCH] locale patch for text2skin plug-in (VDR >= 1.5.7) + skin patches
by Thomas Günther 10 Feb '08

10 Feb '08

Hello! Here is a patch for the text2skin plug-in adding locale handling for VDR >= 1.5.7: http://toms-cafe.de/vdr/download/text2skin-1.1-cvs-locale.diff It bases on cvs snapshot from 2008-01-22 22:30:00Z + 2 patches: - libfreetype6-2.2.1.diff by Jerome <jlacvdr(a)jlac.dyndns.org> (http://vdrportal.de/board/thread.php?postid=489175#post489175) - text2skin-1.1-cvs_ext-0.10-vdr-1.5.4.diff by Stone <syphyr(a)gmail.com> (http://vdrportal.de/board/thread.php?postid=621984#post621984) The skins have to be patched, too. The patches for DeepBlue (http://vdr.pfroen.de), Enigma (http://home.pages.at/brougs78/vdr_enigma.htm) and enElchi (http://www.saunalahti.fi/~rahrenbe/vdr/soppalusikka/files/) are ready: http://toms-cafe.de/vdr/download/deepblue-0.1.4-locale.diff http://toms-cafe.de/vdr/download/enigma-0.3a-locale.diff http://toms-cafe.de/vdr/download/enelchi-0.7.2-locale.diff To patch other skins the Makefile from these patches could be used without any changes, missing translation entries should be added to the *.skin file (e.g. as comments ) Tom

1 0

Trouble with mplayer plugin / audio
by Jörn Reder 10 Feb '08

10 Feb '08

Hiho, I'm using vdr 1.4.7 and mplayer plugin from e-tobi on Debian Etch with a full featured Hauppauge Nexus-S card and having trouble with audio during video playback. When I configure mplayer to decode audio with the Nexus by setting AO="mpegpes:card=1" in /etc/vdr/plugins/vdrmplayer.sh.conf, movie playback doesn't work at all. I get a black screen, TV audio mutes but movie playback doesn't start. The mplayer process is there, but seems to do nothing: /usr/bin/mplayer -vo mpegpes:card=1 -ao mpegpes:card=1 \ -vf scale=704:331,expand=704:576:-1:-1:1,lavc=5000:25 \ -framedrop -cache-min 10 -slave -nolirc -subpos 80 \ -sub-bg-color 0 -sub-bg-alpha 30 -quiet -osdlevel 0 \ /movies/foo.avi When I press "Exit" (a few times) on my remote, vdr resumes to TV playback, but often I need to restart vdr for proper operation. Otherwise I can't tune all channels resp. I'm getting messages of channels not available. I stopped vdr and tried the command line above (only removed -slave option): this works pretty well. I get proper video and audio playback. For me it seems, that vdr still occupies the DVB (audio) device when the plugin starts mplayer for video playback. Is that possible? I tried playing audio via the onboard soundchip by setting AO="alsa" and this works so far. But audio and video are getting seriously out of sync, so this is no reasonable workaround for the problem (besides that switching my amplifier to the other audio line is somewhat annoying ;) Something I'm doing wrong? Any help is appreciated. If you need more configuration information please ask for it. Thanks, Jörn -- sub i($){print$_[0]}*j=*ENV;sub w($){sleep$_[0]}sub _($){i"$p:$c> ",w+01 ,$_=$_[0],tr;i-za-h,;a-hi-z ;,i$_,w+01,i"\n"}$|=1;$f='HO';($c=$j{PWD})=~ s+$j{$f."ME"}+~+;$p.="$j{USER}\@".`hostname`;chop$p;_"kl",$c='~',_"zu,". "-zn,*",_"#,epg,lw,gwc,mfmkcbm,cvsvwev,uiqt,kwvbmvb?",i"$p:$c> ";w+1<<07

1 1

begginer question
by Mauricio Henriquez 10 Feb '08

10 Feb '08

Hi to all!!! This is my first post to the list, so me name is Mauricio Henriquez and I write you from Chili. I want to develop a vdr backup system, but one requirement os to support USB capture or frame grabber adapters, so I wonder if you can recomend me some USB video capture adapter or USB framegrabber adapter fully suported on linux (if it is multi-channel for multiple video sources is better). in advance thanks you very much... Mauricio

2 2

No replay of recordings possible
by Benjamin Harling 09 Feb '08

09 Feb '08

Hello, I need same help. I realized a few days ago that I am not able to replay my recordings anymore. Choosing a recording loads it (black screen) and I can call up the on screen display (progress bar). If I set marks I can navigate to them and the picture changes accordingly. But I cannot play the recording at all. No fast forward or backward. VDR (version 1.4.6 running on Fedora Core 6 Kernel 2.6.22.9-61.fc6) runs as user vdr:video an there is no permission problem. I didn't change or update anything that I'm aware of and the recordings themselves are pretty ok, that is, they can be replayed using mplayer. So, do you have any ideas/suggestions? Any comment is being appreciated. Bye, Benjamin

1 0

wrong time in tv program
by Martin SCHREIBER 09 Feb '08

09 Feb '08

hello! the time in the vdr (right bottom) is displayed correctly but the time for the tv movies are displayed with a 7 hour displacement. e.g. the local time is 20:11 but the start time of the tv movie is displayed as 13:00. but the correct tv movie name is displayed. 'date' in the shell displays the correct time and also the correct timezone is set up in /etc/timezone as 'Europe/Berlin'. has anyone a solution? thx, martin -- Martin Schreiber http://www.martin-schreiber.net | Im Muehltal 48 | 91171 Greding | GERMANY

2 4

[ANNOUNCE] improved LIRC remote for VDR-1.5.12
by Reinhard Nissl 09 Feb '08

09 Feb '08

Hi, I was quite annoyed how I could operate my EPIA MII-6000E using a LIRC remote. It was almost not possible to navigate through the OSD in a fast way. The attached patch allows now to define timeouts and frequencies for example in Make.config, so there is no need to patch every VDR version. Furthermore, frequencies are now defined in unit 1/s instead of the unit ms (which defined the period), making values more intuitive. There's now an additional frequency which defines, how fast a user is allowed to press the same button repeatedly. The originally used REPEATDELAY allowed only 2.85 button presses per second. On slow and busy machines like my EPIA it happened often that several button presses were read by VDR in a single read, but only the first one got processed. The code now reads only a single button press from LIRC's socket, so button presses don't get lost (although presses of the same button will be skipped as the timeouts don't get reached). To make it less likely that button presses get processed in chunks a further define allows to decrease the thread's niceness which means to boost it's priority. This feature requires VDR to be run as root. This is my setup which follows some common settings found in mainboard bioses for keyboard repeat delay and frequency. > #vdr > REMOTE=LIRC > LIRC_PUSHFREQ=64 # 1/s > LIRC_REPEATDELAY=250 # ms > LIRC_REPEATFREQ=32 # 1/s > #LIRC_REPEATTIMEOUT=500 # ms > #LIRC_RECONNECTDELAY=3000 # ms > LIRC_PRIORITYBOOST=1 Bye. -- Dipl.-Inform. (FH) Reinhard Nissl mailto:rnissl@gmx.de

12 24

[ANNOUNCE] vdr-rotor support patches for VDR-1.5.14
by Reinhard Nissl 08 Feb '08

08 Feb '08

Hi, the attached patch is based on these files: vdr-rotor-0.1.4-vdr1.5.tgz rotor-0.1.4-vdr-15.12.diff For simplicity a patched version is attached too. NOTES: - I couldn't test with a real rotor device - I couldn't test with a FF card Have fun! Bye. -- Dipl.-Inform. (FH) Reinhard Nissl mailto:rnissl@gmx.de

4 8

timers issue
by Cristiano Bozzi 08 Feb '08

08 Feb '08

Hi all, I would need your help for a strange problem :-( I have a gentoo client-server VDR architecture server side: only a PVR150 card (no DVB, only analog channels), VDR 1.4.3, pvrinput-1.0.0, xine 0.7.9. client side: VDR xine-lib-1.1.2_pre20060328. this is an example of my channels.conf: COMPOSITE 1:100:C23D12:C:0:301:300:305:A1:64001:0:0:0 ANALOG D:175250:C12D12:C:0:301:300:305:A1:64002:0:0:0 ANALOG H2:224250:C12D12:C:0:301:300:305:A1:64003:0:0:0 ANALOG 21:471250:C12D12:C:0:301:300:305:A1:64004:0:0:0 ANALOG 22:479250:C12D12:C:0:301:300:305:A1:64005:0:0:0 ANALOG 23:487250:C12D12:C:0:301:300:305:A1:64006:0:0:0 ANALOG 24:495250:C12D12:C:0:301:300:305:A1:64007:0:0:0 ANALOG 26:511250:C12D12:C:0:301:300:305:A1:64008:0:0:0 All the sistem work well except the recordings part. if I try to set a timer or to start an istant recording on the COMPOSITE 1 channel (in any position of the channels.conf) it works. If I try to set a timer or an istant recording on a different ANALOG channel the screen show me the "NO SIGNAL black screen" with a continuos "channel not available" message. I can't see any live streaming image during the record time but, at the end of the timer, live tv return ok and the recording has been completed correctly (replay is ok) The log file show me that, during the recording time, VDR is trying to change channel: Feb 7 10:29:56 192.168.33.136 LiveServer-203401 vdr: [6895] switching device 2 to channel 2 Feb 7 10:29:56 192.168.33.136 LiveServer-203401 vdr: [6895] timer 1 (2 1030-1032 'ANALOG D') start Feb 7 10:29:56 192.168.33.136 LiveServer-203401 vdr: [6895] waiting for EPG info... Feb 7 10:30:00 192.168.33.136 LiveServer-203401 vdr: [6895] no EPG info available Feb 7 10:30:00 192.168.33.136 LiveServer-203401 vdr: [6895] executing '/usr/lib/vdr/bin/vdrrecord-gate.sh before "/mnt/vdr/video/ANALOG_D/2008-02-07.10.30.50.99.rec"' Feb 7 10:30:00 192.168.33.136 LiveServer-203401 vdr: [6895] record /mnt/vdr/video/ANALOG_D/2008-02-07.10.30.50.99.rec Feb 7 10:30:00 192.168.33.136 LiveServer-203401 vdr: [6895] creating directory /mnt/vdr/video/ANALOG_D Feb 7 10:30:00 192.168.33.136 LiveServer-203401 vdr: [6895] creating directory /mnt/vdr/video/ANALOG_D/2008-02-07.10.30.50.99.rec Feb 7 10:30:01 192.168.33.136 LiveServer-203401 vdr: [6895] recording to '/mnt/vdr/video/ANALOG_D/2008-02-07.10.30.50.99.rec/001.vdr' Feb 7 10:30:01 192.168.33.136 LiveServer-203401 vdr: [32065] file writer thread started (pid=32065, tid=32065) Feb 7 10:30:01 192.168.33.136 LiveServer-203401 vdr: [32066] recording thread started (pid=32066, tid=32066) Feb 7 10:30:01 192.168.33.136 LiveServer-203401 vdr: [32067] receiver on device 6 thread started (pid=32067, tid=32067) Feb 7 10:30:02 192.168.33.136 LiveServer-203401 vdr: [6895] switching to channel 3 Feb 7 10:30:02 192.168.33.136 LiveServer-203401 vdr: [6895] info: Channel not available! Feb 7 10:30:02 192.168.33.136 LiveServer-203401 vdr: [32068] Text2Skin: message display update thread started (pid=32068, tid=32068) Feb 7 10:30:04 192.168.33.136 LiveServer-203401 vdr: [32068] Text2Skin: message display update thread ended (pid=32068, tid=32068) Feb 7 10:30:04 192.168.33.136 LiveServer-203401 vdr: [6895] switching to channel 2 Feb 7 10:30:04 192.168.33.136 LiveServer-203401 vdr: [6895] info: Channel not available! Feb 7 10:30:04 192.168.33.136 LiveServer-203401 vdr: [32069] Text2Skin: message display update thread started (pid=32069, tid=32069) Feb 7 10:30:06 192.168.33.136 LiveServer-203401 vdr: [32069] Text2Skin: message display update thread ended (pid=32069, tid=32069) Feb 7 10:30:06 192.168.33.136 LiveServer-203401 vdr: [6895] ERROR: Channel not available! Feb 7 10:30:06 192.168.33.136 LiveServer-203401 vdr: [32072] Text2Skin: message display update thread started (pid=32072, tid=32072) Feb 7 10:30:08 192.168.33.136 LiveServer-203401 vdr: [32072] Text2Skin: message display update thread ended (pid=32072, tid=32072) Feb 7 10:30:08 192.168.33.136 LiveServer-203401 vdr: [6895] ERROR: Channel not available! Feb 7 10:30:08 192.168.33.136 LiveServer-203401 vdr: [32073] Text2Skin: message display update thread started (pid=32073, tid=32073) Feb 7 10:30:10 192.168.33.136 LiveServer-203401 vdr: [32073] Text2Skin: message display update thread ended (pid=32073, tid=32073) Feb 7 10:30:21 192.168.33.136 LiveServer-203401 vdr: [6895] switching to channel 3 Feb 7 10:30:21 192.168.33.136 LiveServer-203401 vdr: [6895] info: Channel not available! Feb 7 10:30:21 192.168.33.136 LiveServer-203401 vdr: [32100] Text2Skin: message display update thread started (pid=32100, tid=32100) Feb 7 10:30:23 192.168.33.136 LiveServer-203401 vdr: [32100] Text2Skin: message display update thread ended (pid=32100, tid=32100) Feb 7 10:30:23 192.168.33.136 LiveServer-203401 vdr: [6895] ERROR: Channel not available! Feb 7 10:30:23 192.168.33.136 LiveServer-203401 vdr: [32101] Text2Skin: message display update thread started (pid=32101, tid=32101) Feb 7 10:30:25 192.168.33.136 LiveServer-203401 vdr: [32101] Text2Skin: message display update thread ended (pid=32101, tid=32101) Feb 7 10:30:25 192.168.33.136 LiveServer-203401 vdr: [6895] ERROR: Channel not available! Feb 7 10:30:25 192.168.33.136 LiveServer-203401 vdr: [32114] Text2Skin: message display update thread started (pid=32114, tid=32114) Feb 7 10:30:27 192.168.33.136 LiveServer-203401 vdr: [32114] Text2Skin: message display update thread ended (pid=32114, tid=32114) Feb 7 10:30:38 192.168.33.136 LiveServer-203401 vdr: [6895] switching to channel 3 Feb 7 10:30:38 192.168.33.136 LiveServer-203401 vdr: [6895] info: Channel not available! Feb 7 10:30:38 192.168.33.136 LiveServer-203401 vdr: [32129] Text2Skin: message display update thread started (pid=32129, tid=32129) any ideas? thanks in advance Cristiano

1 0

HD-TV hardware decoding on motherboard instead of waiting for FF DVB-S2 card
by Ondrej Wisniewski 08 Feb '08

08 Feb '08

With VDR getting ready for HD-TV it seems that today the MPEG4 decoding can only be done on a high end processor or an external decoder card. Many people are still waiting for a FF DVB-S2 card but it doesn't look very promising at the moment. So I was wondering if it would be possible to use the on board video decoder chips of the VIA EPIA boards like the VIA EPIA EX15000G http://www.via.com.tw/en/products/mainboards/motherboards.jsp?motherboard_i… This board mounts a CX700M2 chipset which features MPEG2/4 hardware decoding. It has DVI and Y/Pb/Pr video output as well as analog and SPDIF audio (coaxial and optical). So that's everything we need, isn't it. I know, currently the OpenChrome video driver doesn't support MPEG2/4 video decoding for the CX700M2 and there are probably other things missing from the software support side. But from what I see, this or a similar motherboard in combination with a budget DVB-S2 card have all the hardware features that are needed to have HD-TV. So we actually have the proper hardware platform *today* for a quite a low budget. So if all the efforts go into driver and application development for such a platform, there is no need to wait for FF DVB-S2 cards. Or am I missing something here? -- Ondrej

14 19

Re: [vdr] vdr-rotor support patches for VDR-1.5.14
by lucian orasanu 08 Feb '08

08 Feb '08

Hy. use this patch too. --- device.c 2008-01-28 10:33:00.000000000 +0000 +++ device.c.new 2008-01-28 10:32:47.000000000 +0000 @@ -790,7 +790,7 @@ bool cDevice::SwitchChannel(int Directio return result; } -eSetChannelResult cDevice::SetChannel(const cChannel *Channel, bool LiveView) +eSetChannelResult cDevice::SetChannel(const cChannel *Channel, bool LiveView, cDevice *SpecificSourceDevice) { if (LiveView) { StopReplay(); ____________________________________________________________________________________ Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ

1 0

← Newer
1
...
5
6
7
8
9
10
11
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr February 2008