mpc-hc
mpc-hc copied to clipboard
clsid2
MPC-HC Timeout when closing filter graph.
So every time I want to close or open up another video file on MPC-HC it opens up another player right before the currently used player closes. Then the screenshot below pops up before the new video is about to play on the newly opened player.
For the "Open options" under Player tab, I have the "Use the same player for each media file" dot ticked.
How can I prevent this from happening all the time? Is there an option somewhere I'm supposed to change?
You can avoid the problem by disabling the option to show video preview on the seekbar.
The cause of the closing delay is unknown. It seems to happen only for a small group of people. I am unable to reproduce it.
It might be related to your graphics driver.
There was another user where it happend only with AMD driver 24.9.1 and 24.10.1, but was working good with 24.8.1.
You can avoid the problem by disabling the option to show video preview on the seekbar.
The cause of the closing delay is unknown. It seems to happen only for a small group of people. I am unable to reproduce it.
I notice that if I untick the option you mentioned "show video preview" along with "show time" I haven't seen the timeout window popup. Before I did it with just unticking the "show video preview" and I was still getting the popup.
The way it happens for me is if you're in the middle of a video and pause and then click on another video to open and play, another new mpc-hc player opens and the previous stays hanging until the timeout popup window shows asking you if you want to close the player or leave it open and wait 15 seconds for it to start playing the new video. Sometimes I had both media players loading and playing the same video together.
So there's no fix for this issue yet?
Yes, the fix is to install a different graphics driver as mentioned above. The cause of the problem is outside of the player. So I am not able to fix it.
Ah okay. I can't install a different graphics card on this pc so I'm out of luck but at least I know the two options to uncheck if I want to get rid of the yes/no popup window.
Not a different GPU, but a different driver version for it.
Everyone who has this problem should at least mention which GPU and driver they have.
Not a different GPU, but a different driver version for it.
Everyone who has this problem should at least mention which GPU and driver they have.
Where can I find this information about my GPU and it's drivers at?
Okay, thanks. Here you go...
MPC-HC (64-bit)
Build information: Version: 2.3.9.4 (ba9da2134) Build date: Dec 27 2024
LAV Filters: LAV Splitter: 0.79.2.20 LAV Video: 0.79.2.20 LAV Audio: 0.79.2.20 FFmpeg compiler: MinGW-w64 GCC 13.3.0
Operating system: Name: Windows 10 (Build 22H2) Version: 10.0.19045 (64-bit)
Hardware: CPU: Intel(R) Core(TM) i3-8100 CPU @ 3.60GHz GPU: Intel(R) UHD Graphics 630 (driver version: 25.20.100.6446) Monitor: \.\DISPLAY1 - Generic PnP Monitor [3840x2160 32-bit 288 DPI] - [Current]
Text: Scale Factor: 1.000000 Ansi Codepage: 1252
Try this newer driver: https://www.intel.com/content/www/us/en/download/776137/intel-7th-10th-gen-processor-graphics-windows.html
I got an error message when trying to install.
--Something went wrong.-- Your system has a driver that is locked to manufacturer specifications. Please try downloading the latest driver from the manufacturer's website to update. Installer exit: code: 1.
It also produces an error log txt file.
@Blue-Ike This means you need to visit the support website for your computer, not Intel's website. The manufacturer of your computer has modified the generic Intel driver to cause this. If you do visit the support site for your computer and there is no driver update, there is nothing you can do in that regard. You may uninstall the current driver completely and install the Intel one. This is generally the better option for desktop computers.
@clsid2 This is happening to me with AMD drivers (6900 XT). I rolled back to 24.7.1 and it went away. This issue is an Intel GPU. Are we sure that the GPU drivers are solely to blame? Two different pieces of hardware here with the same bug. If not, there could be a bug report that needs to be submitted to a library that is included in this player.
I was the user with the same problem, but as mentioned I have an amd card (Radeon 6700xt). I confirm that I reported the bug to amd as indicated, the latest driver still have the issue though, we will see the next release, it's interesting that this user doesn't have an amd video card though. I disabled the option you mentioned but it doesn't fix the issue.
That's my info: MPC-HC (64-bit)
Build information: Version: 2.3.9 (cde2a82a9) Build date: Dec 18 2024
LAV Filters: LAV Splitter: 0.79.2.20 LAV Video: 0.79.2.20 LAV Audio: 0.79.2.20 FFmpeg compiler: MinGW-w64 GCC 13.3.0
Operating system: Name: Windows 10 (Build 21H2) Version: 10.0.19044 (64-bit)
Hardware: CPU: AMD Ryzen 7 5700X 8-Core Processor GPU: AMD Radeon RX 6700 XT (driver version: 32.0.12033.1030) Monitor: \.\DISPLAY1 - AOC 2781 [1920x1080 32-bit 96 DPI] - [Corrente]
Text: Scale Factor: 1.000000 Ansi Codepage: 1252 I also use madvr if it matters.
Do any of you have any software installed that may interact with graphics in any way, like screen recorders, OBS, discord, gaming overlays, etc? Or tools that modify Windows start menu or appearance.
Or did you enable Hardware-Accelerated GPU Scheduling (HAGS) in Windows?
If so, test if disabling those makes any difference.
like screen recorders, OBS, discord, gaming overlays, etc?
Nope. With all of these closed, the message still appears.
Or tools that modify Windows start menu or appearance.
These cause problems with Windows as a whole so I never use these.
An interesting discovery that adds to this. I do have an Intel A380 I am able to use. It is a secondary GPU. Under [System] > [Display] > [Graphics], I leave MPC to default "Let Windows decide." When using the AMD GPU to drive the displays, I get the warning. When changing it to a specific GPU, the A380, the warning message never appears. However, if I set it back to default "Let Windows decide" and use the A380 to drive the display, the warning message appears.
MPC-HC (64-bit)
---------------
Build information:
Version: 2.3.9 (cde2a82a9)
Build date: Dec 18 2024
LAV Filters:
LAV Splitter: 0.79.2.20
LAV Video: 0.79.2.20
LAV Audio: 0.79.2.20
FFmpeg compiler: MinGW-w64 GCC 13.3.0
Operating system:
Name: Windows 11 (Build 23H2)
Version: 10.0.22631 (64-bit)
Hardware:
CPU: AMD Ryzen 7 5800X3D 8-Core Processor
GPU1: AMD Radeon RX 7900 XT (driver version: 32.0.12033.1030)
GPU2: Intel(R) Arc(TM) A380 Graphics (driver version: 32.0.101.6449)
Monitor: \\.\DISPLAY5 - Generic PnP Monitor [2560x1440 32-bit 96 DPI] - [Current]
Monitor: \\.\DISPLAY6 - Generic PnP Monitor [1920x1080 32-bit 96 DPI]
Text:
Scale Factor: 1.000000
Ansi Codepage: 1252
Do any of you have any software installed that may interact with graphics in any way, like screen recorders, OBS, discord, gaming overlays, etc? Or tools that modify Windows start menu or appearance.
Or did you enable Hardware-Accelerated GPU Scheduling (HAGS) in Windows?
If so, test if disabling those makes any difference.
I haven't any of those programs, and since I use Windows 10 ltsc there isn't the HAGS option.
Do any of you have any software installed that may interact with graphics in any way, like screen recorders, OBS, discord, gaming overlays, etc? Or tools that modify Windows start menu or appearance.
Or did you enable Hardware-Accelerated GPU Scheduling (HAGS) in Windows?
If so, test if disabling those makes any difference.
Hello :)
AMD 7900 XTX (AMD driver 24.12.1) owner here. I tried to disable everything in W11 :
But unfortuantly the problem remains :
MPC-HC options :
That is a timeout when closing the main filter graph, rather than the preview filter graph.
If you use MadVR, then do not use ED2 as dither method, as that is broken with current AMD drivers.
That is a timeout when closing the main filter graph, rather than the preview filter graph.
If you use MadVR, then do not use ED2 as dither method, as that is broken with current AMD drivers.
Thank you it fixed the issue.
That is a timeout when closing the main filter graph, rather than the preview filter graph.
If you use MadVR, then do not use ED2 as dither method, as that is broken with current AMD drivers.
What if you're using MPC Video Renderer? Is there any settings to change in the Shader Video Processor options?
Here are my current settings:
@icedterminal It is showing the AMD gpu as number 1 is your copy/paste. So that is what Windows chooses by default. Are you also using MadVR? Then do not use Error Diffusion 2 dithering option. Or if you do not use that option, test with different renderer.
@bennj57 Are you also using MadVR?
@Blue-Ike Are you perhaps using any external filters?
If I tell Windows to use the A380, I no longer have the timeout error.
I do use MadVR, and I did check to see if ED2 was enabled but it is not.
Small update, the issue doesn't seem solved even if I changed the madvr filter as dither method. Now the issue is mostly present when you press the button to reproduce the next video. What have amd done with those drivers...
i get this issue too when switching between very short lossless h264 files. and i'm using nvidia.
it fully hangs too. The program mpc-hc64.exe version 2.3.6.11 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel. Process ID: 830 Start Time: 01db6862d7f94e22 Termination Time: 7 Application Path: C:\Program Files\MPC-HC\mpc-hc64.exe Report Id: fdd79f84-49b4-4a8f-845b-ac87ab29eeb3 Faulting package full name: Faulting package-relative application ID: Hang type: Unknown
2.3.9 has the same issue but a hang was not reported in the event viewer yet.
If it only happens for you with specific files, then upload one of those files for me.
Is it timeout of main graph or preview graph?
Does it also happen without Madvr?
It's probably time to move on from MadVR, I just checked and the latest release is from august 2018, so it's now 7 years old. The problem is that I was unable to find any similar application. Also I was able what are the amd drivers which works flawlessly: whql-amd-software-adrenalin-edition-24.3.1