We have a media transcode operation that runs through a user plugin to perform a DXVA alpha blend. The video pipeline is similiar to this:
RTSP Unwrap -> Decode -> Alpha Blend -> VPP Colorspace conversion -> Encode -> FFMpeg container with segmentation
This pipeline has run for multiple weeks at a time (using an RTSP 1080p/60 h.264 camera) on the May video driver (build 3621). However recently we have tried using the newer graphics drivers (August, as well as the latest version from 10/3/14 -- 3960). After about an hour or transcoding the video gets heavily corrupted. There are many updates to the graphics driver which we would like to take advantage of however this corruption is forcing us to stay on build 3621.
Has anyone experienced issues with the Media SDK on new graphics drivers?
Thanks in advance,
We have many changes from Driver build 3621 -> Build 3960. So we need more information about the platform to root cause the corruption issue you are seeing with Build 3960, If you can send us the logs from these tools. I will be able to further look into the issue and update you with further information.
Thank you for the logs. We are not able reproduce the issue from the tracer logs using the same pipeline on our side. Can you please provide us more info on the application you are using or a package that will help us reproduce the issue you are seeing. You can send me your package using PM.
Let us know which application are you using if it is samples or tutorials. In general, we recommend you to use our samples and tutorials to reproduce the issue. Let us know if you can reproduce the issue you are seeing with driver Build ->3960 with the samples/tutorials. This information will help us further look into the issue.
Will do, this is with a custom application so I will need to make a smaller application to replicate it so I can transfer it. The samples do not take a continuous video stream so are not conducive to replicate the issue (they all work on a file).
I will get a suitable repro and post it in the next week.
Following up on this issue- Are you still seeing the same behavior? There has been many bug fixes in the driver,you might want to update to the latest driver and check.