gounthar

Isn't there a port of ffmpeg that permits hardware encoding for RK3399? I think I saw it there.

Hi there, I bought a few months ago a H616 based TV Box, and made the same kind of mistakes this week. I bought an OrangePi Zero2, also sporting a H616. I bought the TVBox because at that time: "wow, an undocumented AllWinnner SoC!", how stupid is that? I bought the Zero2 because CNX software gave a few hints about the SoC features, like the fact the G31 GPU is a Bitfrost GPU, meaning it supports Vulkan, and down the line, it could potentially be supported by Panfrost open-source graphics driver. I'm still dreaming of an Armbian based video encoding SBC, and this SoC (like so many others on the paper) looks promising: Video Decoding 10-bit H265/HEVC up tp 4Kp60 or 6Kp30 VP9 up to 4Kp60 H264/AVC up to 4Kp30 AVS2 up to 4Kp60 Encoding H.264 up to 4Kp25 or 1080p60 JPEG up to 1080p60 What do you folks think?

Done, thanks.

As the documentation is now marked as obsolete, what is the correct way to install Docker on a recent Armbian Buster? ___ ____ _ _ _ / _ \ _ __ __ _ _ __ __ _ ___| _ \(_) | || | | | | | '__/ _` | '_ \ / _` |/ _ \ |_) | | | || |_ | |_| | | | (_| | | | | (_| | __/ __/| | |__ _| \___/|_| \__,_|_| |_|\__, |\___|_| |_| |_| |___/ Welcome to Armbian 20.08.17 Buster with Linux 5.8.17-rockchip64 I think at one time, it was available in armbian-config, but I may be wrong.. And I'm trying that on an unsupported board (OrangePi4). Here is what I have done: sudo apt-get remove docker docker-engine docker.io containerd runc sudo apt-get install apt-transport-https ca-certificates curl gnupg-agent software-properties-common curl -fsSL https://download.docker.com/linux/debian/gpg | sudo apt-key add - sudo apt-key fingerprint 0EBFCD88 sudo add-apt-repository "deb [arch=arm64] https://download.docker.com/linux/debian $(lsb_release -cs) stable" sudo apt update sudo apt-get install docker-ce docker-ce-cli containerd.io sudo docker run hello-world Thanks.

Me too, I had to write them because I could not get my entry (a problem about "illegal" words). They solved the "bug" and I was then able to add my entry.

I applied, you never know...

I was thinking of using I2S to get mic-in and audio-out on an Orange Pi Zero v1.5 (because no more USB is available, I use them all), but it looks like it requires soldering, and I'm not confident with my soldering skills... Is there any other cheap Orange Pi board that could work with I2S audio out of the box? Thanks.

Definitely have to try that... Thanks a lot for your work!

What about https://discord.gg/HGrtpa ? I think we might get hints over there.

So does the hardware acceleration work for you @a.rodionov ?

I'm not sure I understood everything in this thread (in fact, I'm sure I got less than 10%). Anyway... My goal is to have hardware encoding and decoding for the Orange Pi 4B and RK3399 running Armbian. I'm still running 5.4.49-rockchip64 kernel. Is there an article somewhere for newbies in order to get a working hardware-enhanced version of ffmpeg for these boards? Thanks.

Hi @Myy, this did not work for me today, so I entered a new issue there. Thanks.

I finally had to export CFLAGS= to get the configure script to work.

Thanks, I will have a look at it.

Thanks @usual user.

Hi, I had already compiled ffmpeg on a 32bits OS for my Orange Pi RK3399 when it ran the Orange Pi 32 bits Ubuntu without too much trouble, but now that I have Armbian on my 4B, I'd like to compile ffmpeg too. The issue I have is that gcc is started with bad options (I'm not sure of that, that's what I think I understood): mktemp -u XXXXXX ZgAQ9I test_ld cc test_cc BEGIN /tmp/ffconf.efsAigGe/test.c 1 int main(void){ return 0; } END /tmp/ffconf.efsAigGe/test.c gcc -mfpu=neon -c -o /tmp/ffconf.efsAigGe/test.o /tmp/ffconf.efsAigGe/test.c gcc: error: unrecognized command line option '-mfpu=neon' C compiler test failed. poddingue@orangepi4-armbian:~/ffmpeg_sources/FFMpeg-orig$ ./configure If gcc is a cross-compiler, use the --enable-cross-compile option. Only do this if you know what cross compiling means. C compiler test failed. If you think configure made a mistake, make sure you are using the latest version from Git. If the latest version fails, report the problem to the ffmpeg-user@ffmpeg.org mailing list or IRC #ffmpeg on irc.freenode.net. Include the log file "ffbuild/config.log" produced by configure as this will help solve the problem. gcc is unable to create an executable file. If gcc is a cross-compiler, use the --enable-cross-compile option. Only do this if you know what cross compiling means. C compiler test failed. My gcc version is : gcc -v Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/aarch64-linux-gnu/8/lto-wrapper Target: aarch64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Debian 8.3.0-6' --with-bugurl=file:///usr/share/doc/gcc-8/README.Bugs --enable-languages=c,ada,c++,go,d,fortran,objc,obj-c++ --prefix=/usr --with-gcc-major-version-only --program-suffix=-8 --program-prefix=aarch64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-libquadmath --disable-libquadmath-support --enable-plugin --enable-default-pie --with-system-zlib --disable-libphobos --enable-multiarch --enable-fix-cortex-a53-843419 --disable-werror --enable-checking=release --build=aarch64-linux-gnu --host=aarch64-linux-gnu --target=aarch64-linux-gnu Thread model: posix gcc version 8.3.0 (Debian 8.3.0-6) My machine is running Armbian buster with Linux 5.4.49-rockchip64Debian 10 buster with Kernel: aarch64 Linux 5.4.49-rockchip64. Is there anything I could do with configure so that it uses the right options? I have compiled tons of other sources on that machine, but ffmpeg and x264 really don't like it. Thanks.

Do you think we could get the patch

Hi there, I don't know yet much about the USB gadget framework, but was wondering it I could use it to make an Orange Pi Zero or One seen as a video sink by the host computer. I know the framework should allow the board to be seen as an audio source, a video source, a Midi device and other things, but could it be seen as a video consumer of some sort ? My goal would be to grab the host's webcam content, encode and stream it on the SBC so that the host's CPU still has resource for other tasks. Does it make sense ? Thanks.

Thanks a lot @sfx2000, I will give it a try. ;-)

Well, I have a big heatsink AND a fan running. Without the fan, the temperature goes quickly around 83/84°C. It does not hang up though. These days, it runs around 53°C in the afternoon with a full Rosetta load.

I have updated my 4B with armbian-config today, and I think that now the temperature readings are wrong. It's cold in here, the board is working for Rosetta, but before the update, it was running at full throttle at 42°C, and now it's written 83°C. The big heatsink is cold, the fan is on. There's something fishy.... ___ ____ _ _ _ / _ \ _ __ __ _ _ __ __ _ ___| _ \(_) | || | | | | | '__/ _` | '_ \ / _` |/ _ \ |_) | | | || |_ | |_| | | | (_| | | | | (_| | __/ __/| | |__ _| \___/|_| \__,_|_| |_|\__, |\___|_| |_| |_| |___/ Welcome to Armbian buster with Linux 5.4.43-rockchip64 System load: 5.30 4.19 4.05 Up time: 3:21 Local users: 3 Memory usage: 67 % of 3868MB Zram usage: 16 % of 1023Mb IP: 192.168.0.46 192.168.0.43 CPU temp: 83°C Usage of /: 45% of 15G Last login: Fri Jun 5 19:51:59 2020 On another subject, has anyone attempted to install and use libraries/SDK for the NPU? Thanks.

