Following previous post on AMD hardware video encoders, this shows how better NVIDIA hardware is in comparison. And they sell successor hardware series already!
// Oprogramowanie Roman Ryltsov
Following previous post on AMD hardware video encoders, this shows how better NVIDIA hardware is in comparison. And they sell successor hardware series already!
AMD is not seemingly making any progress in improving video encoding ASICs on their video cards. New stuff looks pretty depressing. AMD Radeon RX 5700 XT was a bit of a move forward, a bit. New series look about the same but even slower a bit, however it is quite clear that existing cheaper NVIDIA…
I was under impression that AMD hardware allows just one video encoding session and prevents from having multiple side by side. This has been the consistent behavior I was seeing and I was always wondering why it had to be that tight. To my surprise, the actual limitation is higher and, in particular, is sixteen…
Quite a number of AMD GPU based video cards are running outdated drivers for such modern task as low latency game streaming, and users have no clue that the video driver is letting them down. For example, a slice of version structure for those who “have things going rather well”: Current recommended (“stable”?) version is…
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…
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…
A few weeks ago I posted a problem with AMF SDK about a property included into enumeration and triggering a failure in a followup request for value. It appeared to be “internal property” to intentionally tease the caller and report error by design, unlike all other dozens of SDK properties. And of course to raise…