Mumble: Difference between revisions

Line 48:

In the Setting screen Configure>Settings 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.

== Channel Structure for Structured Fleets ==

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. 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. This part of the Mumble setup guide focuses on setting up your key shortcuts for the structured fleet channels.

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''', where the squad members can have their internal chat without bothering the rest of the fleet (or even their SC)

** '''Command Channel''' for FC, WC, SC and scouts to discuss between themselves

** '''Report Channel''', where squad members reports their actions to their SC, e.g. calling points

** '''Order Channel''' for command staff to give orders for persons below them. I.e. FC to talk to whole fleet, WC to their wing, SC to their squad

== Key Bindings for Fleetchannels ==

~~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. This can be invaluable for baitsquads~~ 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. This part of the Mumble setup guide focuses on setting up your key shortcuts for the structured fleet channels~~.

In structured fleets E-UNI is using three different hotkeys, to establish the channels described above and creating an ability to talk "up" and "down" the command structure.

* Keys as called in Mumble:

** Push-to-talk

** Shout to Parent (or whisper if using the older version)

** Shout to Current (or whisper if using the older version)

~~First off, before you set up additional keys to talk up and down in the command structure, there are some things about the Push-to-Talk key you should know. In structured fleets it allows you to:<br>~~

- talk to your squadmates, but not your SC or the rest of the fleet. So this can be used for general chatter between you and your squadmates without disturbing anyone else, but make sure you don't obstruct talk from the commanders!<br>

- talk to all the other commanders but not normal fleetmembers when you are in a command position. This is because all the command subchannels are linked just like the General Chat and PvP waiting room are linked. In this sense, Mumble is set up backwards from Teamspeak as you now need a separate key to talk to the fleet instead of to command.

Line 65:

Line 79:

There you will see this screen (sans the whisper keys, because we are going to set them up for you now!). Press the Add button in the bottom of the screen.

~~===Talk to your SC===~~

After you’ve clicked Add, a new empty key setup appears. For Function, choose Whisper. After you chose Whisper, click on the empty field under Data and click the (…) button. ~~We’ll first set up the key that enables squad members to talk to their squad commander.~~

===Shout to Parent===

After you’ve clicked Add, a new empty key setup appears. For Function, choose Whisper. After you chose Whisper, click on the empty field under Data and click the (…) button.

[[File:Mumble2.png]]

First, click Whisper (or Shout if you’ve got the RC2 version) to Channel at the top. Next, choose Parent and check Whisper to subchannels. What this does is it sends a message to your SC and your squad members, to call out points for example. Be aware that this message is not relayed directly to the rest of the fleet! This means you can chatter with your squad without cluttering up fleet comms, but it also means your information will not be available to the rest of the commanders or the whole fleet directly! Especially SC’s need to be aware of this as they need to relay important information to command.

First, click Whisper (or Shout if you’ve got the RC2 version) to Channel at the top. Next, choose Parent and check Whisper to subchannels.

Click OK and set a key binding by clicking the empty field under Shortcut. Next, add a another key. This key will be for commanders to talk to their subordinates~~. This enables bait squad SC’s to coordinate with their squad without confusing the rest of the fleet and it lets WC’s talk to just their wing members~~.

Click OK and set a key binding by clicking the empty field under Shortcut. Next, add a another key. This key will be for commanders to talk to their subordinates.

===~~Talk~~ to ~~your subordinates~~===

===Shout to Current===

[[File:Mumble1.png]]

Line 81:

Line 96:

Again, set the Function field to Whisper and click the (…) key. Click Whisper to Channel, select Current and check Whisper to subchannels.

===~~Final notes~~===

== 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 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)

* 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)

* Scout:

** Push-to-talk => Command channel

** Whisper/Shout to Parent (No use for a scout)

** Whisper/Shout to Current (No use for a scout)

~~Be aware that giving orders by using this key does~~ not ~~transmit your message to other commanders~~ in ~~the same or higher level~~. ~~So when an~~ SC ~~talks using this key, he needs~~ to ~~communicate his actions separately with the rest of the commanders~~. ~~But, being the good SC he is, he should have been doing that from the start anyway~~. ~~There is one big note that should be~~ made ~~when~~ using ~~this setup, however. Setting up your keys like this makes~~ sure ~~information is only streamed~~ to ~~those that need~~ to ~~know. On the other hand, SC’s are required to be a lot more active in~~ relaying information to ~~the rest of~~ command~~. This information then needs~~ to ~~be relayed by the FC~~ to ~~the rest of the fleet, if he deems it important~~ for ~~the rest of the fleet to know it also.~~

* 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.

@@ Line 48: / Line 48: @@
 In the Setting screen Configure&gt;Settings 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.
+== Channel Structure for Structured Fleets   ==
+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. 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. This part of the Mumble setup guide focuses on setting up your key shortcuts for the structured fleet channels.
+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''', where the squad members can have their internal chat without bothering the rest of the fleet (or even their SC)
+** '''Command Channel''' for FC, WC, SC and scouts to discuss between themselves
+** '''Report Channel''', where squad members reports their actions to their SC, e.g. calling points
+** '''Order Channel''' for command staff to give orders for persons below them. I.e. FC to talk to whole fleet, WC to their wing, SC to their squad
 == Key Bindings for Fleetchannels  ==
