101 replies to this topic

[martossien]

OK Thank's a lot Ims ( and Other )

 

Next release it 's new build release in  OpenPLi4 or new release OpenPli 5 ?

&

[WanWizard]

Next release is a new OpenPLi version. Up until now, there are no releases, OpenPli 4 is essentially a nightly automatic and daily changing development build.

[martossien]

OK like a OpenPli 4.0 to OpenPli 4.1 for exemple.

 

I use all i find so see cpu frequency

dmesg ( i see power cpu reservation )

i install cputool but with no Mhz details

check /proc/cpuinfo

 

But no found ... any idea ?

[martossien]

Another little ask

The 7251s the s is for vp9 capacity , do you know if the libvpx-vp9 of ffmpeg was include in the compile ?

[Erik Slagter]

The support for VP9 is in the hardware of this SoC, it has nothing to do with ffmpeg or libvpx. On the other hand, support it must be licensed by the manufacturer, so if the SoC supports it, it may or not be supported by the receiver it's in.

 

To see the speed of the CPU in the SoC, see http://openpli.org/wiki/comparison. But the CPU speed is mostly irrelevant on a STB.

[martossien]

OK escuse me SOC ( 7251S  ) not cpu (amrv7 neon ) have the hardware VP9 capacity with S at the and of Broadcom so 7251S have it , but the ffmpeg must building-with-libvpx to have it.

[Erik Slagter]

No really not. Read again. This is about a hardware decoder, libvpx is a software decoder.

[martossien]

ok and more , if it have it in the receiver  it don't have encoding capacity ... so only software ...

         

3

SoC Vendor Part Number Application CPU core   VP9 Decoder VP9 Encoder  

4

Broadcom BCM7251S STB ARM   Yes No

[WanWizard]

Logical, an STB does not have the need to encode VP9, so why would the manufacturer make the box more expensive by including that license? Makes perfect sense to me.

[martossien]

true ...

some one you have HD51 or HD51 clone could try ffmpeg :

 

record one video flux at 1080P ( make a top in another session)

 

ffmpeg -i test.ts" -c:a ac3 -ac 1 -ar 11025 -b:a 64k -c:v libx264 -pix_fmt yuv420p -crf 23 -s 320x240 -r 22 -preset:v ultrafast -vf "[in] crop=iw-150\:ih-40\:75\:20 [out]" -c:v libx264 outFile.mkv

ffmpeg -i test.ts" -c:a ac3 -ac 1 -ar 11025 -b:a 64k -c:v libx264 -pix_fmt yuv420p -b:v 200k -bt 8334 -maxrate:v 200k -bufsize:v 20k -s 300x220 -r 20 -preset:v ultrafast -vf "[in] crop=iw-150\:ih-40\:75\:20 [out]" -c:v libx264 outFile.mkv

I test it on external device , first it is quality , second is fast .

you change the source by :

-i "http://192.168.0.28:...:820000:0:0:0:"

And destination

http://127.0.0.1:8002/stream1.ffm

[martossien]

delete " after test.ts

I look for transcoding with less cpu ...

[martossien]

windows version ( must install ffmpeg-3.3.1-win64-static.zip in c:\ffmpeg )

 

c:\ffmpeg\bin\ffmpeg -v 32   -i "http://192.168.0.28:...3F:820000:0:0:0:" -c:a ac3 -ac 1 -ar 11025 -c:v libx264 -pix_fmt yuv420p -b:v 200k -bt 8334 -maxrate:v 200k -bufsize:v 20k -s 300x220 -r 20 -preset:v ultrafast -vf "[in] crop=iw-150\:ih-40\:75\:20 [out]" -c:v libx264 outFile2.avi

[martossien]

and if we can have ffserver (from ffmpeg ) too to the new version ...

IN this case easy to make our own web stream ...

[martossien]

tested on raspberry and use 75 % on the cpu ...

 

could someone can test on this receiver ?

[martossien]

raspberry :

 

ffmpeg -i http://192.168.0.28:...3F:820000:0:0:0 -c:a ac3 -ac 1 -ar 11025 -b:a 64k -c:v libx264 -pix_fmt yuv420p -crf 23 -s 320x240 -r 22 -preset:v ultrafast -c:v libx264 outFile4.avi
 

i look now for FFserver in daemon mode ( in this case i have external solution for transcoding )

