Video playback stuck at opening and does not recover

[simonebarattin]

Good morning,

I'm having an issue with the AMC SDK. I'm developing a streaming application in C#, which shows the live stream of 5 different cameras and allows then the user to record and playback the videos.

Everything works, but something strange happens after some time of using the playback function. Basically if I give the command play and stop in rapid sequence, at least one of the 5 displays stops working. I have a listener on the status change that shows a loading screen, and what happens in the "faulty" AMC instance is that it stays in the status AMC_STATUS.AMC_STATUS_OPENING, while the others correctly load and start playing the videos.
I tried looking for possible causes in the code but couldn't really find anything.
What I did was work around the problem: whenever I have a timeout on the loading I hard-reset the 5 AMC displays. This solution seemed to work at first, after having the timeout the displays resetted as intended and started playing the videos normally.
With resetting I mean removing the control, instantiating it again, and loading it back in the graphic.

However, when I tested the solution on a bigger screen (meaning bigger Axis displays) the solution did not work anymore. What happens is that the faulty class, even after resetting it, stayed in the "OPENING" status and after trying to play other files the problem spreads to the other 4 classes as well. Also, If I continue trying to reset and play different videos, the Axis classes reach a point where they stay in status 0.
I don't really understand what could be the cause of the problem.. is it a bug on my side? the things that I dont understand is that my "workaround" stopped working after the displays got bigger, does this mean it's a renderer problem?

FYI: the cameras are 5 AXIS F2135-RE Fisheye Sensor connected to 2 AXIS F9114 Main Unit. The version of the firmware is the latest and the same goes for the SDK version (7.52). The files I play are the ones I obtain untouched from the recording (.asf videos)

Thank you for your support. Regards,
Simone

[github-actions[bot]]

This automatically generated reply acts as a friendly reminder.

Answers to your questions will most often come from the community, from developers like yourself. You will, from time to time, find that Axis employees answers some of the questions, but this is not a guarantee. Think of the discussion forum as a complement to other support channels, not a replacement to any of them.

If your question remains unanswered for a period of time, please revisit it to see whether it can be improved by following the guidelines listed in Axis support guidelines.

[vivekatoffice]

Hi @simonebarattin ,
As Rocky Ji suggested here, you can try updating the Axis OS.

[simonebarattin]

Yes I will try to create a small sample that recreates the problem, thank you.

In the meantime,

try to check if the other status codes can be used to refresh only those controls that have already started

you mean that I can force a status on a specific instance? Or are you asking what is the status of the other AMC instances?

[vivekatoffice]

No, we can't force a status but may use it to perform different operations.

[simonebarattin]

Could you provide an example of some operations that I could perform? For the moment what I'm doing is taking every instance of Axis and resetting it like this

this.pnlContentCamera.Controls.Remove(this.videoView);
System.ComponentModel.ComponentResourceManager resources = new System.ComponentModel.ComponentResourceManager(typeof(FormDisplay));

this.videoView = new AxAXISMEDIACONTROLLib.AxAxisMediaControl();
this.videoView.Dock = System.Windows.Forms.DockStyle.Fill;
this.videoView.Enabled = true;
this.videoView.Location = new System.Drawing.Point(0, 0);
this.videoView.Name = "videoView";
this.videoView.OcxState = ((System.Windows.Forms.AxHost.State)(resources.GetObject("videoView.OcxState")));
this.videoView.Size = new System.Drawing.Size(1140, 719);
this.videoView.TabIndex = 0;

((System.ComponentModel.ISupportInitialize)(this.videoView)).EndInit();
this.pnlContentCamera.Controls.Add(this.videoView);

After I do that, the faulty components are still in status OPENING, and for the working ones after some time (after resetting) they go from OPENING to INITIALIZED, like there is an ongoing process that is not disposed when I reset the component. Maybe that's the problem?

[vivekatoffice]

Hi @simonebarattin ,
I meant to use it like the following as mentioned in the doc file:

