Login at Kodi Home

yanniks · 2014-03-25, 21:43

I see. Does somebody care about something like that? I think that will be important in the future and many people (particularly from Germany) are interested in that. Otherwise the TV function of XBMC will be more and more unimportant.

**sarbes** · 2014-03-29, 17:06

(2014-03-25, 21:43)yanniks Wrote: I see. Does somebody care about something like that? I think that will be important in the future and many people (particularly from Germany) are interested in that. Otherwise the TV function of XBMC will be more and more unimportant.

I don't think so. We already have a system far better than HbbTV. The existing Add-ons cover all the VOD content, while HbbTV is just a small subset. It also unifies all sources under one user interface.

Adding a HTML engine is not necessary in my opinion. Porting it to all platforms will be impossible or at least very time consuming. The only thing that XBMC lacks of is the link between the TV part and the Add-ons. Many German broadcasters have an extensive API, far better than what HbbTV could deliver. Cross searching between shows from the EPG and online content is not a problem. This should be trivial to add compared to a full blown rendering engine.

I would love to implement such system from the Add-on side. I have explored and documented some parts of the ARD (German broadcaster) API. If anyone wants some information about this, feel free to pm me.

giaur · (This post was last modified: 2014-03-29, 17:43 by giaur.)

Quote:I don't think so. We already have a system far better than HbbTV. The existing Add-ons cover all the VOD content, while HbbTV is just a small subset. It also unifies all sources under one user interface.

Even if you have better system than hbbtv, it's not the point of our interests here. We are asking for access to hbbtv content served by broadcesters. There are also things better than dvb-t epg, teletext already available but it doesn't mean that we should not ask for support for them.

CSylvain · (This post was last modified: 2014-03-29, 23:55 by CSylvain.)

I think you did not quite look at the possibilities of HbbTV 1.5, it allows you to interact with the web TV content (DVB-S2/T2/C) on a single page HTML5 .
For me XBMC has years of delays on the TV connected, HbbTV is based on the WebKit, and change many things for which to be interactive with models of video processors , for example resize screen and move in an area that will display on a web page , or as mute TV when you start a video on the web.
Perfect for easily creating applications HTML/PHP.
Unfortunately HbbTV decide to privatize the project and provides the source code if you are a member and you pay 8000 euros per year.
https://www.hbbtv.org/pages/hbbtv_associ...ership.php

Anyway, I work on my side on a model of Broadcom with the manufacturer AirDigital which ensure compatibility with OperaTV I get soon SDK of 1300MHz processor dual cores which I hope will include bookstores "OpenGL ES".

**sarbes** · 2014-03-31, 16:35

I see HbbTV as a collection of random user interfaces, each with its own design, menus and shortcuts. This is a huge step back from the XBMC gui.

I can see why device manufactures want to establish such a system: to cut costs in maintanance and development. Old products will always be up to date (as long it supports the current standard). Broadcasters can archive a wider coverage. XBMC however, is based around a huge community, which develops Add-ons for almost every source available.

HbbTV has serveral limitations:
- VOD is only a subset of the online content
- opens a huge attack surface
- needs to be maintananced every release
- needs short release cycles because of webkit hotfixes
- adds excessive user tracking
- look and feel is different for every app

There are some shortcomings within XBMC when it comes to Live TV/VOD integration, but these can be overcome rather easily, compared to the work required adding HbbTV. I don't see any reason why it should be added.

CSylvain · 2014-03-31, 19:06

I'm looking for such a solution does not need to develop modules in Python and XML, I 'm not comfortable with this language debugger, while on the web, updating enough to test the code.
Imagine also the opening that you can give to developers who are more comfortable with web code such as PHP.
I totally agree on the opinion to change the GUI, it will actually be a disaster on the optimization part, as well as video player.
By cons I see it more as an additional option to create applications HTML5 as already Boxee.
I spent some months to design a HbbTV 1.1, and it is possible with PyQt5.QtWebKit (more stable and faster than GTK), I solved the same attention transparent background with a light composer (Compton).

