Re: [vdr] BUG: DVB-T and DVB-S[2] do not work with VDR & multiproto [Was: Two VDR's on one machine]

2008-01-12 Thread Stefan Lucke
On Saturday 12 January 2008, Morfsta wrote:
> On Jan 12, 2008 3:37 PM, Stefan Lucke <[EMAIL PROTECTED]> wrote:
> > Same here.
> > Which DVB-T device do you use ? I'm using a cinergyT2.
> >
> > Ioctl's for this device are not passed
> > via the common frontend interface. The new "API" has to get
> > integrated into the cinergyT2 driver or client programs like vdr etc.
> > have to recognize the driver supported API ;-) .
> >
> 
> I am using two Hauppauge Nova-T (tda1004x and cx2388x).
> 
> Manu said in an earlier thread that there should be compatibility with
> the old API so he doesn't think that should be a problem. The driver
> in the multiproto tree for my devices have not been changed so should
> work through the compatibility layer.
> 
> The odd thing is that when I use an older pre-compiled VDR 1.4.x with
> the new multiproto drivers everything works fine but when I compile
> 1.5.12 with multiproto includes it doesn't work.

So I guess in your case, there is still an issue with the compatibility
layer of http://jusst.de/hg/multiproto/ .

In my case I managed to get my cinergyT2 work with Reinhard's
modified vdr, with attached diff.