AMC has successfully started playing a stream or file when the status property value includes the AMC_STATUS_FLAG_PLAYING but not the AMC_STATUS_FLAG_OPENING flag.

For example, if a media stream is simultaneously being played and recorded, the value of the Status property will be 1035 (AMC_STATUS_INITIALIZED + AMC_STATUS_FLAG_PLAYING + AMC_STATUS_FLAG_RECORDING + AMC_STATUS_FLAG_EXTENDED_TEXT).

To check if a flag is active, use a bitwise AND operator. For example, in C#:

if ((amc.Status & (int)AMC_STATUS.AMC_STATUS_PLAYING) > 0 && // is playing
    (amc.Status & (int)AMC_STATUS.AMC_STATUS_OPENING) == 0) // is not opening 
{
  System.Diagnostics.Trace.WriteLine("now playing");
}

[simonebarattin]

To check if it is done loadin the video, after initializing the classes I subscribe the OnStatusChange to an event handler

_acmEngine = new AxisControlMediaEngine(videoView, logName);
if (!IsLive)
    _acmEngine._amcEngine.OnStatusChange += OnStatusChangeEventHandler;

defined like this

private void OnStatusChangeEventHandler(object sender, _IAxisMediaControlEvents_OnStatusChangeEvent e)
{
    long newStatus = e.theNewStatus;
    long prevStatus = e.theOldStatus;

    lock (_lockObject)
    {
        if ((newStatus & (int)AMC_STATUS.AMC_STATUS_OPENING) == 0)
        {
            if ((prevStatus & (int)AMC_STATUS.AMC_STATUS_OPENING) > 0)
            {
                frmLoading.HideLoading();
                VideoLoaded?.Invoke();
            }
        }

        if ((newStatus & (int)AMC_STATUS.AMC_STATUS_OPENING) > 0)
        {
            if (nOpenFiles == 0)
            {
                frmLoading.ShowLoading();
                VideoLoading?.Invoke();
            }
        }
    }
}

What happens when the problem occurs is that the faulty instance never goes in the first if statement, meaning that the opening flag is still on. If I try to print the status code I get constantly the status 19, which should be AMC_STATUS_INITIALIZED + AMC_STATUS_OPENING + AMC_STATUS_FLAG_PLAYING.
In this case the other displays start playing the video, while the faulty doesn't show anything.
I also enabled the status bar to check if there was any additional info, but it just displays "Opening >>>>>>"

[fre3de]

Hi,

Are you using the default renderer, EVR? You could try with VMR9 and see if that makes a difference.
AMV. VideoRenderer = 0x10000 for EVR. 0x1000 is VMR9.

Run the attached Axdiag.exe.
AxDiag.zip

1. Open the attached Axdiag.exe
2. Right click on "Axis Media Control SDK Components x64" and select "Enable all logging".
3. Reproduce the problem.
4. Right click again and select "Save Logs..."
5. Attach the log files.

Also, when one instance is stuck in opening. Locate the process in Windows task manager. Right click on the process and select Create memory dump file. Share the dumpfile.

Best regards
Fredrik

[simonebarattin]

Hello @fre3de,

Yes I am using the VMR9 renderer, as I noticed that with the EVR I have worst performances.
_acmEngine.VideoRenderer = (int)AMC_VIDEO_RENDERER.AMC_VIDEO_RENDERER_VMR9;

Thank you for the diagnostic tool! I attach the log files, the problem occured at the end of it:
AXIS_Media_Control_SDK_Components_x64_Logs_25-10-2024_13-51-08.zip

About the process dump, you mean I should send the dump of the whole application or of the single process of the media playing (if this is the case, how can I find the process of direct show?)

Thank you, best regards

[fre3de]

Hi,
Thanks for the log file.
I tried to reproduce this problem and if I run 20 amc instances and recreate them at every play stop I can reproduce a deadlock. But only when I use vmr9, not with EVR.
Does your recording only have video or audio too?

If you dump the main process, I can open the dump and see where the deadlock has occured. Seems likely though that it, like in my case, has deadlock in quartz.dll which is Directshow.

