40 replies to this topic

[rantanplan]

ARM need Patch.

It would be interesting to know whether mipsel is still running properly.
As I understand it, arm build needs a patch to be applied via glibc.

[betacentauri]

There is no Widewine for Mipsel.

[doglover]

On mipsel it never worked, because of the missing Widevine.

[rantanplan]

Thanks beta ;-)
I hadn't even considered that.
So on the one hand there would be the question make this widevine possibel for mips and then apply the patch.
That would be a lot of  work.
Is it worth it?

[betacentauri]

It doesn’t work on mipsel boxes as there is no mipsel widevine library available. Not available at all. So, it doesn’t make sense to add patches to mipsel boxes for that. Well, you can do it if it makes it easier for you (e.g. one patch for all boxes), but it will never work.

Edited by betacentauri, 14 September 2021 - 12:59.

[A.A.]

My 2 cents here: let OpenPLi provide kodi and the inputstream helpers.

The whole kodi-plugins thing is out of our control.

 

A.A.

[doglover]

Is there an image out there which supports Widevine on ARM STB's?

[littlesat]

…

Edited by littlesat, 14 September 2021 - 18:54.

[rantanplan]

Is there an image out there which supports Widevine on ARM STB's?

Wait for PN
ImageBuild takes a lot of time
MultiboxSE Image?
 

[doglover]

MultiboxSE Image?

 

 

 

Yes.  For me that is....
 

 

[doglover]

Today flashed develop 21/9/2021 on the Maytec-MultiboxSE

Kodi works again with DRM channels (Widevine again supported)

 

Only the audio problem remains.

 

When I start Kodi on the Multibox the audio is very faint even with the volume turned at maximum.

In order to increase the volume, I have to crank up the volume in enigma2 to a maximum.

Then start Kodi.

Now in Kodi I can set the volume to a desired level.

But then when I return to enigma2 the speakers are at maximum, and you run out the house of the noise.  So set the volume again to normal.

It is workable, but this could be better.

Edited by doglover, 22 September 2021 - 06:47.

[doglover]

Install errors:

Configuring libevdupdate-alternatives: Linking /usr/bin/ndg_httpclient to /usr/bin/ndg_httpclient.python-ndg-httpsclient
Assertion failure: 0 == flags, at ../../../../nspr-4.21/nspr/pr/src/pthreads/ptio.c:3418
/usr/bin/signlibs.sh: line 14:  2549 Aborted                 $SIGN_BINARY -i $FN
Assertion failure: 0 == flags, at ../../../../nspr-4.21/nspr/pr/src/pthreads/ptio.c:3418
/usr/bin/signlibs.sh: line 14:  2552 Aborted                 $SIGN_BINARY -i $FN
Assertion failure: 0 == flags, at ../../../../nspr-4.21/nspr/pr/src/pthreads/ptio.c:3418
/usr/bin/signlibs.sh: line 14:  2555 Aborted                 $SIGN_BINARY -i $FN
Collected errors:
* pkg_run_script: package "nss" postinst script returned status 134.
* opkg_configure: nss.postinst returned 134.
ev.

Configuring enigma2-plugin-extensions-kodi.
An error occurred during installing enigma2-plugin-extensions-kodi - Please try again later
Assertion failure: 0 == flags, at ../../../../nspr-4.21/nspr/pr/src/pthreads/ptio.c:3418
/usr/bin/signlibs.sh: line 14:  2574 Aborted                 $SIGN_BINARY -i $FN
Assertion failure: 0 == flags, at ../../../../nspr-4.21/nspr/pr/src/pthreads/ptio.c:3418
/usr/bin/signlibs.sh: line 14:  2577 Aborted                 $SIGN_BINARY -i $FN
Assertion failure: 0 == flags, at ../../../../nspr-4.21/nspr/pr/src/pthreads/ptio.c:3418
/usr/bin/signlibs.sh: line 14:  2580 Aborted                 $SIGN_BINARY -i $FN
Collected errors:
* pkg_run_script: package "nss" postinst script returned status 134.
* opkg_configure: nss.postinst returned 134.

Configuring enigma2-plugin-extensions-tmbd.
Configuring nss.
An error occurred during installing enigma2-plugin-extensions-tmbd - Please try again later
Assertion failure: 0 == flags, at ../../../../nspr-4.21/nspr/pr/src/pthreads/ptio.c:3418
/usr/bin/signlibs.sh: line 14:  2628 Aborted                 $SIGN_BINARY -i $FN
Assertion failure: 0 == flags, at ../../../../nspr-4.21/nspr/pr/src/pthreads/ptio.c:3418
/usr/bin/signlibs.sh: line 14:  2631 Aborted                 $SIGN_BINARY -i $FN
Assertion failure: 0 == flags, at ../../../../nspr-4.21/nspr/pr/src/pthreads/ptio.c:3418
/usr/bin/signlibs.sh: line 14:  2634 Aborted                 $SIGN_BINARY -i $FN
Collected errors:
* pkg_run_script: package "nss" postinst script returned status 134.
* opkg_configure: nss.postinst returned 134.

