#Quicksync h.264 windows 10

Important property of hardware encoder is that even that it does consume some of CPU time, the most of the complexity is offloaded to video hardware. IntelÂ® Quick Sync Video H.264 Encoder MFT CODECAPI_AVEncCommonRateControlMode: VT_UI4 0, default VT_UI4 0, modifiable // eAVEncCommonRateControlMode_CBR = 0ĬODECAPI_AVEncCommonQuality: minimal VT_UI4 0, maximal VT_EMPTY, step VT_EMPTYĬODECAPI_AVEncCommonBufferSize: VT_UI4 3131961357, default VT_UI4 0, modifiableĬODECAPI_AVEncCommonMaxBitRate: default VT_UI4 0ĬODECAPI_AVEncCommonMeanBitRate: VT_UI4 3131961357, default VT_UI4 2222000, modifiableĬODECAPI_AVEncCommonQualityVsSpeed: VT_UI4 50, default VT_UI4 50, modifiableĬODECAPI_AVEncH264CABACEnable: modifiableĬODECAPI_AVEncMPVDefaultBPictureCount: VT_UI4 0, default VT_UI4 0, modifiableĬODECAPI_AVEncMPVGOPSize: VT_UI4 128, default VT_UI4 128, modifiableĬODECAPI_AVEncVideoForceKeyFrame: VT_UI4 0, default VT_UI4 0, modifiableĬODECAPI_AVLowLatencyMode: VT_BOOL 0, default VT_BOOL 0, modifiableĬODECAPI_AVEncVideoLTRBufferControl: VT_UI4 65536, values ĬODECAPI_AVEncVideoEncodeFrameTypeQP: VT_UI8 111670853658ĬODECAPI_AVEncSliceControlMode: VT_UI4 2, minimal VT_UI4 0, maximal VT_UI4 2, step VT_UI4 1ĬODECAPI_AVEncSliceControlSize: VT_UI4 0, minimal VT_UI4 0, maximal VT_UI4 3, step VT_UI4 1ĬODECAPI_AVEncVideoMaxNumRefFrame: VT_UI4 1, minimal VT_UI4 0, maximal VT_UI4 16, step VT_UI4 1ĬODECAPI_AVEncVideoMeanAbsoluteDifference: VT_UI4 0ĬODECAPI_AVEncVideoMaxQP: VT_UI4 51, minimal VT_UI4 0, maximal VT_UI4 51, step VT_UI4 1ĬODECAPI_AVEncVideoTemporalLayerCount: minimal VT_UI4 1, maximal VT_UI4 3, step VT_UI4 1 Not just bitrate, profile, GOP length, B frame settings but even more sophisticated parameters. Either way, both encoders have a number of ways to fine tune the encoding process. NVIDIA H.264 Encoder produces somewhat better output supposedly by choosing higher bitrate. IntelÂ® Quick Sync Video H.264 Encoder produces files like these: 720×480.mp4, 2556×1440.mp4, which are of decent quality (with respect to low bitrate and “hard to handle” background changes). Test runs are as simple as taking reference video source signal of different properties, pushing it through encoder filter and either writing to a file (to inspect the footage) or to Null Renderer Filter to measure performance. Still the pictures do show that both encoders are well usable for many scenarios including HD processing, simultaneous data processing etc. The pictures below show metrics for encoder defaults (bitrate, profiles and many other options that create a great deal of encoding modes).

A wrapper over MFT that converts them into DirectShow filters, make them available to DirectShow where it is already way easier to run various test runs. It is not convenient or fun to do things with Media Foundation, but good news is that Media Foundation components are well-separable. Video Adapter 2: NVIDIA GeForce GTX 750.

Video Adapter 1: Intel HD Graphics 4600 (on-board, not connected to monitors).

#Quicksync h.264 windows 10

Out of the box, Windows 10 offers stock software only encoder, and hardware encoders in form factor of Media Foundation Transform (MFT). Some would say it is already time for H.265 encoders.Įither way, on my test machine both encoders are available without additionally installed software (that is, no need for Intel Media SDK, Nvidia NVENC, redistributable files etc.). Both encoders are nothing new: IntelÂ® Quick Sync Video H.264 Encoder and NVIDIA H.264 Encoder already have been around for a while. At this time, it is a turn of hardware H.264 encoders and more to that, two of them and side by side.

Some time ago there were some pictures explaining performance and other properties of software H.264 encoder (x264).