Re: [vdr] VDR 1.5.17 - pre 1.3.19 compatibility mode problems

2008-04-08 Thread Stefan Lucke
On Wednesday 05 March 2008, Klaus Schmidinger wrote: > On 03/04/08 10:58, Tero Siironen wrote: > > Hi, > > > > I upgraded from VDR 1.4.7 to 1.5.17 and noticed that some of my old > > recordings won't play decently with this new version. Here's a syslog > > entry and example clip can be found f

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

2008-04-08 Thread Jouni Karvo
Ian Bates wrote: > One more remark, if as I believe from the comments in the code above, > that the '16:9 crop to 4:3' behaviour is not implemented in > xineliboutput, am I the only one suffering from the lack of this > feature? Am I the only one still using a 4:3 TV? I don't think so, > what

Re: [vdr] VDR as a set top box

2008-04-08 Thread Simon Baxter
> On Tuesday 08 April 2008, Simon Baxter wrote: > >> checking for cdio_open in -lcdio... no >> configure: error: *** Please install libcdio first! *** >> >> [EMAIL PROTECTED] oxine]# rpm -qa | grep libcdio >> libcdio-0.78.2-2.fc6 > > yum install libcdio-devel Ah idiot error! Now I have a new erro

Re: [vdr] VDR continuously initializing CAM

2008-04-08 Thread Tuomas Jormola
On 9 Apr 2008, at 00:26, Klaus Schmidinger wrote: > On 04/08/08 23:17, Tuomas Jormola wrote: >> On 8 Apr 2008, at 23:49, Klaus Schmidinger wrote: >>> Since this apparently happens also without VDR, I guess it will have >>> to >>> be fixed in the driver. >> Well, the funny thing is that VDR 1.4.7 w

Re: [vdr] How can VDR record with timer if behind a decoder ?

2008-04-08 Thread Michael Mauch
vroemm wrote: > There is something i do not understand. > Here is how i though it works: > > My TV provider, Casema in the netherlands, delivers digital TV via a decoder > with a sort of credit card. > Normally you use the remote control of this decoder to choose the tv prog to > watch. > Thus

Re: [vdr] VDR continuously initializing CAM

