--- In AirTrafficControl@yahoogroups.com, "juanjo55555"
<walnutdoor@...> wrote:
I believe there are a bunch of parameters that were set up through
the old .NET GUI options and now they are unreachable in the latest
build. Would it be possible to make those "hidden" parameters such as
elevation, etc available to the host as VST parameters for automation
or external control?


I am considering exposing the following as VST parameters:

Global settings:
Set Elevation <feet>
Set Mute All 0 | 1

Per input or output channel:
Set Mute 0 | 1
Set Name <name> (name can be an image file)


> - FR: Attenuation and cutoff for inputs. The attenuation and cutoff
areas on the outputs are two of the things that make this plugin so
flexible... would it be possible to implement them for the inputs as
well? I understand that the interaction between inputs and outputs
would then be a bit more complex, but I think it would be worth the
effort.


Anything is possible I suppose. :)
But consider that the audio "model" would have to change drastically,
and I don't know that it should. Presently the inputs just play their
sound at some level, and the outputs (ears!) adjust how they listen.
The ears adjust by setting how far they can hear, which is already
kind of strange - and VERY useful.

To do as you suggest we'd have to make a rule that sound doesn't
travel more than some distance from its source regardless of how
listening is done. That could be useful, but I think the listening
control is far more important. That's my opinion at this time...

> Oh, and I also have a very minor cosmetic issue to report:
> - BR: Inputs from 29 to 60 appear superimposed
> When you rename the dll so it has more than 28 inputs, all the
inputs from the 29 onwards appear superimposed... so if you want to
click and drag, say, input 42 you have to get inputs 29 through 41 out
of the way first. Perhaps a 2 or 3 column arrangement of the inputs by
default would solve this.

I'll be looking at this.