This is absolutely correct, VMix is excellent software. When you pair it with the correct hardware even low cost hardware, it is very stable and reliable (and powerful). it’s also very reasonably priced, for one particular client twice a year I do a large 2 to 3 day livestream. We buy two copies of their $50 a month pro version (by default it is not a reoccurring subscription), each event. Every aspect of vmix can be automated or scripted, and they have a very easy to use XML based API (I can code but I’m definitely not a coder). Over the years we’ve built some incredible automated graphics for displaying on large billboards at the event, as well as using the second copy to produce the livestream where we pull in five professional ptz cams (via rtsp) and 2x sdi video feeds (via a capture card). We also use the NDI app on two iPhones to add their video into the mix (using the built-in vmix scripting, when someone presses the send button in the NDI app, V-Mix notices the audio level going above zero, and switches that live video feed into program). Note to do ndi over iphone wifi we use a dedicated ruckus R610 access point with no other clients on it, the video has ZERO latency, and amazing 4k quality). We also use companion running on a raspi5, connected to 2x stream decks, so that the entire set up can be controlled via the stream deck buttons.

Geewiz, 700 usd and only updates for a year of you want similar features to obs.

Thanks to the api you can do quite complex (or wacky) streams with obs. I don't get the "only very simple streams" argument.

Btw, there is a midi plugin for obs. I used it, worked like charm.

what features does vMix have, which OBS doesnt, that would be worth switching to a proprietary and paid program instead of a free, open source one?

I'd be interested to know as well. I may be in the minority, but I'll take a FOSS project with 80% of the features over a proprietary one with 100% of the features, almost every time. The philosophy of freedom is usually more important to me than squeezing out every last drop of functionality in exchange for a black box that I have to pay for and rely on some company that may or may not exist in a few years to develop it.

I’m pretty sure this has changed now, but when I first looked at OBS versus vmix, OBS did not have good NDI Support. Since the twice a year video production I put on is kind of like a hobby although I get paid, I just went with VMix and haven’t looked back. (Video is not my main job)

vMix is Windows-only, so I'd imagine the people it targets don't think about licensing much.

>vMix is Windows-only, so I'd imagine the people it targets don't think about licensing much.

they probably think about money, though. and whether there's a significant difference in features or not.

100%.

It's similar to AI... the only people trying to tell you "it's the future" are those with financial stakes.

There have been people going back to Turing thinking AI is the future and I don't think he was trying to pump his AI stocks.

Yeah. Rosenblatt, von Neumann, McCarthy, Weizenbaum... buncha morons

I feel very different about AI. I have still no clear idea what crypto is good for except money laundering. AI feels very different. It might not live up to all it’s promises. But it is clearly very capable.

You're forgetting the true believers.

The difference is that AI is a huge array of technologies (not only LLMs) and are being used in several fields with different, useful purposes.

There's a cult and a bubble too, though, and I agree with that part.

Crazy that people really need instructions on how to self-host stuff these days... this stuff used to be something most devs could figure out.

I noticed this in development mode but performance improved substantially in production

You seem to be an extreme outlier and probably not the target audience for such applications. No offense, but nobody is carrying around multiple devices when the one device we all have can do everything and do it better.

It's a dead end for your use case, let's be very clear about that.

And it's funny that you think anything about React and/or Vue is 'trivial'.

Surely you’re not saying the frameworks famous for ui = f(state) actually suck at managing state…

If it only were true. React is nothing like ui = f(state). More like ui = f(some_trivial_state) + lifecycles magic + probably global_state.

Garbage. But effective devrel.

This type of dismissive attitude is so strange to me. The only reason "lifecycles magic + probably global_state" would be causing your app to behave unpredictably is - this is going to shock you - because you closed your mind to a tool by dismissing it as garbage before you used it, and then failed to use it properly because you think its popularity boils down to PR.

For instance, you could entirely forgo the influence of lifecycles and global state by putting everything in a top-level Context with 1 state object that you only ever update by calling `setState`.

After that, you might find reasons to optimize your app, which could lead you to more interesting approaches like reducers or state management libraries or memoization, but I'm guessing you would never get that far and just go back to what you were doing before, since YOUR preferences are battle hardened and reliable software, while things you don't know about are only popular because of Facebook. Obviously.

So, redux? It's either redux or, sorry, "lifecycles magic + probably global_state". And who uses redux in 2025?

Honestly, if you’re getting thru life with this attitude, good for you, but you might want to consider if it’s the only way

I'm doing fine, thank you. Perhaps you didn't understand what I said.

My best ballpark guess for global redux usage in react projects is between 25% and at best 50% if you include redux/TEA-like libraries, but not non-pure usage.

So yes, saying that react is `ui = f(state)` does everyone a disservice. It might be true for you, but it's probably not even the average.

Well, for anyone using Vue you get automatic observability baked in, right? And reactive programming state management libraries within react are plenty popular, not to mention the built in state management being quite literally UI = f(state).

The fact people use the tortured disaster that is redux isn’t really a knock on react in any sane person’s view, we all know the JS community is full of beginners who don’t know better

kinda does, tbh.

I find Go's type system to be extremely lackluster.

Ok can you elaborate?