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 th
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.
> While copying the code here to ask for help in searching the bug,
> it seems that I found the bug -- a missing break in the DVB-T
> case ;-)
>
> Please try the attached patch.
Reinhard you've done it!!! All working! :-)
Thanks a lot for your work, I'm sure a lot of people are going to be very h
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 yo
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]
_
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
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
> >
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 l
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
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 e
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 creat
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,
12 matches
Mail list logo