For those of us with certain kinds of hearing disabilities, adding any
distortion or reduction in volume might make communication impossible.
Our ears add an incredible amount of distortion and noise already. On
top of that you wouldn't believe the lousy quality of hearing aid sound
at 133Db.
There has to be an option in flightgear to allow clear communication,
even at a distance.
That said, I'd never make it in a real cockpit. Current real aircraft
audio is just about impossible to understand.
On Sat, 17 Aug 2013 13:07:25 + TDO Brandano
tdo_brand...@hotmail.com wrote:
I'd leave to the client the task of distorting the received signal
based on the distance and other environmental parameters. The server
should just re-broadcast the clear signal, maybe culling over a
simple range bubble.
From: clem...@hotmail.fr
To: flightgear-devel@lists.sourceforge.net
Date: Sat, 17 Aug 2013 03:02:37 +0200
Subject: Re: [Flightgear-devel] FGCOM
Hi Holger,
I'm glad to know that FGCom integration is surprising you.
It seems you have a pretty well vision of the perfect solution for
radio simulation and I agree with you on this how-it-should-works.
As James said, all of this is mostly based on P2P architecture which
is far to be the easier things to create :)
- Each client need to know the position of others clients
- Each client must send a _clean_ sound signal (no distortion, no
attenuation...)
- Each client need to calculate the distorsion/attenuation of others
clients depending of their distance (I'm callsign01; callsign02 is at
20nm from me = I can hear him loud, callsign03 is at 120nm from me =
I can hear him quiet, callsign04... etc... etc...)
We could also use a centralized architecture with a server which
could works like:
- I know the position and frequency of each clients
- callsign01 is speaking on 122.50MHz
- callsign02 is listening on 122.50MHz, the distance between
callsign01 and callsign02 is 20nm = I send a clean signal from
callsign01 to callsign02
- callsign03 is listening on 122.50MHz, the distance between
callsign01 and callsign03 is 120nm = I send a distorted/attenuated
signal from callsign01 to callsign02
- ...
- ...
I can't imagine the amount of work to create this new system. Also I
have absolutely no idea where we should start if we really want
(need?) this _much_ realistic system. Do you have any hint ?
For sure this level of realism would be a really nice feature. But I
admit I don't know if our users will be _much_more_ happy with this
level of realism and they need/want this level of realism OR are they
already very happy to have a simple way of communication better
than a simple TeamSpeak-like application ? In this case is it
necessary to work during months and months on this project ? Is it
worth ?
Of course if this level of realism I would be happy to use it ! But
I'm not sure to be ready to work on this (big) project for only few
of our pro-realistic users. But if the task is supported by some
people, devs are involved, and my skills are sufficient, yes I would
be part of this effort ;)
Regards,
Clément
--
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
--
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with 2% overhead.
Download for free and get started troubleshooting in minutes.
http://pubads.g.doubleclick.net/gampad/clk?id=48897031iu=/4140/ostg.clktrk
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
