Mumble - Recent changes [en]

User:Deri8000

2009-11-25T18:41:30Z

New user account

New page

FAQ/English

2009-11-25T17:44:20Z

What are the bandwidth requirements?: we raised default bw.

← Older revision		Revision as of 17:44, 25 November 2009
Line 42:		Line 42:
	== What are the bandwidth requirements? ==		== What are the bandwidth requirements? ==

-	From 0.9.1, this is highly variable, and mostly up to the user. With top quality, minimum latency and positional information sent, it is 110 kbit/s (as of 1.2) including the IP and UDP overhead. With 80 ms transmission delay, the lowest quality speech and no positional information, it is 11.0 kbit/s (again with IP and UDP overhead). The default quality setting (as of 1.2) uses 54 kbit/s. When comparing with other products, remember to compare the total bandwidth use and not just the bitrate of the audio encoding.	+	From 0.9.1, this is highly variable, and mostly up to the user. With top quality, minimum latency and positional information sent, it is 110 kbit/s (as of 1.2) including the IP and UDP overhead. With 80 ms transmission delay, the lowest quality speech and no positional information, it is 11.0 kbit/s (again with IP and UDP overhead). The default quality setting (as of 1.2) uses 58.8 kbit/s. When comparing with other products, remember to compare the total bandwidth use and not just the bitrate of the audio encoding.

	There are two parts to tuning the bandwidth; the audio bitrate per audio frame (20ms) and the amount of frames to put in each packet. Each transmitted packet has a overhead of 28 bytes from IP and UDP alone, so at the highest transmission rate (50 packets per second), that is 1400 bytes of data for raw network overhead alone. You should try to find a balance that works well for you, but we generally recommend sacrificing high audio bitrate for lower latency; Mumble sounds quite good even on the lowest quality setting.		There are two parts to tuning the bandwidth; the audio bitrate per audio frame (20ms) and the amount of frames to put in each packet. Each transmitted packet has a overhead of 28 bytes from IP and UDP alone, so at the highest transmission rate (50 packets per second), that is 1400 bytes of data for raw network overhead alone. You should try to find a balance that works well for you, but we generally recommend sacrificing high audio bitrate for lower latency; Mumble sounds quite good even on the lowest quality setting.

ACL and Groups/English

2009-11-25T17:40:49Z

added section on access tokens, i wrote it a while ago i hope it's all still correct

← Older revision		Revision as of 17:40, 25 November 2009
(One intermediate revision not shown)
Line 96:		Line 96:

	This lets anyone that's currently in a descendant of Root (B's parent) and has a path length of exactly 2 (length of Root.B -1 + 2) join, so this rule would match someone in A1, but not A or Sub1.		This lets anyone that's currently in a descendant of Root (B's parent) and has a path length of exactly 2 (length of Root.B -1 + 2) join, so this rule would match someone in A1, but not A or Sub1.
		+
		+	== Channel Passwords and Access Tokens ==
		+
		+	Beginning with Mumble 1.2, it is now possible to set access on channels based on "tokens" or "passwords". Passwords are stored in a tokens list in the client for each server, with the client using them as needed. From this point forward, we will refer to channel passwords as "tokens" instead, for clarity.
		+
		+	=== Configuring a Channel Password ===
		+
		+	Access Tokens are configured by creating special groups, which consist of the token prefixed by a pound symbol. For example a token called "letmein" corresponds to a group called #letmein.
		+
		+	The Channel Editor dialog box contains a field called "password". Entering "letmein" in the password field will automatically create a token group called #letmein, then by default will deny "Enter" access to @all and allow "Enter" access to users in the group #letmein, which will consist of any user who has that token in their token list.
		+
		+	To create token groups manually, first enable the Advanced Channel Editor. Then Edit a channel and go to the ACL tab. On the bottom of the ACL list, select the @all entry and check the "Deny Enter" permissions box. Now click "Add", and in the "Group" combobox at the bottom write #letmein and press enter. Now check the "Allow Enter" permissions box, and click OK to dismiss the editor.
		+
		+	=== Using an Access Token ===
		+
		+	You may add access tokens to your client by selecting "Access Tokens" from the "Server" menu. Click add, type the token (e.g. "letmein") and click "OK". It should take effect immediately, granting you whatever permissions are associated with that token group.

	= Permission Definitions =		= Permission Definitions =
Line 128:		Line 144:

	Allows a player to make a subchannel in the current channel. The player will automatically be added to the ''admin'' group in the new channel, so make the inheritable ACLs give the privileges you desire.		Allows a player to make a subchannel in the current channel. The player will automatically be added to the ''admin'' group in the new channel, so make the inheritable ACLs give the privileges you desire.
		+
		+	== Make Temporary Channel ==
		+
		+	Allows a player to make a temporary subchannel in the current channel, which will automatically be deleted when the last user leaves it. The creator will automatically be moved into the channel after creating it.

	== Link Channel ==		== Link Channel ==

FAQ/English

2009-11-25T17:31:00Z

make it a little clearer

← Older revision		Revision as of 17:31, 25 November 2009
(2 intermediate revisions not shown)
Line 34:		Line 34:
	== Compiling Mumble ==		== Compiling Mumble ==

-	[[BuildingLinux]]	+	We currently maintain pages with instructions on building Mumble from source on [[BuildingLinux\|Linux]],[[BuildingWindows\|Windows]], and [[BuildingFreeBSD\|FreeBSD]].
-		+
-	[[BuildingWindows]]	+

	== What makes Mumble better? ==		== What makes Mumble better? ==
Line 44:		Line 42:
	== What are the bandwidth requirements? ==		== What are the bandwidth requirements? ==

