Adapt to latest descrambler info API changes about pvr.hts HOT 31 CLOSED

Just a side note: This was added in HTSP v24

EDIT: Who needs this kind of things?

from pvr.hts.

It's an old Enigms thing so old it's from the time when cardsharing was so awesome you had to see it in action on every zap.

from pvr.hts.

hehe

from pvr.hts.

Even thought all the fancy stuff about ECM times are unnecessary before Kodi has a way to display them in the UI we still need to implement this new method to be able to properly show which CAID is being used (since HTSP v24 the CAID is always set to 0x0000 in subscriptionStart, clients are supposed to listen for this new message instead).

I'll try to come up with something next week. Will have to set up a complete test environment because I'm not touching my main tvheadend build.

from pvr.hts.

Any progress here?

from pvr.hts.

Sorry not yet, haven't had time to code for a while.

from pvr.hts.

@perexg I tried to start implementing this today but I can't get tvheadend to actually send any descramblerInfo HTSP messages. I'm trying the latest master in a virtual machine with a mux URL from my main tvheadend instance. Oscam is connected using DVBAPI and descrambling works. Please advice.

from pvr.hts.

Do you see ECM info in the tvh subscriptions tab ?

This is supported only for recent oscam (dvbapi network protocol v2).

from pvr.hts.

I have oscam r10500 something so it should be new enough. I didn't check the subscription tab, will do later and report back.

from pvr.hts.

I think that the network protocol v2 was added around 10700 or so.. You should upgrade oscam.

from pvr.hts.

It said protocol version 2 when I connected, but I guess I'll upgrade then.

from pvr.hts.

I finished the part of the code where the status is parsed and stored in the demuxer, but we have now hit a road block. Kodi needs a new API method for retrieving all this data during streaming instead of during channel import since the CAID is not available when fetching the list of channels. I'll have to think about the best way to add this to the API.

from pvr.hts.

When you press "O" in Kodi, it displays information about channel priovider, frequency, etc... There is also information about CAID (actually it is FFFF). This information if fetched from TVH on channel playback, not during importing channel list. After changes made by perexg, I believe TVH should pass information about current CAID to clients.

from pvr.hts.

That id incorrect, the CAID is only updated when the channel is updated. That's why this PR is not yet ready.

from pvr.hts.

Any news about tihs?

from pvr.hts.

Not really, haven't had the motivation to work on it for a while.

from pvr.hts.

Would it be hard to change so atleast existing CAID works again?

from pvr.hts.

@ksooo I'm thinking we could parse the descrambler data coming from tvheadend, then when we get the CAID we tell Kodi to update that channel. The only downside is that there would be one update per channel switch, which isn't exactly ideal.

from pvr.hts.

+1

from pvr.hts.

Whats the progress here?

from pvr.hts.

zero ;-)

from pvr.hts.

Would be nice to get this finally working

from pvr.hts.

Sure, but as we are all 100% volunteers, this absolutely is a question of a dev being in the mood for this ... and currently I'm not. Mainly monkey work - boring. Actual value of this feature is nearly zero. What's the point in knowing a channel is FTA or Nagra or whatever encrypted? :-/

from pvr.hts.

I would like this working too
And it's good way to see if everything is working as it should.
Should atleast get Encyption that Aeon Nox skin for example shows working.

from pvr.hts.

@belliash @Leatherface75 like this ?

point to do it this - more diagnostic information - if we got info "no subscription" to know if our CARD loose privileges - subscription, or when we have more card if choose correct encryption system etc.
also we can mark on channel list scrambled channel or put icon if yes in what system etc.

Skins develoepers can use that or not but better leave doors open

from pvr.hts.

Looks perfect. I just wonder what it will show as source if dvbapi socket used instead of IP? Maybe some name would be a better idea instead of IP (if possible to get also card name)?

from pvr.hts.

Guys, please stay on topic of this issue. Skinning is nothing that belongs to here. Otherwise I will lock this conversion.

from pvr.hts.

guys is other way -> make addon-service to got rest information from API of tvheadend
... and it works

from pvr.hts.

Problem is not that we don't know what or how to implement it. HTSP provides everything we need. No need to use the http API. The only "problem" is that none of the people with the required skills is currently in the mood to do it. End of discussion.

from pvr.hts.

Will be fixed with #315

from pvr.hts.

This can be closed as it is implemented meanwhile.

from pvr.hts.