Cedrus on Armbian

[divis1969 8]

Hi,

Did anybody play with Cedrus on the recent kernels?

I'm going to play with it on Bananapi m1, kernel 5.4 and Ubuntu Bionic.

Should I just got step-by-step using this instructions http://linux-sunxi.org/Sunxi-Cedrus ?

The goal is to evaluate whether this is suitable solution for video surveillnace. I'd used kerberosio with an IP camera for couple years and this does not work good with motion detection.

[Werner 191]

cedrus module should be available at boot for sunxi and sunxi64 configurations. Just check with lsmod.

Also someone else playing with it:

 

[Tido 186]

11 hours ago, divis1969 said:

play with Cedrus on the recent kernels

If you find an image over here: https://libreelec.tv/  and its HW-Acceleration works properly. You already know - there is a way to go. Before try and error.

 

[MacBreaker 13]

@divis1969

 

I also use kerberosio since years with some OrangePi's (Frontdoor, Garden Cam..)
and USBCameras. But not directly in kerberosio. I'm runing mjpg_streamer for live-streaming and in kerberosio i us it like a IP-Camera.

 

Did you try out Zoneminder? I think about to try it in the next time when i've time.

 

[divis1969 Topic author 8]

On 4/27/2020 at 11:13 AM, MacBreaker said:

Did you try out Zoneminder? I think about to try it in the next time when i've time.

Yes, I did. If was long time ago and I found kerberosio more attractive. There was also a performace issue with ZM on bananapi that time.
I've tested ZM recently again (on bananapi m3) and it seems using less CPU than kerberosio while movement detection. So, I would switch to ZM if it will be able to handle >1 cameras.
But I decided to first play with HW decoding on bananapi prior to migrating to ZM.

 

-----

Here are the results of my attempt to use cedrus.
- I've built libva-v4l2-request. There were few issues with it. It requires libva-dev and libdrm-dev, I've installed it with apt.
Version release-2019.03 of libva-v4l2-request failed on build due to libva-dev version mismatch (this package seems declared incorrect verion for pkg-config).
I've switched to a tip of the master branch was built successfully (but with small change in the /usr/include/linux/videodev2.h - I've added v4l2_timeval_to_ns which
is missing. BTW, I've also installed linux headers with apt, these headers contain v4l2_timeval_to_ns but libva-v4l2-request does not use these)

This lib is installed by default to /usr/lib/dri/, but libVA will search it under /usr/lib/arm-linux-gnueabihf/dri/ and I've just create a symbolic link. Maybe --prefic should be specified to autoconf instead.

- I've tried to use this lib with ffmpeg (default, installed with apt):

export LIBVA_DRIVER_NAME=v4l2_request
ffmpeg -v verbose -hwaccel vaapi -hwaccel_device /dev/video0 -hwaccel_output_format vaapi -i big_buck_bunny_720p_H264_AAC_25fps_3400K.MP4 -r 5 -an stream.mp4

It produces the following error:
 

[AVHWDeviceContext @ 0x1d7a820] libva: VA-API version 1.1.0
[AVHWDeviceContext @ 0x1d7a820] libva: va_getDriverName() returns -1
[AVHWDeviceContext @ 0x1d7a820] libva: User requested driver 'v4l2_request'
[AVHWDeviceContext @ 0x1d7a820] libva: Trying to open /usr/lib/arm-linux-gnueabihf/dri/v4l2_request_drv_video.so
[AVHWDeviceContext @ 0x1d7a820] libva: Found init function __vaDriverInit_1_1
[AVHWDeviceContext @ 0x1d7a820] libva: va_openDriver() returns 0
[AVHWDeviceContext @ 0x1d7a820] Initialised VAAPI connection: version 1.1
[AVHWDeviceContext @ 0x1d7a820] Unknown driver "v4l2-request", assuming standard behaviour.
Stream mapping:
  Stream #0:0 -> #0:0 (h264 (native) -> h264 (libx264))
Press [q] to stop, [?] for help
[h264 @ 0x1d77fc0] Reinit context to 1280x720, pix_fmt: vaapi_vld
v4l2-request: Unable to set control: Bad address
v4l2-request: Unable to queue media request: No such file or directory
[h264 @ 0x1d77fc0] Failed to end picture decode issue: 1 (operation failed).
[h264 @ 0x1d77fc0] hardware accelerator failed to decode picture

Kernel log also contains errors:
 

[94838.781065] cedrus 1c0e000.video-codec: Missing required codec control
[94838.785428] cedrus 1c0e000.video-codec: Missing required codec control
[94838.791230] cedrus 1c0e000.video-codec: Missing required codec control
[94838.794613] cedrus 1c0e000.video-codec: Missing required codec control

- I've built v4l2-request-test and play with it. Initially it complains "Unable to start display engine" so, I've commented this functionality (so it can decode, but does not try to display frames).
This suite contains several test packages (frames). MPEG2 tests works perfectly (decoding only, as I said).

H265 tests fail with error
Processing frame 1/50
Loaded 145064 bytes of video slice data
Unable to set control: Bad address

There was no kernel errors.
H264 tests are disabled because of absence of V4L2_PIX_FMT_H264_SLICE in the system headers (linux headers contain it but autoconf does not see those).

 

Any suggestions how to enable H264? Should I also rebuild the kernel? What's wrong with H265?

Edited April 30 by divis1969
Corrections

[MacBreaker 13]

I also like to change mjpg streamer to ffmpeg.

But in the moment i haven'd time for this..

 