We have noticed that VMR9-renderer has problems to render high resolution. That's why we changed to EVR as default renderer in AMC What kind of problems do you get with EVR?

[fre3de]

I had a look at the dmp-file but it's hard to figure out where it's stuck. I think it can be easier to fix the crash you get when using EVR.
The crash seems to happen in the h265-decoder. Can you check if there is a crash dump in C:\ProgramData\Axis Communications\Components\CrashDumps
If you run h264 instead, do you get the same crash? Are you using hw-decoding? If you do, try with H265EnableHWDecoding = false.

[simonebarattin]

Hi @fre3de, ok I understand, then I will try to fix the program with EVR, thank you. Let's say though that the deadlock is in quartz.dll like in your case, what could I do to avoid the problem?

I checked for the crash dump but there was nothing in the folder except for the logs that were saved after using the diagnostic tool.
I have yet to try using h264 as the live+recording feed of 5 cameras simultaneusly gets a bit laggy with it and h265 gives a smoother live. If the problem with h265 persists I will switch to that.

So I changed to EVR and set H265EnableHWDecoding = false and now in my PC the problem seems to be gone. But when I tested the application on another PC the application started to crash as soon as I started playing a video. On this second PC I installed the AxisMediaControl SDK, and from its folder all the decoders form the redistX64 folder. Am I missing some packages? What does the software decoding need in order to work properly? The difference is that in the PC where it works I have a GPU and not in the other, but if I'm using sw-decoding that should not matter right?

The following is the log of the H265 decoder, it stops when it crashed

