From 9e6b298e6808a9f8f3f8e4cc1ee2ef72f3a55ffb Mon Sep 17 00:00:00 2001
From: Saninn Salas Diaz <5490201+distante@users.noreply.github.com>
Date: Tue, 19 Mar 2024 22:00:02 +0100
Subject: [PATCH 1/2] Fix: correct group assigment for HW Acceleration

`/dev/dri/renderD128 does not belongs to the `video` group, but to the `render` group.

Following the old steps will cause an `VA-API device (/dev/dri/renderD128) has incorrect permissions on the Memories config` error
---
 docs/hw-transcoding.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/hw-transcoding.md b/docs/hw-transcoding.md
index 748df40cb..afc6fa692 100644
--- a/docs/hw-transcoding.md
+++ b/docs/hw-transcoding.md
@@ -108,7 +108,7 @@ On the Nextcloud machine, you need to make sure that the `www-data` user has acc
 ## Ubuntu
 sudo apt-get update
 sudo apt-get install -y intel-media-va-driver-non-free ffmpeg # install VA-API drivers
-sudo usermod -aG video www-data # add www-data to the video group (may be different)
+sudo usermod -aG render www-data # add www-data to the render group (may be different)
 
 ## Alpine
 apk update

From 95bc12aaf0e21f2fa4696c422df1174753997c18 Mon Sep 17 00:00:00 2001
From: Saninn Salas Diaz <5490201+distante@users.noreply.github.com>
Date: Wed, 20 Mar 2024 07:11:15 +0100
Subject: [PATCH 2/2] Add detailed description for correct device group

---
 docs/hw-transcoding.md | 18 ++++++++++++++++--
 1 file changed, 16 insertions(+), 2 deletions(-)

diff --git a/docs/hw-transcoding.md b/docs/hw-transcoding.md
index afc6fa692..120f68a7a 100644
--- a/docs/hw-transcoding.md
+++ b/docs/hw-transcoding.md
@@ -102,19 +102,33 @@ Memories ships with an internal transcoder binary that you can directly use. In
 
 If you are running Nextcloud on bare metal, you can install the drivers and ffmpeg directly on the host. If you are running nextcloud in a Virtual Magine or LXC container configuration, you will also need to pass through the hardware resource to the nextcloud machine. Some helpful guides can be found for [Proxmox VM](https://pve.proxmox.com/wiki/PCI_Passthrough) / [LXC Container](https://gist.github.com/packerdl/a4887c30c38a0225204f451103d82ac5?permalink_comment_id=4471564). 
 
-On the Nextcloud machine, you need to make sure that the `www-data` user has access to the `/dev/dri` devices. You can do this by adding the `www-data` user to the appropriate groups.
+On the Nextcloud machine, you will need to install the required drivers
 
 ```bash
 ## Ubuntu
 sudo apt-get update
 sudo apt-get install -y intel-media-va-driver-non-free ffmpeg # install VA-API drivers
-sudo usermod -aG render www-data # add www-data to the render group (may be different)
+
 
 ## Alpine
 apk update
 apk add --no-cache bash ffmpeg libva-utils libva-vdpau-driver libva-intel-driver intel-media-driver mesa-va-gallium
 ```
 
+And make sure that the `www-data` user has access to the `/dev/dri` devices. You can do this by adding the `www-data` user to the appropriate groups. First see to which group `/dev/dri/renderD128` belongs to with `sudo ls -l /dev/dri/`. I will return something similar to:
+
+```
+$ sudo ls -l /dev/dri/
+crw-rw---- 1 root video  226,   0 Mar 19 20:38 card0
+crw-rw---- 1 root video  226,   1 Mar 19 20:38 card1
+crw-rw-rw- 1 root render 226, 128 Mar 19 20:38 renderD128   
+```
+Here, the `renderD128` device belongs to the `render` group. you have to `www-data` to that group with:
+
+```
+sudo usermod -aG render www-data # add www-data to the render group (in other cases it can belong to `video` for example)
+```
+
 In some cases, along with adding `www-data` to the appropriate groups, you may also need to set the permissions of the device manually:
 
 ```bash