I had a lot of stability issues with the original Orange Pi image, and it's running like a charm with Armbian. Thanks, folks!

Reading further in the tutorial mentioned earlier, I changed the content of /etc/systemd/system/parprouted.service [Unit] Description=proxy arp routing service Documentation=https://raspberrypi.stackexchange.com/q/88954/79866 [Service] Type=forking # Restart until wlan0 gained carrier Restart=on-failure RestartSec=5 TimeoutStartSec=30 ExecStartPre=/usr/bin/perl -e 'sleep 1 until -e "/sys/class/net/wlan0"' ExecStartPre=/bin/echo 'parprouted: wlan0 is online' # clone the dhcp-allocated IP to eth0 so dhcp-helper will relay for the correct subnet ExecStartPre=/bin/bash -c '/sbin/ip addr add $(/sbin/ip -4 addr show wlan0 | /bin/grep -Po "\\d+\\.\\d+\\.\\d+\\.\\d+\/")32 dev eth0' ExecStartPre=/sbin/ip link set dev eth0 up ExecStartPre=/sbin/ip link set wlan0 promisc on # v minus sign ExecStart=-/usr/sbin/parprouted eth0 wlan0 ExecStopPost=/sbin/ip link set wlan0 promisc off ExecStopPost=/sbin/ip link set dev eth0 down ExecStopPost=/bin/bash -c '/sbin/ip addr del $(/sbin/ip -4 addr show eth0 | /bin/grep -c1 -Po "\\d+\\.\\d+\\.\\d+\\.\\d+")/32 dev eth0' [Install] WantedBy=multi-user.target And the error is gone. My PC still can't see the network, but we're progressing.

