# Don't give up on HW Transcoding after checking one device in /dev/dri **URL:** \ **Category:** Plex Media Server\ **Tags:** server-linux, server-docker\ **Created:** [February 21, 2023, 5:37pm UTC](https://forums.plex.tv/t/dont-give-up-on-hw-transcoding-after-checking-one-device-in-dev-dri/831832 "2023-02-21T17:37:20Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![historybandgeek](https://sea1.discourse-cdn.com/plex/user_avatar/forums.plex.tv/historybandgeek/32/299477_2.png) [@historybandgeek](https://forums.plex.tv/u/historybandgeek)\ **Post date:** [February 21, 2023, 5:37pm UTC](https://forums.plex.tv/t/dont-give-up-on-hw-transcoding-after-checking-one-device-in-dev-dri/831832/1 "2023-02-21T17:37:20Z")
As the tile says, it would have saved me a bit of time if when attempting to start a hardware transcode plex could check multiple devices rather than the default behavior of checking just the first device listed in /dev/dri and moving on to software transcoding if the first result doesn’t work. Yes, I’m a noob – but a noob who spent two days messing with permissions and compiling drivers and trying different versions of and different images. (And that’s on me, and I learned a lot!) But the fix was just adding HardwareDevicePath=“/dev/dri/renderD129” to the plex preferences.xml. If possible (again, I’m a noob), it would’ve been great if plex thought to check the next device in /dev/dri automatically and I would’ve had no issue in the first place. Thanks! ---
**Author:** ![system](https://global.discourse-cdn.com/plex/original/3X/2/a/2acb9765406f63293d357b4ec509ec39aa28f2ad.png) [@system](https://forums.plex.tv/u/system)\ **Post date:** [May 22, 2023, 5:37pm UTC](https://forums.plex.tv/t/dont-give-up-on-hw-transcoding-after-checking-one-device-in-dev-dri/831832/2 "2023-05-22T17:37:22Z")
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.