23 replies to this topic

[MCelliotG]

@@MCelliotG, Do you have a list of t2mi pids from your experiments with astra-sm?

Nope, cause I only have Ku Band and the only T2-MI I receive are from 4.8E. I partly received 80E but the satellite was moved for retirement a couple of days ago. Either way that was pid 4096 too!

 

Now in depth info, from Octagon's side they (semi) confirmed that they used a modified t2mi_decap which they implemented into driver firmware. This is why it's fully compatible with astra-sm's commands and requires the pid to be entered manually and this is why I firmly believe that decap can work alongside enigma2 as a process. Of course cpu consumption is a thing to consider, all boxes above 751 Mhz don't seem to struggle with T2-Mi through astra-sm, but will the same be for real time software decapsulation inside the enigma system?

 

Anyway, the T2-MI enigma changes that run on OpenATV now are truly annoying. They are enabled for all MIS capable tuners and I now have the options on HD51 which are completely useless, and since the support is pretty much dropped, I don't expect them to enable decapsulation in drivers. The worst is that now their Enigma2 reports a t2mi_plp_id value of 0 in all DVB-S2 services (which will lead me to drop temporarily the indication on my skin since it's erroreous).It should be -1 or None when the service is not T2-MI.

Oh whatever....

Edited by MCelliotG, 6 February 2019 - 00:20.

[twol]

 

@@MCelliotG, Do you have a list of t2mi pids from your experiments with astra-sm?

Nope, cause I only have Ku Band and the only T2-MI I receive are from 4.8E. I partly received 80E but the satellite was moved for retirement a couple of days ago. Either way that was pid 4096 too!

 

Now in depth info, from Octagon's side they (semi) confirmed that they used a modified t2mi_decap which they implemented into driver firmware. This is why it's fully compatible with astra-sm's commands and requires the pid to be entered manually and this is why I firmly believe that decap can work alongside enigma2 as a process. Of course cpu consumption is a thing to consider, all boxes above 751 Mhz don't seem to struggle with T2-Mi through astra-sm, but will the same be for real time software decapsulation inside the enigma system?

 

Anyway, the T2-MI enigma changes that run on OpenATV now are truly annoying. They are enabled for all MIS capable tuners and I now have the options on HD51 which are completely useless, and since the support is pretty much dropped, I don't expect them to enable decapsulation in drivers. The worst is that now their Enigma2 reports a t2mi_plp_id value of 0 in all DVB-S2 services (which will lead me to drop temporarily the indication on my skin since it's erroreous).It should be -1 or None when the service is not T2-MI.

Oh whatever....

 

Must be pretty exasperating on OpenATV as especially since they reverted the Octagon  drivers on the OE-A!!

OE-A Revert "[sf8008] update drivers, add t2mi scan option"  This reverts commit 0b06940.

Edited by twol, 6 February 2019 - 10:48.

[littlesat]

A revert without a description of the reason isn't really helpful....

[Huevos]

A revert without a description of the reason isn't really helpful....

Reason for the revert was faulty blindscan executable.

 

There will be no new driver update for this STB until at least 2 weeks time due to Chinese new year celebrations.