Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Re: Mumble rewrite, feature wishlist #4207

Closed
felix91gr opened this issue May 26, 2020 · 4 comments
Closed

Re: Mumble rewrite, feature wishlist #4207

felix91gr opened this issue May 26, 2020 · 4 comments

Comments

@felix91gr
Copy link

felix91gr commented May 26, 2020

From #4195 (comment), #4195 (comment) and #4195 (comment), there seems to be a consensus that, now that the topic of a rewrite is on the table, there should be a thread to discuss / propose / assert what the community wishes the Mumble devs considered either adding or removing to / from the project.

How this works

Propose

If you want to propose something, do the following:

  • Write one comment per idea.
  • Start with a heading H3: ### My idea, so that everyone can see it's a proposal and not a response to something else.

Also, try to leave space for others' ideas as well, so that everyone can make use of the thread :)
So, I'd suggest going for your 2 or 3 most wanted ideas.

You are allowed to iterate on your ideas upon receiving feedback! Try to annotate your edits at the bottom so that people can keep up to date :)

Vote

If you don't have anything left to propose, you can assert your opinion on an idea by voting on it. Use this as your reference:

  • 👍 : Approval
  • 👀 : Mild Approval
  • <nothing> : No opinion
  • 😕 : Mild Disapproval
  • 👎 : Disapproval

Give feedback

If you want clarification, or to improve someone else's idea, you should give them feedback! You can quote their text using > and tag them using @.

If you disagree with someone else's idea: remember that everyone's a person, so give them feedback with kindness ❤️


@theAkito @timokoesters @fedetft you were interested in this, here's the thread ^^

@Krzmbrzl
Copy link
Member

Be aware though that this is only for discussion and will be closed at some point. If there are feature requests for the feature you have in mind, make sure to link to it and also give that an upvote because these are the ones we'll actually process.
(Simply because there we have on issue per feature request. That's just a lot better to maintain than having one thread with dozens of them)

@streaps
Copy link

streaps commented May 27, 2020

Multichannel Audio Stream Ready / Ambisonics

It would be nice to support playback of surround / multichannel streams. In a first version the implementation doesn't have to be sophisticated, even a downmix to stereo would do it. The important thing is that the client will not choke on a multichannel stream and is able to play instead of discarding it completely or important parts of it.

I'm thinking especially of support for Ambisonics as it only needs 3 channels for horizontal 2D audio and already includes an omnidirectional mono signal in the first channel.

If and how this can be implemented with or without breaking compatibility is another question. The idea is to make it easier to add real full-featured surround / multichannel support in the future.

@streaps
Copy link

streaps commented May 28, 2020

Replace Murmur with Grumble

There is already a rewrite of the server part: Grumble. It claims to be 'pretty much feature complete, except for a few "minor" things.'

Instead of fighting with the gRPC implementation for Murmur that crashes the server, what about adding gRPC or some other remote interface to Grumble?

@Krzmbrzl
Copy link
Member

Krzmbrzl commented Jun 7, 2020

Given that we won't do a rewrite, (see #4195 (comment)), I think we can close this issue.

@Krzmbrzl Krzmbrzl closed this as completed Jun 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants