Reinhard Nissl wrote:
Hi,
Morfsta schrieb:
Please report the debug output here for further investigation.
Attached are two files - tuning to the same DVB-T channel using either
system and the Philips frontend... vdr-1.4.x shows the channel fine,
1.5.12 does not.
Hope this helps and
Reinhard Nissl wrote:
Hi,
Morfsta schrieb:
Please report the debug output here for further investigation.
Attached are two files - tuning to the same DVB-T channel using either
system and the Philips frontend... vdr-1.4.x shows the channel fine,
1.5.12 does not.
Hope this
Hi,
Reinhard Nissl schrieb:
Please report the debug output here for further investigation.
Please report the relevant channel from VDR-1.4.x' channel.conf
and from VDR-1.5.12's channel.conf too.
Bye.
--
Dipl.-Inform. (FH) Reinhard Nissl
mailto:[EMAIL PROTECTED]
I spent the whole evening with Manu looking through the emulation
layer and cannot see any obvious errors in the DVB-T case.
Thank-you very much for your time.
Then use VDR-1.4.x (limited to only one device) and tune to a
certain DVB-T channel. Have a look what the driver reports (see
Please report the relevant channel from VDR-1.4.x' channel.conf
and from VDR-1.5.12's channel.conf too.
1.4.x: -
BBC ONE;BBC:73000:I0C34D34M16B8T2G32Y0:T:27500:600:601=eng,602=eng:0:0:4165:
9018:4101:0
1.5.12: -
BBC
Hi,
Morfsta schrieb:
Please report the debug output here for further investigation.
Attached are two files - tuning to the same DVB-T channel using either
system and the Philips frontend... vdr-1.4.x shows the channel fine,
1.5.12 does not.
Hope this helps and thanks again for your
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
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
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
Hi,
Stefan Lucke schrieb:
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
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
This problem keeps coming up over again, but for some reason Reinhard
and Manu don't seem to want to talk about it.
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.
I started modifying VDR to use the old API
12 matches
Mail list logo
