It is long overdue, but today CasparCG 2.5.0 has been released.
Highlights include:
Updated CEF (fixes some stuttering issues)
Initial support for HDR
The full changelog is provided below
Important
We recommend running CasparCG 2.5 on CPUs which support AVX2. Officially Chrome claims to require AVX2, and it is required for some of our in-progress HDR support.
Intel CPUs based on Haswell or later support this, which were first released to consumers in 2013, or 2014 for servers.
Starting with CasparCG 2.6, this will become a requirement.
This is HUGE!
Just in time for a seamless Linux transition…
Thank you very much to everyone involved in this, and specially you Julian, awesome work!
CasparCG is at its best shape yet! It really feels very healthy, performant and very feature rich.
I’m really thankful.
Thanks so much to everyone who worked hard on development and testing. I can’t wait to try out the new features and improvements. Time to download and play around with the new build!
Looks great, indeed! - One question concerning Windows: Has anybody already tested it on Windows 11? My own machines are all still running Win 10, but I have a client explicitly requesting Windows 11. They currently run Version 2.3.0 on Win 11, so I expect no problems with 2.5.0, right?
I know of some broadcasters who are running 2.4 upgraded their machines from 10 to 11.
I don’t think 2.5 should be any different in behaviour than 2.4 really
I upgraded my dev machine to 11 the other day too, so I no longer have anything to test on 10. Although I didn’t test much after doing that upgrade.
Thanks for amazing update!!! I have one old as world question, what about mac’s and m series processors maybe now it’s possible to make casparcg for them?
I tested latest builds on Windows 11 and had to revert back to Windows 10 because performance in an older machine (8th-gen 6-core i5) was lacking. Couldn’t even enable NDI because the CPU was pegged at 100% most of the time. Either background processes (some continuity-like syncing service) or Windows Defender would hog the CPU.
In context, the machine did run 2 playout channels (Decklink + NDI), a Fill+Key channel (Decklink) and a preview channel (NDI) without breaking a sweat, with spare performance to run zoom meetings in other two displays.
That’s why I think linux deserves a shot. Having the possibility to run a sealed headless server and not worrying constantly about security or forced updates is a plus.
We still have the same problem as when this was asked about years ago; the compositor is written in a technology that apple deprecated 6+ years ago and stopped updating even longer before that. That hasn’t changed, and windows and linux still support it as well as they did 10 years ago with no sign of that changing, so motivating rewriting the compositor to support this is a hard sell.
That said, Vulkan support is a plan to do just that and should make it pretty easy to start supporting macos. So things are slowly moving us towards being able to think about it, but no idea on when that might be usable
Looks great.
Since there are a lot of new parameters in the config-file (especially for the Decklink-consumer)
Should we have a breakdown here what they mean and which are optional especially if you are not running HDR.
I just installed tinyw11 core on a old NUC because only 2gb ram.
Cool thing is the installer lets you install install it on older hardware.
You can use the official iso of windows with https://rufus.ie/ also if you want to install it on systems that don’t have Secure Boot or TPM 2.0
Like old HP Z640 systems that still run like beasts.
But now with the tiny 11 core, thinking of installing that on my old Z640 systems. The only thing with the core is that windows update is disabled if you want to stay up to date.
