At 1080p, it can handle transcoding multiple streams at once like a BOSS. If you use hardware transcoding, it barely inches up 5-10% CPU use per stream. I have no 4K, but that is a whole 'nother beast and unlikely to be up to the task for more than 1, as said up above.
I can verify that the 920+ is pretty darn good for Synology for Plex. I’m planning to offload it soon for other reasons, but considering the work that NAS does, I’m impressed it did so well up to now.
Sorry to hijack the thread, but did you need to disable any drivers to get it to do hardware transcoding? I’m using DSM7. I’ve had to disable hardware transcoding because it seemed to cause issues. I still have a bunch of testing to troubleshoot -only had it since this weekend…
Thanks for that… if you did this in DSM7, could you point me in the right direction? All explanations I’ve seen refer to the DSM6 setup, mentioning the Plex folder, which doesn’t exist in DSM7.
I’m still on DSM 6. The location of the preferences.xml file may be in a different spot in DSM7. There was a time where the installation files (appData folder contains preferences.xml) on DSM 7 were unreachable. It seems that in the meantime they MIGHT have been able to replicate the traditional setup where there is a PlexMediaServer share with the appdata files in it. I do not know if this change is retroactive for people who may have installed Plex under the beginning days of getting plex working on DSM7.
I do see a LOT of warnings in one topic that says you should only be digging around in the AppData folder (if you find it) at the behest of Plex Ninjas or devs. I am neither, so I may be providing bad advice by saying anything here.
HOWEVER, as far as I can tell, if you can reach the file, adding the VAAPI driver line at the appropriate spot in the appropriate file SHOULD work, but I hope we can get a ninja in here to confirm. Or preferably provide the proper steps for DSM 7 in changing the HW transcoding driver.