2008-04-08 Thread Christoph Pfister
[ sorry for breaking thread - but people don't seem to honor CC ] On 04/08/08 22:49, Klaus Schmidinger wrote: > > And explanation: > > After a reset CAM is "absent" for a very short time (<14ms == less than > > a scheduler tick) and then it takes ~1.7s to become ready again. (The > > intervall be

Re: [vdr] Looking for Medion MD4688 remote code for VDR

2008-04-08 Thread Udo Richter
Jean-Claude Repetto wrote: > My Medion MD 4688 remote (from Aldi) has lost its codes because the > batteries were dead :-( > I am not using LIRC, but the RC input of a WinTV DVB-S REV 1.3, and this > is my remote.conf file : > > remote-event0._Setup /proc/av7110_ir 8000 20 > remote-event

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

2008-04-08 Thread Petri Helin
Patrick Boettcher wrote: > Hi, > > On Tue, 8 Apr 2008, Ian Bates wrote: >> One more remark, if as I believe from the comments in the code above, >> that the '16:9 crop to 4:3' behaviour is not implemented in >> xineliboutput, am I the only one suffering from the lack of this >> feature? Am I the

Re: [vdr] VDR continuously initializing CAM

2008-04-08 Thread Klaus Schmidinger
On 04/08/08 23:17, Tuomas Jormola wrote: > On 8 Apr 2008, at 23:49, Klaus Schmidinger wrote: >> Since this apparently happens also without VDR, I guess it will have >> to >> be fixed in the driver. > Well, the funny thing is that VDR 1.4.7 with exactly the same kernel > and hardware does not gi

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

2008-04-08 Thread Darren Salt
I demand that Ian Bates may or may not have written... > I have lurked a while on this list but until now have not had reason to > post. > I am unable to configure xineliboutput to my liking. [snip] > My output device is a 4:3 analog TV. Watching a 4:3 stream is fine in the > sense that the ful

Re: [vdr] VDR continuously initializing CAM

2008-04-08 Thread Tuomas Jormola
On 8 Apr 2008, at 23:49, Klaus Schmidinger wrote: > > Since this apparently happens also without VDR, I guess it will have > to > be fixed in the driver. Well, the funny thing is that VDR 1.4.7 with exactly the same kernel and hardware does not give any symptoms at all. On startup CAM is ini

Re: [vdr] VDR continuously initializing CAM

2008-04-08 Thread Klaus Schmidinger
On 04/08/08 21:10, Arthur Konovalov wrote: > Klaus Schmidinger wrote: >> At this point... >> >>> Apr 7 09:06:41 vdr vdr: [4862] ms: 3 >>> Apr 7 09:06:41 vdr vdr: [4862] resetTime1: 0 >>> Apr 7 09:06:41 vdr vdr: [4862] ms: 2 >> >> ...the module status changed from 3 ("ready") to 2 ("present"). >>

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

2008-04-08 Thread Patrick Boettcher
Hi, On Tue, 8 Apr 2008, Ian Bates wrote: > One more remark, if as I believe from the comments in the code above, > that the '16:9 crop to 4:3' behaviour is not implemented in > xineliboutput, am I the only one suffering from the lack of this > feature? Am I the only one still using a 4:3 TV? I d

[vdr] How can VDR record with timer if behind a decoder ?

2008-04-08 Thread vroemm
Hi. There is something i do not understand. Here is how i though it works: My TV provider, Casema in the netherlands, delivers digital TV via a decoder with a sort of credit card. Normally you use the remote control of this decoder to choose the tv prog to watch. Thus decoder sends only the se

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

2008-04-08 Thread Ian Bates
Thank you Torgeir for you response. Now I know the correct terminology! Back to general comments. I have had a look at the xineliboutput source code, and it appears that 'centercutout' and 'pan&scan', features which I think are the ones I want, are at best work in progress: xine_frontend.c: a

Re: [vdr] VDR continuously initializing CAM

2008-04-08 Thread Arthur Konovalov
Klaus Schmidinger wrote: At this point... Apr 7 09:06:41 vdr vdr: [4862] ms: 3 Apr 7 09:06:41 vdr vdr: [4862] resetTime1: 0 Apr 7 09:06:41 vdr vdr: [4862] ms: 2 ...the module status changed from 3 ("ready") to 2 ("present"). The module status is retrieved from the driver in cDvbCiAdapter::

[vdr] vdr-burn gcc 4.3 build fix

2008-04-08 Thread Ville Skyttä
Hi, The attached patch fixes build of vdr-burn (current CVS HEAD) with gcc 4.3's cleaned up C++ headers. Index: adaptor.h === RCS file: /var/cvsroot/burn/adaptor.h,v retrieving revision 1.4 diff -u -r1.4 adaptor.h --- adaptor.h 16 Se

Re: [vdr] VDR as a set top box

2008-04-08 Thread Ville Skyttä
On Tuesday 08 April 2008, Simon Baxter wrote: > checking for cdio_open in -lcdio... no > configure: error: *** Please install libcdio first! *** > > [EMAIL PROTECTED] oxine]# rpm -qa | grep libcdio > libcdio-0.78.2-2.fc6 yum install libcdio-devel ___ v

Re: [vdr] [PATCH] Install headers, add pkgconfig file

2008-04-08 Thread Ville Skyttä
On Wednesday 12 March 2008, Ville Skyttä wrote: > On Wednesday 12 March 2008, clemens kirchgatterer wrote: > > On Tue, Mar 11, 2008 at 3:46 PM, Joerg Pulz <[EMAIL PROTECTED]> wrote: > > > Out of this four cases (there are probably more, one for every Linux > > > distribution on this planet), tel

Re: [vdr] VDR as a set top box

2008-04-08 Thread Simon Baxter
>I am making some experiment with Oxine. > I did also try Freevo. I find Oxine much lighter and much easier to > configure. > > sp I can't get oxine compiled - get stuck at: checking for cdio_open in -lcdio... no configure: error: *** Please install libcdio first! *** [EMAIL PROTECTED] oxine]#

Re: [vdr] [Announce] vdr-streamdev-0.3.4 and CVS branch

2008-04-08 Thread Dominique Simon
Am 07.04.2008 um 18:08 schrieb Frank Schmirler: > streamdev-0.3.4 is finally available from http://streamdev.vdr-developer.org > . Nice to see that development goes on! Thanks for the new Version. Ciao, Dominique ___ vdr mailing list vdr@linuxtv.org

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

2008-04-08 Thread Torgeir Veimo
On 8 Apr 2008, at 16:43, Ian Bates wrote: > What I would like is to maintain the stream 16:9 ratio but by by > cropping the left and right sections of the stream that fall 'outside' > the TV, so the full real estate of the TV is used, at the expense of > losing some stream information. This setti

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

2008-04-08 Thread Ian Bates
Dear all, I have lurked a while on this list but until now have not had reason to post. I am unable to configure xineliboutput to my liking. I don't imagine I am the only one with this issue, but I have not been able to find a solution, either by trial and error or by googling. I would appre

Re: [vdr] VDR continuously initializing CAM

2008-04-08 Thread Klaus Schmidinger
On 04/08/08 10:25, Tuomas Jormola wrote: > Hi, > > I forgot to post this earlier, but in the attachment you'll find logs of > this issue on my system. I modified the code like this: > > eModuleStatus cCamSlot::ModuleStatus(void) > { > cMutexLock MutexLock(&mutex); > eModuleStatus ms = ciAdap

[vdr] Femon and new API.

2008-04-08 Thread lucian orasanu
Helo. I'am tring to port femon to new api and no succes. 1. Questions. Is all new api implemented iet in multiproto? New version of api is 3.3 pr 4.3? Is there any documentation ? 2. My tests and work. I put this code : enum dvbfe_status { DVBFE_HAS_SIGNAL

Re: [vdr] Newbie: Pinnacle PCTV tuner kit rev 1.7 good for VDR ?

2008-04-08 Thread vroemm
On Tuesday 08 April 2008 09:18, vroemm wrote: > Pinnacle PCTV TUNER KIT > I could not find a type number. > On the card is the text "REV 1.7" > It is a PCI card. > On the box are two pictures of DVB-T and DVB-C > And it has a TV input and TV output, according to the picture on the box. > Its price

[vdr] Newbie: Pinnacle PCTV tuner kit rev 1.7 good for VDR ?

2008-04-08 Thread vroemm
Hi. I am new to this vdr mailinglist. I have been admiring the VDR project for a long time. And now am looking seriously into building one. I am having trouble finding a DVB-C PCI card in the city where i live. There is this one: Pinnacle PCTV TUNER KIT I could not find a type number. On the ca

[vdr] Looking for Medion MD4688 remote code for VDR

2008-04-08 Thread Jean-Claude Repetto
Hi, My Medion MD 4688 remote (from Aldi) has lost its codes because the batteries were dead :-( Obviously, I had not written the codes on the back label of the remote control. I have looked at this ML archives and found some codes (308, 336), but they are not working. I am not using LIRC, but t