sat ip client behaviour

[kallquk]

Hello,

 

I installed latest demo version, intention to upgrade to pro, but before I need to sovle some problem:

 

As I have no hardware, I configured DVBViewer as sat ip rtsp tuner and works good.

 

But at fta channels only.

 

It gives the message "There is no matching DVB device avalaible for this channel", and nothing, it goes to previous one.

 

The problem is that DVBViewer neither zap to this scrambled channel.

 

this software is not for fta channels, isn't it ?

How can I solve it ?

 

regards

 

 

[Griga]

13 minutes ago, kallquk said:

The problem is that DVBViewer neither zap to this scrambled channel.

 

Decrambling is not supported by the Sat>IP standard, neither on the server nor on the client side. It can only work with a proprietary protocol outside the standard. DVBViewer supports it if the Sat>IP server is the DVBViewer Media Server (of course) or a Digital Devices OctopusNet server with CI/CAM.

 

Some users overcome this limitation by using software (plugin) descrambling. However, for legal reasons this must not be discussed or supported in this forum.

 

[kallquk]

Thanks for help

 

The problem is that DVBViewer does not consider a not fta channel from satip tuner, and its relevant data is not 'processed',  an goes to previous fta one, not a descrambling issue.

The same pc has a tvheadend which handles the conection to the same sat ip server without problem at a not fta channel, and if I have rights they are cleared else is black screen, but they are 'processed' normally.

 

DVBViewer ignores a channel if it detects that is scrambled, ignores it, does not zap to it but goes to previous, so third part software you mentioned are not called in use

[Griga]

7 hours ago, kallquk said:

It gives the message "There is no matching DVB device avalaible for this channel"

 

Is "Has CI module" checked for the RTSP Network Devices in Options -> Hardware -> Devices? DVBViewer does not use them for scrambled channels, if not.

 

[kallquk]

thank you very much for the help

 

It was the problem, checked and then as expected.