AirFader shows error messages and/or no faders
  • "When AirFader starts, I only see white boxes with a red diagonal crisscross"
  • I get error "System.IO.FileNotFoundException..." when starting AirFader
This simply means you need to install Microsoft .NET Framework version 2, 3 or 3.5. (Newer versions of windows do not require this.)

Microsoft .NET Framework 3.5 is available for free here:

Once that's installed, it should resolve this issue.

I keep getting "Connection Bad" or AirFader disconnects completely

When AirFader is connected to a console, it "checks in" frequently with the console to make sure it's still there. If the console doesn't respond for a few seconds, it shows "Connection Bad" to let you know something's not right. If the interference goes away, changes are reconciled and you can keep mixing.

However, if more than 10 seconds go by without a response, the console won't be able to buffer any changes, so AirFader disconnects and shows "Connection Lost."

This is almost certainly caused by an intermittent network connection. If the wireless router and AirFader are relatively close together, the problem is probably active interference and not simply a weak signal.

Things to check for

  • Is anyone using any wireless mics, in-ear monitors, or guitar packs? Those definitely mess with 2.4GHz wireless networks even if they're not in the same frequency band and the network might show a strong signal. Try forcing the router to use Wireless Channel 1, and if that doesn't help, try 11. Most routers are usually set to "Auto" which means they can usually navigate around other networks... but they are not "smart" enough to work around non-network interference from things like microwaves and guitar packs.

    Every time I've had serious trouble with WiFi it's been related to an In-Ear system nearby, and every time I've been able to fix it by simply forcing the WiFi router to use a different channel.

    By the way - many of the new Wireless DMX systems share 2.4GHz space, too. (It really is a busy spectrum.)

  • If AirFader works fine during sound check, but fails during the show, try hiding your SSID on your WiFi router - especially in larger venues. Normally, any mobile device with WiFi enabled will scan for nearby networks and automatically try to connect. Your security settings should deny the connection, but a few hundred smartphones simply asking to connect will slow most consumer routers to a crawl just with background noise. Hiding your SSID will make adding devices slightly more difficult, but will help avoid this problem. A hidden SSID is not a replacement for security, but it prevents automatic connection attempts at least.
  • Run a "ping -t" test during a show and see if you get random packet loss - that would almost certainly confirm RF interference. With a laptop near the router you should have zero lost packets. To do this in Windows:
    1. Go to "Start --> Run" (or click on the Windows Icon and then click in the "Search Programs and Files")

    2. Type in "cmd" and hit Enter. (That's "Charles Michael David")
    3. Type in "ping -t 192.168.x.x" and hit Enter. (Replace 192.168.x.x with the IP address of your console - not your computer.)

    4. You should get a successful response once per second. If you get a few "Request Timed Out" messages, it means there is definitely a network problem.

    5. If you don't get any lost packets, and connection still keeps dropping consistently, please contact support.
  • Install and run inSSIDer (Free from ) to make sure your WiFi network is not competing against nearby WiFi networks on the same channel. It is always a good idea to run this tool in a new location!

  • Finally, if at all possible, consider using the 5 GHz network band (often referred to as "802.11a" or "802.11n" or MIMO). The 5 GHz band has much more room and much less interference, but not all devices support it yet. If you are using an Android device or a laptop that doesn't support 802.11a/b/g/n then you must continue to use the more-common 2.4 GHz frequencies.


AirFader Mobile (android/iPad) won't connect to server

Here is a quick checklist to follow if you are having problems making Mobile and Server talk to each other.

  1. Make sure the Windows computer and your Android device are connected to the same wireless network before starting AirFader.
  2. Start AirFader (in Windows)
  3. Go to Config > Server in AirFader and make sure the server is running.
  4. Note the IP address listed there. (Probably 192.168.x.x)
  5. Open AirFader Mobile on your Android device
  6. Get into Setup
  7. Enter the IP address from the Server's config tab above (Probably 192.168.x.x) This should NOT be the console's IP address.
  8. Make sure the port is right. It should normally be 12301.
  9. Make sure the username/password match what you set up on the server in Config > Users.
  10. Click "Connect" in the Setup screen in AirFader Mobile to force a re-connect.

If that still doesn't work, you may need to turn off the firewall on your computer.


To Disable Windows Firewall

For Windows XP:

  1. Click Start, click Run, type Firewall.cpl, and then click OK.
  2. On the General tab, click Off (not recommended).
  3. Click OK.


For Windows Vista:

  1. Open Windows Firewall by clicking the Start button, clicking Control Panel, clicking Security, and then clicking Windows Firewall.
  2. Click Turn Windows Firewall on or off. If you are prompted for an administrator password or confirmation, type the password or provide confirmation.
  3. Click Off (not recommended), and then click OK.



Login Form

>> David Ceasar says:
Airfader was the most instrumental addition we made to our sound system. We use Airfader as a full campus tool, using it in our Main Worship Center for IEMs as well as in the Youth Building and Recording Control rooms. We successfully use up to 12 de...
Jan 17, 2016
Litchfield Minnesota
Which console(s) do you have?