985 replies to this topic

[Pr2]

Hi,

 

Change your http stream from SERVICE 1: to 4097:, define :3 at the end to enable buffering. Use ServiceApp and choose extexplayer3 as player.

 

Pr2

[betacentauri]

Or the other way around. Use 1: instead of 4097:.
But we don’t know how the iptv streams are received. Via plugin or not and so on ...

[ian1095]

What causes this error when trying to Record from my Bouquet Lists when using Serviceapp and Exteplayer3 ?

 

Pic Attached with my TvHeadend details edited out obviously.

Attached Files

•  5002_0_1_0_0_0_0_0_0_3_20181020163852.jpg   75.44KB   15 downloads

[tigrousad]

Iptvplayer for android ?

[thawtes]

hi, @samsamsam how to use " [-f ffopt=ffval] any other ffmpeg option "

 

sample

 

exteplayer3 filePath -a 0 -n 0 -f "-c:v CodecName" playbackUri

or

exteplayer3 filePath -a 0 -n 0 -f "-vcodec=CodecName" playbackUri

 

not work!

 

 

writing options available in ffmpeg ; sample  -c:v copy -b:v 500k etc...

 

how to write this parameter in exteplayer3 ?

[gorski]

Anyone else has this problem with exteplayer3 but external gstplayer works, in any other image?

Attached Files

•  E2iPlayer error.jpg   14.48KB   9 downloads

Edited by gorski, 4 November 2018 - 05:32.

[kookesam]

hello install ffmpeg libraries :  http://iptvplayer.vl.../ffinstall.html .

[gorski]

They are present but...

[rantanplan]

which image?
which ffmpeg version?
Error in ServiceApp or in the iptvplayer?

[gorski]

Sorry, the owners of this forum are a little... nervous about the mage, so nomina sunt odiosa...

 

And it is actually the wrong thread - it's in E2iPlayer...

 

This is present in the image:

~ Kernel 4.4.35 (00:04:40). Have a N.I.C.E. day on zgemmah9s ~

root@zgemmah9s:~# ffmpeg -version
ffmpeg version 4.0.2 Copyright (c) 2000-2018 the FFmpeg developers
built with gcc 8.2.0 (GCC)
configuration: --disable-stripping --enable-pic --enable-shared --enable-pthreads --disable-libxcb --disable-libxcb-shm --disable-libxcb-xfixes --disable-libxcb-shape --cross-prefix=arm-oe-linux-gnueabi- --ld='arm-oe-linux-gnueabi-gcc -march=armv7ve -mfpu=neon-vfpv4 -mfloat-abi=hard -mcpu=cortex-a15 --sysroot=/home/tom/Awork/oea43/builds/********/release/zgemmah7/tmp/work/cortexa15hf-neon-vfpv4-oe-linux-gnueabi/ffmpeg/4.0.2-r0/recipe-sysroot' --cc='arm-oe-linux-gnueabi-gcc -march=armv7ve -mfpu=neon-vfpv4 -mfloat-abi=hard -mcpu=cortex-a15 --sysroot=/home/tom/Awork/oea43/builds/********/release/zgemmah7/tmp/work/cortexa15hf-neon-vfpv4-oe-linux-gnueabi/ffmpeg/4.0.2-r0/recipe-sysroot' --cxx='arm-oe-linux-gnueabi-g++ -march=armv7ve -mfpu=neon-vfpv4 -mfloat-abi=hard -mcpu=cortex-a15 --sysroot=/home/tom/Awork/oea43/builds/*******/release/zgemmah7/tmp/work/cortexa15hf-neon-vfpv4-oe-linux-gnueabi/ffmpeg/4.0.2-r0/recipe-sysroot' --arch=arm --target-os=linux --enable-cross-compile --extra-cflags=' -Os -pipe -g -feliminate-unused-debug-types -fdebug-prefix-map=/home/tom/Awork/oea43/builds/********/release/zgemmah7/tmp/work/cortexa15hf-neon-vfpv4-oe-linux-gnueabi/ffmpeg/4.0.2-r0=/usr/src/debug/ffmpeg/4.0.2-r0 -fdebug-prefix-map=/home/tom/Awork/oea43/builds/*******/release/zgemmah7/tmp/work/cortexa15hf-neon-vfpv4-oe-linux-gnueabi/ffmpeg/4.0.2-r0/recipe-sysroot= -fdebug-prefix-map=/home/tom/Awork/oea43/builds/********/release/zgemmah7/tmp/work/cortexa15hf-neon-vfpv4-oe-linux-gnueabi/ffmpeg/4.0.2-r0/recipe-sysroot-native= -march=armv7ve -mfpu=neon-vfpv4 -mfloat-abi=hard -mcpu=cortex-a15 --sysroot=/home/tom/Awork/oea43/builds/**********/release/zgemmah7/tmp/work/cortexa15hf-neon-vfpv4-oe-linux-gnueabi/ffmpeg/4.0.2-r0/recipe-sysroot' --extra-ldflags='-Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed' --sysroot=/home/tom/Awork/oea43/builds/********/release/zgemmah7/tmp/work/cortexa15hf-neon-vfpv4-oe-linux-gnueabi/ffmpeg/4.0.2-r0/recipe-sysroot --enable-hardcoded-tables --libdir=/usr/lib --shlibdir=/usr/lib --datadir=/usr/share/ffmpeg --disable-mipsdsp --disable-mipsdspr2 --cpu=cortex-a15 --pkg-config=pkg-config --enable-avcodec --enable-avdevice --enable-avfilter --enable-avformat --disable-avresample --enable-bzlib --enable-gpl --disable-libgsm --disable-indev=jack --disable-libvorbis --enable-lzma --disable-libmp3lame --disable-openssl --enable-postproc --disable-sdl2 --disable-libspeex --enable-swresample --enable-swscale --enable-libtheora --disable-vaapi --disable-vdpau --disable-libvpx --enable-libx264 --disable-outdev=xv
libavutil      56. 14.100 / 56. 14.100
libavcodec     58. 18.100 / 58. 18.100
libavformat    58. 12.100 / 58. 12.100
libavdevice    58.  3.100 / 58.  3.100
libavfilter     7. 16.100 /  7. 16.100
libswscale      5.  1.100 /  5.  1.100
libswresample   3.  1.100 /  3.  1.100
libpostproc    55.  1.100 / 55.  1.100

I am just asking if somebody noticed it in any other image, like OpenPLi, OpenATV, OpenViX etc. Just curious, that's all...

[WanWizard]

Not sure what you are on about, but we at not nervous about anything.

We are only VERY clear about any activity that is deemed illegal in the EU: we don't want any of that on this forum.

 

To use an analogy, you can talk about hammers and baseball bats all you want, but don't ask how to use one to murder someone...

[samsamsam]

@gorski

 

They are present but...

 

 

You have version 4.X of the ffmpeg libraries not supported at now.

 

As @kookesam you should install valid version according to http://iptvplayer.vl.../ffinstall.html

 

 

I am just asking if somebody noticed it in any other image, like OpenPLi, OpenATV, OpenViX etc. Just curious, that's all... 

 

No if they installed valid version of ffmpeg libraries.

 

When you will use install command mentioned here:

http://iptvplayer.vl.../ffinstall.html

libs will be placed in /iptvplayer_rootfs/ so they will not overwrite system one.

 

But it does not matter. Because gstplayer nor exteplayer3 will not work correctly with zgemma h9s and probably also on any other Enigma2 STB based on the HiSilicon sock.

Because of problem with drivers they wrote own closed player with small open part called hsiliconservice.

hsiliconservice work OK for local media but it is problematic for online playback (it's practically useless for E2iPlayer purpose).

 

For more info read issue created by me:

https://github.com/z...zgemma/issues/7

 

Unfortunately playback via /dev/dvb/adapter0/audio0 and /dev/dvb/adapter0/video0 interfaces works very, very bad on H9.

Many files does not work at all. For example it is not possible to play H.265 via /dev/dvb/adapter0/video0

Even if some codec works like H264 it works very bad. There is many macroblocks and so on. Play/Pause works very badly.

There is no such problem when using servicehisilicon but this cause many disadvantage.

Normally in the Enigma2 media player have two parts:

1. First part - OpenSource part which is responsible to receive data, demultiplexing them, format AUDIO/VIDEO frame adding PES header and codec specific data and injecting this frame to /dev/dvb/adapter0/video0 and /dev/dvb/adapter0/audio0.

2. Second part - closed source, driver part, provide interface for /dev/dvb/adapter0/video0 and /dev/dvb/adapter0/audio0

But /dev/dvb/adapter0/video0 and /dev/dvb/adapter0/audio0 in the H9 are bad.
So, they create separate media player called servicehisilicon, this player do NOT use /dev/dvb/adapter0/video0 and /dev/dvb/adapter0/audio0 interfaces.
So, there is no OpenSource part which will allow to add new format, protocol and so on.

All is closed. So, only set-top-box driver provider can made fix or add support for example for some streaming protocols.

In such way this set-top-box is unusable for IPTV unless /dev/dvb/adapter0/audio0
and /dev/dvb/adapter0/video0 will be fixed.

This is very bad news because hardware is very good, but drivers unfortunately are not.

Edited by samsamsam, 5 November 2018 - 11:47.

[gorski]

WW, except that in your relaxedness some of you delete messages mentioning other images, especially if in such messages I state my opinion (to which we are all entitled) and I say I favour them in some machines, for various reasons...

 

It doesn't help I am not a fan-boy, tribally bent, saying I prefer OpenPLi images for various other machines for xyz reasons...

 

And this happens regularly - deleting my messages - "on behalf od some members of OpenPLi"...

 

C'mon...

[gorski]

 

@gorski

 

They are present but...

 

 

You have version 4.X of the ffmpeg libraries not supported at now.

 

As @kookesam you should install valid version according to http://iptvplayer.vl.../ffinstall.html

 

 

I am just asking if somebody noticed it in any other image, like OpenPLi, OpenATV, OpenViX etc. Just curious, that's all... 

 

No if they installed valid version of ffmpeg libraries.

 

When you will use install command mentioned here:

http://iptvplayer.vl.../ffinstall.html

libs will be placed in /iptvplayer_rootfs/ so they will not overwrite system one.

 

But it does not matter. Because gstplayer nor exteplayer3 will not work correctly with zgemma h9s and probably also on any other Enigma2 STB based on the HiSilicon sock.

Because of problem with drivers they wrote own closed player with small open part called hsiliconservice.

hsiliconservice work OK for local media but it is problematic for online playback (it's practically useless for E2iPlayer purpose).

 

For more info read issue created by me:

https://github.com/z...zgemma/issues/7

 

Unfortunately playback via /dev/dvb/adapter0/audio0 and /dev/dvb/adapter0/video0 interfaces works very, very bad on H9.

Many files does not work at all. For example it is not possible to play H.265 via /dev/dvb/adapter0/video0

Even if some codec works like H264 it works very bad. There is many macroblocks and so on. Play/Pause works very badly.

There is no such problem when using servicehisilicon but this cause many disadvantage.

Normally in the Enigma2 media player have two parts:

1. First part - OpenSource part which is responsible to receive data, demultiplexing them, format AUDIO/VIDEO frame adding PES header and codec specific data and injecting this frame to /dev/dvb/adapter0/video0 and /dev/dvb/adapter0/audio0.

2. Second part - closed source, driver part, provide interface for /dev/dvb/adapter0/video0 and /dev/dvb/adapter0/audio0

But /dev/dvb/adapter0/video0 and /dev/dvb/adapter0/audio0 in the H9 are bad.
So, they create separate media player called servicehisilicon, this player do NOT use /dev/dvb/adapter0/video0 and /dev/dvb/adapter0/audio0 interfaces.
So, there is no OpenSource part which will allow to add new format, protocol and so on.

All is closed. So, only set-top-box driver provider can made fix or add support for example for some streaming protocols.

In such way this set-top-box is unusable for IPTV unless /dev/dvb/adapter0/audio0
and /dev/dvb/adapter0/video0 will be fixed.

This is very bad news because hardware is very good, but drivers unfortunately are not.

 

 

Thank you for precise and exhaustive information!

 

I have tested H9S and H9T for a while now and there are various issues I encountered re. streaming and playback, in various pieces of SW for H9 models but I have not seen a lot of acceptance of the results of my tests, i.e. I have seen some almost dogmatic resilience to proper, extensive tests and feedback and therefore not much movement on the issues yet, sadly... Perhaps they'll listen to you...

[gorski]

SSS:

 

fullwget command (from the tutorial) did not work,

 

wget only did.

 

After starting E2iPlayer, exteplayer3 installation was offered and all proceeded as usual.

 

Thanx!

[rantanplan]

Of course you can also patch the functionality for ffmpeg 4 into the e2iplayer.

--- a/IPTVPlayer/setup/iptvsetupimpl.py	2018-07-27 00:55:11.192716609 +0200
+++ b/IPTVPlayer/setup/iptvsetupimpl.py	2018-07-27 00:58:24.105474454 +0200
@@ -940,16 +940,16 @@
         if len(self.ffmpegVersion) >= 5:
             shortFFmpegVersion = self.ffmpegVersion[:-2]
             
-        if self.platform in ['sh4'] and shortFFmpegVersion in ['1.0', '1.1', '1.2', '2.0', '2.2', '2.5', '2.6', '2.7', '2.8', '3.0', '3.1', '3.2', '3.3', '3.4']: 
+        if self.platform in ['sh4'] and shortFFmpegVersion in ['1.0', '1.1', '1.2', '2.0', '2.2', '2.5', '2.6', '2.7', '2.8', '3.0', '3.1', '3.2', '3.3', '3.4', '4.0']: 
             self.ffmpegVersion = shortFFmpegVersion
             self.exteplayer3Step()
-        elif self.platform in ['mipsel'] and shortFFmpegVersion in ['2.8', '3.0', '3.1', '3.2', '3.3', '3.4']:
+        elif self.platform in ['mipsel'] and shortFFmpegVersion in ['2.8', '3.0', '3.1', '3.2', '3.3', '3.4', '4.0']:
             self.ffmpegVersion = shortFFmpegVersion
             self.exteplayer3Step()
-        elif self.platform in ['armv7'] and shortFFmpegVersion in ['2.8', '3.0', '3.1', '3.2', '3.3', '3.4']:
+        elif self.platform in ['armv7'] and shortFFmpegVersion in ['2.8', '3.0', '3.1', '3.2', '3.3', '3.4', '4.0']:
             self.ffmpegVersion = shortFFmpegVersion
             self.exteplayer3Step()
-        elif self.platform in ['armv5t'] and shortFFmpegVersion in ['2.8', '3.0', '3.1', '3.2', '3.3', '3.4']:
+        elif self.platform in ['armv5t'] and shortFFmpegVersion in ['2.8', '3.0', '3.1', '3.2', '3.3', '3.4', '4.0']:
             self.ffmpegVersion = shortFFmpegVersion
             self.exteplayer3Step()
         elif "" != self.gstreamerVersion: self.gstplayerStep()

Maybe @samsamsam but also like to expand it or even more elegant recompiling with ffmpeg 4.0.2

[samsamsam]

@rantanplan

 

With such patch you still will be not able to use exteplayer3 because at first you need to have exteplayer3 compiled with ffmpeg 4.0.X

Anyway way there is collection of patches prepared for ffmpeg 3.4.2 to fix or improve ffmpeg works in the exteplayer3 use case.

So, you need to port these patches to new version too. 

 

So, this simple patch does not patch anything.

 

Regards,

SSS

[babsy98]

hi samsamsam  i have test your work first time at weekend

 

nice work i use openatv

 

please add more platforms

 

aarch64 for new coming 64 bit bcm models like vu duo 4k and edison os mio 4k

 

thanks

[rantanplan]

@rantanplan

 

With such patch you still will be not able to use exteplayer3 because at first you need to have exteplayer3 compiled with ffmpeg 4.0.X

Anyway way there is collection of patches prepared for ffmpeg 3.4.2 to fix or improve ffmpeg works in the exteplayer3 use case.

So, you need to port these patches to new version too. 

 

So, this simple patch does not patch anything.

 

Regards,

SSS

Hello @samsamsam

I know this, of course. Just wanted to show the way how you could also test a version with the e2iplayer.
Of course, the patches in the ffmpeg would then have to be adjusted.

As far as c ++ and especially Dash is concerned, ffmpeg will take over from you, but you know yourself better.
So, for sure, waiting for your next release would be the easiest for most people.
Of course, everyone can watch for themselves and tinker is allowed.

many Greetings

[samsamsam]

@rantanplan

 

 

I know this, of course. Just wanted to show the way how you could also test a version with the e2iplayer.

 

 

But this patch does not allow this.

 

At first you need compile exteplayer3 with ffmpeg 4.X, and the current source code of exteplayer3 does not compile with ffmpeg 4.X

So, this patch does nothing.

How you want to test new ffmpeg version, without exteplayer3 compiled with this version?

 

 

@babsy98

I do not support the E2iPlayer on this forum. If you want to request any new functionality then you should do this in valid to this purpose place.

 

Regards,

SSS

Edited by samsamsam, 6 November 2018 - 13:55.