[martossien]

OK works only with flv format ... so we can gain more cpu if we find the trouble in avi mode

 

So

 

ffserver.conf

 

HTTPPort 8090
MaxHTTPConnections 200
MaxClients 100
MaxBandwidth 1000
CustomLog -

<Feed dvb1.ffm>
 File /tmp/dvb1.ffm
 FileMaxSize 1G
 ACL allow localhost
 ACL allow 192.168.0.0 192.168.255.255
 </Feed>

<Stream dvb1.avi>
 Format flv
 Feed dvb1.ffm
 VideoFrameRate 22
 VideoSize 320*240
 VideoBitRate 300
 VideoBufferSize 30000
 </Stream>


<Stream status.html>

Format status
 ACL allow localhost
 ACL allow 192.168.0.0 192.168.255.255
 </Stream>
 

launch

sudo ffserver

 

launch

ffmpeg -i http://192.168.0.28:...3F:820000:0:0:0 http://127.0.0.1:8090/dvb1.ffm
 

( it's your channel , here manga on dvb S2 in my hd51 with ip 192.168.0.28 )

 

in VLC, open network flux

 

http://192.168.0.19:8090/dvb1.avi

( 192.1680.19 is my raspberry where we have launch the ffserver )

 

 

With this configuration we have 370 kbits/s so ok for smartphone in 3G connection.

 

NOW :

 

I must create a little web server who can choose the channel and launch ffmpeg to ffserver , an manage the stop/start , etc ...

test a redirect nat external to the rasperry

 

If some who have ffmpeg can test on this receiver ... ( better than my external solution with raspberry )

[martossien]

for HD resolution we must use hardware of raspberry : ( so buy VC1 and MPEG-2 license )

./ffmpeg -c:v h264_mmal -i <inputfile.mp4> -c:v h264_omx -c:a copy -b:v 1500k <outputfile.mp4>

The first -c:v h264_mmal tells FFMpeg to use h264_mmal hardware accelerated decoder

The second -c:v h264_omx tells FFMpeg to use the h264_omx encoder

The -c:a copy tells FFMpeg to simply copy any audio tracks without transcoding

The -b:v tells FFMpeg to set the average video bitrate target to 1500Kbit. You can set this to whatever you want to get the desired file size.

 

What we can have ? ~24FPS h264 1080p

 

So i buy license , make the compile with hardware librairy and i come back with configuration who works.

[WTE]

Logical, an STB does not have the need to encode VP9, so why would the manufacturer make the box more expensive by including that license? Makes perfect sense to me.

 

It's common known that broadcom have upgrade the chipset with VP9 support. Therefor as inform by @martossien the S was add in the BCM7251 which means VP9 support.

Enigma2 has not yet add VP9 support and opus audio. In the new gstreamer only VP8 and VP6 works well. There is a good chance that ffmpeg will work. The bcm7251s/bcm7252s support and have license of VP9.

Edited by WTE, 10 June 2017 - 21:23.

[Trial]

Hi,

the topic was about encoder not decoder.

 

ciao

[martossien]

hello, some news ,

i compile with  raspberry hardware decoder / hardware encoder ( https://www.raspberr...84425&p=1168656 ) , make some change ( gpu_mem to 320, gpu_clock 550, etc... i must make a howto  with )

 

sudo /usr/src/ffmpeg/ffmpeg -c:v h264_mmal -i http://192.168.0.28:...:EEEE0000:0:0:0: -c:v h264_omx -s 320x240 -r 22 -preset:v ultrafast /home/pi/outputfile9.mp4

 

And it's Works !!! , i must make some tuning , but now the HD go to 320 x 240 with 22 ftp !

 

So now what i can say : The dual Arm v7 neon can make software trasncoding in SD to 320 * 240 , for HD it need hardware encoder/decoder BUT i see some source code hardware decoder h264 ( and i see h265 ) for Broadcom BCM7251S, it's not public source but i think some people can have it , in this case we can compile and module ( the same as h264_mmal and h264_omx ) for make it in hardware.

 

So i continue : ( Project in wait of ffmpeg in new version of openpli )

Make tunning adn make a conf for HD to 320 * 240 with 300 to 500 Kbit/s

Make a stream test HD to 320 * 240

Make web to stop/start stream with choose channel

make an how to Hardare Transcoding Enigma2 with and Rasberry Pi ...