Also Mac only, since non Mac users won't have a clue what metal means in this context.

Transpiling shaders is what most game engines have done for a decade now. Everybody thinks it's stupid in that field as well, but there is no viable alternative.

Vulkan is not supported on game consoles, with the exception of Switch, and even there you should use NVN instead.

It is not officially supported on Windows, it works because the GPU vendors use the Installable Client Driver API, to bring their own driver stack. This was initially created for OpenGL, and nowadays sits on top of the DirectX runtime.

On the embedded space, the OSes that support graphical output many are stil focused on OpenGL ES.

Metal does pre date Vulkan, and some people consider it easier to use.

Vulkan capture support on Windows was introduced in v25 (on linux you need to use a plugin). There is no Vulkan renderer support—which the post clearly stated...

OBS has no Vulkan renderer. Only OpenGL, DirectX 11 (on Windows), and now Metal.

As if nobody else ever did that (like Microsoft with DirectX, and almost every single games console)?

Same. I'm a python/typescript guy, so many details flew over my head, but I knew HN would like it.

Modern graphics APIs minimize the number of graphics API calls vs. OpenGL and similar. Vulkan/Metal/DirectX 12 will have you pass command buffers with many commands in them instead of separate API calls for everything.

It's been possible for quite some time.

In the early 2000's there was a book on using Direct3D from C# that was pretty influential as far as changing people's assumption that you couldn't do high performance graphics in a GC'd language. In the end a lot of the ideas overlap with what c/c++ gamedevs do, like structuring everything around fixed sized tables allocated at load time and then minimal dynamic memory usage within the frame loop. The same concepts can apply at the graphics API level. Minimize any dynamic language overhead by dispatching work in batches that reference preallocated buffers. That gets the language runtime largely out of the way.

There is a Metal Obj-C API, Metal implementation is C++.

Yes and https://reviews.llvm.org/D69991

No, it doesn't. You won't find it used much if at all at these levels of the OS. Once you get past cocoa and friends it's restricted subsets of C++ (IOKit for example)

It says in passing As the Metal backend is only supported on Apple Silicon devices, GPU and CPU share the same memory in the part talking about the differences between the Direct3D and Metal render pipelines.

Not sure why though, because Metal 3 is still supported on a bunch of Intel Macs...

Highly depends on what you're streaming. If you stream arcade 2D games of the past, or software development, it should be perfectly fine.

AAA titles with newer graphics, well, you can always send a capture the PC with the nvidia card's screen through a capture card.

Back in my days of streaming, macOS was no option, cca. 2017. Today I'd do it with any M processor mac without a second thought.

Streaming video from camera? In general the newer Mac Minis in general were fine already just because the M-series chips are very fast, but hopefully this should make it much more efficient

Well, to be fair, they say it's an "experimental" version, so they would probably appreciate a bug report.

Please submit a GitHub issue with some details on your setup!

An obvious regression, you hope they'll get it fixed soon.

That is actually sad. It is such basic scene.

I hope the next version actually works in some facility.

see Blender

It's never "doing nothing" - you just need more visibility into your running tasks.

Turning off nearly everything iCloud- or Spotlight-related is a pretty good start; disable network access and you may find even more pearls of wisdom.

Not all streamers are game streamers, and not all obs users are streamers. I installed on all of my workstations for its screen capture and virtual camera features.

Looks neat but seems like a complete hassle to get up and running and maintain, unless if your goal is to learn how screen recorders work.

The linked post is about a new Metal-based renderer for OBS Studio on MacOS. The software you linked is for Linux.

Why not just use quicktime?

Edit: I think you might have skipped reading the post. It's about OBS on MacOS. Where quicktime exists. Your suggestion seems geared toward Linux.

Does anyone know if AMD 8845HS with 780M graphics (running fedora) can into this? Ideally very low system resources used, I only have 16GB RAM, also ideally very little storage space used, one or two frames per second is enough, ideally should compress even more if nothing has changed in the screen for a while, also ideally should create a new file every eight hours or so.

NVIDIA has a "lower overhead" screen recorder, no? It's alt + f9 or something. AFAIK It's supposed to be optimized, because they own the stack and all. It's probably only on Windows though.

This is great, thanks!