-	From 0.9.1, this is highly variable, and mostly up to the user. With top quality, minimum latency and positional information sent, it is ~~64.6~~ kbit/s including the IP and UDP overhead. With 80 ms transmission delay, the lowest quality speech and no positional information, it is 11.0 kbit/s (again with IP and UDP overhead). The default ~~uses 45~~.~~4 kbit/s; we did not hear any noticeable improvement in quality from the last 20~~ kbit/s. When comparing with other products, remember to compare the total bandwidth use and not just the bitrate of the audio encoding.	+	From 0.9.1, this is highly variable, and mostly up to the user. With top quality, minimum latency and positional information sent, it is 110 kbit/s (as of 1.2) including the IP and UDP overhead. With 80 ms transmission delay, the lowest quality speech and no positional information, it is 11.0 kbit/s (again with IP and UDP overhead). The default quality setting (as of 1.2) uses 54 kbit/s. When comparing with other products, remember to compare the total bandwidth use and not just the bitrate of the audio encoding.

	There are two parts to tuning the bandwidth; the audio bitrate per audio frame (20ms) and the amount of frames to put in each packet. Each transmitted packet has a overhead of 28 bytes from IP and UDP alone, so at the highest transmission rate (50 packets per second), that is 1400 bytes of data for raw network overhead alone. You should try to find a balance that works well for you, but we generally recommend sacrificing high audio bitrate for lower latency; Mumble sounds quite good even on the lowest quality setting.		There are two parts to tuning the bandwidth; the audio bitrate per audio frame (20ms) and the amount of frames to put in each packet. Each transmitted packet has a overhead of 28 bytes from IP and UDP alone, so at the highest transmission rate (50 packets per second), that is 1400 bytes of data for raw network overhead alone. You should try to find a balance that works well for you, but we generally recommend sacrificing high audio bitrate for lower latency; Mumble sounds quite good even on the lowest quality setting.
Line 96:		Line 94:
	== Can I change to volume of a specific user? ==		== Can I change to volume of a specific user? ==

-	No, you cannot. Mumble employs AGC ('''A'''utomatic '''G'''ain '''C'''ontrol) to normalize the volumes of all players automatically. This means the individual adjustment of a single user is not required, ~~and~~ wanted. We feel that it makes no sense for every user on a server to adjust the volume of someone manually when the person in question could just fix things on his end instead. Note that pretty much all questions we receive on this this come up because of users who did not bother to do our Audio Wizard, AGC is powerfull but if there is not enough signal to begin with (e.g. Mic volume turned way down) it will not be able to operate correctly.	+	No, you cannot. Mumble employs AGC ('''A'''utomatic '''G'''ain '''C'''ontrol) to normalize the volumes of all players automatically. This means the individual adjustment of a single user is not required, nor wanted. We feel that it makes no sense for every user on a server to adjust the volume of someone manually when the person in question could just fix things on his end instead. Note that pretty much all questions we receive on this this come up because of users who did not bother to do our Audio Wizard, AGC is powerfull but if there is not enough signal to begin with (e.g. Mic volume turned way down) it will not be able to operate correctly.

	= Server =		= Server =

User:Influenza

2009-11-25T17:06:43Z

New user account

New page

User:Crusher

2009-11-25T16:31:37Z

New user account

New page

Running Murmur

2009-11-25T16:04:23Z

User -> Player

← Older revision		Revision as of 16:04, 25 November 2009
Line 225:		Line 225:

	Adding a new registration:		Adding a new registration:
-	dbus-send --system --print-reply --dest=net.sourceforge.mumble.murmur --type=method_call /'''<serverid>''' net.sourceforge.mumble.Murmur.~~registerUser~~ string:"'''<username>'''"	+	dbus-send --system --print-reply --dest=net.sourceforge.mumble.murmur --type=method_call /'''<serverid>''' net.sourceforge.mumble.Murmur.registerPlayer string:"'''<username>'''"

	Fetching an existing registration:		Fetching an existing registration:
	dbus-send --system --print-reply --dest=net.sourceforge.mumble.murmur --type=method_call /'''<serverid>''' net.sourceforge.mumble.Murmur.getRegistration int32:'''<userid>'''		dbus-send --system --print-reply --dest=net.sourceforge.mumble.murmur --type=method_call /'''<serverid>''' net.sourceforge.mumble.Murmur.getRegistration int32:'''<userid>'''
	or		or
-	dbus-send --system --print-reply --dest=net.sourceforge.mumble.murmur --type=method_call /'''<serverid>''' net.sourceforge.mumble.Murmur.~~getRegisteredUsers~~ string:"'''<username>'''"	+	dbus-send --system --print-reply --dest=net.sourceforge.mumble.murmur --type=method_call /'''<serverid>''' net.sourceforge.mumble.Murmur.getRegisteredPlayers string:"'''<username>'''"

	Updating a registration:		Updating a registration:
Line 245:		Line 245:

	<userid> is also a digit number such as 4 or 30, depending on how many people are registered in the database. For instance when you run		<userid> is also a digit number such as 4 or 30, depending on how many people are registered in the database. For instance when you run
-	dbus-send --system --print-reply --dest=net.sourceforge.mumble.murmur --type=method_call /1 net.sourceforge.mumble.Murmur.~~registerUser~~ string:"Name"	+	dbus-send --system --print-reply --dest=net.sourceforge.mumble.murmur --type=method_call /1 net.sourceforge.mumble.Murmur.registerPlayer string:"Name"
	you will see after you run this command "int32" and some other text. There will be a number to the right of "int32". This number is the user's UserID.		you will see after you run this command "int32" and some other text. There will be a number to the right of "int32". This number is the user's UserID.

Line 252:		Line 252:

	On Linux you would run		On Linux you would run
-	dbus-send --system --print-reply --dest=net.sourceforge.mumble.murmur --type=method_call /1 net.sourceforge.mumble.Murmur.~~registerUser~~ string:"Name"	+	dbus-send --system --print-reply --dest=net.sourceforge.mumble.murmur --type=method_call /1 net.sourceforge.mumble.Murmur.registerPlayer string:"Name"
	You will then see some text. In it you will see "int32". Let's say you already had 5 users registered^. The number next to "int32" in the terminal would be 6. Remember this number.		You will then see some text. In it you will see "int32". Let's say you already had 5 users registered^. The number next to "int32" in the terminal would be 6. Remember this number.

Line 259:		Line 259:

	On Windows you would run		On Windows you would run
