[vdr] VDR tuning

Klaus Schmidinger Klaus.Schmidinger at tvdr.de
Sun Jun 10 11:18:54 CEST 2012


On 10.06.2012 06:23, Marx wrote:
> W dniu 2012-06-09 18:42, Klaus Schmidinger pisze:
>> On 09.06.2012 16:18, Marx wrote:
>>> What can be wrong if I can tune chanel with szap, but I can't it watch
>>> via streamdev because VDR can't tune it? Is it driver fault?
>>
>> I don't think it's a driver thing if you can tune with szap.
>> Maybe your DiSEqC setup needs to be adjusted.
>
> I did but no I don't use Diseqc, so in setup.conf it's: DiSEqC = 0
> So is it important that in diseqc.conf I still have Astra and Hotbird defined?

No. If you don't use DiSEqC, you don't need to care about diseqc.conf.

> Strange is I have only 3 channels on the list:
> :sat TV
> TVP 1;CYFRA +:10892:h:S13.0E:27500:166=2:104=pol at 4:503:100,1813,500,B00,B01,1803,1861:4807:318:11900:0
> TVP 2;CYFRA +:10892:h:S13.0E:27500:167=2:108=pol at 4:508:100,1813,500,B00,B01,1803,1861:4808:318:11900:0
> Polsat;Cyfrowy Polsat S.A.:11158:v:S13.0E:27500:257=2:258=pol at 4:264:0:13101:113:13200:0
>
> and while first two works via streamdev, the last one don't.

The last one in your list has a CA-ID of 0, which means FTA. HOwever,
this channel is also encrypted, just like the other two.
Here's the channels.conf entry I get for that channel:

   Polsat;Cyfrowy Polsat S.A.:11158:VC56M2S0:S13.0E:27500:257=2:258=pol at 4:264:1861,1803,100,1813,B01,500:13101:113:13200:0

> What's strange too - VDR reads EPG from all channels so probably it can tune but something is wrong with my setup and the last one can't be played.

The EPG data is received as soon as the transponder has been tuned to.
A particular channel needs more information, in this case the CA-IDs.

> Here's szap output:
> wuwek:/etc/vdr# szap -n 4 -r
> reading channels from file '/root/.szap/channels.conf'
> zapping to 4 'Polsat;Cyfrowy Polsat S.A.':
> sat 0, frequency = 11158 MHz V, symbolrate 27500000, vpid = 0x0101, apid = 0x0102 sid = 0x0108
> using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
> status 1e | signal ea00 | snr ffff | ber 00000000 | unc 00000000 | FE_HAS_LOCK
> status 1e | signal ea00 | snr ffff | ber 00000000 | unc 00000000 | FE_HAS_LOCK
> status 1e | signal ea00 | snr ffff | ber 00000000 | unc 00000000 | FE_HAS_LOCK
> status 1e | signal ea00 | snr ffff | ber 00000000 | unc 00000000 | FE_HAS_LOCK
> status 1e | signal ea00 | snr ffff | ber 00000000 | unc 00000000 | FE_HAS_LOCK
>
> and here is user.log:
> Jun 10 06:16:47 wuwek vdr: [11555] ERROR: no OSD provider available - using dummy OSD!
> Jun 10 06:16:48 wuwek vdr: [11562] DVBAPI: 0.0: status 'ready'
> ...
> Jun 10 06:16:48 wuwek vdr: [11562] DVBAPI: CaInfo: 0.0 sending CA info

Where do these DVBAPI log messages come from?

Klaus



More information about the vdr mailing list