-- 
Stefan Lucke
diff -r 4df151d5b3fe linux/drivers/media/dvb/cinergyT2/cinergyT2.c
--- a/linux/drivers/media/dvb/cinergyT2/cinergyT2.c Sat Dec 01 01:50:24 
2007 +0400
+++ b/linux/drivers/media/dvb/cinergyT2/cinergyT2.c Sat Jan 12 22:45:29 
2008 +0100
@@ -1,5 +1,5 @@
 /*
- * TerraTec Cinergy T²/qanu USB2 DVB-T adapter.
+ * TerraTec Cinergy T²/qanu USB2 DVB-T adapter.
  *
  * Copyright (C) 2004 Daniel Mack <[EMAIL PROTECTED]> and
  * Holger Waechtler <[EMAIL PROTECTED]>
@@ -511,6 +511,106 @@ static uint16_t compute_tps (struct dvb_
return tps;
 }
 
+static uint16_t compute_newtps (struct dvbfe_params *fep)
+{
+   uint16_t tps = 0;
+
+   switch (fep->delsys.dvbt.code_rate_HP) {
+   case DVBFE_FEC_2_3:
+   tps |= (1 << 7);
+   break;
+   case DVBFE_FEC_3_4:
+   tps |= (2 << 7);
+   break;
+   case DVBFE_FEC_5_6:
+   tps |= (3 << 7);
+   break;
+   case DVBFE_FEC_7_8:
+   tps |= (4 << 7);
+   break;
+   case DVBFE_FEC_1_2:
+   case DVBFE_FEC_AUTO:
+   default:
+   /* tps |= (0 << 7) */;
+   }
+
+   switch (fep->delsys.dvbt.code_rate_LP) {
+   case DVBFE_FEC_2_3:
+   tps |= (1 << 4);
+   break;
+   case DVBFE_FEC_3_4:
+   tps |= (2 << 4);
+   break;
+   case DVBFE_FEC_5_6:
+   tps |= (3 << 4);
+   break;
+   case DVBFE_FEC_7_8:
+   tps |= (4 << 4);
+   break;
+   case DVBFE_FEC_1_2:
+   case DVBFE_FEC_AUTO:
+   default:
+   /* tps |= (0 << 4) */;
+   }
+
+   switch (fep->delsys.dvbt.constellation) {
+   case DVBFE_MOD_QAM16:
+   tps |= (1 << 13);
+   break;
+   case DVBFE_MOD_QAM64:
+   tps |= (2 << 13);
+   break;
+   case DVBFE_MOD_QPSK:
+   default:
+   /* tps |= (0 << 13) */;
+   }
+
+   switch (fep->delsys.dvbt.transmission_mode) {
+   case DVBFE_TRANSMISSION_MODE_8K:
+   tps |= (1 << 0);
+   break;
+   case DVBFE_TRANSMISSION_MODE_2K:
+   default:
+   /* tps |= (0 << 0) */;
+   }
+
+   switch (fep->delsys.dvbt.guard_interval) {
+   case DVBFE_GUARD_INTERVAL_1_16:
+   tps |= (1 << 2);
+   break;
+   case DVBFE_GUARD_INTERVAL_1_8:
+   tps |= (2 << 2);
+   break;
+   case DVBFE_GUARD_INTERVAL_1_4:
+   tps |= (3 << 2);
+   break;
+   case DVBFE_GUARD_INTERVAL_1_32:
+   default:
+   /* tps |= (0 << 2) */;
+   }
+
+   switch (fep->delsys.dvbt.hierarchy) {
+   case DVBFE_HIERARCHY_ON:
+   switch (fep->delsys.dvbt.alpha) {
+   case DVBFE_ALPHA_1:
+   tps |= (1 << 10);
+   break;
+   case DVBFE_ALPHA_2:
+   tps |= (2 << 10);
+   break;
+   case DVBFE_ALPHA_4:
+   tps |= (3 << 10);
+   break;
+   }
+   

Re: [vdr] BUG: DVB-T and DVB-S[2] do not work with VDR & multiproto [Was: Two VDR's on one machine]

2008-01-12 Thread Morfsta
On Jan 12, 2008 3:37 PM, Stefan Lucke <[EMAIL PROTECTED]> wrote:
> Same here.
> Which DVB-T device do you use ? I'm using a cinergyT2.
>
> Ioctl's for this device are not passed
> via the common frontend interface. The new "API" has to get
> integrated into the cinergyT2 driver or client programs like vdr etc.
> have to recognize the driver supported API ;-) .
>

I am using two Hauppauge Nova-T (tda1004x and cx2388x).

Manu said in an earlier thread that there should be compatibility with
the old API so he doesn't think that should be a problem. The driver
in the multiproto tree for my devices have not been changed so should
work through the compatibility layer.

The odd thing is that when I use an older pre-compiled VDR 1.4.x with
the new multiproto drivers everything works fine but when I compile
1.5.12 with multiproto includes it doesn't work.

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


Re: [vdr] BUG: DVB-T and DVB-S[2] do not work with VDR & multiproto [Was: Two VDR's on one machine]

2008-01-12 Thread Stefan Lucke
On Saturday 12 January 2008, Morfsta wrote:
> Hi,
> 
> Thanks for speaking with Marco, Reinhard - its appreciated.
> 
> Unfortunately, the patch does not fix the problem. Still no picture on
> DVB-T transmissions.

Same here.
Which DVB-T device do you use ? I'm using a cinergyT2.

Ioctl's for this device are not passed
via the common frontend interface. The new "API" has to get
integrated into the cinergyT2 driver or client programs like vdr etc.
have to recognize the driver supported API ;-) .

> 
> Regards
> 
> On Jan 11, 2008 7:21 PM, Reinhard Nissl <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > Reinhard Nissl schrieb:
> >
> > > So it seems to me that either the emulation layer has a bug for
> > > DVB-T or the patched VDR passes incorrect data to the new API.
> >
> > Looks like the latter is true: Marco Schlüßler informed me that
> > the mapping of TransmissionModes in nit.c for DVB-T is wrong.
> >
> > I've created the attached patch according to his' instructions.
> >
> > Please give the patch a try and report success or failure.
> >
> >
> > Bye.

Stefan Lucke

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


Re: [vdr] BUG: DVB-T and DVB-S[2] do not work with VDR & multiproto [Was: Two VDR's on one machine]

2008-01-12 Thread Morfsta
Hi,

Thanks for speaking with Marco, Reinhard - its appreciated.

Unfortunately, the patch does not fix the problem. Still no picture on
DVB-T transmissions.

Regards

On Jan 11, 2008 7:21 PM, Reinhard Nissl <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Reinhard Nissl schrieb:
>
> > So it seems to me that either the emulation layer has a bug for
> > DVB-T or the patched VDR passes incorrect data to the new API.
>
> Looks like the latter is true: Marco Schlüßler informed me that
> the mapping of TransmissionModes in nit.c for DVB-T is wrong.
>
> I've created the attached patch according to his' instructions.
>
> Please give the patch a try and report success or failure.
>
>
> Bye.
> --
> Dipl.-Inform. (FH) Reinhard Nissl
> mailto:[EMAIL PROTECTED]
>
> ___
> vdr mailing list
> vdr@linuxtv.org
> http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
>
>

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


Re: [vdr] BUG: DVB-T and DVB-S[2] do not work with VDR & multiproto [Was: Two VDR's on one machine]

2008-01-11 Thread Reinhard Nissl
Hi,

Reinhard Nissl schrieb:

> So it seems to me that either the emulation layer has a bug for
> DVB-T or the patched VDR passes incorrect data to the new API.

Looks like the latter is true: Marco Schlüßler informed me that
the mapping of TransmissionModes in nit.c for DVB-T is wrong.

I've created the attached patch according to his' instructions.

Please give the patch a try and report success or failure.

Bye.
-- 
Dipl.-Inform. (FH) Reinhard Nissl
mailto:[EMAIL PROTECTED]
--- ../vdr-1.5.12-dvbs2-other/nit.c	2008-01-01 22:55:18.0 +0100
+++ nit.c	2008-01-11 20:15:15.0 +0100
@@ -239,7 +239,7 @@ void cNitFilter::Process(u_short Pid, u_
  int CodeRateLP = CodeRates[sd->getCodeRateLP()];
  static int GuardIntervals[] = { DVBFE_GUARD_INTERVAL_1_32, DVBFE_GUARD_INTERVAL_1_16, DVBFE_GUARD_INTERVAL_1_8, DVBFE_GUARD_INTERVAL_1_4 };
  int GuardInterval = GuardIntervals[sd->getGuardInterval()];
- static int TransmissionModes[] = { DVBFE_TRANSMISSION_MODE_2K, DVBFE_TRANSMISSION_MODE_4K, DVBFE_TRANSMISSION_MODE_8K, DVBFE_TRANSMISSION_MODE_AUTO };
+ static int TransmissionModes[] = { DVBFE_TRANSMISSION_MODE_2K, DVBFE_TRANSMISSION_MODE_8K, DVBFE_TRANSMISSION_MODE_4K, DVBFE_TRANSMISSION_MODE_AUTO };
  int TransmissionMode = TransmissionModes[sd->getTransmissionMode()];
  static int Alphas[] = { DVBFE_ALPHA_1, DVBFE_ALPHA_2, DVBFE_ALPHA_4 };
  static int Priorities[] = { DVBFE_STREAM_PRIORITY_LP, DVBFE_STREAM_PRIORITY_HP };
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


Re: [vdr] BUG: DVB-T and DVB-S[2] do not work with VDR & multiproto [Was: Two VDR's on one machine]

2008-01-10 Thread Reinhard Nissl
Hi,

Morfsta schrieb:

> This problem keeps coming up over again, but for some reason Reinhard
> and Manu don't seem to want to talk about it.

Well, what should I talk about it? I don't have a DVB-T device
for testing and even if I had one, I live in a DVB-S only area in
Germany.

And furthermore, I was only involved in the multiproto
development as a tester. I don't know much about the internals.
The DVB-S2 port of VDR was contributed by Marco Schlüßler and I
only redistribute it to protect users form the pain to merge two
patchsets by hand.

> I do not understand why you can't use DVB-T with DVB-S2 using the
> multiproto drivers and VDR, but I doubt it can be much of a problem.

Well, both Manu and Marco wrote that the current multiproto tree
provides an emulation layer which allows to access drivers which
only provide the old API via the new API.

So it seems to me that either the emulation layer has a bug for
DVB-T or the patched VDR passes incorrect data to the new API.

> It would be great if someone could look into this for us!

I'm sorry that I cannot help you in this regard.

Bye.
-- 
Dipl.-Inform. (FH) Reinhard Nissl
mailto:[EMAIL PROTECTED]

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr