Teamspeak, vent, skype, or other?
Hello everyone. We are going to be doing a massive multiship fleet engagement sometime in the future and unlike previous times when we have let each ship do it's own thing, this time we want the comms officers to be communicating between ships to keep from having allies run into mines or flying into beam range of a fleet you just launched two nukes at.
Do any of you have any recommendations for software that would be best for this? Keep in mind that for some reason most the ships in the fleet will have Mac hardware so that is a thing.
Do any of you have any recommendations for software that would be best for this? Keep in mind that for some reason most the ships in the fleet will have Mac hardware so that is a thing.
page
1
2 replies
I've used a few different ones--though not with Artemis per-se.
If your Comms stations have dual-screens: one for Artemis, one for the communication app... That might be awesome.
Google Hangout: PRO: allows multiple people to join, cross platform. CON: uses a good bit of CPU power, audio quality is a bit lacking if you're not wearing a headset. Needs Google ID and Internet bandwidth.
Skype: PRO: Audio quality is awesome. If you ensure you ONLY use audio, all traffic in a multi-party call should be peer-to-peer and not require Internet bandwidth. CON: If someone turns on their webcam, the handoff from audio to video can destabilize things a bit.
TeamSpeak: PRO: pretty lightweight when I last used it; LAN hostable. Not sure how Mac joins though.
Now, if you don't mind going the hardware route...
Cell phone: Seriously. Just get a conference call up and running and wear your headset. Done.
DIY Intercom: if you really want to go deep geek, see this:
http://www.epanorama.net/documents/telecom/telephone_intercom.html : scroll down to the "Cheap Intercom" circuit item from ben@staff.prodigy.com. Use wireless phones.
OK, probably too much information. Have fun!
If your Comms stations have dual-screens: one for Artemis, one for the communication app... That might be awesome.
Google Hangout: PRO: allows multiple people to join, cross platform. CON: uses a good bit of CPU power, audio quality is a bit lacking if you're not wearing a headset. Needs Google ID and Internet bandwidth.
Skype: PRO: Audio quality is awesome. If you ensure you ONLY use audio, all traffic in a multi-party call should be peer-to-peer and not require Internet bandwidth. CON: If someone turns on their webcam, the handoff from audio to video can destabilize things a bit.
TeamSpeak: PRO: pretty lightweight when I last used it; LAN hostable. Not sure how Mac joins though.
Now, if you don't mind going the hardware route...
Cell phone: Seriously. Just get a conference call up and running and wear your headset. Done.
DIY Intercom: if you really want to go deep geek, see this:
http://www.epanorama.net/documents/telecom/telephone_intercom.html : scroll down to the "Cheap Intercom" circuit item from ben@staff.prodigy.com. Use wireless phones.
OK, probably too much information. Have fun!
Use VOIP other than Skype. If you have external server access, great! Use vent or ts3. If you need local only, host a ts3 or mumble/murmur server on one machine. It's super easy and lightweight
I run a murmur server on a Raspberry Pi (http://raspberry pi.org) and it works fantastically
I believe mumble is also cross-platform and easy to use on Mac/win/Linux
I run a murmur server on a Raspberry Pi (http://raspberry pi.org) and it works fantastically
I believe mumble is also cross-platform and easy to use on Mac/win/Linux
Hosting a Mumble (Murmur) server @ tsnfenrir.no-ip.org
Having trouble connecting to the TeamSpeak channel: http://tsnfenrir.no-ip.org/ts3
Helm Script for Numerical heading input: https://dl.dropbox.com/u/10193809/ArtemisHelmFSW.zip
Twitter: @lucas99801
Facebook: /lucastarnold
Having trouble connecting to the TeamSpeak channel: http://tsnfenrir.no-ip.org/ts3
Helm Script for Numerical heading input: https://dl.dropbox.com/u/10193809/ArtemisHelmFSW.zip
Twitter: @lucas99801
Facebook: /lucastarnold
Login below to reply:
