With the 2.0 version of SDK, we make a step forward and release a final version of the gpu_pipeline feature.
Now we can process all SDK scenarios with the power of NVidia, Intel or AMD GPU cards.
Gpu pipeline should work fine with all Windows versions older than Windows 7. Unfortunately, Windows 7 doesn't support all DirectX 11 features[reference].
What features are processing with GPU pipeline?
All. Include preview, conversion, scaling, Chroma Keying, CG, HTML5.
How to turn on GPU pipeline?
//We need to turn on this property before you create any other SDK objects.
myFactory = new MFFactoryClass();
You can also choose the graphic card which will be used for the gpu_pipeline with the gpu.index property, where 0 is an active one.
Starting from 184.108.40.20627 we also added the new way to handle the mp:// link and MFSinkSources in GPU pipeline mode
gpu.copy_on_external_receive = false
We advise enabling this option if your current app has a lot of mp://links or MFSinkSources, and you are using GPU pipeline with gpu.copy_on_external_receive=true mode we can reduce the GPU memory usage.
GPU pipeline and GPU decoding.
At this moment, because of architecture aspects, we need to separately turn on the GPU decoding even if the GPU pipeline feature is active. How to do it you can, we wrote in this article: GPU-powered decoding