123 replies to this topic

[Erik Slagter]

I can report it in this form to VU+, but the chances getting it fixed quickly are somewhat higher if more details are known

[meatop]

I can report it in this form to VU+, but the chances getting it fixed quickly are somewhat higher if more details are known

 

Somehow I still lack some basic understanding. I thought OpenPLI is maintained by, well, the "OpenPLI group".

[WanWizard]

The drivers, the interface (or translation layer) between OpenPLi and the underlying hardware are not open source, but are maintained by the manufacturer.

 

So if they contain a bug, all we can do is pass the info along and hope it will be fixed soon.

[Erik Slagter]

And meatop could have known this fact if meatop would have read some of the other messages. That would have saved both sides from needless irritation.

[VladaT]

I confirm it too - Vu+Duo2, enigma2-plugin-extensions-hbbtv doesn't work. What to do?

[Erik Slagter]

I will have a look. When I have time.

[solid80]

Hi,

 

I'm also having the same problem on a Vu+ Solo SE receiver. HbbTV was working fine last week. After some recent update it stopped working. I found en error.log under /usr/local/hbb-browser/home, here is the latest error message. I don't know if it can help. It might be related with the missing URL.

--- 18 Nov 2015 20:33:29 ---
file://localhost/usr/local/hbb-browser/root/directfb-ui/navWindow.html
Unknown thread
Uncaught exception: ReferenceError: Undefined variable: urlChange

Error thrown at line 1, column 0 in program code:
    urlChange('file://localhost/usr/local/hbb-browser/root/directfb-ui/navWindow.html');


--- 18 Nov 2015 20:33:29 ---
file://localhost/usr/local/hbb-browser/root/directfb-ui/navWindow.html
Unknown thread
Uncaught exception: ReferenceError: Undefined variable: setNavigation

Error thrown at line 1, column 0 in program code:
    setNavigation(false, false);


--- 18 Nov 2015 20:33:29 ---
file://localhost/usr/local/hbb-browser/root/directfb-ui/navWindow.html
Unknown thread
Uncaught exception: ReferenceError: Undefined variable: loadingStart

Error thrown at line 1, column 0 in program code:
    loadingStart();


--- 18 Nov 2015 20:33:29 ---
file://localhost/usr/local/hbb-browser/root/directfb-ui/navWindow.html
Unknown thread
Uncaught exception: ReferenceError: Undefined variable: urlChange

Error thrown at line 1, column 0 in program code:
    urlChange('file://localhost/usr/local/hbb-browser/root/directfb-ui/navWindow.html');


--- 18 Nov 2015 20:33:29 ---
file://localhost/usr/local/hbb-browser/root/directfb-ui/navWindow.html
Unknown thread
Uncaught exception: ReferenceError: Undefined variable: setNavigation

Error thrown at line 1, column 0 in program code:
    setNavigation(false, false);

[inah]

Not working still...

[wortellica]

Not working still...

[Erik Slagter]

In the end VU+ will need to fix this...

[zeros]

Whether a hit is obtained only in PLi, or also to other teams work? If it is clear, what caused it?

[Rob van der Does]

I can't see any obvious reason for HbbTV not working; nothing has been changed in this area.
Neither has anything been changed in ATV & ViX; in both HbbTV still works without issues.

[christophecvr]

The reason is a wrong code in enigma2. From pli4. hbbtv works perfect if this code is reverted. There is nothing wrong with hbbtv of vuplus or vuplus drivers self.

 

Wrong code introduced by commit in enigma2 :

 

on 20151108.

 

A lot off obsciour work is done after that. To let the demuxer work back ok like it did for years enigma2 needs to be patched with patch included here.

 

 

Attached Files

•  revertion-off-e2-demuxer-works.patch   14.75KB   21 downloads

[Erik Slagter]

CVR, I suggest your start your own image, especially for VU+ with ALL workarounds from their own image included to make their stuff work, including the workarounds that make other manufacturers' receivers, that come with drivers that better adhere to the dvbapi standard, fail.

[littlesat]

I'm afraid that VU needs to adapt their hbbtv plugin so it can handle the clean-ups in the demux stuff of enigma2... In fact as far I can see and read from this thread the plugin cannot "catch" the URL of the HbbTV webside anymore... When this "catching" the HbbTV URL is fixed in the plugin everything should be fine... note that "orther" boxes HbbTV implementation do not have this issue.

 

I understand that when reverting some code in E2 does solve the VU issue... but this only indicates we trigger some anomaly in VU's HbbTV plugin and this will not say we should revert that stuff... It think it is better to get VUs HbbTV plugin fixed/adjusted to these changes and hope that it is not driver related...

 

P.S. Can someone try on a VU if openopera can "catch" the HbbTV URL? (sorry I do not have a VU box installed at this moment).

Edited by littlesat, 29 November 2015 - 13:24.

[Erik Slagter]

No littlesat, it has nothing to do with that. The current allocation algorithm is actually almost the same as it was (we reverted most of it, due to the VU+ broken drivers). The allocation scheme now may occasionaly select a descrambling demux for clear content, which in itself is perfectly fine. It would be a waste on a receiver that has some non-descramling demuxers, but those are rare nowadays.

 

The problem has probably started with the update of the drivers that should actually some bugs in this area.

 

So for both sides, please study the commits before you draw conclusions.

[littlesat]

Sorry I did not notice that we had a VU driver upgrade very recent....

[christophecvr]

Sorry I did not notice that we had a VU driver upgrade very recent....

It has nothing to do with any vu+ upgraded driver I even wen't back two years on that fact.

 

It's the  code change for demuxer in enigma2 started on commit :

https://github.com/O...9bb9b8a9c96eff8

 

which cause hbbtv to be out on all vu+ from very old till last drivers. Some service info is required in order to let the hbbtv url's to be used and this is missing now that's all what happens.

 

Why if it's the driver ?? which is showed black on white it's not the case inclusif the extra prove off wortellica that it works if you use hbb tv on a stream. There it's not blocked by the demuxer changes on enigma2.

 

But if like Erik Slagter tells it's really the driver, I suggest that he go to vuplus and give some lessons in how to write a driver to the vuplus team.

[littlesat]

Now you come with a different patch.... But note that with my ET10K & HbbTV no issue.... so still a "sleeping" VU issue I suppose.... But triggered by an e2 improvement...

Edited by littlesat, 29 November 2015 - 14:16.

[christophecvr]

Oh jee ....

 

What was was, It always worked perfect whatever driver off vu

 

What is is It does not work anymore on any vu box unless You apply the brute ruff reversal patch which unfortunately must be done completely. Even if with the changes an improvement ??? .... could be there.

I only noticed downgrading, so I gues that's it's again a et only add.

 

No one thinks that there maybe a very good reason why the vu hbbtv application does not allow the url to open if some service pid info is missing. Licence ??

 

By the way perhaps in the mean time it changed but .... The et used a hacked non official hbbtv and browser before.... maybe still ???

 

That from vu is for vu only and is bind to the box. They do pay licence fees to opera and ...  Does et the same ?

 

What will be can be changed?

 

But if it is a driver error, That's a very cheap explanation and easy to tell since it can't be proved.

 

What is well really proved black on white, hbbtv works perfect if the so called demuxer improvements are reverted. And this for drivers off two years old till the last avbl. This for hbbtv version of more then one year old and opera browser and the very recent once.