I tried another way with arp proxy, following this tutorial, but at the end, I only get Apr 24 00:04:54 localhost systemd[1]: parprouted.service: Scheduled restart job, restart counter is at 249. Apr 24 00:04:54 localhost systemd[1]: Stopped proxy arp routing service. Apr 24 00:04:54 localhost systemd[1]: Starting proxy arp routing service... Apr 24 00:05:00 localhost systemd-networkd-wait-online[3263]: Event loop failed: Connection timed out Apr 24 00:05:00 localhost systemd[1]: parprouted.service: Control process exited, code=exited, status=1/FAILURE Apr 24 00:05:00 localhost bash[3286]: Error: any valid prefix is expected rather than "/32". Apr 24 00:05:00 localhost systemd[1]: parprouted.service: Control process exited, code=exited, status=1/FAILURE Apr 24 00:05:00 localhost systemd[1]: parprouted.service: Failed with result 'exit-code'. Apr 24 00:05:00 localhost systemd[1]: Failed to start proxy arp routing service. Apr 24 00:05:05 localhost systemd[1]: parprouted.service: Service RestartSec=5s expired, scheduling restart. Apr 24 00:05:05 localhost systemd[1]: parprouted.service: Scheduled restart job, restart counter is at 250. Apr 24 00:05:05 localhost systemd[1]: Stopped proxy arp routing service. Apr 24 00:05:05 localhost systemd[1]: Starting proxy arp routing service... Apr 24 00:05:12 localhost systemd-networkd-wait-online[3295]: Event loop failed: Connection timed out Apr 24 00:05:12 localhost systemd[1]: parprouted.service: Control process exited, code=exited, status=1/FAILURE Apr 24 00:05:12 localhost bash[3298]: Error: any valid prefix is expected rather than "/32". Apr 24 00:05:12 localhost systemd[1]: parprouted.service: Control process exited, code=exited, status=1/FAILURE Apr 24 00:05:12 localhost systemd[1]: parprouted.service: Failed with result 'exit-code'. Apr 24 00:05:12 localhost systemd[1]: Failed to start proxy arp routing service. Apr 24 00:05:17 localhost systemd[1]: parprouted.service: Service RestartSec=5s expired, scheduling restart. Apr 24 00:05:17 localhost systemd[1]: parprouted.service: Scheduled restart job, restart counter is at 251. Apr 24 00:05:17 localhost systemd[1]: Stopped proxy arp routing service. Apr 24 00:05:17 localhost systemd[1]: Starting proxy arp routing service... I will investigate.

Super cool, ubobrov! I unfortunately have to address other issues, but I sure will come back one of these days to try H264 encoding on Orange Pi Zero running mainline.