-	"C:\Program Files\Mumble\dbus-send.exe" --print-reply --dest=net.sourceforge.mumble.murmur --type=method_call /1 net.sourceforge.mumble.Murmur.~~registerUser~~ string:"Name"	+	"C:\Program Files\Mumble\dbus-send.exe" --print-reply --dest=net.sourceforge.mumble.murmur --type=method_call /1 net.sourceforge.mumble.Murmur.registerPlayer string:"Name"
	You will then see some text. In it you will see "int32". Let's say you already had 5 users registered^. The number next to "int32" in the command prompt would be 6. Remember this number.		You will then see some text. In it you will see "int32". Let's say you already had 5 users registered^. The number next to "int32" in the command prompt would be 6. Remember this number.

Line 278:		Line 278:

	Linux		Linux
-	dbus-send --system --print-reply --dest=net.sourceforge.mumble.murmur --type=method_call /1 net.sourceforge.mumble.Murmur.~~getRegisteredUsers~~ string:"<username>"	+	dbus-send --system --print-reply --dest=net.sourceforge.mumble.murmur --type=method_call /1 net.sourceforge.mumble.Murmur.getRegisteredPlayers string:"<username>"

	Windows		Windows
-	"C:\Program Files\Mumble\dbus-send.exe" --print-reply --dest=net.sourceforge.mumble.murmur --type=method_call /1 net.sourceforge.mumble.Murmur.~~getRegisteredUsers~~ string:"<username>"	+	"C:\Program Files\Mumble\dbus-send.exe" --print-reply --dest=net.sourceforge.mumble.murmur --type=method_call /1 net.sourceforge.mumble.Murmur.getRegisteredPlayers string:"<username>"

DBus Methods

2009-11-25T15:57:36Z

Undo revision 3644 by DD0T (Talk)

← Older revision		Revision as of 15:57, 25 November 2009
Line 87:		Line 87:
	= Server-specific methods =		= Server-specific methods =

-	== ~~getUsers~~ ==	+	== getPlayers ==
	* input:nothing		* input:nothing
-	* returns a list of ~~UserInfoExtended~~(see below)	+	* returns a list of PlayerInfoExtended(see below)

	== getChannels ==		== getChannels ==
Line 111:		Line 111:
	* nothing		* nothing

-	== ~~getUserState~~ ==	+	== getPlayerState ==
-	* ~~user~~ session id(unsigned int) (warning, unsigned ints are special, see below)	+	* player session id(unsigned int) (warning, unsigned ints are special, see below)
-	* ~~UserInfo~~	+	* PlayerInfo

-	== ~~setUserState~~ ==	+	== setPlayerState ==
-	* ~~UserInfo~~	+	* PlayerInfo
	* nothing		* nothing

-	== ~~getUserNames~~ ==	+	== getPlayerNames ==
	* list of session id(unsigned ints) (warning, same as above)		* list of session id(unsigned ints) (warning, same as above)
	* list of names(unicode strings)		* list of names(unicode strings)

-	== ~~getUserIds~~ ==	+	== getPlayerIds ==
	* list of names(strs on unicode strs)		* list of names(strs on unicode strs)
	* list of IDs(ints(regular ones))		* list of IDs(ints(regular ones))
Line 139:		Line 139:
	* nothing		* nothing

-	== ~~kickUser~~ ==	+	== kickPlayer ==
	* session id(unsigned int) , reason(str or unicode str)		* session id(unsigned int) , reason(str or unicode str)
	* nothing		* nothing
Line 152:		Line 152:
	</pre>		</pre>

-	= Structures (e.g. omagad, what is ~~UserInfo~~ ???) =	+	= Structures (e.g. omagad, what is PlayerInfo ???) =

-	*'''~~UserInfo~~''' is a tuple (static list) containing (dont forget to transform session before sending it):	+	*'''PlayerInfo''' is a tuple (static list) containing (dont forget to transform session before sending it):
	:(session:long, mute:bool, deaf:bool, suppressed:bool, selfMute:bool, selfDeaf:bool, channel:int)		:(session:long, mute:bool, deaf:bool, suppressed:bool, selfMute:bool, selfDeaf:bool, channel:int)

-	*'''~~UserInfoExtended~~''' is a tuple (static list) containing (you just receive it with ~~getUserState~~, you never have to send one)(notice that the 7 first are exactly the same as ~~UserInfo~~: (session:long, mute:bool, deaf:bool, suppressed:bool, selfMute:bool, selfDeaf:bool, channel:int, id:int, name:unicode str, onlinesecs:int, bytespersecond:int))	+	*'''PlayerInfoExtended''' is a tuple (static list) containing (you just receive it with getPlayerState, you never have to send one)(notice that the 7 first are exactly the same as PlayerInfo: (session:long, mute:bool, deaf:bool, suppressed:bool, selfMute:bool, selfDeaf:bool, channel:int, id:int, name:unicode str, onlinesecs:int, bytespersecond:int))
	:		:

User:Kswtch

2009-11-25T15:45:02Z

New user account

New page

User:Acerable2010

2009-11-25T14:49:32Z

New user account

New page

User:Agnord

2009-11-25T12:25:03Z

New user account

New page

Murmurguide

2009-11-25T10:30:37Z

Access Tokens:

← Older revision		Revision as of 10:30, 25 November 2009
(2 intermediate revisions not shown)
Line 1:		Line 1:
	=Setting Up a Murmur Server=		=Setting Up a Murmur Server=

-	Note that the instructions of this guide are Windows based, but all of the instructions should be adaptable to Linux. Once your IP is made static, and you get Murmur started, its ini configured, and its port is cleared through whatever firewalls are present, the setup is mostly ~~clientside~~.	+	Note that the instructions of this guide are Windows based, but all of the instructions should be adaptable to Linux. Once your IP is made static, and you get Murmur started, its ini configured, and its port is cleared through whatever firewalls are present, the setup is mostly client-side.
		+
		+	Always remember that there are professional Mumble server hosters. Simply Googling "mumble server hosting" will come up with many excellent, reliable hosts that offer servers at a very cheap price.

	==Preparations==		==Preparations==