If after an expert in WebKit is motivated to reproduce the library OIPF for XBMC (dvb://), then this is a win to create something similar, or even better than HbbTV 1.5. Wink

**sarbes** · 2014-03-31, 20:40

(2014-03-31, 19:06)CSylvain Wrote: I'm looking for such a solution does not need to develop modules in Python and XML, I 'm not comfortable with this language debugger, while on the web, updating enough to test the code.
Imagine also the opening that you can give to developers who are more comfortable with web code such as PHP.

There is almost no need for that if you want to code the "server side" of a normal XBMC Add-on. The client side should be just a few lines of code - I'm sure the community would help. However, custom interfaces are a bit more complicated.

RockerC · 2014-04-01, 17:13

(2014-03-31, 19:06)CSylvain Wrote: I spent some months to design a HbbTV 1.1, and it is possible with PyQt5.QtWebKit (more stable and faster than GTK), I solved the same attention transparent background with a light composer (Compton).

QtWebKit integration into XBMC have been discussed before and is probably not an acceptable solution, just read through these previous threads

http://forum.xbmc.org/showthread.php?tid=55093
http://forum.xbmc.org/showthread.php?tid=127847
http://forum.xbmc.org/showthread.php?tid=89845
http://forum.xbmc.org/showthread.php?tid=25

They all suggest that you would instead have to look into 'pure' non-Qt based WebKit since QtWebKit and Qt in general is too bloated to be embedded into XBMC.

Even better would be to instead use WebKit2 https://trac.webkit.org/wiki/WebKit2 or alternative the new Blink from Chromium http://www.chromium.org/blink

Or perhaps some other modern layout engine that have an even smaller footprint for embedding?

WebKit2 supports a split process model "where where the web content lives in a separate process from the application UI" so sounds well suited for XBMC.

Right now it does look like WebKit2 would be a really good option since it is also at least somewhat backwards compatible with the original WebKit

CSylvain · (This post was last modified: 2014-04-26, 18:16 by CSylvain.)

There are new at prismcube, they begin to write the status changes on the side of XBMC and the Player :
http://www.prismcube-community.net/board...-7-0.1000/
http://update.prismcube.com/git/xbmc-fro...2798a59b09

A good start to approach other manufacturers !

EDIT :
It's seriously, but quite disappointed with the choice.
They use a Webkit I have no idea if he can read urls like this : "dvb://"
However I did not understand the choice of launcher which is GTK+, slower than QT !
http://update.prismcube.com/git/meta-elm...0de58eb0ab

EDIT 2 :
OIPF is included in the plugin libhbbtvplugin.so.
Functions for url "dvb://" are included in the plugin !
http://update.prismcube.com/git/meta-elm...1aaadaf7c6

Now see if it can be used on another box ARM or only processor Apollo Elmo / Trident.
Regarding the HbbTvProc.ko module, it will be very easy to reproduce, because it allows just stored in memory statutes that made XBMC.

I feel like I'm going to order me a Amlogic-MX / DVB-T2.

EDIT 3 :
At first glance it may work on other box ARM :

Code:
; Input MD5   : 51B13D8A771046C0B1C9420F44BDEBC6

; Input CRC32 : DE5DA062

; File Name   : libhbbtvplugin.so

; Format      : ELF for ARM (Shared object)

; Needed Library 'libixml.so.2'

; Needed Library 'librt.so.1'

; Needed Library 'libstdc++.so.6'

; Needed Library 'libm.so.6'

; Needed Library 'libgcc_s.so.1'

; Needed Library 'libc.so.6'

; Needed Library 'ld-linux.so.3'

;

; EABI version: 5

;

; Source File : 'SysChannelMgr.cpp'

; Source File : 'CmdParser.cpp'

; Source File : 'CmdHistory.cpp'

; Source File : 'PluginObject.cpp'

; Source File : 'PluginArrayObject.cpp'

; Source File : 'MimeHandler.cpp'

; Source File : 'PluginInstance.cpp'

; Source File : 'PluginStreamDownloader.cpp'

; Source File : 'PluginProgram.cpp'

; Source File : 'OipfObjectFactory.cpp'

; Source File : 'OipfApplicationManager.cpp'

; Source File : 'OipfApplication.cpp'

; Source File : 'OipfConfiguration.cpp'

; Source File : 'OipfConfigurationImpl.cpp'

; Source File : 'OipfVideobroadcast.cpp'

; Source File : 'OipfVideoMpeg.cpp'

; Source File : 'OipfApplicationPrivateData.cpp'

; Source File : 'OipfAVComponent.cpp'

; Source File : 'OipfChannelConfig.cpp'

; Source File : 'OipfChannelList.cpp'

; Source File : 'OipfChannel.cpp'

; Source File : 'OipfDownload.cpp'

; Source File : 'OipfDownloadCollection.cpp'

; Source File : 'OipfKeyset.cpp'

; Source File : 'OipfDRMControlInfoCollection.cpp'

; Source File : 'OipfDRMControlInformation.cpp'

; Source File : 'OipfCapabilities.cpp'

; Source File : 'OipfDownloadManager.cpp'

; Source File : 'OipfDownloadTrigger.cpp'

; Source File : 'OipfDrmAgent.cpp'

; Source File : 'OipfParentalControlManager.cpp'

; Source File : 'OipfRecordingScheduler.cpp'

; Source File : 'OipfParentalRating.cpp'

; Source File : 'OipfParentalRatingCollection.cpp'

; Source File : 'OipfParentalRatingScheme.cpp'

; Source File : 'OipfParentalRatingSchemeCollection.cpp'

; Source File : 'OipfProgramme.cpp'

; Source File : 'OipfProgrammeCollection.cpp'

; Source File : 'OipfRecording.cpp'

; Source File : 'OipfRecordingCollection.cpp'

; Source File : 'OipfScheduledRecording.cpp'

; Source File : 'OipfScheduledRecordingCollection.cpp'

; Source File : 'OipfStreamEvent.cpp'

; Source File : 'MSMediaPlayer.cpp'

; Source File : 'SysHelperFuncs.cpp'

; Source File : 'SysEventHandler.cpp'

; Source File : 'SITable.cpp'

; Source File : 'SIDescriptorParser.cpp'

; Source File : 'SIDescriptor.cpp'

; Source File : 'DVBAppDescriptorParser.cpp'

; Source File : 'GraphicsConstraintDescriptor.cpp'

; Source File : 'ApplicationIconDescriptor.cpp'

; Source File : 'ApplicationRecordingDescriptor.cpp'

; Source File : 'ExtAppAuthorizationDescriptor.cpp'

; Source File : 'TransportProtocolDescriptor.cpp'

; Source File : 'ApplicationDescriptor.cpp'

; Source File : 'ApplicationNameDescriptor.cpp'

; Source File : 'AITTable.cpp'

; Source File : 'dvbApplication.cpp'

; Source File : 'dvbApplicationMgr.cpp'

; Source File : 'dvbURL.cpp'

; Source File : 'XMLDocument.cpp'

; Source File : 'Mutex.cpp'

; Source File : 'Thread.cpp'

; Source File : 'ThreadList.cpp'

; Source File : 'CondVar.cpp'

; Source File : 'IPCChannelMgr.cpp'

; Source File : 'IPCParam.cpp'

; Source File : 'IPCSocketChannel.cpp'

; Source File : 'IPCSocket.cpp'

; Source File : 'IPCTCPSocket.cpp'

; Source File : 'IPCUnixSocket.cpp'

; Source File : 'CmdMgr.cpp'

; Source File : 'PluginMain.cpp'

; Source File : 'HbbtvPlugin.cpp'

; Source File : 'SystemFunc_IPC.cpp'

; Source File : 'crtstuff.c'

; Source File : 'SysPluginFuncs.cpp'

; Source File : 'ISO639Language.cpp'

; Source File : 'XMLAttr.cpp'

; Source File : 'XMLCDataSection.cpp'

; Source File : 'XMLElement.cpp'

; Source File : 'XMLNode.cpp'

; Source File : 'XMLNodeList.cpp'

; Source File : 'Logger.cpp'

; Source File : 'CmdListMgr.cpp'

; Source File : 'SymListMgr.cpp'

; Source File : 'CmdValue.cpp'

; Source File : 'Sleep.c'

; Source File : 'linux-atomic.c'

; Source File : 'crtstuff.c'

All requests go through port 9000, remains to be seen who receives these requests and executed. Huh

I checked the modules DVB of Prismcube, and there's nothing this side.

bam80 · 2019-01-28, 16:44

Any news? At least on WebKit integration..

comanchero · 2021-05-26, 13:53

Hi, everyone!

It seems that Kodi developers are (obviously) living in non-HbbTV regions. They thus don't understand the advantage of merging Live TV broadcasts with the full-duplex On-Demand on-line services.

Let's tell 'em more:
https://www.hbbtv.org/
https://en.wikipedia.org/wiki/Hybrid_Bro...oadband_TV

Even better, they may (hopefully) get to understand the concept from demonstrations:
https://www.youtube.com/results?search_query=HbbTV

HbbTV brings a lot, e.g.:
- advanced EPG with trailers
- direct access to broadcaster's archive
- broadcaster's news feed
- instant updates
etc.

The importance to the European users is crucial - at this stage Kodi is not an option to us, it in fact is unusable; we are stuck with Android TV or DVBViewer on Windows. Pity.

So, what's gonna be next? THANKS for understanding. Wink

Best!