Radxa 3w RTSP Client on Android and Debian high lags when displaying HDMI

#1

Hello everyone!
Another problem :frowning:
I want to receive an RTSP stream on Radxa 3W x264 1920×1080@60 fps, which is generated by another radxa 3w. There is no problem with stream generation now, everything is received well on PC.

The characteristics of the Radxa 3W processor allow this (listed on the website):

  • OpenGL® ES1.1 / 2.0 / 3.0 / 3.1 / 3.2
  • Vulkan® 1.1, OpenCL™ 2.0
    1x Micro HDMI support 1080P@60fps
    H.264/H.265 decoder up to 4K@60fps
    H.264/H.265 encoder up to 1080P@60fps

Problem description:
Trying to get a stream on Debian 11 (official from the site, updated via rserup):
Compiled ffmpeg according to different instructions
and used this one
https://docs.radxa.com/en/zero/zero3/app-development/rtsp
and used this one


Launch the client
ffmpeg-rockchip/ffplay -vcodec h264_rkmpp rtsp://192.168.10.24:8554/stream
or
ffplay -vcodec h264_rkmpp rtsp://192.168.10.24:8554/stream

As a result, we get a heavy load on the processor and terrible slowdowns in displaying pictures:
image

image
image.jpg1280×576 229 KB

**Trying to get a stream on Android (**also from the official repository):
I use various RTSP clients, everywhere the picture is terribly slow.
Stopped at the open source project


Where in the debugger is there a gap that the hardware codec for some reason does not start:
2024-10-25 14:49:13.980 2191-2309 ACodec com.alexvas.rtsp.demo E decoder can not set low-latency to 1 (err -1010)
2024-10-25 14:49:13.980 2191-2309 ACodec com.alexvas.rtsp.demo E [OMX.rk.video_decoder.avc] configureCodec returning error -1010
2024-10-25 14:49:13.980 2191-2309 ACodec com.alexvas.rtsp.demo E signalError(omxError 0x80001001, internalError -1010) 2024-10-25 14:49:13.980 2191-2308 MediaCodec com.alexvas.rtsp.demo E Codec reported err 0xfffffc0e, actionCode 0, while in state 3

image
image.png1703×676 189 KB

When tested on a mobile phone, this client works correctly, although it has approximately the same video card characteristics as Radxa 3w

Has anyone managed to receive such a stream with correct display without lags via HDMI 1920×1080@60 fps on Radxa 3W? @ChenJaly

#2

Since zero3’s driver on Linux does not yet implement OpenGL, despite the hardware decoding, it still lags and uses high resources when playing videos.

#3

I see. ok
And what about Android?

#4

@yanw Please, check it.

#5

As a result, I managed to launch the RSTP client with FULL HD video display with acceptable FPS on Armbian for Radxa Zero 3W. Apparently, the driver uses hardware resources.
I used the Ubuntu 24.04 (Noble) XFCE image
Debian 12 worked unstably.
https://www.armbian.com/radxa-zero-3/
FFplay was used as a client
Compiled according to various instructions


https://docs.radxa.com/en/zero/zero3/app-development/rtsp?target=ffmpeg
However, the instructions are not complete, you still need to manually install some components to successfully compile ffplay, due to the peculiarity with repositories. Unfortunately, I did not save the console output to describe which components and how to install them, I just searched the Internet for a description of the errors and which components are needed. If ffplay did not compile as a result, but there were no errors in the console, then some components were missing. You need to figure it out and install them, then ffplay will compile and work.

The problem with Android is still relevant.
For some reason, the hardware decoder does not start (description in the first post)
ACodec com.alexvas.rtsp.demo E decoder can not set low-latency to 1 (err -1010)

1 Like