This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(38.4, 94%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EG%3C/text%3E%3C/svg%3E)
Hi,
I'm currently developing a streaming application with HW-Acceleration for Windows, so far everything works fine but using DXVA2 hw accerlation the decoder has problem to decode certain keyframes. I searched for a long time on the internet already but could not find any solution to my problem. I'm using ffmpeg and the reason for not be able to decode that video slice is because the buffer returned from the IDirectXVideoDecoder_GetBuffer function was too small
this is where the error is occurs
I found a question in regards a similar problem but it was never answered. The problem is not present when using a software decoder, D3D11VA or cuda hw acceleration. I attach her the hex value of the key frame here (with sps and pps prepended).
I can compile ffmpeg and could start playing around with it, but I have absolutely no idea what factors the returned buffer size depends on. Is this a limitation of the DXVA2 decoder in general? Are there any settings which one must provide to the decoder so it will be able to deal with larger frame slices? I'm a little bit lost here and if I could get some inputs here of what I can try I would really appreciate that.
If necessary I can provide a minimal reproducable example although I have to admit that I use javacv bindings to the native ffmpeg functions.
What typical size and dxva_size did you observe in case of DXVA2 and D3D11VA for the same problematic keyframe?
@Viorel I patched the ffmpeg version I use with additional logs and when it fails I print out the sizes. According to these logs I receive following output
Buffer for type 5 was too small. size: 58752, dxva_size: 55296
D3D11VA doesn't fail on that frame so I do not receive the information
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(179.20000000000002, 34%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EXY%3C/text%3E%3C/svg%3E)
Hello @Grill2010 , could you please show a minimal, reproducible sample without private information?
This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
I have tried 3 times now to provide an example but my answer automatically gets deleted within half an hour automatically. I will try one more time below this post
As I already said I use javacv for my project, it uses ffmpeg 6.0 internally. There is just one patch in place in the native bundled ffmpeg lib which t is relevant to reproduce the issue (or otherwise you would get a different error because of too much slices). The patch is that MAX_SLICES in h264dec.h was increased to 256.
The project can be found here.
If you just want the native lib you can just unzip the ffmpeg-6.0-1.5.9-SNAPSHOT-windows-x86_64 jar file inside the lib folder of my project. You can build it via .\gradlew build and to run it just use .\gradlew run. Java 17 must be installed on your machine in order to run the project.
If the test frame in the recources could be decoded successfully it will print out
"SUCESS with HW decoding"
or otherwise
"Error on decoding test frame..."
The hardware decoder can be changed by changing this variable "HW_DEVICE_TYPE"
Does the thread https://stackoverflow.com/questions/34602561/failed-to-execute-0x80070057-when-decoding-video-via-ffmpeg-with-dxva2 work for you?
@Xiaopo Yang - MSFT In my opinion I initialise the AvPacket and all it's sizes correctly
As it works with other decoder I don't think this is the root cause of the problem?
@Xiaopo Yang - MSFT I tried now on a 3rd test device a Surface with Intel GPU and to my surprise it my example works perfectly fine there. No issues with DXVA2? Could this be a Nvidea driver problem or a Windows problem in combination with Nvidea GPUs? This is definitely not normal behaviour and I'm curious what's the root cause of the problem.
Hello @Grill2010, it could be a NVIDIA driver problem. There is No issues with DXVA2. I haven't found others report such DXVA2 hardware decoder issue.