16 replies to this topic

[Andi316]

With newest drivers VU added the "fast Channel change" feature to the 4K. In my view this is a "killer-feature". Really impressive with VTI.

Any Chance to get it with openpli anytime soon?

Edited by Andi316, 23 May 2016 - 16:44.

[Erik Slagter]

Short: no.

 

It adds a whole lot of complexity while the gain is minimal.

[littlesat]

And for cards or ci that can decode just a few channels at once it makes no sense at all...

[Andi316]

Itˋs working perfect with german PayTV. Itˋs a new outstanding feature which Nobody else is offering. I believe you are wrong. Iˋm curious how many People will ask for FCC. Time will tell us.

[athoik]

There are more important features still missing like blindscan support, CI+, etc.

Without CI+ you cannot open already those "German channels" if you mean HD+

PS. We already know that VTI/OpenATV has a CI+ solution, but due to GPL issues the files are not public.

[Pr2]

Most of the newest pay card have an internal "rate limit ECM" some cards are only able to decode 2 channels at the same time! And if you didn't protect the card, your card it will consider that you are doing card sharing on it (due to too many ECM at the same time) and this will definitively locked your card.

 

So if this feature is just trying to decode channels that we are not watching just to fasten from a few milliseconds the zapping time this makes no sense to me and it will bring lots of trouble with cards.

[littlesat]

The way vu did implement ci+ does violate the gpl license from enigma2.... Hopefully they will change it soon....

Edited by littlesat, 23 May 2016 - 19:34.

[Rob van der Does]

Short: no.

 

It adds a whole lot of complexity while the gain is minimal.

I fully agree with that statement. An enormous amount of complex changes, just to zap to the next/previous service a bit faster?

If people really want this 'feature', they should simply use VU's original image or any of it's derivatives.

[Erik Slagter]

Or VU+ should implement it at driver level.

[Rob van der Does]

A solution they usually avoid

[littlesat]

Cannot be done in drivers. Drivers Cannot access the channellist.

Edited by littlesat, 26 May 2016 - 20:53.

[Lost in Space]

Nonsense, the Helper for Dreamboxes reads directly from ci assignment file and the lamedb file without problems to check for assignments. Please explain why should a driver be unable to do that too ?

Edited by gutemine, 27 May 2016 - 16:12.

[littlesat]

This is not about CI+ but about FFC... Indeed the drivers could read the lamedb, but this is fully out of scope here....

[Erik Slagter]

Cannot be done in drivers. Drivers Cannot access the channellist.

That's not the point. A lot of the functionality that they build into enigma could be added to the driver instead. Another interesting solution would be to add most of the extra functionality into an external, open source of course, executable, so we won't have to "herverbouw" enigma just for one receiver.

[Erik Slagter]

This is not about CI+ but about FFC... Indeed the drivers could read the lamedb, but this is fully out of scope here....

Now you're talking nonsense, really. Drivers run in kernel space. There is no way they can open or read the contents of a file. If you want that, you need a piece of userspace code that feeds the data into the drivers over the api. But even then, drivers don't know about enigma servicerefs or the way enigma indexes it's tuners, etc.

[littlesat]

Let's wait for Gutemine response.... Let's wait for his magic...

[mrvica]

his magic...

she is a woman