169 replies to this topic

[macnuts]

@fidelcastro54:

I've tested OpenPLi 6 on my vu+duo2 with aforementioned package, many thanks to athoik. It worked well for me, just make sure you install only that one package, no other hbbtv or opera related packages from the feeds. The only inconvenience was that plugin presented itself in the main menu instead of blue button menu (I could "correct" that in py file easily though).

 

Let me state it plain: hbbtv solution present in OpenPLi 6 feeds does not work.

It can be installed (following wiki hint), it can be started, but nothing is displayed - yet the enigma interface is "frozen" as if hbbtv was started ok. After pressing exit button I could return to enigma; exactly the same way as if hbbtv was working ok. No crash log at that time, nothing in enigma2 log when started in command line.In short: everything works as expected except there is no hbbtv on the screen .

On the other hand, opera browser itself can be stared without problems.

 

Regret to say I had to abandon 'OpenPLi 6 stable' at all as, contrary to its name claim, I had many unexpected reboots with no traces to follow (no crash dumps, dmesg rotated), but this is another story...

Edited by macnuts, 7 November 2017 - 14:55.

[Erik Slagter]

Reboots or complete crashes without green screen cannot be caused by bugs in the image.

[macnuts]

@Erik: I understand your point, still it is hard to argue with the facts: rock solid OpenPLi v4 vs. OpenPLi v6 frequent spontaneous reboots. Something does not fit obviously without apparent culprit.

Edited by macnuts, 7 November 2017 - 21:22.

[Erik Slagter]

The difference may be different versions of the drivers.

[macnuts]

I use the same drivers in OpenPLi v4 as those found in OpenPLi v6. Vu+ drivers I mean.

