Channels DVR Raspberry Pi 4 - Lost Hardware Transcoding?

Channels DVR Server
#1

Screenshot 2023-08-11 at 9.40.00 AM
Screenshot 2023-08-11 at 9.40.00 AM708×310 32.9 KB

nvmpi

/mnt/data/channels-dvr/2023.08.09.2030/ffmpeg-dl: error while loading shared libraries: libnvmpi.so: cannot open shared object file: No such file or directory

exit status 127

v4l2m2m

[Parsed_color_0 @ 0xf5b3330] size:640x480 rate:25/1 duration:-1.000000 sar:1/1 Input #0, lavfi, from 'color=black:640x480': Duration: N/A, start: 0.000000, bitrate: N/A Stream #0:0: Video: rawvideo, 1 reference frame (I420 / 0x30323449), yuv420p, 640x480 [SAR 1:1 DAR 4:3], 25 tbr, 25 tbn, 25 tbc Stream mapping: Stream #0:0 -> #0:0 (rawvideo (native) -> h264 (h264_v4l2m2m)) Press [q] to stop, [?] for help [graph 0 input from stream 0:0 @ 0xf5def40] w:640 h:480 pixfmt:yuv420p tb:1/25 fr:25/1 sar:1/1 [h264_v4l2m2m @ 0xf5dc7a0] Could not find a valid device [h264_v4l2m2m @ 0xf5dc7a0] can't configure encoder Error initializing output stream 0:0 -- Error while opening encoder for output stream #0:0 - maybe incorrect parameters such as bit_rate, rate, width or height Conversion failed!

exit status 1

Lost hardware transcoding on RasPi 4
#2

Yep, just checked mine, and I've also lost Hardware transcoding with the latest stable release, 2023.08.07.2138

#3

Same here

#4

I dont have a PI but in my Unraid box Channels can't find my AMD RYzen IGPU. Its in Plex though, so maybe there is an issue with Channels and not me...Though it could be both...

My Errors.

amf
fork/exec /channels-dvr/2023.08.09.2030/ffmpeg-dl: no such file or directory
nvenc

fork/exec /channels-dvr/2023.08.09.2030/ffmpeg-dl: no such file or directory
vaapi@/dev/dri/card0

[AVHWDeviceContext @ 0x7b89280] libva: VA-API version 1.16.0
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [2]
param: 4, val: 0
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [2]
param: 4, val: 0

[AVHWDeviceContext @ 0x7b89280] libva: driver init failed
[AVHWDeviceContext @ 0x7b89280] libva: va_openDriver() returns 18
[AVHWDeviceContext @ 0x7b89280] Failed to initialise VAAPI connection: 18 (invalid parameter).
signal: segmentation fault

vaapi@/dev/dri/renderD128
[AVHWDeviceContext @ 0x7b89280] libva: VA-API version 1.16.0
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [2]
param: 4, val: 0
DRM_IOCTL_I915_GEM_APERTURE failed: Invalid argument
Assuming 131072kB available aperture size.
May lead to reduced performance or incorrect rendering.
get chip id failed: -1 [2]
param: 4, val: 0
[AVHWDeviceContext @ 0x7b89280] libva: driver init failed
[AVHWDeviceContext @ 0x7b89280] libva: va_openDriver() returns 18
[AVHWDeviceContext @ 0x7b89280] Failed to initialise VAAPI connection: 18 (invalid parameter).
signal: segmentation fault

vaapi@/dev/dri/renderD129
no such file or directory

vaapi@/dev/renderD128
no such file or directory
#5

This thread is specifically about hardware transcoding no longer being present on the Pi. Previous DVR releases had no problem, but the current stable release no longer works.

(Was a change to the bundled Ffmpeg made between releases? I, too, am affected by this, and no changes were made to the system other than an update to Channels.)

#6

@Maddox

1 Like
#7

Can you submit diagnostics from your DVR?

#8

Just submitted mine

#9

and same here.

#10

I run my DVR from a container, but here is my output:

robert@norn:~ $ uname -a
Linux norn 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr  3 17:24:16 BST 2023 aarch64 GNU/Linux
robert@norn:~ $ cat /etc/os-release 
PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"
NAME="Debian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
robert@norn:~ $ ls /dev/video*
/dev/video10  /dev/video14  /dev/video19  /dev/video23
/dev/video11  /dev/video15  /dev/video20  /dev/video31
/dev/video12  /dev/video16  /dev/video21
/dev/video13  /dev/video18  /dev/video22
robert@norn:~ $ sudo podman exec -t channels uname -a
Linux media 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr  3 17:24:16 BST 2023 aarch64 Linux
robert@norn:~ $ sudo podman exec -t channels cat /etc/os-release
NAME="Alpine Linux"
ID=alpine
VERSION_ID=3.17_alpha20221110
PRETTY_NAME="Alpine Linux edge"
HOME_URL="https://alpinelinux.org/"
BUG_REPORT_URL="https://gitlab.alpinelinux.org/alpine/aports/-/issues"
robert@norn:~ $ sudo podman exec -t channels ls /dev/video*
/dev/video10  /dev/video13  /dev/video16  /dev/video20  /dev/video23
/dev/video11  /dev/video14  /dev/video18  /dev/video21  /dev/video31
/dev/video12  /dev/video15  /dev/video19  /dev/video22

Diagnostics submitted: 5b4835e4-09b4-468a-997e-6abcd1347df1

#11

Diagnostics submitted.

#12

I have submitted my diagnostics, too, as lost hardware transcoding.

#13

Can confirm that the latest Channels DVR pre-release fixes the transcoding issue on my rpi 4. I fully tested a remote transcode and it worked.

#14

I, too, have regained hardware transcoding with 2023.08.15.0451.

#15

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.