CasparCG 2.1 and Premiere Pro with Windows 11 capture performace problem

I have build 3 windows 11 systems with Intel i9-14900k CPU (24 cores!)
and 64 Mb RAM.
2 with Gigabyte boards and 1 with Asrock.
I used M2 for system and video storage.
There is a Nvidia RTX4070 graphics card on all systems.

These systems use BlackMagic Studio 4K and Duo2 cards for capture and editing.

So these systems are very high performance PC’s with latest hardware.

We want to be able to do HDCAM capture and edit the resulting file while capturing.
I use CasparCG 2.1 for capture and Premiere Pro 2024.6 for editing.

I get a strange performance problem however with Win11 pro, but not with Win10 pro. (same on all 3 systems!)

If I start to capture with CasparCG2.1 in HDCAM MXF format all works fine untill I start Premiere Pro.
When Premiere Pro is running while capture the (playback) Decklink card start to show dropped frames in the DIAG window.
FF mpeg with it’s videochannel is running fine with very low CPU load.
This results in a spedup a bad videofile.
(note I don’t use a Decklink card in Premiere Pro)

I see this on all my 3 new systems with Win11 pro.
I tried different Decklink drivers but I can’t fix this problem.

Today I installed one these systems with Win10 pro and the same software as with the Win11 pro setup.

With Win10 these problems are gone!
I can do anything with Premiere Pro including rendering without any problems while the CasperCG capture runs in the background.

Suggestions are welkom about the bad performance with Win11!

Funny phenomenon. Is there a reason NOT to run it in Win 10, beside the work of reinstalling everything?

Probably it’s the same answer as “why not continue using flash templates with Casparcg “ As adobe is not going to drop yet the support and development for adobe Animate . But I think W10 is going to be out of support soon? I’m not 100% sure though .

In broadcast it is most of the time no problem to use an older OS.
But some day we have to go to newer OS, this is an unexpected problem.
I keep you posted what is causing this problem.

I have two clients, that exctly do that :slight_smile: Sure in the end one would need to phase out the old OS, but I don’t think, that this problem can be solved quickly in Caspar, as it sounds like a Windows problem. So I would just go with Win 10 for now and try again in a year or so, with the next win 11 update. Maybe filing a bug report at Microsoft could help, but I would not expect that.