-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. This can be invaluable for baitsquads 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. This part of the Mumble setup guide focuses on setting up your key shortcuts for the structured fleet channels.
+In structured fleets E-UNI is using three different hotkeys, to establish the channels described above and creating an ability to talk "up" and "down" the command structure.
+* Keys as called in Mumble:
+** Push-to-talk
+** Shout to Parent (or whisper if using the older version)
+** Shout to Current (or whisper if using the older version)
-First off, before you set up additional keys to talk up and down in the command structure, there are some things about the Push-to-Talk key you should know. In structured fleets it allows you to:<br>
-- talk to your squadmates, but not your SC or the rest of the fleet. So this can be used for general chatter between you and your squadmates without disturbing anyone else, but make sure you don't obstruct talk from the commanders!<br>
-- talk to all the other commanders but not normal fleetmembers when you are in a command position. This is because all the command subchannels are linked just like the General Chat and PvP waiting room are linked. In this sense, Mumble is set up backwards from Teamspeak as you now need a separate key to talk to the fleet instead of to command.
@@ Line 65: / Line 79: @@
 There you will see this screen (sans the whisper keys, because we are going to set them up for you now!). Press the Add button in the bottom of the screen.
-===Talk to your SC===
-After you’ve clicked Add, a new empty key setup appears. For Function, choose Whisper. After you chose Whisper, click on the empty field under Data and click the (…) button. We’ll first set up the key that enables squad members to talk to their squad commander.
+===Shout to Parent===
+After you’ve clicked Add, a new empty key setup appears. For Function, choose Whisper. After you chose Whisper, click on the empty field under Data and click the (…) button.
 [[File:Mumble2.png]]
-First, click Whisper (or Shout if you’ve got the RC2 version) to Channel at the top. Next, choose Parent and check Whisper to subchannels. What this does is it sends a message to your SC and your squad members, to call out points for example. Be aware that this message is not relayed directly to the rest of the fleet! This means you can chatter with your squad without cluttering up fleet comms, but it also means your information will not be available to the rest of the commanders or the whole fleet directly! Especially SC’s need to be aware of this as they need to relay important information to command.
+First, click Whisper (or Shout if you’ve got the RC2 version) to Channel at the top. Next, choose Parent and check Whisper to subchannels.
-Click OK and set a key binding by clicking the empty field under Shortcut. Next, add a another key. This key will be for commanders to talk to their subordinates. This enables bait squad SC’s to coordinate with their squad without confusing the rest of the fleet and it lets WC’s talk to just their wing members.
+Click OK and set a key binding by clicking the empty field under Shortcut. Next, add a another key. This key will be for commanders to talk to their subordinates.
-===Talk to your subordinates===
+===Shout to Current===
 [[File:Mumble1.png]]
@@ Line 81: / Line 96: @@
 Again, set the Function field to Whisper and click the (…) key. Click Whisper to Channel, select Current and check Whisper to subchannels.
-===Final notes===
+== 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 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)
+* 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)
+* Scout:
+** Push-to-talk => Command channel
+** Whisper/Shout to Parent (No use for a scout)
+** Whisper/Shout to Current (No use for a scout)
-Be aware that giving orders by using this key does not transmit your message to other commanders in the same or higher level. So when an SC talks using this key, he needs to communicate his actions separately with the rest of the commanders. But, being the good SC he is, he should have been doing that from the start anyway. There is one big note that should be made when using this setup, however. Setting up your keys like this makes sure information is only streamed to those that need to know. On the other hand, SC’s are required to be a lot more active in relaying information to the rest of command. This information then needs to be relayed by the FC to the rest of the fleet, if he deems it important for the rest of the fleet to know it also.
+* 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.