Line 160:		Line 162:
	# Now you need to define what exactly ''MMOPlayers'' can do. The recommended settings would probably be "Allow" on all the permissions except for "Write ACL" and "Make channel"; those two permissions should be set to "Deny".		# Now you need to define what exactly ''MMOPlayers'' can do. The recommended settings would probably be "Allow" on all the permissions except for "Write ACL" and "Make channel"; those two permissions should be set to "Deny".
	# Now only people in the ''MMOplayers'' group should be able to join the channel (and those in the admin group, of course)		# Now only people in the ''MMOplayers'' group should be able to join the channel (and those in the admin group, of course)
		+
		+	===Access Tokens===
		+	Another nice feature of Mumble 1.2.0 is Access Tokens. These are what you could call passwords; basically, if you have a token that is the same name as the channel's access token, you can enter that channel.
		+
		+	So, click the channel, then select Server -> Access Tokens. Now click "Add" and type a unique token name. It's pretty much a password, so you should not give it an overly simple name.
		+
		+	Now each individual user can click themselves, click Server -> Access Tokens, and add the tokens for the channels they want to enter. Remember, channel owners should only give out the token name to those they want to enter their channel.

	===Remote Controlling the Server===		===Remote Controlling the Server===

Mumbleguide

2009-11-25T10:01:57Z

Positional Audio:

← Older revision		Revision as of 10:01, 25 November 2009
(3 intermediate revisions not shown)
Line 37:		Line 37:

	===Whisper===		===Whisper===
-	Mumble 1.2.0 includes a really nice feature: the ability to whisper to a specific player or channel. You must make a shortcut to do this; go to Configure -> Settings -> Shortcuts and click Add. A new entry will be displayed. Under the function field, double click your entry and scroll down to "Whisper." Now double click the "Data" field and then click "..."	+	Mumble 1.2.0 includes a really nice feature: the ability to whisper to a specific player or channel. You must make a shortcut to do this; go to Configure -> Settings -> Shortcuts and click "Add." A new entry will be displayed. Under the function field, double click your entry and scroll down to "Whisper." Now double click the "Data" field and then click "..."

-	A window will pop up where you can select what type of whisper you want: ~~user~~ or Channel.	+	A window will pop up where you can select what type of whisper you want: User or Channel.

-	If you want a user, then click the drop-down box and select a user, clicking Add after each one. If you check "Ignore positional audio," then whatever you transmit will be centered, regardless if you are linked to a game or not. Note that the users you want to add must currently be in the server.	+	If you want a user, then click the drop-down box and select a user, clicking "Add" after each one. If you check "Ignore positional audio," then whatever you transmit will be centered, regardless if you are linked to a game or not. Note that the users you want to add must currently be in the server.

-	Whisper to Channel is self-explanatory.	+	"Whisper to Channel" is self-explanatory.

	===Mesages===		===Mesages===
	'''Advanced Config'''		'''Advanced Config'''

-	As previously discussed, messages can sometimes be annoying. If you want to disable other messages to the log (listed as Console, it's the window that shows text when something happens), or to Notifications (the little messages that Windows pops up at the bottom right corner of your screen), you can also select which ones to activate from Configure -> Settings -> Messages	+	As previously discussed, messages can sometimes be annoying. If you want to disable other messages to the log (listed as "Console"; it's the window that shows text when something happens), or to "Notifications" (the little messages that Windows pops up at the bottom right corner of your screen), you can also select which ones to activate from Configure -> Settings -> Messages

	===Positional Audio===		===Positional Audio===
Line 55:		Line 55:
	Mumble has positional auto for certain [[Games\|games]]. This means that when enabled, the audio transmitted in Mumble will appear to emanate from your in-game avatar. This positional audio is obtained using plugin libraries in the form of DLLs.		Mumble has positional auto for certain [[Games\|games]]. This means that when enabled, the audio transmitted in Mumble will appear to emanate from your in-game avatar. This positional audio is obtained using plugin libraries in the form of DLLs.

-	If you have games on that list, and wish to use PA (positional audio)~~, turn on Advanced config~~, go to the Plugins section, check "Link to Game and Transmit Position," then go to the Audio Output section, check "Positional Audio," and then check "Heaphones" (if you are using headphones). Most people like to hear each other clearly all the time, so it is recommended that you set "Minimum Volume" to at least 90%.	+	If you have games on that list, and wish to use PA (positional audio), go to the Plugins section, check "Link to Game and Transmit Position," then go to the Audio Output section, check "Positional Audio," and then check "Heaphones" (if you are using headphones). Most people like to hear each other clearly all the time, so it is recommended that you set "Minimum Volume" to at least 90%.

	===Skins===		===Skins===

Installing Mumble

2009-11-25T09:57:02Z

Linux:

← Older revision		Revision as of 09:57, 25 November 2009
(5 intermediate revisions not shown)
Line 13:		Line 13:
	== Linux ==		== Linux ==

-	For ~~most~~ Linux distributions,	+	For Linux distributions besides Debian-based,

-	~~the~~ client package name is mumble	+	The client package name is ''mumble''.

-	~~the~~ server package name is murmur	+	The server package name is ''murmur''.

-	~~===~~ Debian ~~or Debian based~~ distributions ~~===~~	+	For most Debian distributions,

-	~~Package for~~ client: mumble	+	The client package name is ''mumble''.

-	~~Package for~~ server: mumble-server	+	The server package name is ''mumble-server''.
		+
		+	'''If''' you do not find an appropriate server package for your distribution, the [http://mumble.info/snapshot/ static build] will usually work. Static builds start with "murmur-static_x86."

	==== Debian ====		==== Debian ====
Line 34:		Line 36:

	Ubuntu carries whatever Mumble version was current at the time of the release in the universe repository. Backports of current releases can be found [https://launchpad.net/~slicer/+archive/ppa in the PPA].		Ubuntu carries whatever Mumble version was current at the time of the release in the universe repository. Backports of current releases can be found [https://launchpad.net/~slicer/+archive/ppa in the PPA].
-
-	~~----~~

	=== SUSE ===		=== SUSE ===

Murmurguide

2009-11-25T09:49:31Z

Connecting to Your Murmur Server:

← Older revision		Revision as of 09:49, 25 November 2009
(5 intermediate revisions not shown)
Line 1:		Line 1:
	=Setting Up a Murmur Server=		=Setting Up a Murmur Server=
		+
		+	Note that the instructions of this guide are Windows based, but all of the instructions should be adaptable to Linux. Once your IP is made static, and you get Murmur started, its ini configured, and its port is cleared through whatever firewalls are present, the setup is mostly clientside.

	==Preparations==		==Preparations==

-	===Configure ~~Windows~~===	+	===Configure the OS===

		+	====Windows====
	Before you can have Murmur completely working, you need to make a few changes to your network on Windows.		Before you can have Murmur completely working, you need to make a few changes to your network on Windows.

	First, make your IP static. Unless you're just going to run this server a few times, or it is a LAN server only to be found via [[Bonjour]], you need to make your IP static so that a person outside of your network can dependably connect to your Murmur server. If you have no idea how to make your IP static, read [http://portforward.com/networking/static-xp.htm this guide] for doing in on Windows XP, and [http://portforward.com/networking/static-vista.htm this guide] for doing it on Windows Vista.		First, make your IP static. Unless you're just going to run this server a few times, or it is a LAN server only to be found via [[Bonjour]], you need to make your IP static so that a person outside of your network can dependably connect to your Murmur server. If you have no idea how to make your IP static, read [http://portforward.com/networking/static-xp.htm this guide] for doing in on Windows XP, and [http://portforward.com/networking/static-vista.htm this guide] for doing it on Windows Vista.

-	===~~Configure~~ Linux===	+	====Linux====

-	~~This guide is mainly for Windows~~, ~~but all of~~ the instructions ~~should be adaptable~~ to ~~Linux~~. ~~Once~~ you ~~have Murmur started, its ini configured, and its port is cleared through whatever firewalls are present, the setup is mostly clientside~~.	+	Generally, the config file for setting a static IP involves either using your distro's GUI network tool or editing configuration files (for example, ''/etc/network/interfaces''). It is recommended that you [http://www.google.com/ Google] for instructions to set a static IP for your specific distribution. Generally something like "Ubuntu static IP" will get what you need.

	===Configure Network===		===Configure Network===
Line 26:		Line 29:

	For nearly all Linux distributions, you can simply use the [http://mumble.info/snapshot/ static binary]. However, if your specific distribution supports Murmur (such as Ubuntu), you should look into using the specific packages for it.		For nearly all Linux distributions, you can simply use the [http://mumble.info/snapshot/ static binary]. However, if your specific distribution supports Murmur (such as Ubuntu), you should look into using the specific packages for it.
		+
	==Setting Up the Server==		==Setting Up the Server==

Line 100:		Line 104:
	The ''Servername'' field contains the name that will be displayed in your server list.		The ''Servername'' field contains the name that will be displayed in your server list.

-	The ''Address'' field is the external IP of your server; if you do not know the external IP, go here (from the computer hosting Murmur): http://whatismyipaddress.com/ ; or your servers bonjour name (prefixed with @).	+	The ''Address'' field is the external IP of your server; if you do not know the external IP, go here (from the computer hosting Murmur): http://whatismyipaddress.com/ ; or your servers bonjour name (prefixed with @). '''Your external IP is ''never'' 192.168.x.x'''

	The ''Username'' field takes your users Name. Be aware that names are case sensitive. If you want to connect as SuperUser mind the capitalization. Since you are going to want to add your user as an admin, put in that username for now.		The ''Username'' field takes your users Name. Be aware that names are case sensitive. If you want to connect as SuperUser mind the capitalization. Since you are going to want to add your user as an admin, put in that username for now.

User:BodkoEd

2009-11-25T06:12:30Z

New user account

New page

1.2.0

2009-11-25T05:20:27Z

← Older revision		Revision as of 05:20, 25 November 2009
Line 92:		Line 92:
	<br style="clear:both"/>		<br style="clear:both"/>

-	== Automatic Plugin Update ==	+	== Automatic Plugin Update and Enhanced Plugin Support ==

	<span style="float:left; margin-right:5px">http://mumble.sourceforge.net/static/plugins_snip.png</span>		<span style="float:left; margin-right:5px">http://mumble.sourceforge.net/static/plugins_snip.png</span>
	As the number of positional audio plugins increase, it has become a bit of a problem that games are updated much more frequently than Mumble releases. There is now a system to automatically update plugins, which means they'll be installed as soon as they are available.		As the number of positional audio plugins increase, it has become a bit of a problem that games are updated much more frequently than Mumble releases. There is now a system to automatically update plugins, which means they'll be installed as soon as they are available.
		+
		+	Also, plugins are now configured so that one only hears positional audio from those who are playing the same game, and in some cases, only from those in the same server and team, depending on the plugin.
	<br style="clear:both"/>		<br style="clear:both"/>

User:Roonie

2009-11-25T05:20:00Z

New user account

New page

Commercial Hosting

2009-11-25T05:15:29Z

← Older revision		Revision as of 05:15, 25 November 2009
Line 13:		Line 13:
	As no processing is done serverside, we were not able to push even 1% of actual CPU usage with 4 users on a Xeon 3.4Ghz. We do see quite a few context switches though, so high quality network cards is likely a requirement.		As no processing is done serverside, we were not able to push even 1% of actual CPU usage with 4 users on a Xeon 3.4Ghz. We do see quite a few context switches though, so high quality network cards is likely a requirement.

-	Mumble uses ~~VBR speex~~, and using the highest quality and lowest latency, the peak bandwidth is ~~65kbit~~/s per speaker per listener (with IP and UDP overhead).	+	Mumble uses CELT, and using the highest quality and lowest latency, the peak bandwidth is 134kbit/s per speaker per listener (with IP and UDP overhead). However, this is the ''max'' bandwidth, and the recommended bandwidth (that has a very unnoticeable quality reduction for normal speech) is 63kbit/s. In other words, a server with 10 users and 1 user speaking will need to replicate the datastream 9 times, for a total of 639=567kbit/s outgoing bandwidth. If all 10 users speak at once, each stream has to be replicated 9 times, for a total of 63kbit/s9*10=5.67 Mbit/s. Note that these are ''absolute'' worst-case scenarios, and the average bandwidth use is around 20-30 kbit/s during speech, multiplied by the number of listeners; it is only possibly in a real world scenario for at most two people to be talking at the same time and still understand what they are saying.
-	In other words, a server with 10 users and 1 user speaking will need to replicate the datastream 9 times, for a total of 659=~~585kbit~~/s outgoing bandwidth. If all 10 users speak at once, each stream has to be replicated 9 times, for a total of ~~65kbit~~/s9*10=5.8 Mbit/s. Note that these are absolute worst-case scenarios, and the average bandwidth use is around 20-30 kbit/s during speech, multiplied by the number of listeners.	+

	Mumble-Tower has their [http://mumble-tower.de/stats/all resource usage for murmur] online. That should give an example of resource use with a large number of virtual servers and users.		Mumble-Tower has their [http://mumble-tower.de/stats/all resource usage for murmur] online. That should give an example of resource use with a large number of virtual servers and users.
Line 70:		Line 69:
	Murmur supports DBus RPC calls, which allow querying all information of the server in real time, and also allow management. Hence, it's fairly easy to write scripts to query and display server status, and also to create web frontends for server administration.		Murmur supports DBus RPC calls, which allow querying all information of the server in real time, and also allow management. Hence, it's fairly easy to write scripts to query and display server status, and also to create web frontends for server administration.

-	[[ICE]] has now also been implemented into Murmur, and ~~may eventually replace~~ [[DBus]], given it's multi-platform features and usability.	+	[[ICE]] has now also been implemented into Murmur, and has all but replaced [[DBus]], given it's multi-platform features and usability.

-	[[Category:Needs Update for 1.2.0]]	+	[[Category:Needs Update for 1.2.0. Updated, need signoff.]]

Mumbleguide

2009-11-25T05:04:30Z

Skins:

← Older revision		Revision as of 05:04, 25 November 2009
(4 intermediate revisions not shown)
Line 6:		Line 6:

	===Wizards===		===Wizards===
-	When you first start Mumble, it will ask you if you want to go through the Audio Wizard and Certificate Wizard. ''You should''. And don't just rush through it. Carefully read each step, and find out what the Wizard is asking you. Especially pay attention to the voice activation pages; you don't want everyone complaining that they can't hear you or that they hear you ''too much''. '''~~Make sure that~~ you back up your certificate to a flash drive or external storage medium ~~in the Certificate Wizard~~!'''	+	When you first start Mumble, it will ask you if you want to go through the Audio Wizard and Certificate Wizard. ''You should''. And don't just rush through it. Carefully read each step, and find out what the Wizard is asking you. Especially pay attention to the voice activation pages; you don't want everyone complaining that they can't hear you or that they hear you ''too much''. '''When you back up your certificate in the Certificate Wizard, save it to a flash drive or external storage medium; do NOT save it to your hard drive!'''

	===GUI===		===GUI===
-	Mumble's GUI is build with the powerful Qt (cute) SDK, and it is slightly different from the GUI used by other applications you might have used in the past. For that reason, it is recommended that on first start, you explore the basic GUI layout of Mumble. Don't change anything, just try and get used to it.
-
	You can permanently change the sub-sections of the Mumble window. For instance, if you want the log at the bottom, hover your mouse at the top of the log window, just below its edge, and wait for about a half-second. A small edge will drop down. When that happens, click and hold, and then drag the window to the bottom of the main window. You can do the same with the chat window; it's recommended that you put it below the log.		You can permanently change the sub-sections of the Mumble window. For instance, if you want the log at the bottom, hover your mouse at the top of the log window, just below its edge, and wait for about a half-second. A small edge will drop down. When that happens, click and hold, and then drag the window to the bottom of the main window. You can do the same with the chat window; it's recommended that you put it below the log.

	After that, open up the Connect window (Server -> Connect). You can add a Favorite server by clicking "Add New...." Contact your server administrator for IP and Port. You can use whatever name you choose when you connect to the server, but whatever name you are using when you register with the server will always be used for that server, unless an admin removes it.		After that, open up the Connect window (Server -> Connect). You can add a Favorite server by clicking "Add New...." Contact your server administrator for IP and Port. You can use whatever name you choose when you connect to the server, but whatever name you are using when you register with the server will always be used for that server, unless an admin removes it.

-	Once you are connected to a server, you should be able to register yourself by clicking your username, right clicking, ~~and~~ then selecting "Register."	+	Once you are connected to a server, you should be able to register yourself by clicking your username, right clicking it, then selecting "Register."

	===Configuration===		===Configuration===
Line 41:		Line 39:
	Mumble 1.2.0 includes a really nice feature: the ability to whisper to a specific player or channel. You must make a shortcut to do this; go to Configure -> Settings -> Shortcuts and click Add. A new entry will be displayed. Under the function field, double click your entry and scroll down to "Whisper." Now double click the "Data" field and then click "..."		Mumble 1.2.0 includes a really nice feature: the ability to whisper to a specific player or channel. You must make a shortcut to do this; go to Configure -> Settings -> Shortcuts and click Add. A new entry will be displayed. Under the function field, double click your entry and scroll down to "Whisper." Now double click the "Data" field and then click "..."

-	A window will pop up where you can select what type of whisper you want: user or Channel. If you want a user, then click the drop-down box and select a user, clicking Add after each one. If you check "Ignore positional audio," then whatever you transmit will be centered, regardless if you are linked to a game or not.	+	A window will pop up where you can select what type of whisper you want: user or Channel.
		+
		+	If you want a user, then click the drop-down box and select a user, clicking Add after each one. If you check "Ignore positional audio," then whatever you transmit will be centered, regardless if you are linked to a game or not. Note that the users you want to add must currently be in the server.

-	Whisper to Channel is self-explanatory.	+	Whisper to Channel is self-explanatory.

	===Mesages===		===Mesages===
Line 58:		Line 58:

	===Skins===		===Skins===
-	If you wish to make your Mumble look pretty, there are many available options. [[Skins\|Here]] is a skins page that has links to many excellent skins~~, and a very easy tool~~ to make a skin with ''any'' colors ~~that~~ you want is [http://zavaboy.com/phpbox/juicer/ Juicer].	+	If you wish to make your Mumble look pretty, there are many available options. [[Skins\|Here]] is a skins page that has links to many excellent skins; if you want to make a skin with ''any'' colors you want, use [http://zavaboy.com/phpbox/juicer/ Juicer].

	'''To install a skin:'''		'''To install a skin:'''

Murmurguide

2009-11-25T04:50:46Z

ACLs:

Mumbleguide

2009-11-25T04:38:34Z

← Older revision		Revision as of 04:38, 25 November 2009
Line 37:		Line 37:
	Server Connected		Server Connected
	Server Disconnected		Server Disconnected
		+
		+	===Whisper===
		+	Mumble 1.2.0 includes a really nice feature: the ability to whisper to a specific player or channel. You must make a shortcut to do this; go to Configure -> Settings -> Shortcuts and click Add. A new entry will be displayed. Under the function field, double click your entry and scroll down to "Whisper." Now double click the "Data" field and then click "..."
		+
		+	A window will pop up where you can select what type of whisper you want: user or Channel. If you want a user, then click the drop-down box and select a user, clicking Add after each one. If you check "Ignore positional audio," then whatever you transmit will be centered, regardless if you are linked to a game or not.
		+
		+	Whisper to Channel is self-explanatory.

	===Mesages===		===Mesages===

User:Mlevinspuhl

2009-11-25T02:25:36Z

New user account

New page

Games

2009-11-25T01:24:13Z

← Older revision		Revision as of 01:24, 25 November 2009
Line 6:		Line 6:
	# Go to ''Plugins'' and check "Link to Game and Transmit Position"		# Go to ''Plugins'' and check "Link to Game and Transmit Position"
	# In ''Audio Output'' check "Positional Audio"		# In ''Audio Output'' check "Positional Audio"
-	# If you use a headset or headphones then check "Headphones".	+	# If you use a headset or headphones then check "Headphones".
		+
		+	'''Just because your game says it is a different version from the plugin does not necessarily mean that the plugin will not work.'''

	It is possible that some plugins are outdated in the current release, in that case please check the lists below.		It is possible that some plugins are outdated in the current release, in that case please check the lists below.

Mumbleguide

2009-11-25T00:27:20Z

← Older revision		Revision as of 00:27, 25 November 2009
(One intermediate revision not shown)
Line 4:		Line 4:

	Ok. So you have Mumble installed. Now you are probably wondering what to do next. Here's a rundown of the basics of Mumble.		Ok. So you have Mumble installed. Now you are probably wondering what to do next. Here's a rundown of the basics of Mumble.
		+
		+	===Wizards===
		+	When you first start Mumble, it will ask you if you want to go through the Audio Wizard and Certificate Wizard. ''You should''. And don't just rush through it. Carefully read each step, and find out what the Wizard is asking you. Especially pay attention to the voice activation pages; you don't want everyone complaining that they can't hear you or that they hear you ''too much''. '''Make sure that you back up your certificate to a flash drive or external storage medium in the Certificate Wizard!'''

	===GUI===		===GUI===
-	Mumble's GUI is build with the powerful Qt (cute) SDK, and it is slightly different from the GUI used by other applications you might have used in the past. For that reason, it is recommended that on first start, you explore the basic GUI layout of Mumble. Don't change anything, just try and get used to it.	+	Mumble's GUI is build with the powerful Qt (cute) SDK, and it is slightly different from the GUI used by other applications you might have used in the past. For that reason, it is recommended that on first start, you explore the basic GUI layout of Mumble. Don't change anything, just try and get used to it.
		+
		+	You can permanently change the sub-sections of the Mumble window. For instance, if you want the log at the bottom, hover your mouse at the top of the log window, just below its edge, and wait for about a half-second. A small edge will drop down. When that happens, click and hold, and then drag the window to the bottom of the main window. You can do the same with the chat window; it's recommended that you put it below the log.

	After that, open up the Connect window (Server -> Connect). You can add a Favorite server by clicking "Add New...." Contact your server administrator for IP and Port. You can use whatever name you choose when you connect to the server, but whatever name you are using when you register with the server will always be used for that server, unless an admin removes it.		After that, open up the Connect window (Server -> Connect). You can add a Favorite server by clicking "Add New...." Contact your server administrator for IP and Port. You can use whatever name you choose when you connect to the server, but whatever name you are using when you register with the server will always be used for that server, unless an admin removes it.

-	Once you are connected to a server, you should be able to register yourself by clicking your username, right clicking, and then selecting "Register."	+	Once you are connected to a server, you should be able to register yourself by clicking your username, right clicking, and then selecting "Register."
-		+
-	~~===Wizards===~~	+
-	When you first start Mumble, it will ask you if you want to go through the Audio Wizard and Certificate Wizard. ''You should''. And don't just rush through it. Carefully read each step, and find out what the Wizard is asking you. Especially pay attention to the voice activation pages; you don't want everyone complaining that they can't hear you or that they hear you ''too much''. '''Make sure that you back up your certificate to a flash drive or external storage medium in the Certificate Wizard!'''	+

	===Configuration===		===Configuration===

Installing Mumble

2009-11-25T00:21:53Z

Linux:

← Older revision		Revision as of 00:21, 25 November 2009
Line 12:		Line 12:

	== Linux ==		== Linux ==
		+
		+	For most Linux distributions,
		+
		+	the client package name is mumble
		+
		+	the server package name is murmur
		+
	=== Debian or Debian based distributions ===		=== Debian or Debian based distributions ===

← Older revision		Revision as of 04:50, 25 November 2009
(One intermediate revision not shown)
Line 113:		Line 113:

	# Join your server following the [[Murmurguide#Connecting_to_Your_Murmur_Server\|previous step]]		# Join your server following the [[Murmurguide#Connecting_to_Your_Murmur_Server\|previous step]]
-	# When you are connected to the server, right click on your username and then click ''Register''	+	# When you are connected to the server, right click on your username, and then click "Register"
-	# Reconnect as the SuperUser - Go back to your server list, and on the main Mumble window click ''Server->Connect''. You will see the server you added in the previous step. Right click it and select "Edit...." Change ''Username'' to SuperUser, click ''OK'', then click ''Connect~~''.~~	+	# Reconnect as the SuperUser - Go back to your server list, and on the main Mumble window click Server -> Connect. You will see the server you added in the previous step. Right click it and select "Edit..." Change ''Username'' to SuperUser, click OK, then click Connect.
-	~~# At the top right of the main Mumble window, click Configure, then Settings. At the bottom left, you will see ''Advanced''~~.	+
	# Right click the "Root" Channel (it will be above your username; it will be whatever you named it if you set the registerName in Murmur.ini) and click ''Edit''.		# Right click the "Root" Channel (it will be above your username; it will be whatever you named it if you set the registerName in Murmur.ini) and click ''Edit''.
	# Go to the Groups tab		# Go to the Groups tab
Line 135:		Line 134:
	Many people have complained about the complexity of ACLs - that they are complicated, hard, and cumbersome. ''They are none of these if used correctly.'' You see, the ACLs ''can'' be as complicated as you want. It is basically a full permissions suite similar to what you would deal with on an Apache server. But it doesn't ''have'' to be that complicated!		Many people have complained about the complexity of ACLs - that they are complicated, hard, and cumbersome. ''They are none of these if used correctly.'' You see, the ACLs ''can'' be as complicated as you want. It is basically a full permissions suite similar to what you would deal with on an Apache server. But it doesn't ''have'' to be that complicated!

-	Do you know what ACL means? Access Control List. That is all. An ACL simply defines where and what a ''Group'' can do. A Group is simply a bunch of users defined by a name. That is all.	+	Do you know what ACL means? Access Control List. That is all. An ACL simply defines where and what a "Group" can do. A Group is simply a bunch of users defined by a name. That is all.

	Here is a basic guide that you can use to create the most essential permissions for your server:		Here is a basic guide that you can use to create the most essential permissions for your server:
Line 145:		Line 144:
	# Make sure that everyone you want to add is registered with the server		# Make sure that everyone you want to add is registered with the server
	# Make the channel for the people who want it (for this example, make an MMO channel)		# Make the channel for the people who want it (for this example, make an MMO channel)
-	# Right click on the root channel, click Edit, then go to the Groups tab	+	# Right click on the root channel, click "Edit", then go to the Groups tab
-	# Click, in the empty box at the top, and type the name of the group you want to add. For example, if you wanted to make a channel for MMO players, you might name your group ''MMOplayers''. Type that into the box and press enter. A new group has been made.	+	# Click, in the empty box at the top, and type the name of the group you want to add. For example, if you wanted to make a channel for MMO players, you might name your group "MMOplayers." Type that into the box and press enter. A new group has been made.
	# Now you need to add members to this group. In the box at the bottom left, type a member name and press enter after each name. The names that you add should appear in the box above the input box.		# Now you need to add members to this group. In the box at the bottom left, type a member name and press enter after each name. The names that you add should appear in the box above the input box.

	Finally, you need to create an ACL for the channel. Close the current window, and then right click on the MMO channel and select Edit. Click the ACL tab.		Finally, you need to create an ACL for the channel. Close the current window, and then right click on the MMO channel and select Edit. Click the ACL tab.

-	# Here is where it ''appears'' to become complicated, when in fact it is not at all. What you first see is inherited ACLs. All inherited means is that the permissions of the above channel are automatically applied to this one. Since we don't want that, uncheck ''Inherit ACLs''.	+	# Here is where it ''appears'' to become complicated, when in fact it is not at all. What you first see is inherited ACLs. All inherited means is that the permissions of the above channel are automatically applied to this one. Since we don't want that, uncheck "Inherit ACLs."
	# Now if you just left it like it is now, then the @all permissions would be in effect for this channel. Anyone who went into this channel (except for those in the admin group; they override this) would have the permissions you see at the right.		# Now if you just left it like it is now, then the @all permissions would be in effect for this channel. Anyone who went into this channel (except for those in the admin group; they override this) would have the permissions you see at the right.
-	# But we want to make some ACLs. Start off by adding an @all. Just click ''Add'' and it will be created. By default, the Group will be ''all''. All the ''@'' means is "apply to." For this group, you probably just want to set ''Deny'' for all the permissions. However, you don't have to manually click ''Deny'' on everything. The group that is defined before it, the ''@all'' in italics, already has set permissions. For example, it defaults to deny ''Write ACL''. So, in the ''@all'' ACL below it, don't check either ''Deny'' or ''Allow'' and it will default to ''Deny''.	+	# But we want to make some ACLs. Start off by adding an "@all." Just click "Add" and it will be created. By default, the Group will be ''all''. All the ''@'' means is "apply to." For this group, you probably just want to set "Deny" for all the permissions. However, you don't have to manually click "Deny" on everything. The group that is defined before it, the "@all" in italics, already has set permissions. For example, it defaults to deny "Write ACL." So, in the "@all" ACL below it, if you don't check either "Deny" or "Allow" and it will default to "Deny."
-	# Now click Add again. However, this time you need to click the ''Group'' box at the bottom left. Delete the ''all'' text from there and type ''MMOplayers'', then press enter.	+	# Now click "Add" again. However, this time you need to click the "Group" box at the bottom left. Delete the "all" text from there and type ''MMOplayers'', then press enter.
-	# Now you need to define what exactly ''MMOPlayers'' can do. The recommended settings would probably be ''Allow'' on all the permissions except for ''Write ACL'' and ''Make channel''; those two permissions should be set to ''Deny''.	+	# Now you need to define what exactly ''MMOPlayers'' can do. The recommended settings would probably be "Allow" on all the permissions except for "Write ACL" and "Make channel"; those two permissions should be set to "Deny".
	# Now only people in the ''MMOplayers'' group should be able to join the channel (and those in the admin group, of course)		# Now only people in the ''MMOplayers'' group should be able to join the channel (and those in the admin group, of course)