Keep on posting your results pls.

 

Regards

[divis1969 Topic author 8]

I've found that the issue with h264 codec is caused by the size of the struct v4l2_ctrl_h264_slice_params defined in include/media/h264-ctrls.h (kernel) and include/h264-ctrls.h (libva-v4l2-request).

Kernel's version adds one more field start_byte_offset with commit

commit 5604be66a56867a784e162299a48c214921ffa1b
Author: Boris Brezillon <boris.brezillon@collabora.com>
Date:   Fri Aug 16 13:01:24 2019 -0300

    media: uapi: h264: Add the concept of decoding mode

I did not find any changes in libva-v4l2-request that match this change in kernel.

I'm going to revert the above commit to test whether this can fix the issue.

[MacBreaker 13]

@divis1969

 

thanks for the info.

 

Regards

[divis1969 Topic author 8]

I have reverted the following commits:
 

341772b82a3b media: cedrus: Specify H264 startcode and decoding mode
8cae93e09011 media: uapi: h264: Add the concept of start code
5604be66a568 media: uapi: h264: Add the concept of decoding mode

Now I can run decoding of H264:

$ export LIBVA_DRIVER_NAME=v4l2_request
$ time ffmpeg -hwaccel vaapi -hwaccel_device /dev/video0 -hwaccel_output_format vaapi -i big_buck_bunny_720p_H264_AAC_25fps_3400K.MP4 -f null /dev/null
...
real    0m15.255s
user    0m5.651s
sys    0m1.693s

Average speed is ~5.3x, fps ~130

There are some errors at the end though:
 

[AVHWFramesContext @ 0xae54cfe0] Failed to destroy surface 0x400000b: 6 (invalid VASurfaceID).

Here is the test of decoding without hardware:

$ time ffmpeg -i big_buck_bunny_720p_H264_AAC_25fps_3400K.MP4 -f null /dev/null
real    0m37.776s
user    0m57.906s
sys    0m1.983s

Average speed is ~2.0x, fps ~50

I also tried to decode in software and encode in hardware. This causes crash of ffmpeg (I was not able to get a stack with gdb yet):

ffmpeg -vaapi_device /dev/video0 -i big_buck_bunny_720p_H264_AAC_25fps_3400K.MP4 -vf 'format=nv12,hwupload' -c:v h264_vaapi -an stream.mp4
...
Segmentation fault

 

[divis1969 Topic author 8]

Re-encoding from 25fps to 5fps (sw-to-sw and hw-to-sw) are almost identical though the second case takes more time (copying hw buffers?):

$ time ffmpeg -hwaccel vaapi -hwaccel_device /dev/video0 -i big_buck_bunny_720p_H264_AAC_25fps_3400K.MP4 -c:v libx264 -r 5 -an stream.mp4
...
real    6m45.657s
user    10m44.271s
sys    0m13.720s

$ time ffmpeg -i big_buck_bunny_720p_H264_AAC_25fps_3400K.MP4 -c:v libx264 -r 5 -an stream_sw.mp4
...
real    6m20.538s
user    10m19.009s
sys    0m3.729s

The video produced with hw decoder has small artifacts at the bottom-right corner.

[xmixahlx 4]

first, very interesting! thanks for your work here.

 

second, wouldn't it make more sense to update libva-v4l2-request? it is known to be out of date...

 

speaking as a rk3399 user (pbp) that would love to adapt it to include hantro and rkvdec.

[divis1969 Topic author 8]

I've tried to ask a question in IRC channel (#cedrus on freenode) but did not get an answer (or maybe I've missed it while I was offline, do not know where to get backlog).

If you mean to update a library by myself, I do not have any experience with H264 (or other video codecs).

The goal was to get a quick estimation whether cedrus is good enough for video surveillance application.

[Sash0k 5]

Hello. Thanks to you post, i've started VPU acceleration in H3 (OrangePI PC). For your SBC seems it will be the same.

 

On 5/29/2020 at 10:09 PM, divis1969 said:

I have reverted the following commits:

 

Seems, it will be better to upgrade backend headers, than downgrade kernel

 

On 5/29/2020 at 10:09 PM, divis1969 said:

[AVHWFramesContext @ 0xae54cfe0] Failed to destroy surface 0x400000b: 6 (invalid VASurfaceID).

 

Try this patch: https://github.com/bootlin/libva-v4l2-request/pull/30/files

 

Details:

https://forum.armbian.com/topic/11184-hardware-graphicvideo-acceleration-in-h3-mainline/?do=findComment&comment=105564

[divis1969 Topic author 8]

Thanks for the tip!

 

BTW, I've got a crash stack for a segmentation fault I've mentioned above:

 

Thread 1 "ffmpeg" received signal SIGSEGV, Segmentation fault.
tiled_to_planar () at tiled_yuv.S:86
86        vld1.8    {d0 - d3}, [SRC :256], TSIZE
(gdb) bt
#0  tiled_to_planar () at tiled_yuv.S:86
#1  0xb6fc25b0 in copy_surface_to_image (driver_data=driver_data@entry=0x466960, surface_object=surface_object@entry=0x469f48, image=image@entry=0xbeffda44) at image.c:159
#2  0xb6fc280e in RequestDeriveImage (context=<optimized out>, surface_id=67108864, image=0xbeffda44) at image.c:200
#3  0xb5a5eb84 in ?? () from /usr/lib/arm-linux-gnueabihf/libavutil.so.55
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

@All Is that something known already?