Re: [vdr] VDR as a set top box

2008-04-11 Thread Stephan Loescher
Simon Baxter [EMAIL PROTECTED] writes: Hi! How do I do this? I've been looking at modifying xinitrc and xinitrc-common to remove the desktop manager, but this seems a bit brutal. I only use X without any desktop. In my runvdr-script I do a startx with this ~/.xinitrc: vdr-sxfe --lirc

[vdr] VDR running on thin clients

2008-04-11 Thread Mike Parker
Has anyone done any work with thin clients and VDR? The price of Neoware thin clients are very low and it would be great to use these as remote receivers from my main vdr box. The boxes PXEboot and I do have them setup and running X, so just need some suggestions for how to view VDR. The machine

[vdr] Antwort: Re: [patch] channels with same pids+channels update

2008-04-11 Thread Peter Dittmann
[EMAIL PROTECTED] schrieb am 10.04.2008 14:53:04: ua0lnj schrieb: Hi If it's interecting for anybody. .. And other feature, this is deleting absent channels. If provider was deleted channels, you need delete it from channels.conf manually. After this patch, vdr auto deleting

[vdr] Output plugin

2008-04-11 Thread Josce
My Hauppauge DVB card rev2.1 (FF) DVB-C card has some connection problem on its video out jack. So sometimes the screen goes blank and I have to slightly adjust the video out plug to regain picture. I am currently using vdr-1.6.0. I would like to use the softdevice plugin but here is the catch:

Re: [vdr] xineliboutput: viewing 16:9 content on 4:3 output device

2008-04-11 Thread Ian Bates
Torgeir Veimo wrote: So (finally) a direct question: how do people with 4:3 output devices and vdr with xineliboutput configure their boxes? (shameless plug) Did you actually try softdevice? Dear Torgeir, Nothing shameless about the plug! Yes, I have tried softdevice (recent CVS and

Re: [vdr] Output plugin

2008-04-11 Thread Theunis Potgieter
on Gentoo there is vdr-mplayer plugin, it is basically a script that calls mplayer as the plugin, it only works for people that use a FrameBuffer or DVB Hardware output device. Now from what I understood at the time is that there are to methods for invoking mplayer there is a mplayer.sh and a

Re: [vdr] Output plugin

2008-04-11 Thread Füley István
d) any other solution? X + tvtime, it uses the MPEG2 decoder of the FF card. István -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ vdr mailing list vdr@linuxtv.org

Re: [vdr] Output plugin

2008-04-11 Thread Josce
X + tvtime, it uses the MPEG2 decoder of the FF card. Sorry, I should have stated that I wanted to avoid using X Windows. (I like vdr specifically because it is not X window) Josce _ Invite your mail contacts to join your friends

Re: [vdr] Output plugin

2008-04-11 Thread Theunis Potgieter
Perhaps the plugin could be adapted to pipe livetv to a unix socket and in the script tell mplayer where to connect to the unix socket? Or start recordings from VDR Admin or SVDRP and watch live-recording. Just playing with ideas. The mplayer script/plugin was designed to be not dependent on X

Re: [vdr] xineliboutput: viewing 16:9 content on 4:3 output device

2008-04-11 Thread Reinhard Nissl
Hi, Ian Bates schrieb: Thanks to everyone for their help and suggestions. More welcome too. In vdr-xine's setup menu, you can specify scaling factors for 16:9 and 4:3 images. Scaling 16:9 images by 133 % will fit it into a 4:3 window (e. g. full screen), dropping information on the left

Re: [vdr] VDR continuously initializing CAM

2008-04-11 Thread Arthur Konovalov
Klaus Schmidinger wrote: Since cCamSlot::Reset() is the only place where resetTime is set to a non-zero value, and you had lines like resetTime1: 1207548401 in your syslog_1 file, apparently the tc[i]-Process() call in cCamSlot::Process() must have failed. Yes, reset came from this procedure. I

Re: [vdr] VDR continuously initializing CAM

2008-04-11 Thread Klaus Schmidinger
On 04/11/08 22:51, Arthur Konovalov wrote: Klaus Schmidinger wrote: Since cCamSlot::Reset() is the only place where resetTime is set to a non-zero value, and you had lines like resetTime1: 1207548401 in your syslog_1 file, apparently the tc[i]-Process() call in cCamSlot::Process() must have

Re: [vdr] VDR continuously initializing CAM

2008-04-11 Thread Klaus Schmidinger
On 04/11/08 07:18, Arthur Konovalov wrote: Klaus Schmidinger wrote: Please change the line for (i = 0; i 200; ++i) { so that it loop 2000 times. That should cover a longer time. I see. Set to 4000. Additionally added before 'return 0;': printf(end: );

Re: [vdr] VDR continuously initializing CAM

2008-04-11 Thread Arthur Konovalov
Klaus Schmidinger wrote: Well, actually it's only one place there where false is returned, and that's when the alive timer times out, which is apparently after the 2 seconds between the resets you're observing, see #define TC_ALIVE_TIMEOUT 2000 One possible test would be to increase this time

Re: [vdr] VDR continuously initializing CAM

2008-04-11 Thread Arthur Konovalov
Now I have next question/problem. From Technisat support I have the following answer: Our CAM TechniCrypt CW is able to do multiple parallel decryptions since the software version 26.1.5.0.11 I have this firmware: Conax CA About 0. Quit menu 1. Software version: 26.1.5.0.11 2. Interface