Audio issues on TCP clients connecting to murmurd running on armel #123

New issue

Closed

opened 2026-02-20 19:14:23 -05:00 by deekerman · 4 comments

deekerman commented

2026-02-20 19:14:23 -05:00

Owner

Originally created by @Uragon on GitHub (Dec 12, 2013).

Running a mumble-server in a SheevaPlug ARM SoC, I have noticed that some users are unable to hear anybody else, including themselves in server loopback mode. I was able to reproduce this by selecting the option to force tcp in the mumble client. Audio reception immediately broke for this client, while sending would still work. Disabling force TCP and going back to UDP connection would immediately fix the problems.

My assumption is that this is some kind of endianness issue in the server software. A bit of more detailed information about the server below:

$ uname -a
Linux plug 3.2.0-4-kirkwood #1 Debian 3.2.51-1 armv5tel GNU/Linux
$ /usr/sbin/murmurd -version
2013-12-12 09:51:46.957 /usr/sbin/murmurd -- 1.2.4-0.2+0coredump2+wheezy
$ cat /etc/debian_version
7.2

Originally created by @Uragon on GitHub (Dec 12, 2013). Running a mumble-server in a SheevaPlug ARM SoC, I have noticed that some users are unable to hear anybody else, including themselves in server loopback mode. I was able to reproduce this by selecting the option to force tcp in the mumble client. Audio reception immediately broke for this client, while sending would still work. Disabling force TCP and going back to UDP connection would immediately fix the problems. My assumption is that this is some kind of endianness issue in the server software. A bit of more detailed information about the server below: $ uname -a Linux plug 3.2.0-4-kirkwood #1 Debian 3.2.51-1 armv5tel GNU/Linux $ /usr/sbin/murmurd -version <F>2013-12-12 09:51:46.957 /usr/sbin/murmurd -- 1.2.4-0.2+0coredump2+wheezy $ cat /etc/debian_version 7.2

deekerman

2026-02-20 19:14:23 -05:00

closed this issue
added the
needs-more-input

needs-ckeck-with-latest-version
labels

deekerman commented

2026-02-20 19:14:31 -05:00

Author

Owner

@crknadle commented on GitHub (Dec 12, 2013):

Just for clarification: the 1.2.4-0.2+0coredump2+wheezy package is a package I put together for wheezy; in terms of mumble-server (murmurd) the source package is the same as the 1.2.4-0.1 package in Debian Sid now except retains the old dependencies for ice34 (because wheezy doesn't have ice35) and g++-4.6 (because newer versions of gcc error out in compiling ice34).. The package is available here:

http://debian-packages.coredump.us/debian/pool/main/m/mumble/

@crknadle commented on GitHub (Dec 12, 2013): Just for clarification: the 1.2.4-0.2+0coredump2+wheezy package is a package I put together for wheezy; in terms of mumble-server (murmurd) the source package is the same as the 1.2.4-0.1 package in Debian Sid now except retains the old dependencies for ice34 (because wheezy doesn't have ice35) and g++-4.6 (because newer versions of gcc error out in compiling ice34).. The package is available here: http://debian-packages.coredump.us/debian/pool/main/m/mumble/

deekerman commented

2026-02-20 19:14:31 -05:00

Author

Owner

@RichoDemus commented on GitHub (Jun 10, 2014):

I just wanted to comment that I've had this problem myself on an Excito B3 which is a similiar computer, also with an Arm-processor.

If I recall correctly, the problem is that some clients are unable to connect to the control-channel. but I might be mistaken

@RichoDemus commented on GitHub (Jun 10, 2014): I just wanted to comment that I've had this problem myself on an Excito B3 which is a similiar computer, also with an Arm-processor. If I recall correctly, the problem is that some clients are unable to connect to the control-channel. but I might be mistaken

deekerman commented

2026-02-20 19:14:32 -05:00

Author

Owner

@Krzmbrzl commented on GitHub (Jan 15, 2020):

Can this problem be reproduced with the latest 1.3 version?

@Krzmbrzl commented on GitHub (Jan 15, 2020): Can this problem be reproduced with the latest 1.3 version?

deekerman commented

2026-02-20 19:14:32 -05:00

Author

Owner

@no-response[bot] commented on GitHub (Feb 14, 2020):

This issue has been automatically closed because there has been no response to our request for more information.
With only the information that is currently in the issue, we don't have enough information to take action.

Please reach out if you have or find the answers we need so that we can investigate further (or if you feel like this issue shouldn't be closed for another reason).

@no-response[bot] commented on GitHub (Feb 14, 2020): This issue has been automatically closed because there has been no response to our request for more information. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further (or if you feel like this issue shouldn't be closed for another reason).