(I always set new drivers as I still haven't lost the hope that new drivers would improve scrolling without breaking anything else. Never happened yet though.)

Edited by macnuts, 9 November 2017 - 12:35.

[dreamboxco]

Hello,

I have installed. the hbbtv plugin.
after a reboot, the plugin was opened but image content is not played.
How can I create a LOG via OpenPLI?

[Rob van der Does]

I don't understand why HbbTV can't be installed on VU's on PLi 6. After all images like ATV & ViX have no issues here: they are on GStreamer 1.13.0, and use the same drivers as PLi does and the same VU-provided HbbTV plugin.

For me it's the only reason for my VU's not to use PLi atm.

[ricki]

Try Satdream,  works for me.

Edited by ricki, 14 November 2017 - 12:30.

[WanWizard]

I don't understand why HbbTV can't be installed on VU's on PLi 6. After all images like ATV & ViX have no issues here: they are on GStreamer 1.13.0, and use the same drivers as PLi does and the same VU-provided HbbTV plugin.

You should know by now we would prefer good solid solutions instead of implementing workarounds and "hack work". As every manufacturer implements it's own solution, and these solutions bite each other, you can not implement them in a shared build environment without tonnes of "if this box then...". Which we reject out of principle.

 

We're working on a more generic HbbTV and browser implementation, which for a subset of boxes might be available as of 6.1.

[littlesat]

Indeed.... so please 'hold-on' a bit...

[Rob van der Does]

I don't understand why HbbTV can't be installed on VU's on PLi 6. After all images like ATV & ViX have no issues here: they are on GStreamer 1.13.0, and use the same drivers as PLi does and the same VU-provided HbbTV plugin.

You should know by now we would prefer good solid solutions instead of implementing workarounds and "hack work". As every manufacturer implements it's own solution, and these solutions bite each other, you can not implement them in a shared build environment without tonnes of "if this box then...". Which we reject out of principle.

I do know that. And I also know for sure that ViX has no work-around to make VU's HbbTV work.

 

We're working on a more generic HbbTV and browser implementation, which for a subset of boxes might be available as of 6.1.

Ah, OK, that sounds good (although does indeed sound like a work-around a work-around ). I'm looking forward to it!

Edited by Rob van der Does, 14 November 2017 - 16:33.

[WanWizard]

ViX is a VU+ clone, so logical that it works there. It's no comparison.

 

No, it's not a workaround, it is a vendor independent implementation.

[Rob van der Does]

ViX is not a VU clone, far from it. Why do you think that?
ViX is derived fro PLi.

[Rob van der Does]

No, it's not a workaround, it is a vendor independent implementation.

LoL, isn't that a perfect description of 'work-around'
After all you work-around the issue that not all manufacturers have their own (working) HbbTV-plugin.

Edited by Rob van der Does, 15 November 2017 - 05:47.

[WanWizard]

No, that is not the case. A workaround is a solution that doesn't fix the original problem.

 

The original problem here is twofold:

- not every manufacturer has an HbbTV implementation.

- implementations of those that do bite each other in a shared build environment.

 

Solution: do not use any of the manufacturer specific implementations, but use a generic implementation, that runs on any box (it can be implemented on, before I get shot again ).

[WanWizard]

ViX is not a VU clone, far from it. Why do you think that?

 
Well, it was. According to ViX itself (which is fun to read):

 

OpenViX is a community based Opensource project focused on developing user friendly, easy to use Linux Enigma 2 set top box software. OpenViX is created by enthusiasts for enthusiasts.

OpenViX team was formed around July 2010 and originally known as the ViX Team. The Team formed by a small group of enthusiasts based on an idea by AndyBlac to create a user friendly Enigma 2 image for the VU+ Duo. AndyBlac coded the ViX core Enigma 2 that is widely used today.
At the time of forming none of team ever perceived how big or popular the ViX image would become. The original ViX name was the initials of VU+ Image Extreme.

 

As time went on the team started development for other brands, the 2nd brand to be supported was Xtrend, at that point the ViX name changed to Virtuosso Image Xtreme. Today the team is simply referred to as the ViX Team or OpenViX.

 

September 2010 the very 1st VU+ Duo ViX image was released based on VU’s Official Open embedded core, to date the team now supports many brands and over fifty different Broadcom powered Linux Enigma receivers and now uses OE-Alliance open embedded core. OpenViX is a founding member of OE-Alliance.

 

This line

 

... ViX image was released based on VU’s Official Open embedded core ...

 

made me write what I wrote. Now it seems to be OE-A based, which is a very old PLi fork.

 

What really made me lol:

 

AndyBlac coded the ViX core Enigma 2 that is widely used today.

 

He must have a lot of balls (or ignorance) to claim that. Even we don't dare, and PLi members are responsible for a lot more of the Enigma codebase...

[littlesat]

I'm afraid VIX and VTI were "mixed" here.... VTI is a clone of de manufacturer image + a bit extra... VIX is a split-off from OpenPLi based on oe-a... also a split-off from openpli.

[Rob van der Does]

ViX is not a VU clone, far from it. Why do you think that?

 
Well, it was. According to ViX itself (which is fun to read):
 

OpenViX is a community based Opensource project focused on developing user friendly, easy to use Linux Enigma 2 set top box software. OpenViX is created by enthusiasts for enthusiasts.
OpenViX team was formed around July 2010 and originally known as the ViX Team. The Team formed by a small group of enthusiasts based on an idea by AndyBlac to create a user friendly Enigma 2 image for the VU+ Duo. AndyBlac coded the ViX core Enigma 2 that is widely used today.
At the time of forming none of team ever perceived how big or popular the ViX image would become. The original ViX name was the initials of VU+ Image Extreme.
 
As time went on the team started development for other brands, the 2nd brand to be supported was Xtrend, at that point the ViX name changed to Virtuosso Image Xtreme. Today the team is simply referred to as the ViX Team or OpenViX.
 
September 2010 the very 1st VU+ Duo ViX image was released based on VU’s Official Open embedded core, to date the team now supports many brands and over fifty different Broadcom powered Linux Enigma receivers and now uses OE-Alliance open embedded core. OpenViX is a founding member of OE-Alliance.

 
This line
 

... ViX image was released based on VU’s Official Open embedded core ...

 
made me write what I wrote. Now it seems to be OE-A based, which is a very old PLi fork.
 
What really made me lol:
 

AndyBlac coded the ViX core Enigma 2 that is widely used today.

 
He must have a lot of balls (or ignorance) to claim that. Even we don't dare, and PLi members are responsible for a lot more of the Enigma codebase...

You refer to an ancient quote; that was the very first ViX-image. Shortly after that they changed to PLi, and some time after that they founded the OE-A, as a common basis for some 15 image building teams.

And the by then so-called 'ViX-core' was solely a plugin.

You see how easy/dangerous it is to pull text out of context, especially if the text is very old and you are not even aware of the context.

Edited by Rob van der Does, 15 November 2017 - 18:21.

[WanWizard]

Don't blame me, I just read what the team wrote. If that is not or no longer true, don't shoot the messenger.

[Rob van der Does]

Let's not get distracted from the good news about the generic PLi HbbTV-plugin!