HEVC decoder exception

[Rob45_]

Hello,

I am unable to decode this HEVC stream from a Panasonic camera, other camera's work.

It generates an exception for every frame.

Best regards,

Robert

[Rob45_]

Using :

               sample_decode.exe h265 -i panasonic.265 -o out1.yuv -sw

I see the h265_exception for every frame, is there a way to find out what is wrong?

I see it only for Panasonic CCTV camera streams, Axis, Bosch, Dahua work fine.

I think it has something to do with the SPS scaling_list, since thats the only difference i can see with the other camera's.

Exception thrown at 0x00007FF8FE0A4F99 in sample_decode.exe: Microsoft C++ exception: UMC_HEVC_DECODER::h265_exception at memory location 0x000000F3EB8FB080.

plugin_loader.h :185 [INFO] Plugin was loaded from GUID: { 0x15, 0xdd, 0x93, 0x68, 0x25, 0xad, 0x47, 0x5e, 0xa3, 0x4e, 0x35, 0xf3, 0xf5, 0x42, 0x17, 0xa6 } (Intel (R) Media SDK plugin for HEVC DECODE)
pretending that aspect ratio is 1:1
Decoding Sample Version 8.4.27.0

Input video HEVC
Output format NV12
Input:
Resolution 1920x1088
Crop X,Y,W,H 0,0,1920,1080
Output:
Resolution 1920x1080
Frame rate 30.00
Memory type system
MediaSDK impl sw
MediaSDK version 1.34

Decoding started
Frame number: 0, fps: 0.000, fread_fps: 0.000, fwrite_fps: 0.000
Decoding finished

I see the same error on an other machine with these specifications,

Windows 10 Pro, 21H1,19043.1288

Intel i9-11900K

UHD Graphics 750, SDK:1.35.65571, DRV:30.0.100.9955

[Rob45_]

sample_decode.exe h265 -i panasonic.265 -o out1.yuv -sw

Exception thrown at 0x00007FF8FE0A4F99 in sample_decode.exe: Microsoft C++ exception: UMC_HEVC_DECODER::h265_exception at memory location 0x000000F3EB8FB080.

I see the same error on an other machine with these specifications,

Windows 10 Pro, 21H1,19043.1288

Intel i9-11900K

UHD Graphics 750, SDK:1.35.65571, DRV:30.0.100.9955

[RahulU_Intel]

Hi,

Thanks for posting in Intel communities. We looked into your case. Could you please share with us below details which will help us resolve your issue

1) Version of Media SDK

2) OS details

3) Screenshot of the errors

4) Commands you are using

Thanks and Regards

Rahul

[Rob45_]

Thanks Rahul, for looking into my problem,

1) Version of Media SDK: 1.35.65571

2) OS details: Windows 10 Pro, 21H1,19043.1288 with Intel driver: 30.0.100.9955, Intel i9-11900K UHD Graphics 750

3) Screenshot of the errors: see attached jpg

4) Commands you are using:  using the intel sample:   sample_decode.exe h265 -i panasonic.265 -o out1.yuv -sw

Visual Studio 16.11.5

[RahulU_Intel]

Hi,

We could reproduce your issue while running this sample with "-sw" option. We don't observe it when we remove that option or replace "-hw" option. Sample decode works with hardware implementation as well. So, we have provided a command below for sample decode example. Please check with the below command and let us know if it works or not. Also, regarding the error with software implementation, we are checking on this internally. we will get back to you with an update.

sample_decode.exe h265 -i panasonic.265 -o output.yuv

Thanks and Regards

Rahul

[Rob45_]

Thanks Rahul,

Sorry for the duplicate posts, i had problems passing the intel spam filter.
Using hardware decoding i have the same type of errors, see screenshot.

Best regards,

Robert

[RahulU_Intel · Accepted solution]

Hi,

We tried reproducing your issue and we observed that there's no issue with Decode sample in MediaSDK. It seems like the input file which you have attached is corrupted. To confirm this we have analyzed your input file using ffprobe (ffprobe tool from ffmpeg gathers information from multimedia streams and prints it in human- and machine-readable fashion) command :

ffprobe panasonic.265

We have attached the screenshot below. If you are not a ffmpeg user, you can install it from this link (https://ffmpeg.org/download.html).

Regards,

Rahul

[Rob45_]

Thank you very much Rahul,

I will have a look to ffprobe, and check our RTSP code where it went wrong.

Best regards, Robert

[RahulU_Intel]

Hi,

Thanks for accepting our solution. If you need any additional information, please post a new question as this thread will no longer be monitored by Intel.

Thanks and Regards

Rahul