![xeon quicksync xeon quicksync](https://www.gadgety.co.il/wp-content/themes/main/thumbs/2016/06/Intel-Xeon-processor-E3-1500-v5_2-350x197.jpg)
NGCodec provided the script below for our testing. We used the script shown below for the x265 encodes, switching between the veryfast and medium presets and tuning for PSNR for the objective testing and not tuning for files produced for the subjective trials:įfmpeg -re -i input.mp4 -c:v libx265 -preset veryfast -x265- params keyint=120:bitrate=5000:vbv- maxrate=5000k:vbv-bufsize=12000 -tune psnr -pix _ fmt yuv420p output.mp4 There are certainly larger computers that could produce our encoding ladder using the veryfast preset in real time, but it would definitely be pricey. On the same system, encoding with the x265 veryfast preset failed to produce a single encoding ladder at the requisite 55 fps. Spot pricing on the system was $0.3466 per hour, yielding a cost per ladder of around $0.1733 per hour.
Xeon quicksync full#
We tested the Intel SVT-HEVC encoder on a C5.9xlarge system equipped with an Intel Xeon Platinum 8000 series (Skylake-SP) processor that produced two simultaneous encodes of the full encoding ladder using preset 6 tune 0. For all HEVC encodes, we boosted the buffer size to twice the target data rate to provide a bit more wiggle room for encoding quality.įfmpeg -SVTnew -i input.mp4 -c:v libsvt _ hevc -tune 0 -rc 1 -preset 6 -b:v 5M -maxrate 5M -bufsize 10M -g 120 output.mp4 This yielded the following command line, which Intel provided (showing tune 0). We used tune 0 for the subjective tests and tune 2 for both VMAF and PSNR. Note that the default is 1, so if you don’t specify tune 0 for your encode, you won’t get optimal visual quality.
![xeon quicksync xeon quicksync](https://www.gadgety.co.il/wp-content/themes/main/thumbs/2016/06/Intel-Xeon-processor-E3-1500-v5-812x542.jpg)
The SVT-HEVC codec has three tuning modes-0 to optimize for visual quality, 1 to optimize for PSNR/SSIM, and 2 to optimize for VMAF. Intel recommended that we test using preset 6, so we did.įigure 6. SVT-HEVC’s quality and performance by preset The HEVC codec has 10 presets, which delivered the performance and quality shown in Figure 6 for the Football clip encoded at 3Mbps. Although not technically a hardware-based codec, Intel’s SVT line of codecs has been designed to run extremely efficiently on Intel Xeon Scalable processors and Intel Xeon D processors. HEVCĪgain, for HEVC, we tested Intel’s SVTHEVC codec, NGCodec’s FPGA-based codec, and x265 using two presets: medium and veryfast. But if this doesn’t matter to you, it really comes down to the cheapest option. For publishers pushing huge stream counts, the data rate stability of the hardware codecs will prove very attractive. Overall, the quality difference among Intel Quick Sync, NVIDIA, and x264 medium wasn’t much of a differentiator. As you’ll read, we did tune for the HEVC objective benchmarks and did not tune for the HEVC clips tested by. Note that for these H.264 clips, we did not use any tuning mechanisms for the objective benchmarks, because according to Intel, there was no way to disable adaptive quantization or otherwise tune the Intel Quick Sync clips for VMAF or PSNR. If your content is gaming or animation, you should definitely run your own tests with your own videos. These roughly followed the objective scores, but not completely. For example, NVIDIA enjoyed a significant advantage over Intel Quick Sync in the Football and Meridian test clips, which Intel Quick Sync reversed with a substantial lead in the GTAV clip, where both hardware codecs ranked behind the x264 medium clip. Note that there was a great deal of variation in the subjective results on a clip-by-clip basis.
Xeon quicksync 720p#
Heres what a 4K transcode to 720p looks like on a 10 series card.Figure 5. Subjective H.264 results from My 10th Gen Nvidia transcodes 4K no issue, so I don't bother splitting my Plex library. It's easier than messing with the headache that is 4k transcoding.Īgree its definately good to split your library with 4K vs non-4K content.doing this he can either not share the 4K library with people remote, or can also utilise tautulli scripts to block users from trying to transcode content from the 4K library, and only allow direct stream (if he has the bandwidth).īut if he uses a modern 7th Gen+ or especially 10th Gen CPU he should be able to handle a couple of 4K transcodes without to much issue.not everyone wants to double up on all their 4K content.
Xeon quicksync 1080p#
Finally don't transcode 4k because it ruins the quality, create a separate 4k library for direct play/streams and a 1080p library for clients that can't do 4k. QuickSync can do more transcodes in general. Plex will always prefer QuickSync even if you have a Nvidia card added.