voc / voctomix

Full-HD Software Live-Video-Mixer in python
https://c3voc.de/
MIT License
573 stars 104 forks source link

Is voctomix alive? #301

Closed filiphanes closed 1 month ago

filiphanes commented 1 year ago

What is the state of development, usage?

MaZderMind commented 1 year ago

Personal Opinion (I don't speak for C3VOC or the Project): I think it is not yet dead (ie it is still used every now and then), but I also don't think there's much development going on.

From my point of view, Covid and Remote/Hybrid Conferences raised he need for much more flexible solutions (ie OBS Studio) which, together with vdo.ninja allows for sophisticated Remote/Hybrid events at the expense of a more complex UI and needing a GPU (however modern CPUs have a decent enough embedded GPU).

In my environment I don't see that remote Speakers / Hybrid Setups will go away anytime soon and I don't see Voctomix gain the necessary flexibility. At the same time, the OBS ecosystem is moving fast and getting better and more complete.

krokodilerian commented 1 year ago

As a data point, FOSDEM still runs on voctomix1 (the one packaged in Debian, actually :) ) for 26 rooms in parallel, and we're happy with it (but not with voctomix2, because it doesn't have the TCP ingest we need, #244 ).

xfxf commented 10 months ago

@MaZderMind we're still using voctomix for many events (pycon australia, everything open / linux.conf.au, etc) - we just use additional tools now including OBS and third party guest webrtc tooling.

I don't view OBS as a replacement for voctomix personally, especially around its flexibility with ingest and export, and there's certainly scope with hybrid events to use multiple tools.

would certainly like to see voc2 development continue!

thomic commented 10 months ago

As a further data point, we just produced FrOSCon and CCCamp 2023 with voc2mix

fightling commented 10 months ago

Just to say something from my side:

I'm currently heavily involved into the development of OpenTalk (which is a a/v conferencing system written in rust). So I do not have much time to do work here.

But I've learned a lot in the last years and I think I would now rewrite many things in voctomix to make it more flexible - what it never was meant for (as @MaZderMind already said).

So I think the current use case is for those people only who are still using voctomix because it fits their traditional needs since version 1. And voctomix2 is just meant to be an advancement of the first version.

Also I once thought that producing a lot of documentation would lead others to get involved more heavily.

I may not be the marketing guy but if someone likes to work on issue fixing and would need some consulting, I would be happy to invite you to a chat or talk to help.

Until then: It was nice to see voctomix2 transitions in the camp23 recordings and that everything seemed stable. But there is also so much more you can do with Transitions if someone would get interested to build custom ones. Also the Insertions never seem to be used which could be fed with outputs from the talk booking. But never mind - maybe it's not that easy ;)

greez

Kunsi commented 1 month ago

I'll close this issue, since the recent release of 2.0 very much means voctomix is atleast somewhat alive.