NameDateSize

..16-Mar-201612 KiB

.gitignore30-Nov-2015633

.gitmodules30-Nov-2015957

.tx/28-Apr-20144 KiB

3rdparty/30-Nov-20154 KiB

3rdPartyLicenses/17-Nov-20154 KiB

CHANGES30-Dec-2014395 KiB

compiler.pri30-Nov-201510.5 KiB

Doxyfile18-Mar-201571.2 KiB

g15helper/30-Nov-20154 KiB

icons/14-Dec-20154 KiB

INSTALL28-Sep-20155.1 KiB

installer/30-Nov-20154 KiB

LICENSE02-Oct-20142.1 KiB

macx/10-Feb-20154 KiB

main.pro30-Nov-20151.8 KiB

man/27-Oct-20144 KiB

overlay/09-Dec-20154 KiB

overlay_gl/30-Nov-20154 KiB

overlay_winx64/27-Apr-20154 KiB

plugins/02-Jan-20154 KiB

qt.pri30-Dec-2014128

rcc.pri30-Nov-2015932

README06-Jul-20152.4 KiB

README.Linux08-May-2015973

README.static.linux06-Jul-20154.1 KiB

README.static.osx06-Jul-20154 KiB

samples/29-Dec-20124 KiB

scripts/09-Dec-20154 KiB

src/30-Nov-20154 KiB

symbols.pri29-Dec-20121.2 KiB

themes/07-Aug-20154 KiB

toolchain/27-Apr-20154 KiB

winpaths_default.pri24-Mar-2014909

winpaths_static.pri24-Mar-2014869

README

1         M U M B L E
2
3 A voicechat utility for gamers
4
5      http://mumble.info/
6
7      #mumble on freenode
8
9Mumble is a voicechat program for gamers written on top of Qt and Speex.
10
11There are two modules in Mumble; the client (mumble) and the server
12(murmur). The client works on Win32/64, Linux and Mac OS X, while the
13server should work on anything Qt can be installed on.
14
15Note that when we say Win32, we mean Windows XP or newer.
16
17Running Mumble
18==============
19
20On Windows, after installation, you should have a new Mumble folder in your
21Start Menu, from which you can start Mumble.
22
23On Mac OS X, to install Mumble, drag the application from the downloaded
24disk image into your /Applications folder.
25
26Once Mumble is launched, you need a server to connect to. Either create your
27own or join a friend's.
28
29Running Murmur on Unix-like systems
30===================================
31
32Murmur should be run from the command line, so start a shell (command prompt)
33and go to wherever you installed Mumble. Run murmur as
34
35murmurd [-supw <password>] [-ini <inifile>] [-fg] [v]
36
37-supw   Set new password for the user SuperUser, which is hardcoded to
38        bypass ACLs. Keep this password safe. Until you set a password,
39        the SuperUser is disabled. If you use this option, murmur will
40        set the password in the database and then exit.
41
42-ini    Use a inifile other than murmur.ini, use this to run several instances
43        of murmur from the same directory. Make sure each instance is using
44        a separate database.
45
46-fg     Run in the foreground, logging to standard output.
47
48-v      More verbose logging.
49
50Running Murmur on Mac OS X
51==========================
52
53Murmur is distributed seperately from the Mumble client on Mac OS X.
54It is called Static OS X Server and can be downloaded from the main webpage.
55
56Once downloaded it can be run in the same way as on any other Unix-like system.
57For more information please see the 'Running Murmur on Unix-like systems' above.
58
59Running Murmur on Win32
60=======================
61
62Doubleclick the Murmur icon to start murmur. There will be a small icon on your
63taskbar from which you can view the log.
64
65To set the superuser password, run murmur with the parameters '-supw <password>'.
66
67Bandwidth usage
68===============
69
70Mumble will use 10-40 kbit/s outgoing, and the same incoming for each user.
71So if there are 10 other users on the server with you, your incoming
72bandwidth requirement will be 100-400 kbit/s if they all talk at the same time.
73

README.Linux

1OpenGL Overlay
2==============
3
4The OpenGL overlay works by intercepting the call to switch buffers, and just
5before the buffer switch we draw our nice GUI.
6
7To load a game with the overlay enabled, start the game as this:
8  LD_PRELOAD=/path/to/libmumble.so.1.1 gamename
9
10If you have Mumble installed through the binary packages, this can be done by
11simply typing:
12  mumble-overlay gamename
13
14Global Keyboard Events
15======================
16
17On Linux, Mumble supports reading the kernel input devices. To use this,
18make sure mumble can open /dev/input/event* for reading. To test it out,
19that should only require:
20  sudo chmod a+r /dev/input/event*
21However, be aware that this will most likely only last until the next reboot
22(at which point devfs is recreated) and you also allow any program run by any
23user to monitor the physical keyboard.
24
25Without this, Mumble will continuously poll the mouse and keyboard state for
26changes, which will use a tiny bit of processing power.
27

README.static.linux

1         M U M B L E
2
3 A voicechat utility for gamers
4
5      http://mumble.info/
6
7      #mumble on freenode
8
9
10What is Murmur?
11===============
12
13Murmur is the server component of Mumble, an open-source voice chat utility.
14
15This package is a statically compiled version of Murmur for Linux. It is
16independent of your distribution's package manager, and is intended to be
17run as-is, or with minimal set up.
18
19
20Running Murmur
21==============
22
23In this build of Murmur, the binary is called 'murmur.x86'. To get Murmur
24up and running, simply execute the following command at your shell:
25
26 $ ./murmur.x86 -fg -ini murmur.ini
27
28This will spawn a foregrounded (Murmur will, by default, run in daemon mode,
29which means it will launch itself as a background process on your system).
30
31
32The First Run
33=============
34
35When Murmur runs for the first time, it performs a few special initialization
36steps, such as setting up its database, as well as generating a certificate
37for its initial server and a password for the SuperUser user.
38
39This password is important for setting up the Murmur server, so make a note
40of it. It is output by the Murmur server the first time it runs, and will
41look something like this:
42
43  <W> HH:MM:DD 1 => Password for 'SuperUser' set to '<YourSuperUserPassword>'
44
45
46Initial User Setup
47==================
48
49Murmur has the concept of a 'SuperUser', which is the initial administrative user
50used to configure your server.  Typically, this user will only be used for initial
51setup, and in recovery situations. A regular user, with some administrative privileges
52is usually set up as a first step.  To do this, follow the steps below:
53
54 1. In your Mumble client, ensure that you have a certificate for your user.
55    (A certificate is generated by Mumble by default, but you can create a new
56     one if you wish -- or use an existing S/MIME email certificate if you wish.)
57
58 2. Connect to your server with the user that you wish to grant administrative
59    privileges to. (Your username will be stored on the server when you register
60    yourself, so pick something you'd like to keep!)
61
62 3. Once connected, right click your user name in the server view and choose
63    'Register'.  This will register your user to the server (this makes the
64    server remember you as a user -- but you still will not have administrative
65    privileges).
66
67 4. Once registered, you can disconnect from the server.  Now it is time to
68    connect using the SuperUser account that the server created for you
69    when you launched it the first time.
70
71    Simply specify SuperUser as your username, and the password that Murmur
72    gave you as the password.
73
74 5. After connecting as the SuperUser, right click the 'Root'-channel and
75    choose Edit.  In the Edit dialog, click the Groups tab.
76
77    In the Groups dropdown, choose the admin group.
78
79    Then, under Members three lists should appear, showing Members, Excluded
80    Members and Inherited Members. We're only interested in Members. Expand
81    the drop down below the member list and find the username of the user
82    you registered in step 3.
83
84    Click Add to add the user to the admin group.
85
86 6. Your user is now an administrator.
87
88For more advanced setup and usage of Murmur, please visit the Mumble Wiki,
89at http://mumble.info/. Some pages of interest are available at:
90
91   http://wiki.mumble.info/wiki/Running_Murmur
92   http://wiki.mumble.info/wiki/ACL_and_Groups
93   http://wiki.mumble.info/wiki/Murmurguide
94
95Additional Murmur Options
96=========================
97
98The above instructions use a very bare-bones approach to running Murmur.
99Several other command line options are available. These are listed below:
100
101murmur.x86 [-supw <password>] [-ini <inifile>] [-fg] [v]
102
103-supw   Set new password for the user SuperUser, which is hardcoded to
104        bypass ACLs. Keep this password safe. If you use this option,
105        Murmur will set the password in the database and then exit.
106
107-ini    Use an ini file other than murmur.ini, use this to run several
108        instances of Murmur from the same directory. Make sure each
109        instance is using a separate database. (Specified in the ini file.)
110
111-fg     Run in the foreground, logging to standard output.
112
113-v      More verbose logging.
114

README.static.osx

1         M U M B L E
2
3 A voicechat utility for gamers
4
5      http://mumble.info/
6
7      #mumble on freenode
8
9
10What is Murmur?
11===============
12
13Murmur is the server component of Mumble, an open-source voice chat utility.
14
15This package is a statically compiled version of Murmur for OS X.
16
17
18Running Murmur
19==============
20
21In this build of Murmur, the binary is called 'murmurd'. To get Murmur
22up and running, simply execute the following command at your shell:
23
24 $ ./murmurd -fg -ini murmur.ini
25
26This will spawn a foregrounded (Murmur will, by default, run in daemon mode,
27which means it will launch itself as a background process on your system).
28
29
30The First Run
31=============
32
33When Murmur runs for the first time, it performs a few special initialization
34steps, such as setting up its database, as well as generating a certificate
35for its initial server and a password for the SuperUser user.
36
37This password is important for setting up the Murmur server, so make a note
38of it. It is output by the Murmur server the first time it runs, and will
39look something like this:
40
41  <W> HH:MM:DD 1 => Password for 'SuperUser' set to '<YourSuperUserPassword>'
42
43
44Initial User Setup
45==================
46
47Murmur has the concept of a 'SuperUser', which is the initial administrative user
48used to configure your server.  Typically, this user will only be used for initial
49setup, and in recovery situations. A regular user, with some administrative privileges
50is usually set up as a first step.  To do this, follow the steps below:
51
52 1. In your Mumble client, ensure that you have a certificate for your user.
53    (A certificate is generated by Mumble by default, but you can create a new
54     one if you wish -- or use an existing S/MIME email certificate if you wish.)
55
56 2. Connect to your server with the user that you wish to grant administrative
57    privileges to. (Your username will be stored on the server when you register
58    yourself, so pick something you'd like to keep!)
59
60 3. Once connected, right click your user name in the server view and choose
61    'Register'.  This will register your user to the server (this makes the
62    server remember you as a user -- but you still will not have administrative
63    privileges).
64
65 4. Once registered, you can disconnect from the server.  Now it is time to
66    connect using the SuperUser account that the server created for you
67    when you launched it the first time.
68
69    Simply specify SuperUser as your username, and the password that Murmur
70    gave you as the password.
71
72 5. After connecting as the SuperUser, right click the 'Root'-channel and
73    choose Edit.  In the Edit dialog, click the Groups tab.
74
75    In the Groups dropdown, choose the admin group.
76
77    Then, under Members three lists should appear, showing Members, Excluded
78    Members and Inherited Members. We're only interested in Members. Expand
79    the drop down below the member list and find the username of the user
80    you registered in step 3.
81
82    Click Add to add the user to the admin group.
83
84 6. Your user is now an administrator.
85
86For more advanced setup and usage of Murmur, please visit the Mumble Wiki,
87at http://mumble.info/. Some pages of interest are available at:
88
89   http://wiki.mumble.info/wiki/Running_Murmur
90   http://wiki.mumble.info/wiki/ACL_and_Groups
91   http://wiki.mumble.info/wiki/Murmurguide
92
93Additional Murmur Options
94=========================
95
96The above instructions use a very bare-bones approach to running Murmur.
97Several other command line options are available. These are listed below:
98
99murmurd [-supw <password>] [-ini <inifile>] [-fg] [v]
100
101-supw   Set new password for the user SuperUser, which is hardcoded to
102        bypass ACLs. Keep this password safe. If you use this option,
103        Murmur will set the password in the database and then exit.
104
105-ini    Use an ini file other than murmur.ini, use this to run several
106        instances of Murmur from the same directory. Make sure each
107        instance is using a separate database. (Specified in the ini file.)
108
109-fg     Run in the foreground, logging to standard output.
110
111-v      More verbose logging.
112