169 replies to this topic

[Supra]

Hi,

 

so i recently switched to the latest OpenPLI 6 candidate, and i'm wondering if someone else is having the same error when trying to install HBBTV

 

I'm using the Vu+ solo2.

Collected errors:
* Calculate_dependencies_for: Cannot satisfy the following dependencies for enigma2-plugin-extensions-hbbtv:
* gstreamer (>= 0.10.36.1+git12092+1bcabb9)
* libgstvideo-0.10-0 (>= 0.10.36.1+git10186+bdb3316)
* libjpeg8 (>= 8d)
** opkg_solver_install: cannot install package enigma2-plugin-extensions-hbbtv.

If anyone knows a fix to this, would be very appreciated.

 

Thanks

[adam59]

Https://forums.openpli.org/topic/51773-openpli-60-%C2%BB-release-candidate/page-11

od postu 206

Edited by adam59, 7 July 2017 - 09:28.

[Supra]

Https://forums.openpli.org/topic/51773-openpli-60-%C2%BB-release-candidate/page-11

od postu 206

Ah i see, i guess i'll have to wait for the update.

 

Thanks.

[Erik Slagter]

Which "the update"? We're completely dependend on VU+ for this, so I wouldn't hold my breath, really.

[Rob van der Does]

Which "the update"? We're completely dependend on VU+ for this, so I wouldn't hold my breath, really.

Well, things can't possibly be very complicated: as I said before ViX & ATV are using GSTreamer >0.1 for ages and have no issues with VU's original HbbTV plugin (from the normal VU-source).

[littlesat]

.

Edited by littlesat, 7 July 2017 - 16:04.

[WanWizard]

Also don't forget the required enigma patches. We don't accept BSP's patching our enigma, so we can't work with 15 manufacturers all trying to reinvent the wheel their own way.

 

While from a technical point of view it isn't all that difficult, all you need is a browser extension that provides the required objects and the javascript API interface, and that extension needs to talk to enigma in other to pass commands along, or to fetch information. The browser is open source, so open source this API, and problem solved, for everyone.

[athoik]

So the first step is to provide a browser for all receivers, right?

What browser is that?

How can i compile it?

Then second step is to make a plugin, sure, lets go to step 1 first.

[WanWizard]

There only two options: webkit and chromium. All other ones, including OpenOpera, are licensed.

 

I think the best option at the moment is https://github.com/meta-qt5/meta-qt5, which is being worked on (and is QT/Chromium based afaik).

[athoik]

What recipe provides browser in meta-qt5?

Also do we need directfb in DISTRO_FEATURES?

[WanWizard]

I don't know, I haven't directly followed the development, so I don''t know in what state it is.

[athoik]

With a working browser we can play make tests from here: http://itv.mit-xperts.com/hbbtvtest/

Maybe manufactures can join this effort.

Even open-source existing impementation, that obviously is closed because 3rd party components closed libraries used.

[WanWizard]

Yes, I posted that link before. Apart from the box specific stuff (all video and controls), Chromium handles that website fine.
 
How to create an API extension: https://www.chromium...eating-new-apis
HbbTV 2.0 API: https://www.hbbtv.or...ication_2_0.pdf

And if we can get node.js running on the box, all you need is https://www.npmjs.com/package/hbbtv (courtesy of the Fraunhofer institute)

 

I checked the VU+ chromium tar.gz, but I don't see any HbbTV stuff in there, just the standard browser and some options to make YouTube work.

[athoik]

Node.js recipe exists!

meta-openembedded/meta-oe/recipes-devtools/nodejs/nodejs_4.6.1.bb

Enable on dev?

[WanWizard]

I think, given the size and complexity of this operation, it warants the creation of our first feature branch. So we don't impact dev while this is being looked at, tweaked, etc.

I haven't checked out the node.js solution in detail to see what it exactly does, because somewhere you need an interaction layer between whatever tool is used and enigma.

 

Perhaps first do the research, before we start coding?

[Erik Slagter]

Yes, I agree. Especially as we're in the middle of a release now.

 

Besides that, thumbs up for anyone that makes the effort to try to implement HbbTV in a decent way!

Edited by Erik Slagter, 7 July 2017 - 20:37.

[Dream1975]

As HbbTV is a standard, it is a pity that there is no "general/standardized" implementation and every manufacturer is using it's own methods. Especially the Open Source manufacturers OpenPLi supports should be able to (together) make a general solution/plugin which works for all of them and is standardized (instead off all inventing the wheel seperately from eachother).

[Erik Slagter]

Yes, this is an area where an open source implementation is very well possible, there is no direct hardware interaction that needs driver code.

[Rob van der Does]

As HbbTV is a standard, it is a pity that there is no "general/standardized" implementation and every manufacturer is using it's own methods. Especially the Open Source manufacturers OpenPLi supports should be able to (together) make a general solution/plugin which works for all of them and is standardized (instead off all inventing the wheel seperately from eachother).

 

Yes, this is an area where an open source implementation is very well possible, there is no direct hardware interaction that needs driver code.

 

And that's probably the reason ATV created one HbbTV plugin that runs on all boxes?

[Dream1975]

And that's probably the reason ATV created one HbbTV plugin that runs on all boxes?

 

It would be nice if they open sourced/shared it then, so everybody can use it (just like OpenPLi shares everything with everybody)..

Edited by Dream1975, 8 July 2017 - 09:12.