Re: [vdr] [ANNOUNCE] VDR developer version 1.7.3

2009-01-18 Thread Klaus Schmidinger
On 13.01.2009 10:44, Oliver Joa wrote: > Klaus Schmidinger wrote: > > [...] > >> Ok, then let's have another id for this... > > What about an id which can be set in the config-file? Should be the > easiest thing to implement. I was more thinking of a command line option, because this is an "in

Re: [vdr] WinTV USB CI-Module and recommended distribution for VDR?

2009-01-18 Thread Lauri Tischler
Sascha Vogt wrote: > Hi Lauri, > > Lauri Tischler schrieb: >> Sascha Vogt wrote: >>> as my hardware is shipping (went for the ASUS M2N78Pro, GeForce 8300 >>> with an Athlon X2 4850e, hopefully that'll work with VDPAU and HD >>> videos) >> Couldn't find M2N78Pro, do you mean M3N78PRO ? > Sorry, you

Re: [vdr] ATSC a good primers guide? (Moving from Italy to the US with my VDR setup)

2009-01-18 Thread Joerg Bornkessel
> I'm looking at moving from Italy to the US in the summer and am trying > to spend my time (while not highly preoccupied about health insurance, > jobs, houses, shipping etc) trying to think through taking my VDR setup > and Dreambox over to the US. > I currently have a couple of Hauppauge DVB-S

Re: [vdr] vdr-sxfe + remote control

2009-01-18 Thread Jukka Tastula
On Saturday 17 January 2009 22:32:55 Alex Betis wrote: > Will try to clarify: > I run VDR with --lirc=/dev/null > When I run vdr-sxfe with --lirc and with --verbose, I can see that it > receives events the same way as irw, but it also receives keyboard > events that are passed to the system by the

Re: [vdr] vdr-sxfe + remote control

2009-01-18 Thread Ville Aakko
If I understood the issue correctly, Alex (the OP) has problems because the USB receiver gives BOTH kb events and makes a lirc device, and the KB events are not wanted and cause problems. I'd look in /dev/input to see which event device is the one for the KB side of the receiver and disable it; pe

Re: [vdr] WinTV USB CI-Module and recommended distribution for VDR?

2009-01-18 Thread Tony Houghton
On Sun, 18 Jan 2009 13:17:11 +0200 Lauri Tischler wrote: > Sascha Vogt wrote: > > Hi Lauri, > > > > Lauri Tischler schrieb: > >> Sascha Vogt wrote: > >>> as my hardware is shipping (went for the ASUS M2N78Pro, GeForce 8300 > >>> with an Athlon X2 4850e, hopefully that'll work with VDPAU and HD >

[vdr] [ANNOUNCE] VDRAdmin-AM v3.6.4

2009-01-18 Thread Andreas Mair
Hello everybody! A new VDRAdmin-AM release is online: http://andreas.vdr-developer.org/vdradmin-am/download.html Have fun! Regards, Andreas *** HISTORY *** * 3.6.3 -> 3.6.4 - Added: Use ".update" in VDR's video directory to check if recordings cache needs to be refreshed. - Added: CACHE_REC_ENAB

Re: [vdr] vdr-sxfe + remote control

2009-01-18 Thread Alex Betis
On Sun, Jan 18, 2009 at 3:44 PM, Ville Aakko wrote: > If I understood the issue correctly, Alex (the OP) has problems > because the USB receiver gives BOTH kb events and makes a lirc device, > and the KB events are not wanted and cause problems. I'd look in > /dev/input to see which event device

Re: [vdr] WinTV USB CI-Module and recommended distribution for VDR?

2009-01-18 Thread Sascha Vogt
Hi, Lauri Tischler schrieb: > Sascha Vogt wrote: >> Lauri Tischler schrieb: >>> Sascha Vogt wrote: as my hardware is shipping (went for the ASUS M2N78Pro, GeForce 8300 with an Athlon X2 4850e, hopefully that'll work with VDPAU and HD videos) >>> Couldn't find M2N78Pro, do you mean M3

[vdr] xineliboutput + vdpau not ready for prime time

2009-01-18 Thread Gerald Dachs
I have made some experiments with xineliboutput and vdpau, it looked promising, but at least I had to give up for now. I have used vdr 1.6.0, xineliboutput 1.0.3, nvidia driver 180.22, xine-lib-vdpau from 20090113 and xinelib 1.1.90hg from 20090114 with vdpau-patch r160. I use it with sdtv, because

Re: [vdr] xineliboutput + vdpau not ready for prime time

2009-01-18 Thread Gerald Dachs
> The biggest problem is that if I switch > channels it happens that the video starts to flicker. You can see that > between the pictures of the current channel the pictures of the > previous channel appear. I noticed now that it get worst if I use "software scaling" in the xineliboutput settings