"I noticed that some of the planned features (e.g. live mode mic,
phone-in shows) depend on having an auxiliary audio input on the Airtime
server. This is problematic in a remote situation without having some
stream from the client, and a remote controlled software mixer on the
server (i.e. enabling manual adjustment to prevent clipping). We don't
want to end up with a design where only half the features work remotely,
because I believe the remote support is Airtime's killer feature.
It might be simpler to say that Airtime itself doesn't have an audio
input, it only accepts streams for rebroadcasting. This would leave
features like live mic input and phone integration to be done in the
third-party desktop client (e.g. IDJC already has these features).
There, the microphone, TBU (analogue phone interface), or Skype client
would be connecting on the same desktop machine, so it would be a lot
simpler, and more robust against network problems.
Later on, we might consider having a software mixer on the Airtime
server, so for example you can do Live Mode in the browser, and mix in a
remote mic input using an N/ACIP stream. It's technically possible;
there is a reference implementation for Windows available under GPL,
based on pjsip:
but maybe this is a little too complicated for the short term.