Configuring enigma2-plugin-systemplugins-serviceapp.
Configuring nss.
An error occurred during installing enigma2-plugin-systemplugins-serviceapp - Please try again later
Assertion failure: 0 == flags, at ../../../../nspr-4.21/nspr/pr/src/pthreads/ptio.c:3418
/usr/bin/signlibs.sh: line 14:  2647 Aborted                 $SIGN_BINARY -i $FN
Assertion failure: 0 == flags, at ../../../../nspr-4.21/nspr/pr/src/pthreads/ptio.c:3418
/usr/bin/signlibs.sh: line 14:  2650 Aborted                 $SIGN_BINARY -i $FN
Assertion failure: 0 == flags, at ../../../../nspr-4.21/nspr/pr/src/pthreads/ptio.c:3418
/usr/bin/signlibs.sh: line 14:  2653 Aborted                 $SIGN_BINARY -i $FN
Collected errors:
* pkg_run_script: package "nss" postinst script returned status 134.
* opkg_configure: nss.postinst returned 134.

They all look related.

Edited by doglover, 22 September 2021 - 07:27.

[rantanplan]

Hisi-Box

I can only strongly recommend not to install the service app on hisi-box.
This then installs the exteplayer3 afterwards.
Then you have 2 libeplayer in the system that lead to errors.
Clearing the system from this installation isn't that easy either.
Carefully uninstalling both is not enough. You still have to re-flash afterwards.

Actually, the exteplayer3 shouldn't bring any advantages.
You can also teach the Hisiplayer (libeplayer3) everything.

[doglover]

Agreed that you can teach the hisilplayer everything.

 

Although I have a couple of remarks:

 

1. The serviceapp is not the cause of the above dmentioned errors.  It is the last installed, and 3 other plug-ins have the same error before the serviceapp.

 

2. The hisilplayer does indeed plays also the streams i want (regional Flemish channels):

#SERVICE 5002:0:1:2:0:32:0:0:0:3:http%3a//player-api.new.livestream.com/accounts/27755193/events/8452381/live.secure.m3u8:atv
#DESCRIPTION atv
#SERVICE 5002:0:1:1:0:32:0:0:0:3:http%3a//api.new.livestream.com/accounts/27755193/events/8452383/live.secure.m3u8:TV Limburg
#DESCRIPTION TV Limburg
#SERVICE 5002:0:1:3:0:32:0:0:0:3:http%3a//api.new.livestream.com/accounts/27755193/events/8511193/live.secure.m3u8:TV Oost
#DESCRIPTION TV Oost

When changing 5002 into 4097, the channels play in the HiSilplayers.

Although only in 630x360.

When using the serviceapp they can be switched to 1280x720.

 

3. This player is getting its bouquet files from a mipsel receiver (Mutant HD2400).

There is no connection to the sat.  Only via the fallback tuner method.

And the HD2400 only plays these HLS streams with the exteplayer3 (serviceapp).

So I have to give these streams a 5002 service ref.  ( I do not want to use the exteplayer3 for everything)

The bouquet files are copied automatically to the Maxytec.

And if I do not install the serviceapp on the Maxytec, these channels are listed as n/a

[WanWizard]

These nss issues have been reported before, but no clue what is causing them. Every now and then they pop up with someone...

[rantanplan]

The lists should not be changed with respect to 4097 as the standard.
But this is done everywhere.
With the change you make yourself dependent on the view in the bouquet of the existence of the service app.
I think it's a mistake to enter something other than 4097.
That the Hisplayer intercepts the stream with a low data rate is negotiated automatically.
Let's see if we can patch something.

[doglover]

This does not play on the Mutant HD2400 (mipsel)

#SERVICE 4097:0:1:2:0:32:0:0:0:3:http%3a//player-api.new.livestream.com/accounts/27755193/events/8452381/live.secure.m3u8:atv

except when setting in the serviceapp the exteplayer3 as standard player.

But this i has serious consequences for other things.

Several channels do not play normally anymore.  A bunch of mkv files only play with stutters etc...

[betacentauri]

I just found out (not regarding this specific stream) that the in e2 integrated gstreamer is quite bad for m3u8 if the server uses cookies or checks user-agent. Because we set special timeout, session data like the user-agent and cookies are not handled properly.

Edited by betacentauri, 23 September 2021 - 14:09.

[rantanplan]

I already understand the 'Problem'.
Conversely, the enigma2 system only knows how to handle 4097.
So these are automatically displayed in the bouquet.
You could possibly symbolize that other service references are always displayed there, even if they are not available via the service app.

One is the handling and better playback options on the part of Mediaframwork ffmpeg. The other is the bouquet representation.

[doglover]

Only the audio problem remains.

 

When I start Kodi on the Multibox the audio is very faint even with the volume turned at maximum.

In order to increase the volume, I have to crank up the volume in enigma2 to a maximum.

Then start Kodi.

Now in Kodi I can set the volume to a desired level.

But then when I return to enigma2 the speakers are at maximum, and you run out the house of the noise.  So set the volume again to normal.

It is workable, but this could be better.

 

 

 

Is this audio problem solved?

 

I have updated the receiver yeserday but no change yet on this.

Or do I have to reflash?

Edited by doglover, 16 October 2021 - 13:18.