mumble icon indicating copy to clipboard operation
mumble copied to clipboard

Improve handling of big messages

Open Xylemon opened this issue 10 years ago • 10 comments

This is something of a huge annoyance as I absolutely can not stand the character/image size limit that Mumble has set on its default client. I think these type of limits for chat/comments should be customized to whatever value the server owner or individual client desires.

Xylemon avatar Jul 31 '14 03:07 Xylemon

If I understand your question correctly, you can already do that. Just go here: http://mumble.sourceforge.net/Murmur.ini#textmessagelength

textmessagelength and imagemessagelength are both configurable. The major problem with huge images is that it will literally crash either the client sending it or the server/people receiving it. This is a VoIP software, not a file sharing one.

nicolasjoly avatar Jul 31 '14 04:07 nicolasjoly

Ah alright, I had no idea that the text message length could be changed via murmur.ini, do these apply to comments too?

Xylemon avatar Jul 31 '14 04:07 Xylemon

I have absolutely no idea if comments are bound by the same rules. The info for "textmessagelength" only talks about sent messages and not comments. Best way to know would be to test it.

nicolasjoly avatar Jul 31 '14 05:07 nicolasjoly

Yes, they do apply to comments as well.

Natenom was much more elaborative and detailed in his German documentation. These details should definitely be added to the English documentation.

Kissaki avatar Jul 31 '14 20:07 Kissaki

So I've modded my configuration file to have no limit on image sizes and text messages yet:

  1. Sometimes it still denies an image being sent due to it being too large.
  2. Images bigger than 128 kb that are in channel comments still don't download.
  3. I have a channel with a lot of images and text and it still spits out: [[ Text object too large to display ]]

Is this something client side? Because I've tried other clients like Plumble (custom Android port) and I don't have these issues.

Xylemon avatar Aug 02 '14 07:08 Xylemon

The “Text object too large to display” is definitely a client side limit. I don’t remember the technical reason. And no idea about the other things you mentioned.

Kissaki avatar Aug 02 '14 07:08 Kissaki

The random image limits could just be due to a client limit as well. The bug should also be renamed since it's about client side limits rather than Server side.

Xylemon avatar Aug 02 '14 07:08 Xylemon

The [ Text object too large to display ] can be configured to an extent. The client side option is in Configure>Options>Messages>Length Threshold. The default is 250 and maximum is 5000. I would assume the option is so nobody sends a massive image and possibly disconnect or lag all of the clients that receive it.

abextm avatar Jun 21 '15 20:06 abextm

That brings up a couple of questions I've had regarding Mumble in comparison to other clients like TeamSpeak:

  • Why does Mumble handle largish images so badly? It seems that what determinants an image to cause hangups is the file size. Couldn't there be some way to load these images better or an optional resizer to prevent freezes but still being able to see the image?
  • Also can't there be a better way to view channels or large text messages? I don't see why a few paragraphs of text should freeze up Mumble, it seems another way of reading them properly could be implemented.

Xylemon avatar Jun 22 '15 06:06 Xylemon

This seems to be related to #3413

Krzmbrzl avatar Jan 19 '20 12:01 Krzmbrzl