|
|
| (177 intermediate revisions by 72 users not shown) |
| Line 1: |
Line 1: |
| − | {{Member Services}} | + | {{eunispecific}} |
| | + | {{tocright}} |
| | | | |
| − | == Why is it useful? ==
| + | '''[https://www.mumble.info/ Mumble]''' is a third-party VOIP (Voice Over Internet Protocol) application that allows people to communicate verbally both in- and out-of-game. |
| | | | |
| − | Mumble is mostly used in two situations: PvP and Classes. In PvP it is very useful because, for example, it is faster to call out a primary target than to type it, especially with PvP related lag. In classes it is great as well because we do not want our poor instructors getting Carpal Tunnel Syndrome from typing everything. In effect, it is just a lot easier and faster than typing. | + | Our Mumble authentication for Members and Guests is handled through Alliance Auth. |
| | | | |
| − | <br>
| + | == Accessing Mumble == |
| | + | Navigate to https://auth.eveuniversity.org/ and sign in using EVE Online SSO - For access to base systems you will only be asked for public scopes: |
| | + | # Select Services from the toolbar on the left hand side of the screen |
| | + | # Select the amber tick at the end of the mumble row and you will see your username and password |
| | + | # Select continue |
| | + | # Click on the Green arrow ''Connect'' button to automatically connect to Mumble |
| | + | # Enter your Mumble password if prompted |
| | | | |
| − | == Very quick guide ==
| + | After you've successfully connected, you can easily save the server settings in your Mumble Desktop client to reconnect easily in the future. |
| | | | |
| − | #Download mumble from [http://mumble.sourceforge.net/ http://mumble.sourceforge.net/] (now on version 1.2.3).<br>
| + | '''Using the Mumble Desktop Client:''' |
| − | #Install and set it up (create your own certificate, etc) | + | # Click on ''Server'' > ''Connect'' > ''Add New'' |
| − | #Start the client and Server>Connect>Add New...
| + | # Click on the ''Fill'' button to automatically fill in the server details |
| − | #*Servername: Eve University | + | # You can modify the Label to anything you like, or just leave it as the default |
| − | #*Address: mumble.eveuniversity.org
| |
| − | #*Port: 64738 (Default)
| |
| − | #*Username: <Your Forum Username, i.e: your character name with nothing either side>
| |
| − | #Connect (you can ignore the certificate warning - this will be fixed later).
| |
| − | #When prompted for your password, use your forum password!
| |
| − | #There is no six!
| |
| − | #You should automatically be dropped in the "Public Lounge" channel.
| |
| − | #Talk. | |
| − | #Restart EVE client if you want overlay to work.
| |
| | | | |
| − | <br>
| + | '''If you are still having problems getting connected, try following the [[#Manual Connection Instructions|manual instructions]] below setup the connection.''' |
| | | | |
| − | == Setting up Mumble<br> == | + | === Manual connection instructions === |
| | + | After setting up your Mumble account through Alliance Auth in the steps above. You can try using these steps to setup a connection to the '''EVE University Mumble''' server if the Green '''Connect''' button isn't working for you. |
| | | | |
| − | === Audio Tuning Wizard ===
| + | '''Using the Mumble Desktop Client:''' |
| | + | # Click on ''Server'' > ''Connect'' > ''Add New'' |
| | + | # Enter the '''EVE University Mumble''' details below then click ''OK'' |
| | + | # Select ''EVE University Mumble'' in the list then click ''Connect'' |
| | | | |
| − | When you run Mumble the first time, an Audio Tuning Wizard is presented to you. If you skip or miss it on the first run you can retake the wizard by clicking Configure > Audio Wizard. It is recommended you go through it carefully, since setting up Mumble correctly will make your and everyone else's life much easier (going through the Audio Tuning Wizard properly will also normalise everyone's voices, such that everyone will sound the same volume regardless of how they have their microphone set up). However there are two things I would like to highlight:
| + | {| class="wikitable" style="text-align: center;" |
| | + | |- style="background: #222222;" |
| | + | ! style="width: 120px;" colspan="2" | EVE University Mumble |
| | + | |- |
| | + | | Address || '''mumble.eveuniversity.org''' |
| | + | |- |
| | + | | Port || '''64738''' ''(default)'' |
| | + | |- |
| | + | | Username || ''<Your Alliance Auth username, i.e: Example_Member>'' |
| | + | |- |
| | + | | Password (only when prompted) || ''<Your Mumble password>'' |
| | + | |- |
| | + | | Label || EVE University Mumble |
| | + | |} |
| | | | |
| − | ==== Push-to-talk ====
| + | Your Alliance Auth username is normally your character name with spaces replaced by underscores. (i.e. Example Member is Example_Member) If you're uncertain, you can see your current username for Mumble on the Alliance Auth [https://auth.eveuniversity.org/services Services] page. |
| | | | |
| − | [[Image:MumbleWizardPTT.png]] | + | If you cannot remember your Mumble password, go back to the [https://auth.eveuniversity.org/services Services] page where you can set a new password using the amber pencil icon or create a new random password using the gray refresh, or circular arrows, icon. |
| | | | |
| − | When you reach a screen that looks like the one above select the top radio button, click on the box on the same line and press the key you you want to use as the push-to-talk key.This is your ''normal'' push-to-talk key; for certain Fleet roles you may need more than one (see the comments in the Fleet channels), but for general E-UNI activity one is sufficient.<br>
| + | If you're still unable to connect to our Mumble server after trying these steps, feel free to reach out for support in '''#alliance-auth''' channel on the [[Discord|EVE University Discord]]. |
| | | | |
| − | ==== Text-to-speech ==== | + | == Initial configuration == |
| | + | === Push to talk === |
| | + | There is nothing more annoying than hearing other people type or breathe into their microphone constantly. If you leave push-to-talk off during a fleet op then you are likely to have some very frustrated Corp mates. This is why push to talk is mandatory. To turn on push to talk for Mumble, follow these steps. |
| | + | # Open up Mumble |
| | + | # Click the “Configure” option at the top, then click settings |
| | + | # You should now be in the Audio Input settings area, under the Transmission area make sure the Transmit drop down box is set to “Push to Talk” |
| | + | # Now you need to assign a key that you will need to press so others can hear you. To do this click the “Shortcuts” button on the left hand side of the Settings dialog box. |
| | + | # There should be a listing there labeled “Push-to-Talk”, click on the Shortcut column and press the key that you wish to be your push to talk key. |
| | | | |
| − | [[Image:MumbleWizardTextToSpeech.png]]
| + | === Whisper key === |
| | + | Some of our mumble rooms, most notably the fleet and general lounge channels are linked to other channels. The purpose of these sub channels is to give the group within the option to talk to each other without all of the linked channels being able to hear it. |
| | | | |
| − | When you reach a screen that looks like the one above I recommend you disable the text to speech notifications.
| + | For example the commander of the logistics group can now talk to only the Logistic pilots without confusing everyone else. |
| | | | |
| − | <br>
| + | A whisper key allows you to talk to just your current channel instead of broadcasting your voice to all of the linked channels. |
| | | | |
| − | === Connecting to the EVE University Server ===
| + | You should already see your existing push-to-talk key set up. It's a good idea to check the Suppress box on any shortcuts, as that will prevent other applications from recognizing your key and performing unforeseen tasks you had not expected (e.g. warp scrambling stargates). |
| | | | |
| − | Once Mumble is all set up and you have run through the Audio Turning Wizard, you will want to connect to the EVE University server. <br>
| + | ==== Setting up your whisper key ==== |
| | + | # Click the Add button in the bottom left, which will bring up a new Unassigned shortcut in the window. |
| | + | # Click the word Unassigned and select Whisper/Shout from the drop-down list. |
| | + | # Click the word Empty next to it, which should cause a [...] button to appear next to that - click that [...] button to open a new Whisper Target window. |
| | + | # Select the Shout to Channel box, and check that “Current channel” is highlighted, and then click OK. |
| | + | # Finally click the Shortcut column of your new shortcut and press the key you wish to use. |
| | | | |
| − | #Go to Server in the toolbar --> Connect.<br>
| + | You now have your Whisper chat key setup! |
| − | #Click the Add New... button in the bottom right.<br>
| |
| − | #Put anything you like in the Label box ("''Eve University''<span style="font-style: italic;">"</span> seems sensible), the Address box needs to be '''mumble.eveuniversity.org''' and the Port needs to be left as default (64738).<br>
| |
| − | #The Username box needs to be <u>your exact E-UNI forum username</u>, which also happens to be <u>your exact character name</u>.<br>
| |
| − | #Click the Connect button.<br>
| |
| − | #n/a<br>
| |
| − | #The server will reject your connection, and prompt you with a Wrong Password box. You need to use your forum password (i.e. the same password you chose when you registered for our forums) in the box, then click OK.<br>
| |
| − | #You are now connected to the Mumble server, which will have moved you into the Public Lounge channel.<br><br>
| |
| | | | |
| − | === Notifications ===
| + | By default you should always use a Whisper Key to chat in EVE University Mumble channels. |
| | | | |
| − | In the Configure --> Settings screen you can find Advanced settings checkbox in the bottom left corner. With it checked you can access the Messages settings. From there you can disable popup and sound notifications about events you don't care about.
| + | === Notifications === |
| | + | Go to Configure > Settings... > Messages. From there you can disable popup and sound notifications about events you don't care about. By default Mumble makes a loud PING and gives you a notification popup for almost any event on the server - this gets annoying pretty fast. |
| | | | |
| − | <br>
| + | Mac version: From the Mumble --> Preferences window (make sure the 'Advanced' checkbox in the upper right is checked), select the 'Messages' tab. The only way to eliminate audio notifications is to uncheck items in the 'Soundfile' column. |
| | | | |
| − | === Other interesting features<br> === | + | === Overlay === |
| | + | It can be useful to have the Mumble Overlay set up for fleet operations as it eliminates the need for checking the Mumble client to see who is talking. See the [[Mumble Overlay]] for a step-by-step guide. |
| | | | |
| − | *Mouse-over anyone's name and their ingame portrait will pop up.<br>
| + | == Chat policies == |
| − | *Right-click on a channel and select Join Channel to move to that channel (double-click sometimes produces strange behaviour with nested channels).
| + | Please remember that our [[Communications Policy]] applies in the Uni Mumble. Moderation can include muting and/or banning. Note that this can severely affect your participation in fleets, classes, and other activities. |
| − | *If the name of the channel that you are in is ''italicized'', then your push-to-talk button, in addition to talking to the current channel, will also talk to everybody in every other channel that is also ''italicized''. Italicized names denote linked channels (you can only see this if you are currently in a linked channel).
| |
| − | *Click the small yellow |c| button on any channel (or any person) to see comments on that channel (or person). The |c| will go white once you've read it (and go yellow again if it changes). You can set your own comment by right-clicking on your own name.<br>
| |
| − | *You will automatically be moved to the AFK & Idle channel if Mumble detects no activity on your computer for at least 4 hours. Everybody is automatically muted in that channel, so you can also move yourself there if you desire peace and quiet
| |
| − | *You can create your own channels for EVE purposes (in the On-Demand Channels section) or for any non-EVE gaming purposes (in the Non-EVE Gaming section) by right-clicking on the relevant section and choosing Add. These are temporary channels, you will have admin powers and once the last person leaves the channel will disappear.
| |
| | | | |
| − | <br>
| + | == Channel rules & access == |
| | + | Mumble is currently set up in the following configuration: |
| | + | * '''General Lounges''' - Two channels, one for members and one for the public. A general hangout space for everyone |
| | + | * '''Classrooms''' - Open to everyone who joins mumble and used by the Teachers to run classes |
| | + | * '''Public Fleets''' - Open to everyone for public roams and fleets (EVE Uni Comms Policy still applies) |
| | + | * '''Uni Fleets''' - Restricted to Uni Members for Uni only roams/fleets or QRF’s |
| | + | * '''Standing Fleets''' - Be in standing fleet and in here if your just hanging out around our staging areas |
| | + | * '''Special Interest Groups''' - Rooms to allow members to connect your content and interests no matter which area of space the operate in |
| | + | * '''On Demand Channels''' - Anyone in EVE Uni can create temporary channels here if there is no suitable channel for their needs. |
| | + | * '''Staff Offices''' - Restricted to EVE University Officers and Management |
| | + | * '''AFK & Idle Room''' - If you're muting your speakers anyways, idle here |
| | | | |
| − | == Overlay == | + | == Moderation == |
| | + | Any of our officers, managers or directors are able to moderate our mumble server. |
| | | | |
| − | [[Image:Overlay example.png|right|Sample overlay]] Mumble provides a very handy and customizable overlay. To configure it go to Configure --> Settings --> Overlay option.
| + | == Note for MacOS users == |
| | + | When updating or reinstalling Mumble on MacOS, it is necessary to go into System Preferences > Privacy & Security > Privacy |
| | | | |
| − | Mumble, being the awesome program that it is, shows in this window an example of what the overlay will look like on your current desktop, as well as instructions on how to alter it. One position that works very well is just to the right of the current location name, like the screenshot on the right. You could even put it above the current location, but then - for me at least - it's too small to see easily.<br> | + | For BOTH the "Accessibility" AND "Input Monitoring" lists: Remove Mumble from the list, then re-add Mumble to the list by clicking-and-dragging the NEW Mumble application from the "Applications" folder to the list. |
| | | | |
| − | The default setting is for the Overlay to display the name of everyone currently in the channel. As you can imagine, this gets unwieldy very quickly. To change this, right-click on the small example overlay in the window, choose Filter >, and tick ''Only talking''. Also untick ''Always show yourself,'' otherwise your name will constantly be displayed on the overlay.<br>
| + | If installing Mumble for the first time ever (on a given Macintosh), then just add Mumble to these two lists. |
| | | | |
| − | The ''Edit...'' option on the right-click menu produces a detailed configuration screen where you can change pretty much anything you like about the overlay: colours, sizes, backgrounds, avatars, etc.<br>
| + | Forgetting to do this when installing, reinstalling, or updating Mumble will result in Mumble being unable to detect keyboard inputs for Push-To-Talk and Whisper/Shout features. |
| | | | |
| − | If your overlay is not showing up, you must have started EVE ''after'' Mumble. If necessary simply restart EVE.<br> | + | === Warning === |
| | + | Do <em>NOT</em> upgrade from mumble <=1.3.x to 1.5.x+<ref>https://www.mumble.info/downloads/</ref>. If you accidentally did upgrade, follow these steps to recover: |
| | + | # When referring to delete, that is dragging app, file or folder icon to trash can or using Command-Delete |
| | + | # Delete Mumble app by going to your Applications folder<ref>https://www.mumble.com/support/how-to-uninstall-mumble-mac.php</ref> |
| | + | # Reveal hidden directories by going to Finder, open up your Macintosh HD folder. Press Command+Shift+Dot |
| | + | # Delete mumble database directory: <code>$HOME/Library/Application Support/Mumble/</code><ref name="Mac location" /> |
| | + | # Delete mumble settings file: <code>$HOME/Library/Preferences/net.sourceforge.mumble.Mumble.plist</code><ref name="Mac location" /> |
| | + | # Remove permissions by going to System Preferences > Privacy & Security > Privacy. For BOTH the "Accessibility" AND "Input Monitoring" lists: Remove Mumble from the list using the minus button. |
| | + | # Install Mumble 1.5.x+ software |
| | + | # Add permissions for new Mumble by going to System Preferences > Privacy & Security > Privacy. For BOTH the "Accessibility" AND "Input Monitoring" lists: Add Mumble from the list using the plus button, and selecting Mumble from Applications. |
| | | | |
| − | [[Image:Mumble overlay.png]]<br>
| + | FYI Mumble download page warns that upgrading directly to 1.5.x+ will break mumble on your macOS machine. |
| | | | |
| − | <br> | + | == References == |
| | + | <references> |
| | + | <ref name="Mac location">https://www.mumble.info/documentation/user/settings-storage-location/</ref> |
| | + | </references> |
| | | | |
| − | === Overlay Settings File<br> ===
| + | {{EVEUniversityNav}} |
| | | | |
| − | If you don't want to go through the Overlay settings, or feel like taking the easy way, I have uploaded a settings file [http://www.filedropper.com/e-uni here], which will make your overlay look like the one in the screenshot above right.
| + | [[Category:Getting Started]] |
| − | | + | [[Category:Applications]] |
| − | *Follow the link above to save it to a handy location on your computer.
| + | [[Category:EVE University Services]] |
| − | *Go to the Overlay settings as explained above.
| |
| − | *Click the ''Load...'' button near the top, navigate to and select the file, click ''Open''. Click ''Apply ''or ''OK ''in the bottom of the Settings window.
| |
| − | *You now have a fully functioning overlay!
| |
| − | | |
| − | I'm not sure how this will behave with different resolutions, screen settings or indeed operating systems - it was created on Windows 7 - so if you have any problems with it you can choose the Restore Defaults button in the bottom of the Settings screen to reset the options.
| |
| − | | |
| − | <br>
| |
| − | | |
| − | === Overlay on Linux ===
| |
| − | | |
| − | To actually display the overlay over Eve in Linux after you've enabled it in Mumble's settings you need to have Mumble launched first and then run '''mumble-overlay''' in front of the wine command that you use to launch Eve. For example:
| |
| − | | |
| − | ''mumble-overlay wine explorer /desktop=Eve,1600x1200 "C:\Program Files\CCP\EVE\eve.exe"''
| |
| − | | |
| − | If you use a WINEPREFIX, then you would insert it after the WINEPREFIX variable like so:
| |
| − | | |
| − | ''WINEPREFIX=/home/username/bin/wine/wine-eve/ mumble-overlay wine explorer /desktop=Eve,3200x1180 "C:\Program Files\CCP\EVE\eve.exe"''
| |
| − | | |
| − | <br>
| |
| − | | |
| − | === Overlay on Mac ===
| |
| − | | |
| − | To Enable the overlay goto Preferences and Click overlay top right button. Click the enable overlay tickbox on the top left corner of the window then using the screen display below drag and size the overlay position to a point on a screen that you feel comfortable with. The red spot moves the anchor of the overlay. You can change the size of the name displayed using mouse scroll wheel.
| |
| − | | |
| − | ==== Version 1.2.3 ====
| |
| − | | |
| − | The new 1.2.3 has a working overlay. After dragging the Mumble Icon out of the dmg which mounts after your download to your folder of choice, right click the icon and choose "Show Package Contents" Navigate to the following folder:
| |
| − | | |
| − | [http://Mumble.app/Contents/Resources/MumbleOverlay.pkg Mumble.app/Contents/Resources/MumbleOverlay.pkg] | |
| − | | |
| − | Launch the package and run the installer. Restart mumble and enable your overlay! Launch Eve as normal; no command line is necessary.
| |
| − | | |
| − | <br>
| |
| − | | |
| − | == Channel Structure for Ivy League Navy ==
| |
| − | | |
| − | One of the great advantages of Mumble over Teamspeak is the ability for squad members and their SC to talk amongst themselves, without clogging up comms for the rest of the fleet - in the '''Structured''' fleet channel, ZZ Alpha Fleet. This can be invaluable for bait squads and instructing new members. In order for this to work however, it requires people to be in the right channel and everyone should have their keys set up correctly. For small fleets this can be a bit overly-elaborate, so we also run '''Semi-structured''' channels for most fleet operations - fleet channels Alpha to Juliet.<br>
| |
| − | | |
| − | An important note to start off on: if, when you join a channel, the channel name becomes ''italicized'', then your current channel is linked to the other ''italicized'' channels, and your normal PTT button you set up during Mumble installation will talk to everybody in every currently ''italicized'' channel.<br>
| |
| − | | |
| − | <br>
| |
| − | | |
| − | === Semi-structured fleet channels ===
| |
| − | | |
| − | Semi-structured fleet channels - such as contain two channels, the main fleet channel named (e.g.) ''Delta Squad'' and a sub-channel name (e.g.) ''Delta Command.'' As you probably already realised, if you are in a command position such as SC, WC or a Scout (or the FC tells you to get into command chat), you should join the Command sub-channel, whilst normal fleet members should join the parent Squad channel. This sort of fleet channel is useful for medium sized fleets (e.g. one or two wings).<br>
| |
| − | | |
| − | The two channels are linked, which means the normal PTT talks to both. Therefore fleet members do not need any special PTT key, your normal PTT you set up during Mumble installation talks to everyone in the fleet (yes, even those in Command). If you are in Command, you will need another PTT key that talks only to the current channel. To set that up, go to Configure -> Settings -> Shortcuts, which will pop up a window that looks like this:<br>
| |
| − | | |
| − | [[Image:Mumble3.png]]
| |
| − | | |
| − | Although on yours, you should see only your current push-to-talk key already set up in the Shortcuts window, as you haven't set up any others yet. It's a good idea to check the ''Suppress'' box on any shortcuts, as that will prevent other applications from recognising your key and performing unforseen tasks you had not expected (e.g. warp scrambling stargates).<br>
| |
| − | | |
| − | #Click the Add button in the bottom left, which will bring up a new ''Unassigned'' shortcut in the window.<br>
| |
| − | #Click the ''Unassigned'' word and select ''Whisper/Shout or Whisper'' depending on your Mumble version from the drop-down list.<br>
| |
| − | #Click the ''Empty'' word next to it, which should cause a (...) button to appear next to that - click that to open a new Whisper Target window.<br>[[Image:Shortcut 1.png]]<br><br>
| |
| − | #Make that new Whisper Target window look like this (i.e. Current channel highlighted), and then click OK. The ''Shout/Whispers to Linked channels'' should be clear.<br>[[Image:Whisper current target.png]]<br><br>
| |
| − | #Finally click the Shortcut column of your new shortcut and press the key you wish to use.
| |
| − | #You now have a Command chat key set up for the semi-structured fleet channels!<br>
| |
| − | | |
| − | Note that it will only talk to Command chat if you yourself are also in Command. If you are in the general fleet channel it will talk to the general fleet ONLY, i.e. not Command. You can also use this key in any channels that are linked together (e.g. Public Lounge and Combat Lounge) - it will only talk to the current channel, and not the linked channels.<br>
| |
| − | | |
| − | <br>
| |
| − | | |
| − | === Fully structured fleet channels ===
| |
| − | | |
| − | This part of the Mumble setup guide focuses on setting up your key shortcuts for the structured fleet channel, currently named ZZ Alpha Fleet. This is used only really for large scale PvP operations (e.g. multiple wings or fleets), so <span style="color: rgb(255, 255, 0);">unless you are expecting to join a huge fleet of hundreds of unistas, you can probably skip this bit for now</span>.<br>
| |
| − | | |
| − | E-UNI fleets will use four distinct "channels" (these are not real channels as such but the concept helps to understand the difference between the actions behind different hotkeys).
| |
| − | | |
| − | *Fleet "Channels":
| |
| − | **'''Squad Channel''' '''(same level)''', where the squad members can have their internal chat without bothering the rest of the fleet (or even their SC)
| |
| − | **'''Command Channel''' '''(same level)''' for FC, WC, SC and scouts to discuss between themselves
| |
| − | **'''Report Channel (upwards)''', where squad members reports their actions to their SC, e.g. calling points
| |
| − | **'''Order Channel''' '''(downwards)''', for command staff to give orders to the members below them in the fleet structure i.e. FC to talk to whole fleet, WC to their wing, SC to their squad
| |
| − | | |
| − | In structured fleet channels three different hotkeys are used to establish the channels described above, and creating an ability to talk "up" and "down" the command structure. <br>
| |
| − | | |
| − | <br>
| |
| − | | |
| − | Your '''normal PTT key''' you set up during Mumble installation acts as the 'same level' shortcut: for squad members it will talk to your "'''Squad Channel'''" (but, do take note, NOT your squad commander); for the FC, WCs, SCs and Scouts, it will talk to the the rest of your command on the "'''Command Channel'''" (because all of the command channel positions are linked).<br>
| |
| − | | |
| − | <br>
| |
| − | | |
| − | Both squad members and command positions will need one more shortcut, and it is different depending on your role.<br>
| |
| − | | |
| − | *For '''squad members''': you will need a '''Whisper/Shout to Parent''' shortcut<br>
| |
| − | *For '''command channel''': you will need a '''Whisper/Shout to Current''' (including subchannels) shortcut<br>
| |
| − | | |
| − | ==== Whisper/Shout to Parent ====
| |
| − | | |
| − | Follow the steps in setting up a shortcut in the previous section. When you get to the Whisper Target window, make it look like this (i.e. Parent highlighted, Whisper/shout to subchannels ticked).<br>
| |
| − | | |
| − | [[Image:Mumble2.png]] | |
| − | | |
| − | It is important the Whisper/Shout to sub-channels <u>is</u> ticked. This is the key that you will use to talk to your Squad Commander (it also talks to the rest of your squad). Note that it will NOT talk to anyone else e.g. FC, Scouts, other squads.<br>
| |
| − | | |
| − | ==== Whisper/Shout to Current ====
| |
| − | | |
| − | Follow the steps in setting up a shortcut in the previous section. When you get to the Whisper Target window, make it look like this (i.e. Current highlighted, Whisper/Shout to sub-channels ticked).<br>
| |
| − | | |
| − | [[Image:Mumble1.png]] | |
| − | | |
| − | It is <u>very</u> important that the Whisper to subchannels <u>is</u> ticked. This is the key that you will use to talk to everyone below you in the fleet structure. That is, for FCs it will talk to the whole fleet, for WCs it will talk to your wing, for SCs it will talk to your squad. For Scouts, you should generally not need it, though if you are in the same channel as the FC it will talk to the whole fleet.
| |
| − | | |
| − | ==== Different channels in Different Roles ====
| |
| − | | |
| − | Now let's show how the key bindings we made link to the channels we mentioned and how they are used in different roles in a Structured fleet:
| |
| − | | |
| − | *'''FC: '''
| |
| − | **Push-to-talk => Command channel
| |
| − | **Whisper/Shout to Parent (No use for an FC)
| |
| − | **Whisper/Shout to Current => Order channel (I.e. FC giving orders to whole fleet)<br>
| |
| − | | |
| − | *'''WC/SC: '''
| |
| − | **Push-to-talk => Command channel
| |
| − | **Whisper/Shout to Parent (No use for an WC/SC)
| |
| − | **Whisper/Shout to Current => Order channel (I.e. WC/SC giving orders to their wing/squad)
| |
| − | ***Other command staff will not hear SC/WC talking to his/her squad/wing on a squad channel. To keep your FC up to date on what the squad/wing is doing SC/WC must remember to inform also the command channel (Push to talk)<br>
| |
| − | | |
| − | *'''Scout: '''
| |
| − | **Push-to-talk => Command channel
| |
| − | **Whisper/Shout to Parent (No use for a scout)
| |
| − | **Whisper/Shout to Current (No use for a scout, though you could use it to talk to the whole fleet)<br>
| |
| − | | |
| − | *'''Squad member: '''
| |
| − | **Push-to-talk => Squad channel (without SC!)
| |
| − | ***Squad Commander will not hear squad members talking in squad channel. Use report channel (Shout-to-Parent) if you want your SC to hear you
| |
| − | **Whisper/Shout to Parent => Report channel (own squad including SC)
| |
| − | ***Other command staff will not hear reports (e.g. call of points) made by a squad members to their SC using the report channel! SC has to make sure to keep your FC up to date by relaying important bits of information to command channel (using their Push-to-talk key)
| |
| − | **Whisper/Shout to Current => (No use for a squad member)
| |
| − | | |
| − | In short, the structured fleet channels enable great streamlining and filtering of information. This way, fleet commanders can focus on leading the fleet rather than having to process endless streams of information and squad members and their commanders can coordinate more efficiently amongst themselves. On the other hand, all this requires a great deal more communication and discretion in doing so from SC’s to the rest of command.
| |
| − | | |
| − | <br>
| |
| − | | |
| − | == Channel Properties for the Public and Combat Lounges ==
| |
| − | | |
| − | Both the Public Lounge and the Combat Lounge are linked on the Mumble server so that both channels can both listen to and speak to each other without having to move yourself between the channels, but there is a restriction on who can be in each channel. Anyone that has a forum account with EVE University's website can access the Mumble server, and the Public Lounge is the equivalent of the public E-UNI chat channel (specifically E-UNI, not Chat.E-UNI) as it is open to anybody regardless of membership. Essentially, Mumble users that are not corporation members with EVE University are restricted from entering the Combat Lounge. This is very important regarding communication that needs to follow the Operational Security rules and guidelines, as discussed here: [[Operational Security]].
| |
| − | | |
| − | === Safely and Securely Announcing Fleets in Mumble's Combat Lounge Channel ===
| |
| − | | |
| − | The process to announce a potential fleet in Mumble that is in accordance with the Operational Security rules and guidelines is the following:
| |
| − | | |
| − | *First check that you are in the Combat Lounge channel on the Mumble server, and that you have your Mumble shortcut for semi-structured fleet channels. You can view how to do this in the [[Mumble#Semi-structured_fleet_channels|previous section of this page]].
| |
| − | *If you're in the Combat Lounge channel you can use your command channel shortcut to speak to only those in the current channel about potential fleet activity. It's best to do this while avoiding anyone else talking over Mumble, as Public Lounge will not be able to hear your message and may speak over you. So please try to keep the message brief and clear so it has the best chance of getting across effectively to those in the Combat Lounge.
| |
| − | | |
| − | <br>
| |
| − | | |
| − | == Setting up an EWAR token ==
| |
| − | | |
| − | If you intend to fly an EWAR Ship make sure to look at [https://docs.google.com/document/d/1lmulCWzEalVg3P53OonshWNhEx28CZZgpTWM56NE_l4/edit?hl=en&authkey=CJik4e4I&pli=1 this guide] by Remric and setup an EWAR token as described there.
| |
| − | | |
| − | == Troubleshooting ==
| |
| − | | |
| − | The Mumble FAQ on the Mumble homepage - [http://mumble.sourceforge.net/FAQ http://mumble.sourceforge.net/FAQ] - has a lot of useful information, and also has a section on Common Problems and Resolutions which may be helpful.
| |
| − | | |
| − | === A referral was returned from the server. ===
| |
| − | | |
| − | "A referral was returned from the server." error while starting Mumble on Windows Check your system time. Windows certificate check will fail if your clock is some years ahead/behind.
| |
| − | | |
| − | For Windows XP: Install the latest Root Certificate update through Windows Update (it's an optional update) to fix this problem.
| |
| − | | |
| − | For Windows Vista/7: Right-click the Mumble executable, select "Properties", select the "Digital Signature" tab, click "Details" and click "Install certificate".
| |
| − | | |
| − | Installing [https://www.startssl.com/certs/ca-bundle.crt https://www.startssl.com/certs/ca-bundle.crt] to the "Trusted Root Certification Authorities" cert store should also work.
| |
| − | | |
| − | If you compiled Mumble yourself either sign the binary or disable signing.
| |
| − | | |
| − | If you are on windows 7 and this doesn't help you, try this out. Press Start, type MMC and press enter go to File and select Add/Remove Snap-ins in available snap-ins select Certificates and press ADD. you get three options, I personally went with "My User Account"
| |
| − | | |
| − | with that done exit the Snap in management window and double click on the Certificate Icon, then double click on the "Trusted Root Certification Authorities" Right click on the Certificate icon that appears and highlight "all tasks" then click on the Import button.
| |
| − | | |
| − | The import wizard will then ask for the filename of the certificate you want imported. First Save As: [https://www.startssl.com/certs/ca-bundle.crt https://www.startssl.com/certs/ca-bundle.crt] in whatever folder you want then link it to the import tool. follow the wizard's instructions and "Voila" you now should be able to use Mumble
| |
|
This page is specific to EVE University. Other corporations or groups in the game may operate differently.
For a summary of EVE University's rules and code of conduct, see EVE University Rules.
|
Mumble is a third-party VOIP (Voice Over Internet Protocol) application that allows people to communicate verbally both in- and out-of-game.
Our Mumble authentication for Members and Guests is handled through Alliance Auth.
Accessing Mumble
Navigate to https://auth.eveuniversity.org/ and sign in using EVE Online SSO - For access to base systems you will only be asked for public scopes:
- Select Services from the toolbar on the left hand side of the screen
- Select the amber tick at the end of the mumble row and you will see your username and password
- Select continue
- Click on the Green arrow Connect button to automatically connect to Mumble
- Enter your Mumble password if prompted
After you've successfully connected, you can easily save the server settings in your Mumble Desktop client to reconnect easily in the future.
Using the Mumble Desktop Client:
- Click on Server > Connect > Add New
- Click on the Fill button to automatically fill in the server details
- You can modify the Label to anything you like, or just leave it as the default
If you are still having problems getting connected, try following the manual instructions below setup the connection.
Manual connection instructions
After setting up your Mumble account through Alliance Auth in the steps above. You can try using these steps to setup a connection to the EVE University Mumble server if the Green Connect button isn't working for you.
Using the Mumble Desktop Client:
- Click on Server > Connect > Add New
- Enter the EVE University Mumble details below then click OK
- Select EVE University Mumble in the list then click Connect
| EVE University Mumble
|
| Address |
mumble.eveuniversity.org
|
| Port |
64738 (default)
|
| Username |
<Your Alliance Auth username, i.e: Example_Member>
|
| Password (only when prompted) |
<Your Mumble password>
|
| Label |
EVE University Mumble
|
Your Alliance Auth username is normally your character name with spaces replaced by underscores. (i.e. Example Member is Example_Member) If you're uncertain, you can see your current username for Mumble on the Alliance Auth Services page.
If you cannot remember your Mumble password, go back to the Services page where you can set a new password using the amber pencil icon or create a new random password using the gray refresh, or circular arrows, icon.
If you're still unable to connect to our Mumble server after trying these steps, feel free to reach out for support in #alliance-auth channel on the EVE University Discord.
Initial configuration
Push to talk
There is nothing more annoying than hearing other people type or breathe into their microphone constantly. If you leave push-to-talk off during a fleet op then you are likely to have some very frustrated Corp mates. This is why push to talk is mandatory. To turn on push to talk for Mumble, follow these steps.
- Open up Mumble
- Click the “Configure” option at the top, then click settings
- You should now be in the Audio Input settings area, under the Transmission area make sure the Transmit drop down box is set to “Push to Talk”
- Now you need to assign a key that you will need to press so others can hear you. To do this click the “Shortcuts” button on the left hand side of the Settings dialog box.
- There should be a listing there labeled “Push-to-Talk”, click on the Shortcut column and press the key that you wish to be your push to talk key.
Whisper key
Some of our mumble rooms, most notably the fleet and general lounge channels are linked to other channels. The purpose of these sub channels is to give the group within the option to talk to each other without all of the linked channels being able to hear it.
For example the commander of the logistics group can now talk to only the Logistic pilots without confusing everyone else.
A whisper key allows you to talk to just your current channel instead of broadcasting your voice to all of the linked channels.
You should already see your existing push-to-talk key set up. It's a good idea to check the Suppress box on any shortcuts, as that will prevent other applications from recognizing your key and performing unforeseen tasks you had not expected (e.g. warp scrambling stargates).
Setting up your whisper key
- Click the Add button in the bottom left, which will bring up a new Unassigned shortcut in the window.
- Click the word Unassigned and select Whisper/Shout from the drop-down list.
- Click the word Empty next to it, which should cause a [...] button to appear next to that - click that [...] button to open a new Whisper Target window.
- Select the Shout to Channel box, and check that “Current channel” is highlighted, and then click OK.
- Finally click the Shortcut column of your new shortcut and press the key you wish to use.
You now have your Whisper chat key setup!
By default you should always use a Whisper Key to chat in EVE University Mumble channels.
Notifications
Go to Configure > Settings... > Messages. From there you can disable popup and sound notifications about events you don't care about. By default Mumble makes a loud PING and gives you a notification popup for almost any event on the server - this gets annoying pretty fast.
Mac version: From the Mumble --> Preferences window (make sure the 'Advanced' checkbox in the upper right is checked), select the 'Messages' tab. The only way to eliminate audio notifications is to uncheck items in the 'Soundfile' column.
Overlay
It can be useful to have the Mumble Overlay set up for fleet operations as it eliminates the need for checking the Mumble client to see who is talking. See the Mumble Overlay for a step-by-step guide.
Chat policies
Please remember that our Communications Policy applies in the Uni Mumble. Moderation can include muting and/or banning. Note that this can severely affect your participation in fleets, classes, and other activities.
Channel rules & access
Mumble is currently set up in the following configuration:
- General Lounges - Two channels, one for members and one for the public. A general hangout space for everyone
- Classrooms - Open to everyone who joins mumble and used by the Teachers to run classes
- Public Fleets - Open to everyone for public roams and fleets (EVE Uni Comms Policy still applies)
- Uni Fleets - Restricted to Uni Members for Uni only roams/fleets or QRF’s
- Standing Fleets - Be in standing fleet and in here if your just hanging out around our staging areas
- Special Interest Groups - Rooms to allow members to connect your content and interests no matter which area of space the operate in
- On Demand Channels - Anyone in EVE Uni can create temporary channels here if there is no suitable channel for their needs.
- Staff Offices - Restricted to EVE University Officers and Management
- AFK & Idle Room - If you're muting your speakers anyways, idle here
Moderation
Any of our officers, managers or directors are able to moderate our mumble server.
Note for MacOS users
When updating or reinstalling Mumble on MacOS, it is necessary to go into System Preferences > Privacy & Security > Privacy
For BOTH the "Accessibility" AND "Input Monitoring" lists: Remove Mumble from the list, then re-add Mumble to the list by clicking-and-dragging the NEW Mumble application from the "Applications" folder to the list.
If installing Mumble for the first time ever (on a given Macintosh), then just add Mumble to these two lists.
Forgetting to do this when installing, reinstalling, or updating Mumble will result in Mumble being unable to detect keyboard inputs for Push-To-Talk and Whisper/Shout features.
Warning
Do NOT upgrade from mumble <=1.3.x to 1.5.x+[1]. If you accidentally did upgrade, follow these steps to recover:
- When referring to delete, that is dragging app, file or folder icon to trash can or using Command-Delete
- Delete Mumble app by going to your Applications folder[2]
- Reveal hidden directories by going to Finder, open up your Macintosh HD folder. Press Command+Shift+Dot
- Delete mumble database directory:
$HOME/Library/Application Support/Mumble/[3]
- Delete mumble settings file:
$HOME/Library/Preferences/net.sourceforge.mumble.Mumble.plist[3]
- Remove permissions by going to System Preferences > Privacy & Security > Privacy. For BOTH the "Accessibility" AND "Input Monitoring" lists: Remove Mumble from the list using the minus button.
- Install Mumble 1.5.x+ software
- Add permissions for new Mumble by going to System Preferences > Privacy & Security > Privacy. For BOTH the "Accessibility" AND "Input Monitoring" lists: Add Mumble from the list using the plus button, and selecting Mumble from Applications.
FYI Mumble download page warns that upgrading directly to 1.5.x+ will break mumble on your macOS machine.
References