Log File (#0)
10/30/24 11:41:24.698 H265Dec:_:[1] - Constructor - H.265 Video Decoder initializing
10/30/24 11:41:24.699 H265Dec:_:[1] - ImageRotation - Rotate image 0 degrees
10/30/24 11:41:24.699 H265Dec:_:[1] - IAxVerify::SetEnableDataVerification - FALSE
10/30/24 11:41:24.763 H265Dec:_:[2] - Constructor - H.265 Video Decoder initializing
10/30/24 11:41:24.764 H265Dec:_:[2] - ImageRotation - Rotate image 0 degrees
10/30/24 11:41:24.764 H265Dec:_:[2] - IAxVerify::SetEnableDataVerification - FALSE
10/30/24 11:41:24.821 H265Dec:_:[3] - Constructor - H.265 Video Decoder initializing
10/30/24 11:41:24.824 H265Dec:_:[3] - ImageRotation - Rotate image 0 degrees
10/30/24 11:41:24.824 H265Dec:_:[3] - IAxVerify::SetEnableDataVerification - FALSE
10/30/24 11:41:24.878 H265Dec:_:[4] - Constructor - H.265 Video Decoder initializing
10/30/24 11:41:24.879 H265Dec:_:[4] - ImageRotation - Rotate image 0 degrees
10/30/24 11:41:24.879 H265Dec:_:[4] - IAxVerify::SetEnableDataVerification - FALSE
10/30/24 11:41:24.933 H265Dec:_:Media subtype: 'HEVC'
10/30/24 11:41:24.933 H265Dec:_:Media subtype: 'HEVC'
10/30/24 11:41:24.934 H265Dec:_:[5] - Constructor - H.265 Video Decoder initializing
10/30/24 11:41:24.934 H265Dec:_:[5] - ImageRotation - Rotate image 0 degrees
10/30/24 11:41:24.934 H265Dec:_:[5] - IAxVerify::SetEnableDataVerification - FALSE
10/30/24 11:41:24.983 H265Dec:_:Media subtype: 'HEVC'
10/30/24 11:41:24.983 H265Dec:_:Media subtype: 'HEVC'
10/30/24 11:41:25.018 H265Dec:_:[1] - Quality Control - Disabled
10/30/24 11:41:25.020 H265Dec:_:Media subtype: 'HEVC'
10/30/24 11:41:25.025 H265Dec:_:[1] - InitDecoder - Starting FFMPEG software mode
10/30/24 11:41:25.025 H265Dec:_:Decoder initialized with 1 thread(s).
10/30/24 11:41:25.025 H265Dec:_:Detected SSE41 feature: 1
10/30/24 11:41:25.037 H265Dec:_:Media subtype: 'HEVC'
10/30/24 11:41:25.037 H265Dec:_:Media subtype: 'HEVC'
10/30/24 11:41:25.070 H265Dec:_:[2] - Quality Control - Disabled
10/30/24 11:41:25.072 H265Dec:_:Media subtype: 'HEVC'
10/30/24 11:41:25.091 H265Dec:_:[2] - Quality Control - Disabled
10/30/24 11:41:25.092 H265Dec:_:Media subtype: 'HEVC'
10/30/24 11:41:25.092 H265Dec:_:[1] - Quality Control - Enabled. Drop threshold: 500 ms
10/30/24 11:41:25.098 H265Dec:_:Media subtype: 'HEVC'
10/30/24 11:41:25.098 H265Dec:_:Media subtype: 'HEVC'
10/30/24 11:41:25.266 H265Dec:_:[3] - Quality Control - Disabled
10/30/24 11:41:25.268 H265Dec:_:Media subtype: 'HEVC'
10/30/24 11:41:25.275 H265Dec:_:[3] - InitDecoder - Starting FFMPEG software mode
10/30/24 11:41:25.275 H265Dec:_:Decoder initialized with 1 thread(s).
10/30/24 11:41:25.275 H265Dec:_:Detected SSE41 feature: 1
10/30/24 11:41:25.293 H265Dec:_:Media subtype: 'HEVC'
10/30/24 11:41:25.293 H265Dec:_:Media subtype: 'HEVC'
10/30/24 11:41:25.331 H265Dec:_:[3] - Quality Control - Enabled. Drop threshold: 500 ms
10/30/24 11:41:25.338 H265Dec:_:[4] - Quality Control - Disabled
10/30/24 11:41:25.339 H265Dec:_:Media subtype: 'HEVC'
10/30/24 11:41:25.350 H265Dec:_:[4] - InitDecoder - Starting FFMPEG software mode
10/30/24 11:41:25.350 H265Dec:_:Decoder initialized with 1 thread(s).
10/30/24 11:41:25.350 H265Dec:_:Detected SSE41 feature: 1
10/30/24 11:41:25.370 H265Dec:_:[4] - Quality Control - Enabled. Drop threshold: 500 ms
10/30/24 11:41:26.935 H265Dec:_:[5] - Quality Control - Disabled
10/30/24 11:41:26.939 H265Dec:_:Media subtype: 'HEVC'
10/30/24 11:41:26.948 H265Dec:_:[4] - Quality Control - Timestamp deviation: 1448 (1448, 1448) ms, Decoding speed: 0.0 (0), Decoded: 4 (2.6 fps), Dropped: 0 (I:0; P:0)
10/30/24 11:41:26.948 H265Dec:_:[5] - InitDecoder - Starting FFMPEG software mode
10/30/24 11:41:26.948 H265Dec:_:Decoder initialized with 1 thread(s).
10/30/24 11:41:26.948 H265Dec:_:Detected SSE41 feature: 1
10/30/24 11:41:26.963 H265Dec:_:[1] - Quality Control - Timestamp deviation: 1382 (1382, 1382) ms, Decoding speed: 0.0 (0), Decoded: 13 (7.0 fps), Dropped: 0 (I:0; P:0)
10/30/24 11:41:26.969 H265Dec:_:[3] - Quality Control - Timestamp deviation: 1388 (1388, 1388) ms, Decoding speed: 0.0 (0), Decoded: 7 (4.3 fps), Dropped: 0 (I:0; P:0)
10/30/24 11:41:26.000 H265Dec:_:[5] - Quality Control - Enabled. Drop threshold: 500 ms
10/30/24 11:41:28.572 H265Dec:_:[5] - Quality Control - Timestamp deviation: 1445 (1445, 1445) ms, Decoding speed: 0.0 (0), Decoded: 4 (2.6 fps), Dropped: 0 (I:0; P:0)
10/30/24 11:43:32.380 H265Dec:_:[1] - Constructor - H.265 Video Decoder initializing
10/30/24 11:43:32.380 H265Dec:_:[1] - ImageRotation - Rotate image 0 degrees
10/30/24 11:43:32.380 H265Dec:_:[1] - IAxVerify::SetEnableDataVerification - FALSE
10/30/24 11:43:32.440 H265Dec:_:[2] - Constructor - H.265 Video Decoder initializing
10/30/24 11:43:32.441 H265Dec:_:[2] - ImageRotation - Rotate image 0 degrees
10/30/24 11:43:32.441 H265Dec:_:[2] - IAxVerify::SetEnableDataVerification - FALSE
10/30/24 11:43:32.497 H265Dec:_:[3] - Constructor - H.265 Video Decoder initializing
10/30/24 11:43:32.497 H265Dec:_:[3] - ImageRotation - Rotate image 0 degrees
10/30/24 11:43:32.497 H265Dec:_:[3] - IAxVerify::SetEnableDataVerification - FALSE
10/30/24 11:43:32.553 H265Dec:_:[4] - Constructor - H.265 Video Decoder initializing
10/30/24 11:43:32.553 H265Dec:_:[4] - ImageRotation - Rotate image 0 degrees
10/30/24 11:43:32.553 H265Dec:_:[4] - IAxVerify::SetEnableDataVerification - FALSE
10/30/24 11:43:32.610 H265Dec:_:Media subtype: 'HEVC'
10/30/24 11:43:32.610 H265Dec:_:Media subtype: 'HEVC'
10/30/24 11:43:32.611 H265Dec:_:[5] - Constructor - H.265 Video Decoder initializing
10/30/24 11:43:32.611 H265Dec:_:[5] - ImageRotation - Rotate image 0 degrees
10/30/24 11:43:32.611 H265Dec:_:[5] - IAxVerify::SetEnableDataVerification - FALSE
10/30/24 11:43:32.662 H265Dec:_:Media subtype: 'HEVC'
10/30/24 11:43:32.662 H265Dec:_:Media subtype: 'HEVC'
10/30/24 11:43:32.704 H265Dec:_:[1] - Quality Control - Disabled
10/30/24 11:43:32.705 H265Dec:_:Media subtype: 'HEVC'
10/30/24 11:43:32.710 H265Dec:_:[1] - InitDecoder - Starting FFMPEG software mode
10/30/24 11:43:32.710 H265Dec:_:Decoder initialized with 1 thread(s).
10/30/24 11:43:32.711 H265Dec:_:Detected SSE41 feature: 1
10/30/24 11:43:32.717 H265Dec:_:Media subtype: 'HEVC'
10/30/24 11:43:32.717 H265Dec:_:Media subtype: 'HEVC'
10/30/24 11:43:32.748 H265Dec:_:[1] - Quality Control - Enabled. Drop threshold: 500 ms
10/30/24 11:43:32.756 H265Dec:_:[2] - Quality Control - Disabled
10/30/24 11:43:32.757 H265Dec:_:Media subtype: 'HEVC'
10/30/24 11:43:32.765 H265Dec:_:[2] - InitDecoder - Starting FFMPEG software mode
10/30/24 11:43:32.765 H265Dec:_:Decoder initialized with 1 thread(s).
10/30/24 11:43:32.765 H265Dec:_:Detected SSE41 feature: 1
10/30/24 11:43:32.775 H265Dec:_:Media subtype: 'HEVC'
10/30/24 11:43:32.775 H265Dec:_:Media subtype: 'HEVC'
10/30/24 11:43:32.801 H265Dec:_:[2] - Quality Control - Enabled. Drop threshold: 500 ms
10/30/24 11:43:32.811 H265Dec:_:[3] - Quality Control - Disabled
10/30/24 11:43:32.813 H265Dec:_:Media subtype: 'HEVC'
10/30/24 11:43:32.837 H265Dec:_:[3] - Quality Control - Disabled
10/30/24 11:43:32.838 H265Dec:_:Media subtype: 'HEVC'
10/30/24 11:43:32.838 H265Dec:_:Media subtype: 'HEVC'
10/30/24 11:43:32.838 H265Dec:_:Media subtype: 'HEVC'
10/30/24 11:43:32.989 H265Dec:_:[4] - Quality Control - Disabled
10/30/24 11:43:32.991 H265Dec:_:Media subtype: 'HEVC'
10/30/24 11:43:32.997 H265Dec:_:[4] - InitDecoder - Starting FFMPEG software mode
10/30/24 11:43:32.997 H265Dec:_:Decoder initialized with 1 thread(s).
10/30/24 11:43:32.997 H265Dec:_:Detected SSE41 feature: 1
10/30/24 11:43:33.028 H265Dec:_:[5] - Quality Control - Disabled
10/30/24 11:43:33.030 H265Dec:_:Media subtype: 'HEVC'
10/30/24 11:43:33.044 H265Dec:_:[5] - Quality Control - Disabled
10/30/24 11:43:33.045 H265Dec:_:Media subtype: 'HEVC'
10/30/24 11:43:33.048 H265Dec:_:[4] - Quality Control - Enabled. Drop threshold: 500 ms
10/30/24 11:43:33.050 H265Dec:_:[5] - InitDecoder - Starting FFMPEG software mode
10/30/24 11:43:33.051 H265Dec:_:Decoder initialized with 1 thread(s).
10/30/24 11:43:33.051 H265Dec:_:Detected SSE41 feature: 1
10/30/24 11:43:33.087 H265Dec:_:[5] - Quality Control - Enabled. Drop threshold: 500 ms
10/30/24 11:43:34.639 H265Dec:_:[5] - Quality Control - Timestamp deviation: 1383 (1383, 1383) ms, Decoding speed: 0.0 (0), Decoded: 5 (3.2 fps), Dropped: 0 (I:0; P:0)
10/30/24 11:43:34.660 H265Dec:_:[2] - Quality Control - Timestamp deviation: 1370 (1370, 1370) ms, Decoding speed: 0.0 (0), Decoded: 13 (7.0 fps), Dropped: 0 (I:0; P:0)
10/30/24 11:43:34.665 H265Dec:_:[1] - Quality Control - Timestamp deviation: 1388 (1388, 1388) ms, Decoding speed: 0.0 (0), Decoded: 14 (7.3 fps), Dropped: 0 (I:0; P:0)
10/30/24 11:43:34.729 H265Dec:_:[4] - Quality Control - Timestamp deviation: 1431 (1431, 1431) ms, Decoding speed: 0.0 (0), Decoded: 7 (4.2 fps), Dropped: 0 (I:0; P:0)

Thank you

[simonebarattin]

You can find here a small piece of code that reproduces the problem (for both the VMR9 and EVR). Since the problem is relative to the renderer and decoding I guess that in my case it occurs more frequently, as for this application we are using a 5120 x 1440 resolution screen (so with 5 acm instances of 1140x719). I've set this small code to create a form of roughly that size and with that I am able to reproduce quite easly the problem. You can just click the "Play File" button and chose a video repeatedly.
https://drive.google.com/file/d/1RN_vrz4eqKTNOWs2nBDdQN0KakUOc3BK/view?usp=sharing
And the logs of the H265 decoder and Axis Components
AXIS_Media_Control_SDK_Components_x64_Logs_30-10-2024_10-43-41.zip
AXIS_H.265_Video_Decoder_x64_Logs_30-10-2024_10-43-51.zip

[fre3de]

"Let's say though that the deadlock is in quartz.dll like in your case, what could I do to avoid the problem?"
When I got the deadlock I ran a fast play-stop test with 20 AMC instances and AMC was recreated every play stop cycle. Deadlock only happened with VMR9, not with EVR. To recreate AMC shouldn't be needed. It's more safe to just use stop and play again. When I did that I couldn't reproduce a problem.

"I checked for the crash dump but there was nothing in the folder except for the logs that were saved after using the diagnostic tool."
Run the application as admin and see if that makes a difference. If not, you may have to enable crash dumps in the registry:
https://helpx.adobe.com/xd/kb/how-to-generate-crash-dump-on-windows-machine.html

"I have yet to try using h264 as the live+recording feed of 5 cameras simultaneusly gets a bit laggy with it and h265 gives a smoother live."
This is strange. Since h265 compression is more advanced the files are smaller but the decoding requires more resources compared to h264. Could be if the file transfer, e.g over slow network, makes the video jerky.

"But when I tested the application on another PC the application started to crash as soon as I started playing a video"
Can you show the anc log file from this computer? Any crash dump?

"Am I missing some packages? What does the software decoding need in order to work properly?"
The redist +decoder is enough.
Could be that the computer is missing EVR. Can you run windows media player legacy on that computer? It also uses EVR for rendering.

I have attached another test application that you can try on your system. It can be used to playback files and you can specify how many amc instances that should be created for each file. You can run play stop tests and also select to recreate AMC if you want to but I recommend to not do that in your application. Under settings tab you can select video renderer, evr is default.
There are 3 checkboxes to the right under cameras (they have tooltip). The middle one is to enable hw-decoding
Check that you can reproduce the problem with this test-application.

Just to summarize where we are:
Computer 1: H265 playback works with EVR and hardware decoding disabled. Crash with hw-decoding enabled: What graphics card in this computer?
Computer 2: Nothing works. Check if WMP can playback the asf files.

[simonebarattin]

Could be if the file transfer, e.g over slow network, makes the video jerky

Yes that is the problem. The bandwidth is very limited, that's why I need to use the best compression possible.

Can you show the anc log file from this computer? Any crash dump?

The two logs I attached were from the second PC. I will attach here updated ones, though having a quick look does not seem to show any error. Also, I enabled the saving of crash dumps. I attach that as well here https://drive.google.com/file/d/1bYWFvNJsiH8IxC1aQBAV1N_P3CiBH0xA/view?usp=sharing
AXIS_H.265_Video_Decoder_x64_Logs_30-10-2024_10-43-51.zip
AXIS_Media_Control_SDK_Components_x64_Logs_30-10-2024_10-43-41.zip

Can you run windows media player legacy on that computer?

I tried running the .asf files with WMP legacy, and everythign works normally (I am able only to play one instance at a time)

I have attached another test application that you can try on your system

I can't seem to find it, maybe it was too large. Could you send it again? Maybe a download link will work. Thank you

Computer 1: H265 playback works with EVR and hardware decoding disabled. Crash with hw-decoding enabled: What graphics card in this computer?
Computer 2: Nothing works. Check if WMP can playback the asf files.

Correct. The computer has a RTX A500. And correct - WMP can playbac the files

[fre3de]

Sorry, I just forgot to attach the AMCTestTool file, it should be attached now.
The good news is that the dmp-file does show a crash in the h265-decoder (same crash could potentially happen in h264 too). I have attached a new h265 decoder, version 7.1.1.0, which should solve this crash.
Try with this decoder and we'll see where that takes us.
AMCTestTool.zip
Uploading AxisH265DecoderSetupX64.zip…

[simonebarattin]

Ok great! Thank you @fre3de for the tool and for the new decoder!
Sorry, could you check the attachment of the decoder? The link just takes me to the page of this discussion but no download starts. In the meantime I'll try the tool you sent

[fre3de]

I uploaded the decoder on wetransfer instead: https://we.tl/t-RB0To9idBO

[simonebarattin]

Amazing! I updated the decoder with the one you sent and started testing with my application and now it seems to work without problems when using EVR!
I will stress test it with the last tool you provided and let you know if other problems occur, but so far it seems to work correctly.
Thank you @fre3de