// Oprogramowanie Roman Ryltsov
In continuation of previous AMD AMF encoder latency at faster settings posts, side by side comparison to NVIDIA encoders. The numbers are to show how different they are even though they are doing something similar. The NVIDIA cards are not high end: GTX 1650 is literally the cheapest stuff among Turing 16xx series, and GeForce…
A follow-up observation about encoders of Radeon RX Vega M GH Graphics of Hades Canyon NUC and the measurement app from the previous post: The side by side comparison with desktop RX 570 card shows a few interesting things: Radeon RX Vega M GH Graphics has the latest driver, but AMF runtime version is way…
Just a small tool here to try a few of a popular resolutions and measure video encoding latency. The encoder is running in configuration to address needs of real-time encoding with speed over quality setup. Note that the performance might be affected by side load, such as graphics application (I often use this application for…
It is embarrassing, my friends…
An interesting Media Foundation question on StackOverflow: Weird connection between CoInitializeSecurity() and Media Foundation Encoders A developer has reasons to discard standard COM security and go RPC_C_IMP_LEVEL_ANONYMOUS. Surprisingly this has effect on Windows Media Foundation API in the part of available codecs (Media Foundation Transforms). Sample code: CoInitializeSecurity line in the code above removes the…
GPU NVIDIA GeForce GTX 1080 Ti NVIDIA GeForce GTX 1660 Ti Microarchitecture Pascal Turing H.264 NV_ENC_CAPS_SUPPORT_FIELD_ENCODING Yes No H.264 NV_ENC_PRESET_HP_GUID entropyCodingMode NV_ENC_H264_ENTROPY_CODING_MODE_CAVLC NV_ENC_H264_ENTROPY_CODING_MODE_CABAC H.265/HEVC NV_ENC_CAPS_NUM_MAX_BFRAMES 0 5 H.265/HEVC NV_ENC_CAPS_SUPPORT_TEMPORAL_AQ No Yes Apart from the capabilities, a whitepaper mentions these H.265/HEVC improvements: Turing GPUs also ship with an enhanced NVENC encoder unit that adds support for…
Another problem (bug) with Microsoft Media Foundation MPEG-4 Media Source H.265/HEVC handler is that it ignores conformance_window_flagflag and values from H.265’s seq_parameter_set_rbsp (see H.265 spec, F.7.3.2.2.1 General sequence parameter set RBSP syntax). The problem might or might not be limited to fragmented MP4 variants. It is overall questionable whether it has been a good idea…