Login to your unRAID box using the GUI and open a terminal window.
If your config meets all of the above requirements, give these commands a shot, you should know straight away if you can use Hardware Acceleration. =/ you'd have better luck using the new unRAID Nvidia Plugin. So as far as any OS is concernedĮven though the Intel CPU supports Quick Sync, the Matrox one doesn't. Unfortunately this means that the server has 2 GPUs and ALL GPU output from the server passed through the ancient Matrox GPU. Some machines like the HP MicroServer Gen8 have iLO / IPMI which allows the server to be monitored / managed remotely. If you find that this is the case on your setup you can buy a dummy HDMI doo-dad that tricks your unRAID box into thinking that something is plugged in. In some cases this may require you to have the HDMI output plugged in and connected to a monitor in order for it to be active. You will need to enable iGPU on your motherboard BIOS
Intel CPU that has Quick Sync Capability - Search for your CPU using Intel ARK A Plex Pass - If you require Plex Hardware Acceleration Test to see if your system is capable before buying a Plex Pass.Ģ. "(hw)" will not be shown if Quick Sync isn't being used in transcoding.ġ. I have Quick Sync enabled hence the "(hw)" which stands for, you guessed it, Hardware. If you head back to the Now Playing section in Plex you will see that the stream is now being Transcoded. Click on Settings > Quality > Show All > Choose a Quality that isn't the Default one To initiate some transcoding, go to where your media is playing. It just means is that your Plex Media Server is able to perform the transcode faster than is necessary. Log into Plex and go to Settings > Status > Now PlayingĪs you can see this file is being direct played, so there's no transcoding happening. You're able to see how media is being served by playing a first something on a device. This can dramatically reduce the CPU overhead required for transcoding and Plex can leverage this using their Hardware Acceleration feature. Fortunately Intel CPUs have a little thing called Quick Sync which is their native hardware encoding and decoding core. The issue is that depending on which format your transcoding from and to, this can absolutely pin all your CPU cores at 100% which means you're gonna have a bad time.
#Intel quicksync decoder 1080p
This is because a 240p file will require considerably less bandwith compared to a 1080p file. Playing the file in 1080p is taking up too much bandwith so to get a better experience you can watch your media in glorious 240p without stuttering / buffering on your little mobile device by getting Plex to transcode the file first. You're away from home and you have a crappy internet connection. You could either manually convert each file or get Plex to transcode the file on the fly into another format to be played. This should be okay in most cases, but you may be accessing Plex remotely or on a device that is having difficulty with the source media. This is great in most cases as there will be very little if any overhead on your CPU. If all of the above is met, Plex will Direct Play or send the media directly to the client without being changed. Media is stored in a compatible file container Plex will check against the device trying to play the media: When streaming media from Plex, a few things are happening. Special thanks to Hoopster whose post(s) I took this from.
Granted this has been covered in a few other posts but I just wanted to have it with a little bit of layout and structure.
#Intel quicksync decoder code
I've fixed the code blocks below and all should be Plexing perfectly now This was causing people to get errors when typing commands verbatim.
#Intel quicksync decoder update
***Update*** : Apologies, it seems like there was an update to the Unraid forums which removed the carriage returns in my code blocks.
0 kommentar(er)
