search

mumble-voip / mumble

Mumble is an open-source, low-latency, high quality voice chat software.
https://www.mumble.info
Other
6.42k stars 1.12k forks source link

Feature request: delayed "spectator" channel #1415

Open ThisIsAreku opened 10 years ago

ThisIsAreku commented 10 years ago

I know it may be a difficult thing (because of the memory management of the delay) but now that more and more online games have a spectator mode delayed by a specific amount of time, it would be nice to have a option to mirror a channel, but with a delay.

I'm not aware of any other gaming VoIP software that allow this, so it would be a great argument in favor of mumble

nicolasjoly commented 10 years ago

There's a bot that does that. I don't know if it still works. It's called Eve-Bot : http://wiki.mumble.info/wiki/3rd_Party_Applications#Bots_for_Mumble

ThisIsAreku commented 10 years ago

I know, but it generate a lot of traffic between the bot and the server, so it's not possible if you don't have access to the server (ie. hosted mumble). It would be better to not have to rely on a 3rd party app

Kissaki commented 10 years ago

I would not consider it “a lot” of traffic. If you host it yourself, it only adds an inbound and outbound traffic channel which use as much traffic as if you were talking yourself. Sure, it’s more continuous, but it is not magnitudes higher.

ghost commented 1 year ago

I have seen similar types of features where users are moved to a spectator room on Teamspeak when they are defeated in co-op style games. Most of the implementations I have seen like this are a plugin to the chat software or a game mod that interacts with the chat software (or some combination of both). This is usually a safer option to handle it on a case by case basis.

Krzmbrzl commented 1 year ago

The problem with client-side solutions (like plugins) is that this will rely on compliant clients and therefore you can never be sure that there isn't someone that is cheating by letting their client simply ignore the delay and playback immediately instead.

So this should probably be implemented on the server-side.